Please enable JavaScript.
Coggle requires JavaScript to display documents.
5) Requirements Analysis and Design Definition - Coggle Diagram
5) Requirements Analysis and Design Definition
Tasks
Specify and Model Requirements
Elements
Model Requirements
Matrices
Diagrams
Modeling categories
Rationale
Activity Flow
Capability
Data and Information
People and Roles
Analyze Requirements
Represent Requirements and Attributes
Implement the Appropriate Levels of Abstraction
Verify Requirements
Elements
Characteristics of Requirements and Designs Quality
Atomic
Complete
Consistent
Concise
Feasible
Unambiguous
Testable
Prioritized
Understandable
Verification Activities
Checklists
Validate Requirements
Elements
Identify Assumptions
Define Measurable Evaluation Criteria
Evaluate Alignment with Solution Scope
Define Requirements Architecture
A business analyst would use Requirements Architecture in order to:
Understand which models are appropriate for the domain, solution scope,
and audience.
Organize requirements into structures relevant to different stakeholders
Illustrate how requirements and models interact with and relate to each
other, and show how the parts fit together into a meaningful whole.
Ensure the requirements work together to achieve the overall objectives
Make trade-off decisions about requirements while considering the overall
objectives
Elements
Requirements Viewpoints and Views
viewpoint examples
Business process models
Data models and information
User interactions and use cases
Audit and security
Business models
Template Architectures
Completeness
Relate and Verify Requirements Relationships
Quality criteria:
The relationship is DEFINED
The relationship is NECESSARY
The relationship is CORRECT
The relationship is UNAMBIGUOUS
The relationship is CONSISTENT
Business Analysis Information Architecture
Define Design Options
Elements
Define Solution Approaches
Create
Purchase
A combination of both
Identify Improvement Opportunities
Increase Efficiencies
Improve Access to Information
Identify Additional Capabilities
Requirements Allocation
Describe Design Options
Design elements may describe:
Business policies and business rules
Business processes to be performed and managed
People who operate and maintain the solution, including their job
functions and responsibilities
Operational business decisions to be made
Software applications and application components used in the solution
Organizational structures, including interactions between the
organization, its customers, and its suppliers
Analyze Potential Value and Recommend Solution
Elements
Expected Benefits
Expected Costs
Timeline
Effort
Operating costs
Purchase and/or implementation costs
Maintenance costs
Physical resources
Information resources
Human resources
Determine Value
Assess Design Options and Recommend Solution
Factors to take into consideration:
Available Resources
Constraints on the Solution
Dependencies between Requirements
Application to BACCM
Change
This core concept refers to how elicitation results are transformed into requirements and designs in order to define change.
Need
This core concept refers to how needs are analyzed in order to be able to
recommend a solution that meets the needs.
Solution
This core concept refers to defining solution options and the recommendation of the solution that is most likely to meet the business need as well as having the most value.
Stakeholder
This core concept refers to how the stakeholders relate to the requirements and designs produced by the business analysts.
Value
This core concept refers to analyzing and quantifying the potential value of solution options.
Context
This core concept refers to how the business analyst models and describes the context in formats that are understandable and usable by all stakeholders.