Page 261 - Software and Systems Requirements Engineering in Practice
P. 261
ç ç 3 O F T W A R E ç ç 3 Y S T E M S ç 2 E Q U I R E M E N T S ç % N G I N E E R I N G ç ) N ç 0 R A C T I C E
USE CASES AND CONCRETE USE CASES ARE THE BASIS FOR TEST
GENERATION
0ACKAGE DIAGRAMS ARE APPLIED TO PROVIDE A HIERARCHY TO
DIVIDE A LARGE MODEL FOR EASIER NAVIGATION AND THEY ALSO CAN
BE USED TO SPLIT A LARGE MODEL INTO MULTIPLE FILES TO SUPPORT
MULTIPLE USERS
!CTIVITY DIAGRAMS ARE USED TO SHOW DETAILS OF EACH USE CASE IN
RELATION TO STEPS ON USING THE SYSTEM !CTIVITIES ARE USED NOT
ONLY TO SHOW TEST STEPS BUT ALSO TO SHOW EXPECTED RESULTS OR
VALIDATION STEPS 3WIM LANES ARE USED TO DISTINGUISH BETWEEN
TEST STEPS AND VALIDATION STEPS !CTIVITIES CAN BE ANNOTATED
WITH PROPERTIES TO PROVIDE INFORMATION TO BE USED IN TEST
GENERATION
#LASS DIAGRAMS ARE USED TO DEFINE EQUIVALENCE CLASSES TO
REPRESENT DATA VARIATIONS USED IN TESTING 6ARIABLES ARE DESCRIBED
AS NOTES WITHIN AN ACTIVITY DIAGRAM TO REFERENCE AN EQUIVALENCE
CLASS OF DATA VARIATIONS DEFINED IN A CLASS DIAGRAM
)N THIS APPROACH THE USE CASE MODEL REFERS TO A MODEL THAT
DESCRIBES THE USE CASES FROM A TESTER S POINT OF VIEW %ACH USE CASE
DESCRIBES HOW TO TEST THE VARIOUS SCENARIOS 4HIS IS DIFFERENT FROM THE
USE CASES THAT DESCRIBE THE IMPLEMENTATION OF THE SYSTEM 4HE TESTER S
USE CASES DO NOT DESCRIBE HOW TO IMPLEMENT EACH USE CASE BUT
DESCRIBE HOW TO TEST EACH USE CASE BY DESCRIBING THE INPUTS AND
EXPECTED RESULTS
4EST CASES CAN BE AUTOMATICALLY GENERATED WITH TOOL SUPPORT
USING THIS -"4 APPROACH %ACH TEST IS REPRESENTED BY A SERIES OF TEST
STEPS %ACH TEST STEP IS REPRESENTED BY AN ACTIVITY $ECISION POINTS IN
THE ACTIVITY DIAGRAM REPRESENT ALTERNATIVE USAGE SCENARIOS 'UARD
CONDITIONS ON TRANSITIONS PROVIDE A WAY TO RESTRICT INFEASIBLE TEST
SCENARIOS &IGURES AND SHOW EXAMPLES OF USE CASE AND
ACTIVITY DIAGRAMS THAT CAN BE USED TO SUPPORT MODEL BASED TESTING
$" $ #"
!" !" $ "
$"
# "% " ! $"
$"
$"
$" ! !" %
$" $" # !"
#
" "
1, Ên°£Ê 1ÃiÊV>ÃiÊ`>}À>