1. Designing Applications

2. What is “Designing”? • Thinking, Planning, Scheming, Engineering, Deciding, Documenting, Trying Out, … • Good designers prevent retro-designing by using systems thinking • Changes are 50-200 times more expensive than when in the original phase

3. The Phases of App Dev • Analysis Phase (includes documentation) • Design (includes documentation) • Coding Phase • Testing • Documentation • Acceptance • Review * All phases may be repeated (iteration)

4. Analysis Phase Documentsand sign off to continue • Preliminary analysis Approval for next stage of analysis • Needs Analysis Approval for next stage of analysis • Requirements Analysis Approval for next stage of analysis

5. Preliminary Analysis • A high-level statement (often an oral statement) must address the following business issues • What need will the App serve? • What are the constraints (organization, business, technical)? • How is the work currently done? • What alternatives are available? • What is the optimal schedule? • Business case: • Competitive analysis • Market analysis • Revenue projections

6. Needs Analysis Statement • Based on Preliminary Analysis • Makes the business case for the App • Focus on what needs will be met • Avoids stating how needs will be met • Business case must be documented

7. Requirements Statement • Technical Design • Features and Benefits • Application Description • Component Descriptions • Quality Assurance Plans (see Requirements Guidelines)

8. Coding Phase • Write the App based on analysis and design. • Break down work into stages by components. • Pert component schedules. • Include within each component stage… • Testing • Documentation • Acceptance

9. Review • Post mortem • Include all groups in the organization • Look for ways to improve… • Reduce friction • Lower costs • Improve communications