Docstoc

l4

Document Sample
l4 Powered By Docstoc
					Software Engineering: Lecture Number 4
Requirements Engineering

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department, Dr. B. A. Tech. University Lonere-402 103 akiwelekar@gmail.com

January 30, 2009

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University January 30, 2009akiwelekar@gm Software Engineering: Lecture Dr. B. 4 Lonere-402 103 1/9

Requirements Engineering

Requirements Engineering Tasks Inception Elicitation Elaboration Negotiation Specification Validation Requirements management

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University January 30, 2009akiwelekar@gm Software Engineering: Lecture Dr. B. 4 Lonere-402 103 2/9

Requirements Engineering

Requirements Management Features Traceability Table Source Traceability Table Dependacy Traceability Table Subsystem Traceability Table Interface Traceability Table

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University January 30, 2009akiwelekar@gm Software Engineering: Lecture Dr. B. 4 Lonere-402 103 3/9

Requirements Engineering

Requirements Inception Identifying the Stakeholders Recognizing multiple viewpoints Working toward collaboration

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University January 30, 2009akiwelekar@gm Software Engineering: Lecture Dr. B. 4 Lonere-402 103 4/9

Requirements Engineering

Requirements Gathering Collaborative Techniques Quality Function Deployment
1 2 3

Normal requirements Expected Requiremnts Exiciting Requirements

User Scenarios

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University January 30, 2009akiwelekar@gm Software Engineering: Lecture Dr. B. 4 Lonere-402 103 5/9

Requirements Engineering

Requirements Analysis What is the problem? Why is it important to solve the problem? What are the possible solution to the problem? What exactly are the data input to the system and what exactly are the data output required of the system? What are the likely complexities that might arise while solving the problem?

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University January 30, 2009akiwelekar@gm Software Engineering: Lecture Dr. B. 4 Lonere-402 103 6/9

Requirements Engineering

Requirements Analysis Analysis is intended to identify
anomalies in the requirements.Eg. Overloading in Time Table Scheduling inconsistency in the requirements.Eg.cancelled/adjustment (Dynamic Timetabling) Incompleteness (eg. Adjutsment of time table slot in case of absence)

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University January 30, 2009akiwelekar@gm Software Engineering: Lecture Dr. B. 4 Lonere-402 103 7/9

Software Requirements Specification (SRS)

Uses of SRS
Stakeholder Users, Customers and Marketing Personnel Software developers Test Engineers User documentation writers Project Manager Maintenance Engineers Concerns To ensure that the product meets the needs of the customer To make sure that they devlop exactly what is required by the customer To validate the working of the software To understand the product well enough to be abale to write the users’ manuals. To estimate the cost and plan the project To understand the functionality of the system.

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University January 30, 2009akiwelekar@gm Software Engineering: Lecture Dr. B. 4 Lonere-402 103 8/9

Software Requirements Specification (SRS)

Contents of SRS Functional Requirments
How to identify Functional Requiremnts(Who is doing what?) How to document functional requiremnts (Input, output, precondition, postcondition for every function)

Non-Functional Requirements (Eg. Distribution, Web-Access) Goals of Implementation (Why?)

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University January 30, 2009akiwelekar@gm Software Engineering: Lecture Dr. B. 4 Lonere-402 103 9/9

Structure of SRS Document
1

Introduction
1 2 3

Background Overall Description Environmental Characterstics
1 2 3

Hardware Peripherals People

2 3 4 5

Goals of Implementation Functional Requirements Non-Functional Requirements Behavioural DEscriptions
1 2

System States Events and Actions

Arvind W. Kiwelekar Assistant Professor Computer Engineering Department,Number A. Tech. University Lonere-4022009 akiwelekar@gm Software Engineering: Lecture Dr. B. 4 January 30, 103 10 / 9


				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:26
posted:1/30/2009
language:French
pages:10