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
