2. Maintain Requirement

Question 1

Purpose

Answer 1

Retain reqs accuracy and consistency throughout and beyond the change during the entire reqs life cycle
And to support reuse of reqs in other solution

Question 2

Description

Answer 2

To max benefit of maintain and reuse should be:
- consistently represented
- reviewed and approved for maintenance using standard process, access right and quality
- easily accessible and understandable

Question 3

Inputs

Answer 3

Reqs + Designs

Question 4

Elements 1

Answer 4

1. Maintain reqs
   - reqs must be clearly named and defined, and easily available to sh
   - maintain the relationships among reqs

Question 5

Elements 2

Answer 5

2. Maintain attributes
   Some attributes change as the BA uncovers more info and conduct further analysis
   An attribute may change even though the reqs does not

Question 6

Elements 3

Answer 6

3. Reusing reqs
   Reqs can reused:
   - within the current initiative
   - within similar initiatives
   - within similar departments
   - throughout the entire org

Question 7

Guidelines and tools

Answer 7

Information mng approach: indicates how reqs will be manage for reuse

Question 8

Techniques

Answer 8

Biz rules analysis
Data flow diagrams
Data modeling
Document analysis
Functional decomposition
Process modeling
Use cases and scenarios
User stories

Question 9

Stakeholder

Answer 9

Domain sme
Implementation sme
Operational support
Regulator
Tester

Question 10

Outputs

Answer 10

Reqs + designs (maintained)