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

2

                                                                              G
                                     ç
                                                I
                                                R
                                                 E
                                            E
                                             Q
                                              U
                                                                             N
                                                                        4
                                                                         E
                                 P
                                A
                               H
                              #
                                                                          S
                                                                            T
                                                                             I
                                  T
                                   E
                                    R
                                                                  Y
                                                                   S
                                                                 3
                                                               N
                                                                ç
                                                                        ç
        ç ç                   # H A P T E R ç     ç ç  2 E Q U I R E M E N T S   $ R I V E N ç 3 Y S T E M ç 4E S T I N G ç ç
                                                                      M
                                                                    T
                                                                     E
                                                             E
                                                      T
                                                       S
                                                     N
                                                  M
                                                    E
                                                           R
                                                            I
                                                            V

                                                         $
                         4HE TEST DERIVATION APPROACHES APPLIED ON THE DIFFERENT MODEL
                      TYPES  ARE  SOMETIMES  CLASSIFIED  INTO  SPECIFICATION BASED  TESTING   OR
                      BLACK BOX  TESTING   IF  THEY  ARE  BASED  ON  REQUIREMENTS  MODELS   AND
                      PROGRAM BASED TESTING  OR WHITE BOX TESTING  IF SOURCE CODE IS USED
                      AS THE UNDERLYING MODEL
                         )N RECENT YEARS  -"4 GAINED IMPORTANCE IN CONNECTION WITH THE
                      MODEL DRIVEN ARCHITECTURE  -$!  INITIATIVE OF THE /BJECT -ANAGEMENT
                      'ROUP  /-'  AND CONCEPTS OF TEST DRIVEN DEVELOPMENT FOR SOFTWARE
                      PRODUCTS  /THER ADVANCES IN SOFTWARE AND SYSTEMS ENGINEERING  LIKE
                      THE  USE  OF  EXECUTABLE  SPECIFICATION  LANGUAGES   THE  PATTERN BASED
                      DETECTION OF FAULTS IN SOURCE CODE  OR THE INFERENCE OF PROGRAM BEHAVIOR
                      FROM  RUNTIME  OBSERVATIONS   CONTRIBUTE  TO  A  RENAISSANCE  OF  -"4
                      APPROACHES  ALTHOUGH THE ROOTS OF -"4 GO BACK TO THE EARLY BEGINNINGS
                      OF COMPUTER SCIENCE ;-OORE     =
                         4O  APPLY  -"4  SUCCESSFULLY  IN  TODAY S  INDUSTRIAL  SOFTWARE
                      DEVELOPMENT PROJECTS  IT IS IMPORTANT TO AUTOMATE THE EXECUTION OF THE
                      TESTS  THAT  ARE  GENERATED   4ODAY   A  WIDE  RANGE  OF  TEST  AUTOMATION
                      SOLUTIONS OF VARYING ABSTRACTION LEVELS EXIST  DEPENDING ON THE ACTUAL
                      APPLICATION DOMAIN AND PROJECT HISTORY
                         &ROM  THE  PERSPECTIVE  OF  THEIR  CURRENT  PRACTICAL  USAGE   -"4
                      APPROACHES BASED ON REQUIREMENTS MODELS AND APPROPRIATE COVERAGE
                      CRITERIA ARE DOMINANT  4HEY CAN BE EASILY IMPLEMENTED USING GRAPHICAL
                      SPECIFICATION  TECHNIQUES  LIKE  5-,  ;'ROSS      =   ;(ARTMANN  ET  AL
                          =   ;5TTING  ET  AL       =  AND  THE  5-,       4ESTING  0ROFILE
                      ;3CHIEFERDECKER  ET  AL       =   )N  PARTICULAR   THESE  APPROACHES  BENEFIT
                      FROM METHODOLOGIES FOR TEST DRIVEN DEVELOPMENT THAT ARE CURRENTLY IN
                      VOGUE  4HEY ALSO CIRCUMVENT THE TEST ADEQUACY PROBLEM ASSOCIATED
                      WITH THE TESTS DERIVED FROM DESIGN MODELS THAT OCCURS IF PRODUCTION
                      CODE FROM THE SAME MODEL IS AUTOMATICALLY GENERATED
                         7E HAVE DISCUSSED HOW 5-, DIAGRAMS CAN BE USED FOR DESCRIBING
                      REQUIREMENTS MODELS IN #HAPTERS   AND    &OR MODEL BASED TESTING
                      TEST ENGINEERS MAY UTILIZE THE FOLLOWING DIAGRAMS  USE CASE DIAGRAMS
                      PACKAGE  DIAGRAMS   ACTIVITY  DIAGRAMS   SEQUENCE  DIAGRAMS   STATE
                      MACHINE DIAGRAMS  AND CLASS DIAGRAMS  )N OUR EXPERIENCE  USE CASE
                      MODELS AND ACTIVITY DIAGRAMS ARE PARTICULARLY EFFECTIVE BECAUSE THEY
                      BRIDGE REQUIREMENTS TO SYSTEM TESTS  AND THEY CAN BE CREATED EARLY IN
                      THE DEVELOPMENT LIFE CYCLE  4HE USE CASE MODELS CAN BE CREATED BASED
                      UPON THE SYSTEM REQUIREMENTS AND ALSO FROM THE USE CASE DESCRIPTIONS
                      THAT ARE CREATED AS PART OF THE SYSTEM REQUIREMENTS
                         4HE USE CASES FOR TESTING CAN BE DEVELOPED EARLY IN THE PROJECT
                      LIFE CYCLE AS SOON AS REQUIREMENTS ARE AVAILABLE  )N THE EARLY PHASES
                      OF THE PROJECT  THESE USE CASES ARE SOMEWHAT ABSTRACT  )N LATER PHASES
                      THE  USE  CASES  ARE  POPULATED  WITH  ENOUGH  INFORMATION  TO  CREATE
                      EXECUTABLE  SYSTEM  TESTS   !N  APPROACH  TO  USE  MODELS  FOR  TEST
                      GENERATION IS DESCRIBED AS FOLLOWS
                               5SE CASE DIAGRAMS ARE USED TO IDENTIFY THE USAGE SCENARIOS OF
                             THE SYSTEM  !BSTRACT USE CASES REPRESENT RELATED COLLECTIONS OF
   255   256   257   258   259   260   261   262   263   264   265