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;
10 Cards in this Set
- Front
- Back
- 3rd side (hint)
|
Purpose |
To ensure that the reqs collectively support one another to fully achive the objectives |
Reqs architecture is the structure of all of the reqs of a change |
|
|
Description |
BA use a reqs architecture to: - Understand which models are appropriate for the domain, solution scope and audience - organize reqs into structure relevant to defferent stakeholder - illustrate how reqs and model interact with and relate to each other, and show how the parts fit together into s meaningful whole - ensure the reqs work together to achieve the overall objectives - make trade off decisions about reqs while considering the overall objectives |
|
|
|
Input |
- information management approach - reqs (any state) - solution scope |
|
|
|
Output |
Requirements architecture |
The reqs and inter relationships among them, as well as any contextual information that is recorded |
|
|
Elements |
1. Reqs viewpoints and views |
A viewpoints is a set of conventions that define how reqs will be represented, how these representations will be organized and how they will be related. Viewpoints provide templates for addressing the concerns of particular stakeholder groups Views describe the actual reqs and designs that they are produced |
|
|
Element |
2. Template architectures 3. Completeness |
|
|
|
Elements 4. Relate and verify reqs relationships |
Relationships quality criteria: - defined: a relationship and the type of the relationship is described - necessary: the relationship is necessary for understanding the reqs holistically - correct: the elements do have the relationships described - unanbiguous: the are no relationship that linknelements in to diffrent and conflicting ways - consistent: described in the same way, using the same set of standard description as defined in the viewpoints |
|
|
|
Elements |
5. Business analysis information architecture |
|
|
|
Techniques |
1. Data modelling 2. Interviews 3. Workshops 4. Scope modelling 5. Functional decomposition 6. Organizational modelling |
|
|
|
Stakeholder |
Domain SME Implementation SME Project manager Sponsor Tester => may assist in defining and confirming the reqs architecture Any stakeholder: may also use the reqs architecture to assess the conpleteness of the reqs |
|
