Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
6 Cards in this Set
- Front
- Back
|
traceability
|
the clarity of linkage between artifacts. It provides assurance that the software created matches what the stakeholders wanted. It is helped by use cases.
|
|
|
4 aspects of traceability
|
analysis model
design testing user interface |
|
|
Analysis Model Traceability
|
Each step in a Use Case translates into an operation passed between the actor and the system and ultimately a set of messages passed between software objects on a UML sequence diagram. The Use Case is also the source for the candidate classes (nouns and noun phrases) which will be documented in a UML class diagram; contain ONLY entity classes.
|
|
|
Design Model Traceability
|
Similar to Analysis Model, but add, in addition to the entity classes in analysis models, both boundary and control classes. Boundary classes come from the UI design; control classes are created for each use case and are used to manage the other objects that are part of transactions by passing them data and/or instructions
|
|
|
Test Model Traceability
|
Clearest traceability link; Use Cases are Test Cases – just moved to the start of the development lifecycle and called functional requirements. Test plans are typically organized by use case and they focus on each use case path
|
|
|
User Interface (UI) Model Traceability
|
UI come from the software requirement, including the Use Cases. Use Cases are the stories the user interface must illustrate as storyboards
|
