You are asked by your company's management to help plan a possible large software project. You may pick one of the following to estimate: a weather satellite (it's hurricane season) You may email me with another possible dependable system of interest for me to approval if you have something more interesting to you. After you pick a topic or I approved you topic, estimate or as I learned at NASA: take a WAG (wild-ass-guess). But understand a WAG needs some basis to convince and green light the project. Your guess most likely will be off but the estimate is in the "ballpark". You will learn more about the topic as the project proceeds but note your understanding of the topic as assumptions. You may want to do some research about the topic as background.

Try to break out the software part of the project. Assume all the hardware you need is available and working. The software remains to be written. Attempt to sub-divide the software into components. Pick one of these components to estimate and assume that the other software components are already written and working. You will estimate the work for requirement analysis, design, coding, testing, and deploying your component.

Deliverables:

(1) A table with tasks, durations, and dependencies as shown in Figure 23-5: Tasks, duration, and dependencies. Since we are most likely new to our chosen topic, we must make a well-educated guess at what the tasks are, how long each will take, and how many people we will need to complete the system. Use the waterfall methodology.

(2) A graphic table with tasks as shown in Figure 23-6. The full system duration will be based on your assumptions from (1) above and task dependencies. You may use the technique from the video if you want.

(3) A best guess at the number of lines of source code (SLOC) that will be needed for the dependable software sub-system component. Section 23.5 (Estimation Tech.) from the text may be used as a source. Include all your assumptions that make up your estimate. You may use this SLOC for item (1) above.

Figure 23.5 Tasks, durations, and Fiqure 23.6