PROJECT INFO, PRESENTATION INFO, AND IMPACT ANALYSIS
November 13, 2012
Tuesday, November 13, 12
PROJECT INFO, PRESENTATION INFO, AND IMPACT ANALYSIS November 13, - - PowerPoint PPT Presentation
PROJECT INFO, PRESENTATION INFO, AND IMPACT ANALYSIS November 13, 2012 Tuesday, November 13, 12 PAPER AND PRESENTATIONS After class, sign up for a presentation date Presentations: 4 classes, 18 people = 15 minutes per presentation (4 or
November 13, 2012
Tuesday, November 13, 12
After class, sign up for a presentation date Presentations: 4 classes, 18 people = 15 minutes per presentation (4 or 5/day) Your presentation should be 11 minutes long 4-5 minutes for questions/switchover You will receive warnings at 2 minutes, 1 minute, and 30 seconds remaining Please send me all slides at least 5 hours before your presentation!
Tuesday, November 13, 12
Before starting, think about main points - will not have time to go over everything!!!! Oral Communication is different from written communication K.I.S.S. (Keep it simple, stupid.) Focus on getting one to two key points across Think about your audience Some are experts in sub-area, some are experts in general area, and others know Should be accessible to all on some level Think about your goals Leave your audience with clear picture of the gist of your contribution Make them want to read your work
Tuesday, November 13, 12
Based on Dave Patterson’s Ten Commandments (Powerpoint by Rolf Riedi)
How to give a Bad Talk (by David Patterson) http://pages.cs.wisc.edu/~markhill/conference-talk.html#badtalk
Tuesday, November 13, 12
Transparencies and hard-discs are expensive. If you can save five slides in each talks per year, you save 7.00/year in transparencies! This is equivalent to 350 kB precious memory!
Do you want to continue the stereotype that engineers can't write? Always use complete sentences, never just key words. If possible, use whole paragraphs and read every word.
You need the suspense! Overlays are too flashy.
Be humble -- use a small font. Important people sit in front. Who cares about the riff-raff?
Flagrant use of color indicates uncareful research. It's also unfair to emphasize some words over others.
Confucius says ``A picture = 10K words,'' but Dijkstra says ``Pictures are for weak minds.'' Who are you going to believe? Wisdom from the ages or the person who first counted goto's?
You should avert eyes to show respect. Blocking screen can also add mystery.
You prepared the slides; people came for your whole talk; so just talk faster. Skip your summary and conclusions if necessary.
Tuesday, November 13, 12
Tuesday, November 13, 12
W h
a r e s w h a t 3 p e
l e t h i n k ?
Tuesday, November 13, 12
Who cares what 30 people think?
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
Tuesday, November 13, 12
– It could take several hours out of your two years of research. – How can you appear spontaneous if you practice?
and make sure your talk is longer than the time you have to present it.
the other nine,
Tuesday, November 13, 12
For a 11 minute talk, ~7 slides Suggested outline (proposal) 1) Title slide 2-3) Intro and motivation/background 4-5) Implementation 6) Evaluation idea 7) Discussion and conclusion
Tuesday, November 13, 12
For a 11 minute talk, ~7 slides Suggested outline (proposal-ish) 1) Title slide 2-3) Intro and motivation 4-5) Other techniques 6) Discussion of your idea 7) Conclusion
Tuesday, November 13, 12
For a 11 minute talk, ~7 slides Suggested outline (lit review) 1) Title slide 2-3) Intro and motivation 4-5) Techniques you examined (pick the big ones) 6) What you’ve learned 7) Conclusion
Tuesday, November 13, 12
System: Existing music lending library Goal of this release: Add automated way to borrow music Materials: 2 collections in zip format Interviews (written, audio) Pictures Data ALL information in your SRS should link back to the elicited data Write an SRS using IEEE Std 830-1998 format
Tuesday, November 13, 12
Week 1: Begin looking over and sorting through the materials. Week 2: Fill out the requirements specification document following the template Week 3: Put requirements into the Requirements Management System. More info to come about the Management System Friday, November 30th: Submission of SRS documents Thursday, December 6th: Submission of group evaluations of SRS projects
Tuesday, November 13, 12
Provides accurate understanding of the change Helps team make good business decisions Examines the proposed change: What will be created? What will be modified? What will be discarded? What effort’s associated with each?
Tuesday, November 13, 12
Understand possible implications of making the change Identify all files, models, and documents to be changed Identify tasks to implement change Estimate effort needed to complete tasks
Tuesday, November 13, 12
Do any existing requirements in the baseline conflict with the proposed change? Do any other pending requirements changes conflict with the proposed change? What are the business or technical consequences of not making the change? What are possible adverse side effects or other risks of making the proposed change? Will the proposed change adversely affect performance requirements or other quality attributes? Is the proposed change feasible within known technical constraints and currents staff skills?
Tuesday, November 13, 12
Will the proposed change place unacceptable demands on any computer resources required for the development, test, or operating environments? Must any tools be acquired to implement and test the change? How will the proposed change affect the sequence, dependencies, effort, or duration of any tasks currently in the project plan? Will prototyping or other user input be required to verify the proposed change? How much effort that has already been invested in the project will be lost if this change is accepted? Will the proposed change cause an increase in product unit cost, such as by increasing third-party product licensing fees? Will the change affect any marketing, manufacturing, training, or customer support plans?
Tuesday, November 13, 12
Identify any user interface changes, additions, or deletions required. Identify any changes, additions, or deletions required in reports, databases, or files. Identify the design components that must be created, modified, or deleted. Identify the source code files that must be created, modified, or deleted. Identify any changes required in build files or procedures. Identify existing unit, integration, system, and acceptance test cases to be modified or deleted. Estimate new unit, integration, system, and acceptance test cases now required. Identify any help screens, training materials, or other user documentation that must be created or modified. Identify applications, libraries, or hardware components affected by the change. Identify any third-party software that must be purchased or licensed. Identify any impact the change will have on the project's software project management plan, quality assurance plan, configuration management plan, or other plans.
Tuesday, November 13, 12
Work through checklist of questions Work through checklist for potential impact (Use traceability information) Estimate labor hours needed to update, create, modify, and develop each component Total effort estimates Identify sequence tasks must occur in (parallelize with existing?) Is change along the critical program path? Estimate impact on schedule and cost Evaluate change’s priority Report analysis results to CCB
Tuesday, November 13, 12
* Modify template for your project’s needs
Tuesday, November 13, 12
Improving the requirements process Fundamentals of software process improvement Process improvement cycle
Tuesday, November 13, 12