CEN 5035, Software Engineering

Slides:



Advertisements
Similar presentations
CS 411W - Notes Product Development Documentation.
Advertisements

Informatics 43 – April 16, Homework 1 What is the purpose and goal of each section in the document? Two audiences: non-technical users and technical.
VCE IT Theory Slideshows By Mark Kelly Vceit.com Software Requirements specifications (SRS)
Web Order Software Requirements Specification. Purpose This Software Requirement Specification provides a complete description of all the functions, constraints.
0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
A summary of the PSS-05 URD template
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
L/O/G/O Prepared By Abdullah Mustafa Abu Nada Hussian Abd-Jaleel Shaalan Nael Wael Skaik Supervised By.
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: IEEE Standard, Daniel Amyot.
Software Requirement Specification(SRS)
Requirements Engineering
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 1 Requirements Analysis Document Template 1.Introduction.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
SOFTWARE REQUIREMENTS SPECIFICATION (SRS)
S/W Project Management
CS 4310: Software Engineering Lecture 3 Requirements and Design.
Software Requirements Specification (SRS) Complete description of external behavior of software system Complete description of external behavior.
Typical Software Documents with an emphasis on writing proposals.
Software Engineering 2003 Jyrki Nummenmaa 1 REQUIREMENT SPECIFICATION Today: Requirements Specification Requirements tell us what the system should.
Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
1 Lecture 5.2.b: Requirements Specifications (IEEE 830) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Standard SRS Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture.
Software Requirements Engineering CSE 305 Lecture-2.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa REQUIREMENT SPECIFICATION Today: Requirements Specification.
Some Sub-Activities within Requirements Engineering 1.Prototyping 2.Requirements Documentation 3.Requirements Validation 4.Requirements Measurements 5.Requirements.
Requirements Engineering ments_analysis.
Requirements Documentation CSCI 5801: Software Engineering.
VCE IT Theory Slideshows By Mark Kelly McKinnon Secondary College Vceit.com Software Requirements specifications (SRS)
Lecture 7: Requirements Engineering
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
Requirement Handling
System Context and Domain Analysis Abbas Rasoolzadegan.
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.
CONTENTS OF THE SRS REPORT. Software Requirements Specification (SRS) template The SRS document describes recommended approaches for the specification.
OHTO -01 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Requirements Engineering ments_analysis.
Software Requirements Specification Document (SRS)
ITEC 370 Lecture 6 Requirements. Review Requirements –What are some of the stages of the requirements gathering process? –What is the end result of this.
1 SUMS Requirements Spot universal mote system Team Awesome.
Daniel Amyot, University of Ottawa Based on slides by Gunter Mussbacher (2009) and Stéphane Somé (2008) with material from these standards: IEEE ,
Requirements Specification with the IEEE 830 and IEEE Standards
Software Quality Control and Quality Assurance: Introduction
Classifications of Software Requirements
Chapter 4 – Requirements Engineering
Requirements specifications
Requirements Engineering (continued)
SYSTEM ANALYSIS AND DESIGN
SE and SSE Trade-Off Analyses
IT Roles and Responsibilities
CSC480 Software Engineering
System Requirements Specification
Requirements Specification with the IEEE Standard
Introduction to Policies and Procedures Toolkit
Software Requirements Specification Document
Software Requirements Specification (SRS) Template.
Engineering Processes
Requirements Specification with the IEEE Standard
Requirements Document
<Project Title>
Requirement Analysis.
Applied Software Project Management
Requirements Engineering Lecture 6
Joint Application Development (JAD)
SRS : Software Requirement Specification. How to Write a Software Requirements Specification (SRS Document)  A software requirements specification (SRS)
Presentation transcript:

CEN 5035, Software Engineering Software Requirement Specification Template Discussion 1

What is SRS ? Organization's understanding of a customer or potential client's system requirements and dependencies at a particular point in time (usually) prior to any actual design or development work. a two-way insurance policy that assures that both the client and the organization understand the other's requirements 2

Introduction 1.1 Purpose 1.2 Document conventions 1.3 Intended audience 1.4 Project Scope & Additional information 1.5 Contact information/SRS team members 1.6 References 3

Overall Description 2.1 Product perspective 2.2 Product functions & features 2.3 User classes and characteristics 2.4 Operating environment 2.5 User environment 2.6 Design/implementation constraints 2.7 User Documentation 2.8 Assumptions and dependencies 4

External Interface Requirements 3.1 User interfaces 3.2 Hardware interfaces 3.3 Software interfaces 3.4 Communication protocols and interfaces 5

System Features 4.1 System feature A 4.2 System feature B 4.1.1 Description and priority 4.1.2 Action/result 4.1.3 Functional requirements 4.2 System feature B 6

Nonfunctional Requirements 5.1 Performance requirements 5.2 Safety requirements 5.3 Security requirements 5.4 Software quality attributes 5.5 Project documentation 5.6 User documentation 7

Other Requirements Appendix A: Terminology/Glossary/Definitions list Appendix B: To be determined, Issues etc. 8