SOFTWARE REQUIREMENT SPECIFICATION

Slides:



Advertisements
Similar presentations
Project management Project manager must;
Advertisements

Characteristics of a good SRS
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
Requirements Analysis CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 7, 2003.
SE 555 Software Requirements & Specification Requirements Management.
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 1 (cont ’d) Title : Client requirements (Review) Mandatory reading: I.
SE 555 Software Requirements & Specification Requirements Validation.
Project Management Session 7
Iterative development and The Unified process
1 Software Requirements Specification Lecture 14.
S R S S ystem R equirements S pecification Specifying the Specifications.
Capability Maturity Model
Data Structures and Programming.  John Edgar2.
SOFTWARE REQUIREMENTS SPECIFICATION (SRS)
RUP Requirements RUP Artifacts and Deliverables
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
Typical Software Documents with an emphasis on writing proposals.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
N By: Md Rezaul Huda Reza n
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Requirements Engineering CSCU 411 Ch 9. LEARNING OBJECTIVES To understand that requirements engineering is a cyclical process involving three types of.
CPSC 873 John D. McGregor Session 4 Requirements V & V - continued.
Lecture 7: Requirements Engineering
© Mahindra Satyam 2009 Configuration Management QMS Training.
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
Requirements Collection By Dr. Gabriel. Requirements A requirement is any function, constraint, or property that the system must provide, meet, or satisfy.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 10 Slide 1 Chapter 13 Finalizing Design Specifications.
Capturing the requirements  Requirement: a feature of the system or a description of something the system is capable of doing in order to fulfill the.
(SRS) SOFTWARE REQUIREMENT SPECIFICATION(SRS) 1. Topics to be discussed.. What is an SRS? Purpose of an SRS Who reads the SRS? Who writes the SRS? Characteristics.
1 Quality Attributes of Requirements Documents Lecture # 25.
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
Requirements / Specifications. 01/18/10CS-499G2 Requirements Determine what the customer needs (wants) the software to do  What are requirements?  An.
Requirements Engineering
Winter 2007SEG2101 Chapter 31 Chapter 3 Requirements Specifications.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Software Requirements Specification Document (SRS)
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
Information Technology Project Management, Seventh Edition.
 System Requirement Specification and System Planning.
Software Development Module Code: CST 240 Chapter 6: Software Maintenance Al Khawarizmi International College, AL AIN, U.A.E Lecturer: Karamath Ateeq.
Daniel Amyot, University of Ottawa Based on slides by Gunter Mussbacher (2009) and Stéphane Somé (2008) with material from these standards: IEEE ,
Verification and Validation. Topics covered l Verification and validation planning l Program Testing l Software inspections.
Project Planning: Scope and the Work Breakdown Structure
An Overview of Requirements Engineering Tools and Methodologies*
PREPARED BY G.VIJAYA KUMAR ASST.PROFESSOR
Testing Process Roman Yagodka ISS Test Leader.
SYSTEM ANALYSIS AND DESIGN
Chapter 5: Project Scope Management
System Requirements Specification
SQA Role during Software Requirements Phase
CS 790M Project preparation (I)
John D. McGregor Session 4 Requirements V & V - continued
UNIT II.
Requirements Analysis
Capability Maturity Model
Requirement Documentation &
Chapter 13 Finalizing Design Specifications
Dr. Jiacun Wang Department of Software Engineering Monmouth University
REQUIREMENT ANALYSIS.
FdSc Module 107 Systems Analysis
Applied Software Project Management
Capability Maturity Model
CS 426 CS 791z Topics on Software Engineering
Software Reviews.
CS 426 CS 791z Topics on Software Engineering
Why Are Documented Requirements Important?
Presentation transcript:

SOFTWARE REQUIREMENT SPECIFICATION Chapter 10 SOFTWARE REQUIREMENT SPECIFICATION

Software requirement specification (srs) Is a complete description of the behaviour of the system to be developed. Includes a set of use cases that describes the interaction that the user will have with the software. Use cases = functional requirement. SRS also has non functional requirements (supplementary) included which impose constraints on the design. Ie, quality standards

Benefits of srs Establish the basis for agreement between the customers & the suppliers on what the software product is to do. Reduce the development effort Provide a basis for estimating costs & schedules Provide a baseline for validation & verification Facilitate transfer Serve as a basis for enhancement

Characteristics of a good srs SRS should be; Correct Unambiguous Complete Consistent Ranked for importance & stability Verifiable Modifiable Traceable

Characteristics of a good srs Correct – keep the specification up to date when you find things that are not correct. Unambiguous – every requirement stated has only one interpretation, so fix as soon as you find it. Complete – complete software is the final result Consistent – consistent when you use a word referring to one meaning, don’t keep changing Ranked for importance – some may have marketing value to it. Verifiable – provide a quantitative requirement that gives clear ideas.

Characteristics of a good srs Modifiable – should be able to be modified where ever necessary Traceable – should be traceable.