2
Introduction
• Requirements form the basis for all
software products
• Requirements engineering is the
process, which enables us to
systematically determine the
requirements for a software product
docsity.com
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Introduction-Software Requirement-Lecture Slides, Slides of Software Project Management
This course includes types of requirements, modeling of non functional, static and dynamic modelling, requirement elicitation and use case modeling. This lecture includes: Stakeholders, Affected, System, Documents, Existing, Domain, Business, Area
Typology: Slides
2011/2012
1 / 35
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Introduction-Software Requirement-Lecture Slides and more Slides Software Project Management in PDF only on Docsity!
2
Introduction
- Requirements form the basis for all
software products
- Requirements engineering is the
process, which enables us tosystematically determine therequirements for a software product
3
Software Requirements
Lecture # 1
5
Software Requirements - 1
- A complete description of
what
the
software system will do withoutdescribing
how
it will do it is
represented by the softwarerequirements
6
Software Requirements - 2
- Software requirements are complete
specification of the desired externalbehavior of the software system to bebuilt
- They also represent External behavior
of the system
8
Software Requirements - 4
- Software requirements may be:
- Part of the bid of contract– The contract itself– Part of the technical document, which
describes a product
9
IEEE Definition
- A condition or capability that must be
met or possessed by a system...tosatisfy a contract, standard,specification, or other formallyimposed document– IEEE Std 729
11
Levels of Software Requirements
- Stakeholders describe requirements at
different levels of detail–
“What versus How”
“One person’s floor is another person’sceiling
”
12
What Versus How
User needsProduct spaceActual product’s behaviorArchitecture/data flowModule specificationsAlgorithmsCode
WhatHowWhatHowWhatHowWhatHowWhatHowWhatHow
14
Examples of Requirements - 1
- The system shall maintain records of
all payments made to employees onaccounts of salaries, bonuses,travel/daily allowances, medicalallowances, etc.
15
Examples of Requirements - 2
- The system shall interface with the
central computer to send daily salesand inventory data from every retailstore
17
Examples of Requirements - 4
- The system shall allow users to search
for an item by title, author, or byInternational Standard Book Number
- The system’s user interface shall be
implemented using a web browser
18
Examples of Requirements - 5
- The system shall support at least
twenty transactions per second
- The system facilities which are
available to public users shall bedemonstrable in ten minutes or less
20
Kinds of Software Requirements• Functional requirements• Non-functional requirements• Domain requirements• Inverse requirements• Design and implementation constraints
21