1. Homework #1a Lifecycle Paper For each stage of the life cycle provide a list of items you think should be there. There should be at a minimum of five items for each stage (10 would be better). –Concept - often missed –Requirements - almost never done well –Define exit criteria - almost never done –Design/prototype- often missed –Official design - often rushed –Implementation- almost never planed correctly –Test - first to go to meet schedule –Maintenance - 80%+ the life of the software

2. Concept – how do we sell this project mission statement functional spec stakeholders project milestone definitions marketing research target env user survey competitive analysis use-cases user-scanerios file any patents

3. Requirements detailed user-scenarios, use-cases mock-ups p/w, s/w, h/w requirements financial requirements initial project plan what do people need to know –know –training –background what data exists and where (think SOR) who do you need to integrate with what enterprise integration system (EIS) mechanism how are we going to test this how do we know when we are successful

4. Define Exit Criteria exit criteria for each phase define testing strategies to validate (nothing should be subjective) define basic use guide lines cost/benefit analysis benchmark test and numbers for things like –performance –functionality –resource usage –specs –… identify key areas to prototype

5. Design/Prototype – think patent High-level design of the system Detailed design of the sub-system functional specs are pushed to the next level UI guide are formalized dev guides are formalized modules, topology integration plan prototype code design/prototype reviews high-level project plan risk vs gain evaluation identify fish or cut-bait decision points

6. Official Design Designed Reviewed and signed off by: –overall system design –adjacency sub-systems –stakeholders –architects –finance Everything else but formalized in the previous phase Initial announcement plans Detailed project plan risk vs gain evaluation identify fish or cut-bait decision points

7. Implementation final design review and understandings code reviews unit test plan and test reviews detailed project plan continuously reviewed and updated code test debug risk vs gain evaluation identify fish or cut-bait decision points

8. Test Integration test plan and scripts QA test plan and scripts Automation use-case testing user-scenarios tests perf/scale/resource testing acceptance testing identify fish or cut-bait decision points

9. Maintenance maintenance schedule – five 9s risk vs gain evaluation identify fish or cut-bait decision points “as is” documents updated –user manual –user guides –dev guides –design documents All the above but at a smaller scale

10. Homework #1b Provide the pseudo code for computing the following method –public long factorial(long x) Then provide the set of tests you will need to write to validate that factorial is producing the correct value.