1. Larman chapter 41 Inception Larman chapter 4 and 7

2. Larman chapter 42 Inception is not the requirements phase

3. Larman chapter 43 Unified process Inception

4. Larman chapter 44 Inception - goals What is the vision and business case for the project? Feasible? Rough unreliable range of cost Buy and/or build? Should we proceed or stop? duration : –1 to 2 weeks –Write 1. version of relevant artifacts

5. Larman chapter 45 Inception - artifacts 1. version of artifacts – often incomplete Vision and business case (Larman page 109 and note Software Design page 89) –What are the benefits of the system for the company –Describes high-level goals Use case model (Larman page 66 – 72) –Identifies most of the functional requirements –Describes app. 10% of the functional requirements (high risk) in detail Glossary (Larman page 115) –Key domain terminology

6. Larman chapter 46 Inception - artifacts Domain rules (Larman page 117) Supplementary specification (Larman page 107)

7. Larman chapter 47 Inception - process Start with your Business Model (Analyze and describe- SWOT, Porters five, Etc…) Write a brief draft of the Vision Identify user goals and supporting use cases by name Write some use cases in detail, start with the Supplementary Specification Refine the Vision, summarizing information from these

8. Larman chapter 48 You misunderstood inception if: inception is more than a few weeks long You attempt to define all requirements Estimates and plans are expected to be reliable You try to defines the architecture There is no business case or vision artifact Names of most of the use cases and actors were not identified All the use cases are written in detail No use cases are written in detail