Documente Academic
Documente Profesional
Documente Cultură
Specifications
Tathagat Varma
MindTek, 11-Mar-2004
Contents
Big Picture of The Problem
Common Problems with Requirements
Volere
My Experiences with Volere
References
Q&A
Disclaimer
This presentation is based on
Dilbert on Requirements
The Problem
The Problem
The Problem
For software projects, according to the
The Problem
Hidden Factories
Unacknowledged rework due to defects is
Lack of Training
Missing Requirements
Using standards like Mil-Std-490 or IEEE P1233 can help ensure you dont miss out
most of the requirements.
At the minimum, include the following:
Functional
Reliability
Performance
Maintainability
Interface
Operability
Environment
Safety
Facility
Regulatory
Transportation
Security
Deployment
Privacy
Training
Design constraints
Personnel
Support
But not limited to
Etc.
And/Or
WRONG: The system shall support the training coordinator in defining training
scenarios.
RIGHT: The system shall provide input screens for defining training scenarios.
The system shall provide automated training scenario processes.
The terms but not limited to, and Etc. are put in place because the person
writing the requirements suspects that more may be needed than is
currently listed. Using these terms will not accomplish what the author wants
and can backfire.
Ambiguous Terms
Requirements Definition
Volere
Volere
Volere is the umbrella that covers the
Why Volere ?
American Express
Aventis Pharmaceuticals
BankOne
Cesky Mobil
Commonwealth Bank
Cordis Europa NV
Emirates Airlines
ETAS GmbH
Federal Express
GEC Marconi
Guinness UDV
H&R Block
Harvard Online
Hewlett-Packard
IBM
Insurance Australia Group
International Atomic Energy Authority
Jaguar
KMD
Lloyds TSB
Micron Computer
Ministry of Defence
MobiFon
National University of Ireland
Nationals Air Traffic Service
Nordstrom Nordstrom
Optus
Patni Computer Systems Ltd. (India)
PixelPark
Plymouth City Council
PriceWaterhouseCoopers
Rohde & Schwarz
SBEI Finland
sd&m
Servcon South Africa
Siemens
Spacetec
Swinburne University
Telecom Italia
Telemedicine,
Victoria Legal Aid
Wachovia
Woolworths
Project Drivers
Project Constraints
Functional Requirements
Non-functional Requirements
Project Issues
chapters, total 27
Project Drivers
Project drivers
Project Constraints
Functional Requirements
Non-Functional Requirements
contd
Project Issues
Fit Criterion
Requirements Description
Need. If there is a doubt about the necessity of a requirement, then ask: What is
the worst thing that could happen if this requirement were not included? If you do
not find an answer of any consequence, then you probably do not need the
requirement (i.e., it might just be a gold-plating)
Verification. As you write a requirement, determine how you will verify it.
Determine the criteria for acceptance. This step will help insure that the
requirement is verifiable.
Attainable. To be attainable, the requirement must be technically feasible and fit
within budget, schedule, and other constraints. If you are uncertain about
whether a requirement is technically feasible, then you will need to conduct the
research or studies to determine its feasibility. Even is a requirement is
technically feasible, it may not be attainable due to budget, schedule, or other,
e.g., weight, constraints. There is no point in writing a requirement for something
you cannot afford -- be reasonable.
Clarity. Each requirement should express a single thought, be concise, and
simple. It is important that the requirement not be misunderstood -- it must be
unambiguous. Simple sentences will most often suffice for a good requirement.
Reviewing Requirements
Irrespective of the SDLC (Waterfall / V-
Testing Requirements
References
http://www.processimpact.com/articles/qualreqs.html
http://www.stickyminds.com/sitewide.asp?
ObjectId=6335&Function=DETAILBROWSE&ObjectT
ype=COL
http://www.spmn.com/lessons.html#four
http://www.odegard.com/enews/aug2003/dcopq.htm
http://www.stevemcconnell.com/articles/art04.htm
http://www.artima.com/weblogs/viewpost.jsp?
thread=5446
Any questions ?