Software Lifecycle detailed...

• Feasibility Study: Goals, documentation, focus, key participants produce req. doc
• Functional Spec: - define terminology, requirements, volume & scale, what is needed and how it will work, conversion plan to new software, users help write specs (not review)
• Detailed Design: - Define standards & conventions, identify development tools, define application architecture
• Programming: - creating bugs
• Unit Testing: - You Nit!, insure consistency to spec, insure program produces correct results, test plan, use drivers & stubs!
• System Testing: - System meets functional spec., modules worktogether, identify programming and integration problems, insure system meets performance requirements. Check system with consistent and inconsistent input (users are not always consistent in their typing, on average 50% of code should be consistency checking).
• Parallel testing: - Does system produce correct business results? Does system meet user requirements, compare old and new methods of doing business.
• Training:- get users familiar with system, get operations familiar, allow time for developers to learn the new area where code will be used. Users should develop the training manual! Users should write the users manual.
• Documentation: - Comprehensive, consistent with system, completed before system and parallel testing. Program documentation should be in code andextracted using utilities (like PDF).
• Conversion: - Provide real data to new system. Enable users to do testing (system & parallel). catch problems before life operations. This is a large part ofthe software Lifecycle, should be 10% ofprogramming effort. Allow plenty of time for users to test it.
• Pilot: - Phase the new system in a controlled way. Catch problems on a small scale while things can still be changed.
• GO live: - the primary goal
• Maintenance/Enhancements: - getting the chance to do things the way it should have been down the first time
  

Support Required:

• Project Mgmt: - provides direction, defines responsibilities, monitors progress,institutes change
• Progress Report: - Daily where we are, what we did to get there, what Tasks want to be, what needs to be done to get there. (spend no more than 1hr/wk. on this)
• Review & Audit: we are; problems & opportunities; communicate and resolve issues; identify, evaluate, and reduce risks.