Requirements Development and Management презентация

System
Project
Goals
Use Cases
User
Requirements
Functional /
Non-Functional
Requirements
Quality
Attributes
Business
Rules
Business Analyst
Stakeholders
Dev Team
WHAT IS A REQUIREMENT?
Business Requirements
Models
Constraints
Mock-ups
BR1
UR1
UR2
UR3
UC1
Business Analyst
Structured/
Traced
Requirements
UC2
UC3
UC4
UC5
BR2
UR4
UC6
UC7
Solution
Requirements
User
Requirements
Business
Requirements

LEVELS OF REQUIREMENTS
Business level
Functional
Requirements
Non-Functional
Requirements
Functional
Requirements
Detailed level
User level
Use Cases
Process
Models
Vision &
Scope
Business
Rules
Quality
Attributes
Constraints
What system does?
How system works?
User
Requirements
Mock-ups
Characteristics
Industry
Standards
NFRs: Performance,
Availability
Reliability
Usability
Security
Portability
Extendibility
Data Integrity
etc…
Project Goals
Industry Standards
Business
Requirements
System Requirements
System Models

EXAMPLES OF REQUIREMENTS
Business Requirements
User Requirements
User Story
Functional Requirements
Example
We as an airline want to reduce the cost of check-in counter employees by 25%
Passenger shall be able to quickly check in for the flight
FR1 System shall allow the user with “Customer” role to select the Flight from the dropdown list
FR1.1 The list of Flights shall include Flights labelled as “Outbound” only
As a passenger I want to be able to check in quickly to get to the plane in time
Idea behind
Why the organization needs this system?
What user should be able to do within the system?
What user should be able to do within the system to achieve the goal?
Non-Functional Requirements
System shall support 10 000 CCU
How should the system behave?
What functions the system should perform?

Change Needed
REQUIREMENTS DEVELOPMENT CYCLE

Idea behind
QUALITY OF REQUIREMENTS
Correctness
to cover all the requirements that are expected from the system
to make sure that there’s only one interpretation
all parts of requirements are fully documented
there’s no conflicts between the requirements
to have the criterion to classify the requirements as less or more important
it should be easy to generate test cases from the requirements
it should be possible to implement the requirement within the timeframe and the budget
can be changed without unwanted consequences
ability to trace requirements to design component, test case and code segment
Independent
Negotiable
Valuable
Estimable
Small
Testable
I
N
V
E
S
T
Agile
Traceability
Modifiability
Feasibility
Testability
Prioritization
Consistency
Completeness
Unambiguousness
Set of requirements

REQUIREMENT LIFECYCLE
Documented
Elicitation
Analysis
Documentation
Reviewed
Cancelled
Approved
Implemented
Baseline. Its version can be updated via Change Management process
Validation
Development

REQUIREMENTS MANAGEMENT
Requirements management knowledge area describes the tasks that business analysts perform in order to maintain the integrity, accuracy, and currency of requirements:
Maintaining Requirements
Tracing Requirements
Prioritizing Requirements
Requirements Change Management
Approving Requirements

REQUIREMENT ATTRIBUTES
Unique ID
Priority
Status
Estimation
Creation Date
Due Date
Component/ Feature
Text of the requirement
Requirement name
Creator
Assignee
Links,
dependencies
Version number

REQUIREMENTS’ TRACEABILITY
Horizontal traceability
Vertical traceability
Purpose of Traceability Matrix:
Helps to find the context if requirements have been changed
Control integrity of requirements and linked activities

REQUIREMENTS’ PRIORITIZATION
Value
Due Date
Dependencies
Cost
MoSCoW
Must Have
Should Have
Could Have
Won’t
Have
Development
Blocker
Critical
Major
Normal
Low
Backlog

Existing Product
REQUIREMENTS CHANGE MANAGEMENT
Change
Request 1
Change
Request 2
Change
Request 3
Change
Request n
New Product

REQUIREMENTS CHANGE MANAGEMENT FLOW
Change Management mechanisms are already built-in to Scrum
Change Management is a separate process in Plan-oriented frameworks
Change Request Identified
Analyzed
Rejected
Approved
Implemented
Cancelled
Tested
Incorporated
New Item added to Product Backlog
Groomed and prioritized
Added to next Sprint Backlog
Implemented

User Acceptance Testing (UAT)
The last phase of the software testing process.
Performed by stakeholders on the client side
The goal is to assess whether the software can fulfill business goals and user scenarios.