Scribd
Upload
99 views13 pages

Requirements Engineering Good Practices

This document discusses good practices for requirements engineering. It outlines the objectives of understanding different stages of the requirements development process framework and how to implement them. The contents include requirements engineering good practices, a requirements development process framework covering elicitation, analysis, specification and validation. It also discusses a representative requirements development process and requirements management.

Uploaded by

Long Nguyễn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
99 views13 pages

Requirements Engineering Good Practices

This document discusses good practices for requirements engineering. It outlines the objectives of understanding different stages of the requirements development process framework and how to implement them. The contents include requirements engineering good practices, a requirements development process framework covering elicitation, analysis, specification and validation. It also discusses a representative requirements development process and requirements management.

Uploaded by

Long Nguyễn
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

CHAPTER 3

Requirements engineering
good practices
Objectives
• Student should enhance every stage in the requirement
development process framework and how to implement these
stages.
• Student should obtain a wide range of good practice in software
requirements to prepare for the next chapters
• Need to help student understand these practices aren’t suitable for
every situation, so use good judgment, common sense, and
experience. Even the best practices need to be selected, applied,
and adapted thoughtfully to appropriate situations by skilled
business analysts.
• Student must enhance that different practices might be most
appropriate for understanding the requirements for different
portions of a given project.
• Use cases and user interface prototypes might help for the client
side, whereas interface analysis is more valuable on the server
side…etc.
Contents

1. Requirements engineering good practices


2. A requirements development process
framework
- Elicitation
- Analysis
- Specification
- Validation
3. A representative requirements development
process
4. Requirements management
Requirements engineering
good practices
A requirements development process
framework
A representative requirements
development process
Requirements elicitation

• Define product vision and project scope


• Identify user classes and their characteristics
• Select a product champion for each user class
• Conduct focus groups with typical users
• Work with user representatives to identify user requirements
• Identify system events and responses
• Hold elicitation interviews
• Hold facilitated elicitation workshops
• Observe users performing their jobs
• Distribute questionnaires
• Perform document analysis
• Examine problem reports of current systems for requirement ideas
• Reuse existing requirements
Requirements analysis

• Model the application environment


• Create user interface and technical prototypes
• Analyze requirement feasibility
• Prioritize the requirements
• Create a data dictionary
• Model the requirements
• Analyze interfaces between your system and
the outside world
• Allocate requirements to subsystems
Requirements specification

• Adopt requirement document templates


• Identify requirement origins
• Uniquely label each requirement
• Record business rules
• Specify nonfunctional requirements
Requirements validation

• Review the requirements


• Test the requirements
• Define acceptance criteria
• Simulate the requirements
Requirements management

• Establish a requirements change control process


• Perform impact analysis on requirements changes
• Establish baselines and control versions of
requirements sets
• Maintain a history of requirements changes
• Track the status of each requirement
• Track requirements issues
• Maintain a requirements traceability matrix
• Use a requirements management tool
Knowledge

• Train business analysts


• Educate stakeholders about requirements
• Educate developers about the application domain
• Define a requirements engineering process
• Create a glossary
Project management

• Select an appropriate software development life cycle


• Plan requirements approach
• Estimate requirements effort
• Base project plans on requirements
• Identify requirements decision makers
• Renegotiate project commitments when requirements
change
• Analyze, document, and manage requirements-related risks
• Track the effort spent on requirements
• Review lessons learned regarding requirements on other
projects

You might also like