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

q
                                               u
                                                i

                                           R
                                             e
                                                     e
                                                      n
                                                       t
                                                 r
                                                  e
                                                   m
                                &

                                  S
                             r
                              e

                                       e
                                        m
                                          s
                                    y
                                     s
                                      t
                                                        s
                                                                         n

                                                                           P
                                                                      :

                                                                        I
                                                                               t
                                                                                i
                                                                                 c
                                                                            r
                                                                             a
                                                                              c
                                                             g
                                                              i
                                                               n

                                                          E
                                                           n
                                                                   i
                                                                    n
                                                                     g
                                                                e
                                                                 e
                                                                  r
                            a
                       o
                         f
                      S
                320    S o f t w a r e   &   S y s t e m s   R e q u i r e m e n t s   E n g i n e e r i n g :   I n   P r a c t i c e e
                320
                          t
                           w
                      traceability                  use case points, 85
                        based on roles/organization,   use case realizations, 115, 116
                           200, 201                 use case scenarios, 105, 107,
                        described, 13, 14             130–132, 145
                        engineering project traceability   use case tracing, 115, 116
                           model, 202–204           use cases, 59–62
                        factors, 152                  abstract, 101, 103, 107–108,
                        goal-based, 202                  223–227
                        incomplete, 204               components of, 59
                        requirements, 13, 200–204     concrete, 94, 102–110, 224–226
                        requirements management,      conflicting requirements, 243
                           200–204                    decomposition, 92
                        requirements specifications, 14  defining, 102–105
                      traces categories, 202          extending, 59, 92, 107–108
                      tracing relationships, 115–116  including other use cases,
                      tracing to requirements, 229       107–108
                      training, 4, 6, 42, 217         out-of-scope, 100
                      transparency, 250               vs. packages, 101
                      treatment, 284                  relationships, 108
                      tree structure, 215             terminal, 90–91
                                                      for testing, 223–227
                           U                        use-case context diagram, 141
                      UI (user interface)           user interface (UI)
                        interactions, 246             interactions, 246
                      “umbrella” requirements, 14   user manuals, 222
                      UML (Unified Modeling         user-driven interactions, 244
                        Language), 4, 75, 99–113
                      UML 2.0 Testing Profile, 223       V
                      UML diagrams, 223, 226–227    “V” model, 202–204, 220, 221
                      UML models, 75, 226–227       validation, 220
                      understandability, 136        validation activities, 220
                      Unified Modeling Language.    validity, 9, 10, 14
                        See UML                     value-added resellers
                      Unified Requirements Modeling   (VARs), 157
                        Language (URML), 86, 88     variables, independent, 155
                      URML (Unified Requirements    VARs (value-added
                        Modeling Language), 86, 88    resellers), 157
                      usage models, 222             verifiability, 11, 14
                      use case analysis, 59–62      verifiable requirements, 11
                      use case diagrams, 102–104, 107,   verification, 220
                        141, 223–224                version control, 195–198, 208,
                      use case modeling, 85           210–211
                      use case models, 80, 81, 92–94  video communications, 269
   353   354   355   356   357   358   359