Software Requirements Analysis (Finals) Flashcards

(29 cards)

1
Q

Begins before a project progresses into the
development stage.

A

Requirements Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

It helps an analyst or project manager discovering business goals to document and test them or create a visual representation.

A

Requirements Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

This process designs optimal software with the fewest risks possible.

A

Requirements Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

The first step of the requirements analysis process is to identify key stakeholders
who are the main sponsors of the project.

A

Identify Stakeholders and End-users

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

They will have the final say on what
should be included in the scope of the project.

A

Stakeholders

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

A process of analysis that helps to identify software requirements from user stories, use cases, and other techniques.

A

Requirement Gathering

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Define the project scope without too much detail.

A

Data flow program (DFP)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

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.

A

Use Case

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Focus on user needs, user expectations, and user goals.

A

User stories

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

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.

A

Build Prototypes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

The system behavior and how it responds to user input. Req

A

Functional requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Technical issues to be considered for the successful implementation of the product. req

A

Technical requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

The attributes or performance of the system. req

A

Non-functional requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Operations to be carried out in the backend for proper functioning of the product. req

A

Operational requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Steps required to implement a new product smoothly. req

A

Transitional requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Requirements Analysis Stages

A

Draw a Context Diagram
Develop a Prototype
Model Requirements
Finalize Requirements
Requirements Documentation

16
Q

Systematic process used to assess the potential consequences of changes to a system.

A

Impact Analysis

16
Q

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.

A

Finalize Requirements

16
Q

A simple model that defines the boundaries and interfaces of the proposed systems with the external world.

A

Context Diagram

16
Q

This stage involves creating requirement models that ultimately allow customers and stakeholders to imagine the product in the making.

A

Model Requirements

16
Q

Finalizes the first five steps, after which a project team awaits a sign-off before completing a software project.

A

RAD - Requirement Analysis Document

16
Q

Analysis Technique used to create graphs that simplify the understanding of the business process.

A

Business Process Model and Notation (BPMN)

16
Q

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.

A

Business Motivation Model

16
Q

Requirements Analysis Techniques

A
  • Business Process Model and Notation (BPMN)
  • Business Motivation Model
  • Customer Journey Mapping
  • Flowchart Technique
  • Gap Analysis
  • Gannt Charts
  • Unified Modelling Language (UML)
16
analysis technique that allow project managers to distinguish the gap between where the requirements are and where they should be.
Gap Analysis
16
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
16
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
16
an analysis technique used to plan and tracks scheduled task timelines.
Gannt Charts
16
a powerful tool for requirements management , communication, and collaboration. It usesmultiple diagrams
Unified Modelling Language (UML)