Please enable JavaScript.
Coggle requires JavaScript to display documents.
3.4. Business Analysis Information Management, 3.4.1. Purpose - Coggle…
3.4. Business Analysis Information Management
Develop an approach for how BA info will be stored and accessed
3.4.2. Description
Include all info BA elicit, create, collect and disseminate when performing BA tasks
Identify
How info should be organized
Level of detail that info should be captured
Any relationships between info
How info may be used
How info should be accessed and stored
Characteristics abt info must be maintained
=> Ensure that BA info:
is organized in a functional and useful manner
is easily accessible to appropriate personnel
is stored for necessary length of time
3.4.3. Input
BA approach
Governance approach
SH engagement approach
3.4.4. Elements
.1. Organization of BA info
Efficient access and use
Well structured to ensure
Not difficult to locate
Not conflict with other info
Needlessly duplicated
BA determines the best to structure & organize BA info at the start
Consider type and amount of info to be collected
Consider SH's access and usage needs
Consider size & complexity of change
Define relationships among types of info
.2. Level of Abstraction
Describe the width and depth of the info provided
To determine the detail level of each SH, consider:
the needs of SH
the complexity of what is being explained
the importance of the change
BA should present info with appropriate breadth (width) and detail level based on each SH's role
.3. Plan Traceability Approach
.4. Plan for requirements reuse
.5. Storage and Access
.6. Requirement attribute
Some commonly used attributes:
Absolute reference: provide a unique identifer
Author: provide name of person to be consulted
Complexity
Ownership: indicates the individual/group needing the req or will be the business owner after the solution is implemented
Priority: indicate relative importance of req
Risk: uncertain events may impace req
Source: origin of req
Stability: maturiry of req
Status: state of req (proposed, accepted, verified,...)
Urgency: how soon the req is needed
Provide info about requirements in the ongoing management of the rqm throughout the changes
Allow BA to associate info with individual/related groups of requirements
Help team efficiently and effectively:
make trade-offs btw requirements,
identify SH affected by changes
understand the effect of a proposed change
3.4.1. Purpose