Requirements Engineering Lecture 6

Slides:



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

RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
Requirements Engineering Copyright, 1999 © Jerzy R. Nawrocki Jerzy Nawrocki Personal Software Process Lecture 2.
S R S S ystem R equirements S pecification Specifying the Specifications.
Lecture 18: Specifications
RequisitePro (2) Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
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.
DiscussionsDiscussions Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
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.
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
Requirements Engineering How do we keep straight what we are supposed to be building?
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Quality Model for Requirements Eng. Copyright, 2002 © Jerzy R. Nawrocki Quality.
Standard SRS Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
소프트웨어공학 강좌 1 Chap 4. Software Requirements - Descriptions and specifications of a system - Soo-Mi Choi
Software Requirements Engineering CSE 305 Lecture-2.
Requirements Verification & Validation Requirements Engineering & Project Management.
Software Engineering – University of Tampere, CS DepartmentJyrki Nummenmaa REQUIREMENT SPECIFICATION Today: Requirements Specification.
Good Practices of Requirements Eng. Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Requirements Documentation CSCI 5801: Software Engineering.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Lecture 7: Requirements Engineering
Quality of Usage Scenarios Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Introduction to Requirements Engineering Copyright, 2000 © Jerzy R. Nawrocki Requirements.
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
SOFTWARE REQUIREMENT ANALYSIS AND SPECIFICATION. What is a requirement? It may range from a high-level abstract statement of a service or of a system.
1 Quality Attributes of Requirements Documents Lecture # 25.
RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
OHTO -01 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it.
Requirements Specification Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Configuration Management at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Quality Model for RE Process Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
DiscussionsDiscussions Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
System Requirements Specification
Introduction to Quality Management Copyright, 2000 © Jerzy R. Nawrocki Quality.
Configuration Management (II) Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Requirements Analysis
Software Engineering Lecture 10: System Engineering.
Requirements Management and Changes Copyright, 2003 © Jerzy R. Nawrocki Requirements.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
 System Requirement Specification and System Planning.
Daniel Amyot, University of Ottawa Based on slides by Gunter Mussbacher (2009) and Stéphane Somé (2008) with material from these standards: IEEE ,
Requirements Engineering Lecture 13
Requirements Engineering Lecture 4
Requirements Engineering Lecture 2
Requirements Validation – II
Requirements Engineering (continued)
Software Requirements
Requirements Elicitation – 1
Introduction to PRINCE 2
System Requirements Specification
Requirements Analysis
Software Requirements Specification Document
Software Requirements Specification (SRS) Template.
Requirements Document
A partially automated class scheduling system
Requirement Analysis.
Presentation transcript:

Requirements Engineering Lecture 6 Jerzy Nawrocki Requirements Engineering Lecture 6 Standard SRS Jerzy.Nawrocki@put.poznan.pl www.cs.put.poznan.pl/jnawrocki/mse/require/ Copyright, 2000 © Jerzy R. Nawrocki Requirements Eng., Lecture 6

J. Nawrocki, Requirements Eng., Lecture 6 Plan of the lecture Introduction Requirements document Good practices in describing requirements Use scenarios J. Nawrocki, Requirements Eng., Lecture 6

Computer-based systems Jerzy Nawrocki Computer-based systems Software Hardware People Database Documentation Procedures J. Nawrocki, Requirements Eng., Lecture 6 Requirements Eng., Lecture 6

J. Nawrocki, Requirements Eng., Lecture 6 Restraining factors Assumptions Simplifications Limitations Constraints Preferences J. Nawrocki, Requirements Eng., Lecture 6

J. Nawrocki, Requirements Eng., Lecture 6 A good SRS Unambiguous (one interpretation) Verifiable (one can check that req. are met) Complete (responses to invalid input) Consistent (no conflicts between req.) Modifiable (changes are not a big problem) Traceable (origin of each req. is clear) Usable during the Operation and Maintenance Phase J. Nawrocki, Requirements Eng., Lecture 6

Source Documents for Requir’s SRS SRS Ver. n+1 Manual Ver. n J. Nawrocki, Requirements Eng., Lecture 6

Source Documents for Requir’s SD4R: Source document for requirements Types of SD4R: Email Video File Audio Hard(copy) . . . Advice: Try to keep all the SD4Rs as text files J. Nawrocki, Requirements Eng., Lecture 6

Requirements document (1) 1. Introduction 1.1 Purpose of the document 1.2 Scope of the product 1.3 Definitions, acronyms and abbreviations 1.4 References 1.5 Overview of the document J. Nawrocki, Requirements Eng., Lecture 6

Requirements document (2) 2. General description 2.1 Product perspective 2.2 Viewpoints 2.2.1 Stakeholders 2.2.2 Users 2.2.3 Domain 2.2.4 Components 2.3 System architecture and use cases in UML 2.4 General constraints 2.5 Assumptions and dependencies J. Nawrocki, Requirements Eng., Lecture 6

Requirements document (3) 3. Technical requirements 3.1 Functional requirements 3.1.1 Requirement 1 3.1.1.1 Introduction Viewpoint and source(s) Firmness and importance Verifiability and clarity 3.1.1.2 Inputs 3.1.1.3 Processing 3.1.1.4 Outputs J. Nawrocki, Requirements Eng., Lecture 6

Requirements document (4) . . 3.2 External interface requirements 3.2.1 User interfaces 3.2.2 Hardware interfaces 3.2.3 Software interfaces 3.2.4 Communication interfaces 3.3 Performance requirements J. Nawrocki, Requirements Eng., Lecture 6

Requirements document (5) 3.4 Design constraints 3.4.1 Standards compliance 3.4.2 Hardware limitations . . . 3.5 Attributes 3.5.1 Security 3.5.2 Maintainability J. Nawrocki, Requirements Eng., Lecture 6

Requirements document (6) 3.6 Other requirements 3.6.1 Database 3.6.2 Operations 3.6.3 Site adaptation 3.6.4 Training . . . 3.7 Non-technical requirements Appendixes Index J. Nawrocki, Requirements Eng., Lecture 6

Davis’ Principles for RE Understand the problem before you begin to create the analysis model Develop prototypes showing how the human-machine interaction will occur Record the origin of and the reason for every requirement Use multiple views of requirements (data, functional, and behavioural) Prioritise requirements Work to eliminate ambiguity J. Nawrocki, Requirements Eng., Lecture 6

J. Nawrocki, Requirements Eng., Lecture 6 Jerzy Nawrocki Further readings IEEE Guide to Software Requirements specification, ANSI/IEEE Standard 830-1984 I. Sommerville, P. Sawyer, Requirements Engineering, John Wiley & Sons, Chichester, 1997  J. Nawrocki, Requirements Eng., Lecture 6 Requirements Eng., Lecture 6

J. Nawrocki, Requirements Eng., Lecture 6 Jerzy Nawrocki Homework Write SRS for a personal library system. J. Nawrocki, Requirements Eng., Lecture 6 Requirements Eng., Lecture 6

J. Nawrocki, Requirements Eng., Lecture 6 Quality assessment 1. What is your general impression? (1 - 6) 2. Was it too slow or too fast? 3. What important did you learn during the lecture? 4. What to improve and how? J. Nawrocki, Requirements Eng., Lecture 6