SOFTWARE REQUIREMENTS ENGINEERING

SOFTWARE ENGINEERING

 "the application of a systematic, disciplined, quantifiable approach to the development,

operation, and maintenance of software".[IEEE]

Scope

Quality

Cost Schedule
 “Successful software development is about creating value, not software”

 Fitness of purpose
 Quality
 Risk
 Cost of Operation
 Warranty
 Life
 Cost
GOALS OF A SOFTWARE SYSTEM

Business goals

Improve Improve confidence

Reduce total cost of Improve market Support Improved
capability/quality of in and perceptions
ownership position Business Processes
System of the system
REQUIREMENTS – A PROBLEM

Approximately 60%-70% of IT project failures result

from poor requirements gathering, analysis, and
management.
- Meta Group, March 2003
“If you do a investigation evaluation on
unsuccessful software projects, you'll find that
most of them failed because the person
responsible didn't properly manage the
project's requirements and expectations.”
- Andy Feibus
REQUIREMENTS – A PROBLEM

 A study by project management consulting company identifies five top causes of troubled projects:
 Requirements: Unclear, lack of agreement, lack of priority, contradictory, ambiguous (Confusing)
inaccurate. (incorrect)
 Resources: Lack of resources, resource conflicts, turnover of key resources, poor planning.
 Schedules: Too tight, unrealistic, over confident.
 Planning: Based on insufficient data, missing items, insufficient details, poor estimates.
 Risks: Unidentified or assumed, not managed.
COURSE GOALS/OBJECTIVES

 Understanding key concepts of Requirements Engineering

 Prepare for, and undertake the requirements elicitation tasks
 Analyze client needs
 Create models of requirements
 Prepare software requirements specifications using an industry standard
 Prepare for, and undertake specification reviews.
 Manage Requirements for a Small/Medium scale project.
REQUIREMENTS - A PROBLEM
PROJECT SUCCESS & REQUIREMENTS
Reliable
Formal Estimates
methodology Minimized scope
Standard
infrastructure 5% 5% Clear business
6% 12% objectives
14%
Executive 15%
support
17%
14%
5% 7%
User
involvement
Experienced
Project Manager
Skilled Staff Agile requirements process

Source: “Chaos Chronicles, III, 2003”.

www.standishgroup.com
ANY QUESTION?