Please enable JavaScript.
Coggle requires JavaScript to display documents.
BA (6 Knowldge Areas, Documenting, Application Creation Process) - Coggle…
BA
6 Knowldge Areas
Business Analysis Planning and Monitoring
Plan a business analysis approach
Plan stakeholder's engagement
Plan business analysis governance
Plan business analysis information management
Identify business analysis performance improvements
Performance analysis
Assessment measures
Results analysis
Actions for improvement recommendation
how the information used in the process of business analysis is captured, stored, and integrated with other information available within an organization
requirements management process
business analysis risk management
requirements change management
business analysis information management
Stakeholder Management and Communication Plan
Elicitation and Collaboration
To prepare for elicitation
To conduct elicitation
To confirm elicitation results
To communicate business analysis information
To manage stakeholder collaboration
ensure that the elicited requirements are consistent with the stakeholders' vision and other available information
Types of requirements:
business requirements;
Vision&Scope
Business Requirements Document
• stakeholder requirements;
(user requirements)
User story
Definition of Ready (DoR)
Definition of Done (DoD)
Backlog
2 more items...
Use Cases
• solution (system) requirements
◦ functional
◦ non-functional requirements;
Software Requirements Specification
• transition requirements
Requirements Life Cycle Management
To trace requirements
To maintain requirements
To prioritize requirements
To assess requirements changes
To approve requirements
Risk Management
Scope management
3 more items...
Change Management
Minimum Viable Product (MVP)
MoSCoW prioritization
Kano
Systemico
Traceability Types and Relationships
Derive – relationships between the requirements when one requirement is obtained from another one, and they are usually on different requirements levels. For example, a functional requirement which is acquired from a stakeholder's one
Depend – relationships between different requirements which are on the same level; however, one of them can be developed only after the predecessor is implemented
Satisfy – relationships between functional requirements and different solution requirements; it helps us to identify the coverage
Validate – relationships between a requirement and test cases to ensure that everything we have captured is implemented
in alignment with each other and to manage the impact of changes if they happen.
Requirements Life Cycle
Stated
Confirmed
Communicated
Traced
Approved
Maintained for reuse
1 more item...
Strategy Analisys
To analyze the current state
To define the future state
To assess risks
To define change strategy
Requirements Analysis and Design Definition
To specify and model requirements
To verify requirements
To validate requirements
To define requirements architecture
To define solution design options
To analyze potential value and recommend solutions
correspond to business needs of an organization
Validation Techniques
Revision of the requirement
Usability test or prototyping
Product demo
Release
requirements follow the organization's quality standards.
Verification techniques
Commenting
Inspections
Checklist
Perspective-based reading
Requirements Modeling
Flowchart
Context diagram
To understand boundaries of the system and its informational flows
MindMap
Decision Table
to model requirements that deal with complex business rules
Entity Relationship Diagram
Data dictionary
o standardize the definitions of data elements
Modeling Languages
Business process modeling notation (BPMN)
Requirements modeling language (RML)
System modeling language (SysML) is a dialect of UML and is used to describe complex systems.
Unified modeling language (UML)
activities allow you to transform elicited information into requirements and designs
Solution Evaluation
To measure solution performance
To analyze performance measures
To assess solution limitations
To assess enterprise limitations
To recommend actions to increase solution value
Documenting
Vision and Scope
Business Requirements Document
Software Requirements Specification
Application Creation Process
Ideation
Conception
Elaboration
Design
Development
Introduction
Conduct user acceptance sessions and gather feedback.
Document improvements so that they can be prioritized for future releases.
Break down epics into stories and define acceptance criteria.
Assist a PO in backlog prioritization.
Support the team during the product development by answering questions and providing additional information.
Manage the scope of the solution.
Present the product to business stakeholders.
Write user guides and other product-related documentation.
Verify the solution architecture design against business requirements, high-level solution requirements, internal company's operations, compliance, and security policies.
Elicit and document user requirements.
Capture functional and non-functional system requirements.
Identify assumptions and constraints.
Define the scope of a system in terms of what will and will not be supported by the system.
Create high-level epics for the future backlog.
Define high-level business requirements.
Define a preliminary solution and get bulk estimates of this solution.
Assist in creating a business case.
Facilitate the ideation process applying an appropriate business analysis toolkit (for example, brainstorming, mind mapping, interviewing).
Ensure that product ideas are collected, recorded, and properly evaluated.
Assist with defining criteria for evaluating product ideas.
Summarize and present the information in an easy to understand and follow manner.