Scribd
Upload
25 views

Week 1 SRE

This document provides an overview of a course on software requirement engineering. It discusses key topics that will be covered like requirement levels, evolution, and management. It emphasizes the importance of clearly defined requirements for project success. Examples of well-written requirements are provided for systems like a library management system. Guidelines are given for documenting requirements consistently and avoiding computer jargon.

Uploaded by

Wardaddy
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
25 views

Week 1 SRE

This document provides an overview of a course on software requirement engineering. It discusses key topics that will be covered like requirement levels, evolution, and management. It emphasizes the importance of clearly defined requirements for project success. Examples of well-written requirements are provided for systems like a library management system. Guidelines are given for documenting requirements consistently and avoiding computer jargon.

Uploaded by

Wardaddy
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/ 20

Overview of the Course

l Software Requirements
l Levels/layers of requirements
l Requirement evolution
l Requirement prioritization
l Requirement management ,
l Requirement elicitation
l Requirement specification
l Requirements validation
l Requirements engineering for agile methods 1-
1
Software Engineering, COMP201 Slide 1
Software Requirement Engineering

Software Engineering, COMP201 Slide 2


Key aspects of successful
Software Development

l What are they?


• Resources
• User input and involvement
• Effective management and support
• Clearly defined, complete requirements

1-
3
Software Engineering, COMP201 Slide 3
Project Success Factors
1. User Involvement 15.9%
2. Executive Management Support 13.9%
3. Clear Statement of Requirements 13.0%
4. Proper Planning 9.6%
5. Realistic Expectations 8.2%
6. Smaller Project Milestones 7.7%
7. Competent Staff 7.2%
8. Ownership 5.3%
9. Clear Vision & Objectives 2.9%
10. Hard‐Working, Focused Staff 2.4% 1-
11. Other 13.9% 4
Software Engineering, COMP201 Slide 4
Other factors and risks
• Lack of commitment – management and user
• Misunderstanding requirements
• End user expectations
• Scope change, new technology
• Expertise
• Requirements froze/change
• Low method use

1-
5
Software Engineering, COMP201 Slide 5
Levels of Software Requirements
l Stakeholders describe requirements at
different levels of detail
• “What versus How”
• “One person’s floor is another person’s ceiling”

Software Engineering, COMP201 Slide 6


Requirements engineering
Requirements engineering is the process of establishing
l the services that the customer requires from a system

l the constraints under which it operates and is developed

Requirements
The descriptions of the system
services and constraints
that are generated during the
requirements engineering
process

Software Engineering, COMP201 Slide 7


What is a requirement?
l It may range from a high-level abstract statement of
a service or of a system constraint to a detailed
mathematical functional specification
• Develop a calculator

• The code must be Object Oriented

• The calculator must allow matrix multiplication of up to 10 x 10 matrix


using dot multiplication method

Software Engineering, COMP201 Slide 8


Why to RE
l We try to separate problem from the design and from
the solution

l We need to establish benchmarks, metrics, and


views about the problem to select the right approach

1-
9
Software Engineering, COMP201 Slide 9
So let’s ask again, why RE?
• To minimize costs
• Software is everywhere, a major part of many small (microwave) and
big (airliner) systems
• Serious consequences of failures
• Rework/fixing costs – 50 x the price of fix during the requirements
specification
• Costs, costs, costs…

• To build systems that have purpose, value

1-
10
Software Engineering, COMP201 Slide 10
Sources of Requirements
l Stakeholders
People affected in some way by the system
l Documents
l Existing system
l Application Domain

1-
11
Software Engineering, COMP201 Slide 11
Guidelines for writing requirements
l Invent a standard format and use it for all requirements
l Use language in a consistent way. Use
shall for mandatory requirements,
should for desirable requirements
l Use text highlighting to identify key parts of the
requirement

Avoid the use of computer jargon !!!


Software Engineering, COMP201 Slide 12
Examples of Requirements - 1
l The system shall maintain records of all payments
made to employees on accounts of salaries,
bonuses, travel/daily allowances, medical
allowances, etc.

Software Engineering, COMP201 Slide 13


Examples of Requirements - 2
l The system shall interface with the central computer
to send daily sales and inventory data from every
retail store

Software Engineering, COMP201 Slide 14


Examples of Requirements - 3
l The system shall maintain records of all library
materials including books, serials, newspapers and
magazines, video and audio tapes, reports,
collections of transparencies, CD-ROMs, DVDs, etc.

Software Engineering, COMP201 Slide 15


Examples of Requirements - 4
l The system shall allow users to search for an item by
title, author, or by International Standard Book
Number

l The system’s user interface shall be implemented


using a web browser

Software Engineering, COMP201 Slide 16


Examples of Requirements - 5
l The system shall support at least twenty transactions
per second

l The system facilities which are available to public


users shall be demonstrable in ten minutes or less

Software Engineering, COMP201 Slide 17


Software Requirements
l Why should we make the software?
Class Task
Find answers to
l What the software needs to do? all the questions
l What functionalities should be provided? posed for a
Library
l What is visible to the user interact with it? Management
l What are the quality attributes? System

l What are the features of a software?


l How should it be developed?
l When & Where should it be developed?
l Where would be we get the information from?
Software Engineering, COMP201 Slide 18
References
l ‘Requirements Engineering: Processes and
Techniques’ by G. Kotonya and I.
Sommerville, John Wiley & Sons, 1998
l Software Requirements: Objects, Functions,
and States by A. Davis, PH, 1993
l Software Engineering 6th Edition, by I.
Sommerville, 2000
l Software Engineering 5th Edition, by R.
Pressman

Software Engineering, COMP201 Slide 19


Key points
l Requirements set out what the system should do
and define constraints on its operation and
implementation
l User requirements should be written in natural
language, tables and diagrams
l System requirements are intended to communicate
the functions that the system should provide
l A software requirements document is an agreed
statement of the system requirements

Software Engineering, COMP201 Slide 20

You might also like