Page 264 - Software and Systems Requirements Engineering in Practice

$

S
R
E
V
I
T
R
I
U
E
N
E
M
N
S
E
4
T
G
N
I
ç
Y
3
ç
S
M
E
T
P
T
E
ç ç # # H A P T E R ç ç ç 2 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 ç ç
H
A

E
Q
R
ç

1, Ên°{Ê `ˆÌˆ˜}Ê«Àœ«iÀ̈iÃʜvÊ>ÊÃiiVÌi`Ê>V̈ۈÌÞ
!CTIVITIES CAN ALSO REFERENCE OTHER USE CASES WHICH CAN BE USED TO
BREAK UP LARGER DIAGRAMS OR TO ACHIEVE REUSE OF MODELING ACTIVITIES
5SING USE CASE MODELS FOR MODEL BASED TESTING MEANS THAT WE ARE
INTERPRETING THE USE CASE MODELS FOR THE PURPOSE OF TEST GENERATION
4HIS MEANS THAT ERRORS IN THE MODEL CAN PREVENT THE ABILITY TO GENERATE
TESTS 4HUS BEFORE TEST GENERATION WE CHECK THE MODEL FOR ERRORS THAT
WOULD PREVENT THE GENERATION OF A CORRECT TEST 7E CHECK FOR ERRORS
SUCH AS USE CASES WITHOUT ACTIVITY DIAGRAMS ACTIVITIES WITHOUT
TRANSITIONS ILLEGAL CONSTRAINTS ILLEGAL CONSTRUCTS IN NOTE DECLARATIONS
AND MISSING START STOP STATES

õ 4ESTINGõ0ERFORMANCEõANDõ3CALABILITYõ2EQUIREMENTS
7E DESCRIBE HERE AN APPROACH TO EFFICIENTLY BUILD OPTIMIZED SIMULATION
MODELS USING 5-, DIAGRAMS ;!VRITZER ET AL = THAT CAN BE USED TO
ASSIST WITH TESTING PERFORMANCE AND SCALABILITY REQUIREMENTS 7E
ANNOTATE THE DEPLOYMENT DIAGRAM MODELS AND SEQUENCE DIAGRAM
MODELS WITH ARRIVAL RATES AND DEPARTURE RATES AND AUTOMATICALLY
GENERATE PERFORMANCE MODELING SCENARIOS FROM THESE DIAGRAMS 4HE
5-, MODELS ARE USED TO SPECIFY THE MESSAGE FLOW AMONG OBJECTS AS
WELL AS THE ARRIVAL AND DEPARTURE RATES )N ADDITION WE USE A LIBRARY