Inception

							                    Inception is not the
                   requirements phase
                      Larman chapter 4




Larman chapter 4                           1
                             Unified process
                                                             transi
             Sample      incep-
                                elaboration   construction      -
          UP Disciplines tion
                                                              tion
                                                                      The relativ e ef f ort in
                Business                                              disciplines shif ts
                Modeling                                              across the phases.

             Requirements                                             This example is
                                                                      suggestiv e, not literal.
                   Design

            Implementation
                             ...
                       ...



                   Inception

Larman chapter 4                                                                                  2
                   Inception - goals
• What is the vision and business case for the
  project?
• Is it 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
Larman chapter 4                                 3
                   Inception - artifacts
• 1. version of artifacts – often incomplete
• Vision and business case
     – What are the benefits of the system for the company
     – Describes high-level goals
• Use case model
     – Identifies most of the functional requirements
     – Describes app. 10% of the functional requirements
       (high risk) in detail
• Glossary
     – Key domain terminology

Larman chapter 4                                             4
 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 define 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

Larman chapter 4                                    5