Software Requirements Analysis (Finals) Flashcards
Begins before a project progresses into the
development stage.
Requirements Analysis
It helps an analyst or project manager discovering business goals to document and test them or create a visual representation.
Requirements Analysis
This process designs optimal software with the fewest risks possible.
Requirements Analysis
The first step of the requirements analysis process is to identify key stakeholders
who are the main sponsors of the project.
Identify Stakeholders and End-users
They will have the final say on what
should be included in the scope of the project.
Stakeholders
A process of analysis that helps to identify software requirements from user stories, use cases, and other techniques.
Requirement Gathering
Define the project scope without too much detail.
Data flow program (DFP)
Determine system behaviour and communicate from the end user’s
perspective. Provide a walkthrough of the entire product through the eyes of the end-user.
Use Case
Focus on user needs, user expectations, and user goals.
User stories
A prototype provides users a sample look and feel of the final product. This technique will help address feasibility issues and identify problems ahead of time.
Build Prototypes
The system behavior and how it responds to user input. Req
Functional requirements
Technical issues to be considered for the successful implementation of the product. req
Technical requirements
The attributes or performance of the system. req
Non-functional requirements
Operations to be carried out in the backend for proper functioning of the product. req
Operational requirements
Steps required to implement a new product smoothly. req
Transitional requirements
Requirements Analysis Stages
Draw a Context Diagram
Develop a Prototype
Model Requirements
Finalize Requirements
Requirements Documentation
Systematic process used to assess the potential consequences of changes to a system.
Impact Analysis
The final stage of requirements analysis is when analysts study and correct data flow
problems on the graphics, prototypes, and modules used to create user flow designs for analysis.
Finalize Requirements
A simple model that defines the boundaries and interfaces of the proposed systems with the external world.
Context Diagram
This stage involves creating requirement models that ultimately allow customers and stakeholders to imagine the product in the making.
Model Requirements
Finalizes the first five steps, after which a project team awaits a sign-off before completing a software project.
RAD - Requirement Analysis Document
Analysis Technique used to create graphs that simplify the understanding of the business process.
Business Process Model and Notation (BPMN)
Model is used to help a company make decisions, but analysts also use it to make business-related decisions regarding requirements in the analysis stage.
Business Motivation Model
Requirements Analysis Techniques
- Business Process Model and Notation (BPMN)
- Business Motivation Model
- Customer Journey Mapping
- Flowchart Technique
- Gap Analysis
- Gannt Charts
- Unified Modelling Language (UML)
analysis technique that allow project managers to distinguish the gap between where the requirements are and where they should be.
Gap Analysis
Another brilliant visual representation used during requirement analysis. It displays customer fears, objections, and motivation to ensure the requirements will meet business and user needs.
Customer Journey Mapping
Another requirement analysis model used in the third stage of the process. It depicts the control logic and sequential flow of relevant activity sets.
Flowchart Technique
an analysis technique used to plan and
tracks scheduled task timelines.
Gannt Charts
a powerful tool for requirements management , communication, and collaboration. It usesmultiple diagrams
Unified Modelling Language (UML)
