Page 61 - Software and Systems Requirements Engineering in Practice
P. 61

p
                        a
                       h
                             r
                           e
                          t
                                               s
                                                    g
                                                     i
                                                     n

                                                 E
                                                  n
                                              t
                                         e
                                        r
                                        i
                                             n
                                            e
                                          m
                                      u
                               :
                              2

                                     q
                                    e
                                   R

                                                                       M
                                                                        o
                                                                     t
                                                                  f
                                                                   a
                                                                    c
                                                                             n
                                                                              g
                      C C h a p t e r   2 :      R e q u i r e m e n t s   E n g i n e e r i n g   A r t i f a c t   M o d e l i n g      33 33
                                                                             i
                                                                         d
                                                                           e
                                                                            l
                                                           n
                                                            g

                                                          i
                                                       e
                                                        e
                                                         r
                                                              A
                                                                 i
                                                                t
                                                               r
                      or  set  of  quality  indicators  (see  Figure  2.11)  that  can  be  used  to
                      determine:
                          •  What is the quality of the artifact? Does it need rework?
                          •  Has  the  artifact  been  completed?  What  are  the  criteria  for
                             completion?
                          •  What  is  the  status  of  the  artifact;  e.g.,  suggested,  draft,
                             completed, sunset?
                       Business and Customer Requirements            Mandatory
                       Responsible: Prod M         Contributing: RE, SA
                       Description: The Business Objectives and Customer Requirements identify the
                       primary benefits that the new system will provide to the customer and to the
                       organization that is developing the system.
                       Business Objectives                           Mandatory
                       Summarize the important business benefits the system will provide, preferably
                       in a way that is quantitative and measurable. The background and business
                       opportunities of the future system are described. This includes a description
                       of business problems that are being solved, and a comparative evaluation of
                       existing systems and potential solutions. The rationale for the system
                       development is described, and how the system aligns with market trends or
                       corporate strategic decisions is defined.
                       Customer Requirements                         Mandatory
                       Summarize the needs of typical customers or users. Customer needs are
                       defined at a high level for any known critical conditions, interface, or quality
                       requirements. They provide examples of how the customer will use the system
                       and identify the components (hardware and software) of the environment in
                       which the system will operate. Explicitly define the value the customer/user
                       will receive from the future system and how it will lead to improved customer
                       satisfaction.
                       Purpose: Business and customer requirements serve as entry points to
                       context analysis and the specification of the required features and
                       characteristics of the System Vision and the definition of the general
                       Conditions & Scope of the development.
                       By identifying the business objectives, the situation, and the critical conditions,
                       collect business risks associated with the developing (or not developing) this
                       system systematically as input to risk and cost/benefit analysis (ROI & Risk).
                       References: [Wie 1999] gives an overview of business requirements and provides
                       a list of possible customer values.
                      FIGURE 2.13  Filled-in artifact template for business requirements
   56   57   58   59   60   61   62   63   64   65   66