Requirement Analysis Flashcards
quize
High-quality Requirements are documented,
actionable, measurable, testable, traceable, helps to
identify business opportunities, and are defined to a facilitate System Design
Requirement Analysis
The process of gathering requirements by
communicating with the customers thru:
○ Formal or Informal Interviews
○ Survey Questionnaire
○ Focus Group Discussions
Eliciting Requirements
Process to determine the quality of the
requirements
● Involves identifying whether the
requirements are unclear, incomplete,
ambiguous, and contradictory
Analyzing Requirement
The requirements are usually documented
in different formats such as:
○ Use Cases
○ User Stories
○ Natural-language Documents
○ Process Specification
Requirements Modeling
Conducted to reflect on the previous
iterations of requirements gathering in a
bid to make improvements in the process
going forward
Review and Retrospective
● Depicts the sequential flow and control logic of a
set of activities that are related.
● Can represent system interactions, data flows, etc.
● Easy to understand and can be used by both the
technical and non-technical team members
● Helps in showcasing the critical attributes of a
process
● Different formats: linear, cross-functional, and
top-down
Flowchart
● Similar to process flowcharts, although it has own
symbols and elements.
● Used to create graphs for simplify understanding
the business process
● Widely popular as a process improvement
methodology
Business Process Modeling
● Used to visually represent systems and processes
that are complex and difficult to describe in text
● Represent the flow of information through a
process or a system
● Includes the data inputs and outputs, data stores,
and the various sub-process through which the
data moves
● By visualizing all the elements of the system it is
easier to identify any shortcomings to be
eliminated in a bid to create a robust solution
Data Flow Diagram
● Consists of an integrated set of diagrams that are
created to specify, visualize, construct and
document the artifacts of a software system
● A useful technique while creating object-oriented
software and working with the software
development process
● Help in validating the architectural design of the
software
Unified Modeling Language (UML)
● A role-oriented process model
● A high-level view that captures the dynamics and
role structure of an organization
○ Roles are used to grouping together activities
into units of responsibilities
○ Activities are the basic parts of a role
■ An activity may be either carried out in isolation
or it may require coordination with other
activities within the role
Role Activity Diagrams (RAD)
● Represents the functions of a process and their
relationships to child and parent systems with the
help of a box
● Provides a blueprint to gain an understanding of
an organization’s system
Integrated Definition for Function Modeling
● Used in project planning as they provide a visual
representation of tasks that are scheduled along
with the timelines
● Help to know what is scheduled to be completed
by which date
○ The start and end dates of all the tasks in the project
can be seen in a single view
Gantt Charts
● Technique which helps to analyze the gaps in
performance of a software application to
determine whether the business requirements are
met or not
● Involves the steps that are to be taken to ensure
that all the business requirements are met
successfully
Gap Analysis
denotes the difference between the present
state and the target state
● Also known as:
○ Need Analysis
○ Need Assessment
○ Need-gap Analysis
Gap Analysis
