Requirements analysis and design definition Flashcards
describes a set of requirements or designs in detail using analytical techniques.
Specify and Model Requirement
ensures that a set of requirements or designs has been developed in enough detail to be usable by a particular stakeholder, is internally consistent, and is of high quality
Verify Requirements
ensures that a set of requirements or designs delivers business value and supports the organization’s goals and objectives.
Validate Requirements:
structures all requirements and designs so that they support the overall business purpose for a change and that they work effectively as a cohesive whole.
Define Requirements Architecture:
identifies, explores and describes **different possible ways **of meeting the need.
Define Solution Options:
assesses the business value associated with a potential solution and compares different options, including trade-offs, to identify and recommend the solution option that delivers the greatest overall value.
Analyze Potential Value and Recommend Solution
used when the business analyst is modelling a requirement or set of requirements that have a complex but uniform structure, which can be broken down into elements that apply to every entry in the table.
Matrices
is a visual, often pictorial, representation of a requirement or set of requirements.
Diagrams
Business analysis information is decomposed into components to further examine for:
* anything that must change to meet the business need,
* anything that should stay the same to meet the business need,
* missing components,
* unnecessary components, and
* any constraints or assumptions that impact the components.
Analyze Requirements
Business analysts identify information for requirements and their attributes as part of the elicitation results. Requirements should be explicitly represented and should include enough detail such that they exhibit the characteristics of requirements and designs quality
Represent Requirements and Attributes
The level of abstraction of a requirement varies based on the type of requirement and audience for the requirement.
Implement the Appropriate Levels of Abstraction
Atomic
Complete
Consistent
Concise
Feasible
Unambiguous
Testable
Prioritized
Understandable
Characteristics of Requirements and Designs Quality
(Verify Requirements)
checking for compliance with organizational performance standards for business analysis, such as using the right tools and methods,
* checking for correct use of modelling notation, templates, or forms,
* checking for completeness within each model,
* comparing each model against other relevant models, checking for elements that are mentioned in one model but are missing in other models, and verifying that the elements are referenced consistently,
* ensuring the terminology used in expressing the requirement is understandable to stakeholders and consistent with the use of those terms within the organization, and
Verification Activities
(Verify Requirements)
used for quality control when verifying requirements and designs. Checklists may include a standard set of quality elements that business analysts use to verify the requirements, or they may be specifically developed to capture issues of concern.
Checklists
(Verify Requirements)
If an organization is launching an unprecedented product or service, it may be necessary to make ___________ about customer or stakeholder response, as there are no similar previous experiences on which to rely.
Identify Assumptions
(Verify Requirements)
While the expected benefits are defined as part of the future state, the specific measurement criteria and evaluation process may not have been included.
Define Measurable Evaluation Criteria
(Verify Requirements)
A requirement can be of benefit to a stakeholder and still not be a desirable part of a solution.
Evaluate Alignment with Solution Scope
(Verify Requirements)
a set of conventions that define how requirements will be represented, how these representations will be organized, and how they will be related.
Requirements Viewpoints and Views
(Define Requirements Architecture)
framework that is a collection of viewpoints that is standard across an industry, sector, or organization.
Template Architectures
(Define Requirements Architecture)
An architecture helps ensure that a set of requirements is complete. The entire set of requirements should be able to be understood by the audience in way that it can be determined that the set is cohesive and tells a full story.
Completeness
(Define Requirements Architecture)
Requirements may be related to each other in several ways when defining the requirements architecture.
Defined
Necessary
Correct
Unambiguous
Consistent
Relate and Verify Requirements Relationships
(Define Requirements Architecture)
describes whether solution components will be created or purchased, or some combination of both.
Create
Purchase
Combination of both
Define Solution Approaches
(Define Design Options)
When proposing design options, a number of opportunities to improve the operation of the business may occur and are compared
* Increase Efficiencies
* Improve Access to Information
* Identify Additional Capabilities
Identify Improvement Opportunities
(Define Design Options)
are investigated and developed while considering the desired future state, and in order to ensure the design option is valid.
Describe Design Options
(Define Design Options)
**describe the positive value **that a solution is intended to deliver to stakeholders. Value can include benefits, reduced risk, compliance with business policies and regulations, an improved user experience, or any other positive outcome.
Expected Benefits
(Analyze Potential Value & Recommend Solutions)
timeline, * effort,
* operating costs, * purchase and/or implementation costs, * maintenance costs, * physical resources, * information resources,
* human resources.
Expected Costs
(Analyze Potential Value & Recommend Solutions)
The potential value of a solution to a stakeholder is based on the benefits delivered by that solution and the associated costs.
Determine Value
(Analyze Potential Value & Recommend Solutions)
Each design option is assessed based on the potential value it is expected to deliver.
Assess Design Options and Recommend Solution
(Analyze Potential Value & Recommend Solutions)
