SlideShare a Scribd company logo
1 of 18
Gregor v. Bochmann, University of Ottawa
Based on Powerpoint slides by Gunter Mussbacher (2009)
with material from:
IEEE 830-1998 Standard,
Daniel Amyot 2008, Stéphane Somé 2008
Requirements Specification with
the IEEE 830 Standard
DRAFT
SEG3101 (Fall 2010)
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
2
Table of Contents
• Requirements Specification Document
• IEEE 830 Standard
• Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
3
Requirements Specification Document (1)
• Clearly and accurately describes each of the essential
requirements (functions, performance, design constraints,
and quality attributes) of the system / software and its
external interfaces
• Defines the scope and boundaries of the system / software
• Each requirement must be described in such a way that it is
feasible and objectively verifiable by a prescribed method
(e.g., by inspection, demonstration, analysis, or test)
• Basis for contractual agreements between contractors or
suppliers and customers
• Elaborated from elicitation notes
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
4
Requirements Specification Document (2)
• Specifications are intended to a diverse audience
• Customers and users for validation, contract, ...
• Systems (requirements) analysts
• Developers, programmers to implement the system
• Testers to check that the requirements have been met
• Project Managers to measure and control the project
• Different levels of detail and formality is needed for each
audience
• Different templates for requirements specifications
• e.g. IEEE 830
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
5
Example Specification (1)
• When the switch lever is moved down, then, within 0.1
seconds, the lamp illuminates.
• When the switch lever is moved up, then, within 0.2 seconds,
Appearance
12 cm
lamp
switch
lever
Causal
relationship
OutputInput Timing
relationship
Source: Bray 2004
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
6
Example Specification (2)
• Extract from the requirements specification
• R1: The system shall provide illumination of at least 500 candela.
• R2: The system shall fit within a cube with maximum width of 15cm.
• R3: The illumination can be switched on and off by a human operator.
• R4: The system shall respond to operator input within 0.5 seconds.
• R5: The system shall have a built-in power supply which should be
capable of maintaining continuous illumination for at least 4 hours.
• etc . . . . . . .
• Several alternative designs could satisfy these requirements
Source: Bray 2004
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
7
IEEE 830-1998 Standard
• Title of Standard
• « IEEE Recommended Practice for Software Requirements
Specifications »
• Describes the content and qualities of a good software
requirements specification (SRS)
• Presents several sample SRS outlines
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
8
IEEE 830-1998 Standard – Objectives
• Help software customers to accurately describe what they
wish to obtain
• Help software suppliers to understand exactly what the
customer wants
• Help participants to:
• Develop a template (format and content) for the software requirements
specification (SRS) in their own organizations
• Develop additional documents such as SRS quality checklists or an
SRS writer’s handbook
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
9
IEEE 830-1998 Standard – Benefits
• Establish the basis for agreement between the customers
and the suppliers on what the software product is to do
• Reduce the development effort
• Forced to consider requirements early  reduces later redesign,
recoding, retesting
• Provide a basis for realistic estimates of costs and schedules
• Provide a basis for validation and verification
• Facilitate transfer of the software product to new users or
new machines
• Serve as a basis for enhancement requests
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
10
IEEE 830-1998 Standard – Considerations
• Section 4 of IEEE 830 (how to produce a good SRS)
• Nature (goals) of SRS
• Functionality, interfaces, performance, qualities, design constraints
• Environment of the SRS
• Where does it fit in the overall project hierarchy
• Characteristics of a good SRS
• Generalization of the characteristics of good requirements to the document
• Evolution of the SRS
• Implies a change management process
• Prototyping
• Helps elicit software requirements and reach closure on the SRS
• Including design and project requirements in the SRS
• Focus on external behavior and the product, not the design and the
production process (describe in a separate document)
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
11
IEEE 830-1998 Standard – Structure of the SRS
• Section 5 of IEEE 830
• Contents of SRS
• Introduction
• General description of the software product
• Specific requirements (detailed)
• Additional information such as appendixes and index, if necessary
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
• Title
• Table of Contents
• 1. Introduction
• 1.1 Purpose
• 1.2 Scope
• 1.3 Definitions. Acronyms, and Abbreviations
• 1.4 References
• 1.5 Overview
• 2. Overall Description
• 3. Specific Requirements
• Appendices
• Index
IEEE 830-1998 Standard – Section 1 of SRS
•Describe purpose of this SRS
•Describe intended audience
•Identify the software product
•Enumerate what the system will and will not do
•Describe user classes and benefits for each
•Define the vocabulary of the SRS
(may reference appendix)
•List all referenced documents including sources
(e.g., Use Case Model and Problem Statement;
Experts in the field)
•Describe the content of the rest of the SRS
•Describe how the SRS is organized
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
IEEE 830-1998 Standard – Section 2 of SRS
• Title
• Table of Contents
• 1. Introduction
• 2. Overall Description
• 2.1 Product Perspective
• 2.2 Product Functions
• 2.3 User Characteristics
• 2.4 Constraints
• 2.5 Assumptions and Dependencies
• 3. Specific Requirements
• 4. Appendices
• 5. Index
•Present the business case and operational concept of the system
•Describe how the proposed system fits into the business context
•Describe external interfaces: system, user, hardware, software, communication
•Describe constraints: memory, operational, site adaptation
•Describe and justify technical skills
and capabilities of each user class
•Summarize the major functional capabilities
•Include the Use Case Diagram and supporting narrative
(identify actors and use cases)
•Include Data Flow Diagram if appropriate
•Describe other constraints that will limit developer’s
options; e.g., regulatory policies; target platform,
database, network software and protocols, development
standards requirements
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
IEEE 830-1998 Standard – Section 3 of SRS (1)
• …
• 1. Introduction
• 2. Overall Description
• 3. Specific Requirements
• 3.1 External Interfaces
• 3.2 Functions
• 3.3 Performance Requirements
• 3.4 Logical Database Requirements
• 3.5 Design Constraints
• 3.6 Software System Quality Attributes
• 3.7 Object Oriented Models
• 4. Appendices
• 5. Index
Specify software requirements in sufficient
detail to enable designers to design a system to satisfy
those requirements and testers to verify
requirements
State requirements that are externally perceivable by
users, operators, or externally connected systems
Requirements should include, at a minimum, a
description of every input (stimulus) into the system,
every output (response) from the system, and all
functions performed by the system in response to an
input or in support of an output
(a) Requirements should have characteristics of
high quality requirements
(b) Requirements should be cross-referenced to
their source.
(c) Requirements should be uniquely identifiable
(d) Requirements should be organized to
maximize readability
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
• …
• 1. Introduction
• 2. Overall Description
• 3. Specific Requirements
• 3.1 External Interfaces
• 3.2 Functions
• 3.3 Performance Requirements
• 3.4 Logical Database Requirements
• 3.5 Design Constraints
• 3.6 Software System Quality Attributes
• 3.7 Object Oriented Models
• 4. Appendices
• 5. Index
IEEE 830-1998 Standard – Section 3 of SRS (2)
•Detail all inputs and outputs
(complement, not duplicate, information presented in section 2)
•Examples: GUI screens, file formats
•Include detailed specifications of each
use case, including collaboration and
other diagrams useful for this purpose
•The main body of requirements organized in a variety of
possible ways:
a) Architecture Specification
b) Class Diagram
c) State and Collaboration Diagrams
d) Activity Diagram (concurrent/distributed)
•Include:
a) Types of information used
b) Data entities and their relationships
•Should include:
a) Standards compliance
b) Accounting & Auditing procedures
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
16
IEEE 830-1998 Standard – Templates
• Annex A of IEEE 830
• Section 3 (Specific Requirements) may be organized in many
different ways based on
• Modes
• User classes
• Concepts (object/class)
• Features
• Stimuli
• Organizations
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
17
Relationship of IEEE 830 and ISO/IEC 12207 (1)
• 12207
• Common framework for « Software life cycle processes »
• ISO/IEC 12207 = IEEE/EIA 12207
• IEEE 830-1998 and IEEE/EIA 12207.1-1997 both place
requirements on documents describing software
requirements
• Annex B of IEEE 830 explains the relationship between the
two sets of requirements for those who want to produce
documents that comply with both standards simultaneously
• Such compliance may be required by customers when
requesting proposals or issuing call for tenders
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher
18
Relationship of IEEE 830 and ISO/IEC 12207 (1)
Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207

More Related Content

What's hot

An Introduction to Software Failure Modes Effects Analysis (SFMEA)
An Introduction to Software Failure Modes Effects Analysis (SFMEA)An Introduction to Software Failure Modes Effects Analysis (SFMEA)
An Introduction to Software Failure Modes Effects Analysis (SFMEA)Ann Marie Neufelder
 
SDLC or Software Development Life Cycle
SDLC or Software Development Life CycleSDLC or Software Development Life Cycle
SDLC or Software Development Life CycleJyothi Vbs
 
SRS(software requirement specification)
SRS(software requirement specification)SRS(software requirement specification)
SRS(software requirement specification)Akash Kumar Dhameja
 
Configuration Management
Configuration ManagementConfiguration Management
Configuration ManagementSaqib Raza
 
Software Engineering Diversity
Software Engineering DiversitySoftware Engineering Diversity
Software Engineering DiversitySayedMokarrom
 
SE CHAPTER 2 PROCESS MODELS
SE CHAPTER 2 PROCESS MODELSSE CHAPTER 2 PROCESS MODELS
SE CHAPTER 2 PROCESS MODELSAbrar ali
 
IT8076 - SOFTWARE TESTING
IT8076 - SOFTWARE TESTINGIT8076 - SOFTWARE TESTING
IT8076 - SOFTWARE TESTINGSathya R
 
IGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docx
IGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docxIGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docx
IGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docxAnilVhatkar
 
Unified process model
Unified process modelUnified process model
Unified process modelRyndaMaala
 
SDLC RAD model
SDLC RAD modelSDLC RAD model
SDLC RAD modelJay Sharma
 
Automotive architecture examples with EAST-ADL models
Automotive architecture examples with EAST-ADL modelsAutomotive architecture examples with EAST-ADL models
Automotive architecture examples with EAST-ADL modelsJuha-Pekka Tolvanen
 
Complete dbms notes
Complete dbms notesComplete dbms notes
Complete dbms notesTanya Makkar
 
Service Oriented Architecture (SOA) [1/5] : Introduction to SOA
Service Oriented Architecture (SOA) [1/5] : Introduction to SOAService Oriented Architecture (SOA) [1/5] : Introduction to SOA
Service Oriented Architecture (SOA) [1/5] : Introduction to SOAIMC Institute
 
Spring vs java ee
Spring vs java eeSpring vs java ee
Spring vs java eeWalid Yaich
 

What's hot (20)

An Introduction to Software Failure Modes Effects Analysis (SFMEA)
An Introduction to Software Failure Modes Effects Analysis (SFMEA)An Introduction to Software Failure Modes Effects Analysis (SFMEA)
An Introduction to Software Failure Modes Effects Analysis (SFMEA)
 
SDLC or Software Development Life Cycle
SDLC or Software Development Life CycleSDLC or Software Development Life Cycle
SDLC or Software Development Life Cycle
 
Domain Modeling
Domain ModelingDomain Modeling
Domain Modeling
 
SRS(software requirement specification)
SRS(software requirement specification)SRS(software requirement specification)
SRS(software requirement specification)
 
Configuration Management
Configuration ManagementConfiguration Management
Configuration Management
 
software characteristics
software characteristicssoftware characteristics
software characteristics
 
Software Engineering Diversity
Software Engineering DiversitySoftware Engineering Diversity
Software Engineering Diversity
 
SE CHAPTER 2 PROCESS MODELS
SE CHAPTER 2 PROCESS MODELSSE CHAPTER 2 PROCESS MODELS
SE CHAPTER 2 PROCESS MODELS
 
IT8076 - SOFTWARE TESTING
IT8076 - SOFTWARE TESTINGIT8076 - SOFTWARE TESTING
IT8076 - SOFTWARE TESTING
 
Component based software engineering
Component based software engineeringComponent based software engineering
Component based software engineering
 
IGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docx
IGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docxIGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docx
IGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docx
 
Unified process model
Unified process modelUnified process model
Unified process model
 
SDLC RAD model
SDLC RAD modelSDLC RAD model
SDLC RAD model
 
Automotive architecture examples with EAST-ADL models
Automotive architecture examples with EAST-ADL modelsAutomotive architecture examples with EAST-ADL models
Automotive architecture examples with EAST-ADL models
 
Rad model
Rad modelRad model
Rad model
 
Complete dbms notes
Complete dbms notesComplete dbms notes
Complete dbms notes
 
Service Oriented Architecture (SOA) [1/5] : Introduction to SOA
Service Oriented Architecture (SOA) [1/5] : Introduction to SOAService Oriented Architecture (SOA) [1/5] : Introduction to SOA
Service Oriented Architecture (SOA) [1/5] : Introduction to SOA
 
Software requirements
Software requirementsSoftware requirements
Software requirements
 
Unified process Model
Unified process ModelUnified process Model
Unified process Model
 
Spring vs java ee
Spring vs java eeSpring vs java ee
Spring vs java ee
 

Viewers also liked

L 02 industrial management
L 02 industrial managementL 02 industrial management
L 02 industrial managementTanya Mathur
 
Software requirements Specification
Software requirements SpecificationSoftware requirements Specification
Software requirements SpecificationPreshan Pradeepa
 
Software Requirement Specification
Software Requirement SpecificationSoftware Requirement Specification
Software Requirement SpecificationVishal Singh
 
SRS on Online Blood Bank Managment system...
SRS on Online Blood Bank Managment system... SRS on Online Blood Bank Managment system...
SRS on Online Blood Bank Managment system... GCWUF
 
Software requirements specification
Software  requirements specificationSoftware  requirements specification
Software requirements specificationKrishnasai Gudavalli
 

Viewers also liked (6)

L 02 industrial management
L 02 industrial managementL 02 industrial management
L 02 industrial management
 
Ieee 830 srs
Ieee 830 srsIeee 830 srs
Ieee 830 srs
 
Software requirements Specification
Software requirements SpecificationSoftware requirements Specification
Software requirements Specification
 
Software Requirement Specification
Software Requirement SpecificationSoftware Requirement Specification
Software Requirement Specification
 
SRS on Online Blood Bank Managment system...
SRS on Online Blood Bank Managment system... SRS on Online Blood Bank Managment system...
SRS on Online Blood Bank Managment system...
 
Software requirements specification
Software  requirements specificationSoftware  requirements specification
Software requirements specification
 

Similar to Requirements documentation standards ieee830

<a>clicks</a>
<a>clicks</a><a>clicks</a>
<a>clicks</a>Testing32122
 
SEG3101-p2-Specification (1).pptx
SEG3101-p2-Specification (1).pptxSEG3101-p2-Specification (1).pptx
SEG3101-p2-Specification (1).pptxAdvantumConsulting
 
04IEEEPTPpresentation.pdf
04IEEEPTPpresentation.pdf04IEEEPTPpresentation.pdf
04IEEEPTPpresentation.pdfewnetukassa2
 
Requirements Engineering - "Ch2 an introduction to requirements"
Requirements Engineering - "Ch2 an introduction to requirements"Requirements Engineering - "Ch2 an introduction to requirements"
Requirements Engineering - "Ch2 an introduction to requirements"Ra'Fat Al-Msie'deen
 
W4 lecture 7&8 - requirements gathering
W4 lecture 7&8 - requirements gatheringW4 lecture 7&8 - requirements gathering
W4 lecture 7&8 - requirements gatheringFareeha Iftikhar
 
Mobile Broadband Wireless Access
Mobile Broadband Wireless AccessMobile Broadband Wireless Access
Mobile Broadband Wireless AccessBirju Tank
 
L02_RequirementEngineering.ppsx
L02_RequirementEngineering.ppsxL02_RequirementEngineering.ppsx
L02_RequirementEngineering.ppsxVijayAgrahari3
 
IJSRED-V2I3P91
IJSRED-V2I3P91IJSRED-V2I3P91
IJSRED-V2I3P91IJSRED
 
IJSRED-V2I3P91
IJSRED-V2I3P91IJSRED-V2I3P91
IJSRED-V2I3P91IJSRED
 
the-ieee-8021-standards.pptx
the-ieee-8021-standards.pptxthe-ieee-8021-standards.pptx
the-ieee-8021-standards.pptxCMWason
 
Sw Requirements Engineering
Sw Requirements EngineeringSw Requirements Engineering
Sw Requirements Engineeringjonathan077070
 
Fpga asic technologies_flow
Fpga asic technologies_flowFpga asic technologies_flow
Fpga asic technologies_flowravi4all
 
DI-EMCS - Contro procedures, test procedures e test report
DI-EMCS - Contro procedures, test procedures e test reportDI-EMCS - Contro procedures, test procedures e test report
DI-EMCS - Contro procedures, test procedures e test reportAlessandro Corniani
 

Similar to Requirements documentation standards ieee830 (20)

<a>clicks</a>
<a>clicks</a><a>clicks</a>
<a>clicks</a>
 
SEG3101-ch1-IEEE830.pptx
SEG3101-ch1-IEEE830.pptxSEG3101-ch1-IEEE830.pptx
SEG3101-ch1-IEEE830.pptx
 
SEG3101-p2-Specification (1).pptx
SEG3101-p2-Specification (1).pptxSEG3101-p2-Specification (1).pptx
SEG3101-p2-Specification (1).pptx
 
SEG3101-p2-Specification.pptx
SEG3101-p2-Specification.pptxSEG3101-p2-Specification.pptx
SEG3101-p2-Specification.pptx
 
04IEEEPTPpresentation.pdf
04IEEEPTPpresentation.pdf04IEEEPTPpresentation.pdf
04IEEEPTPpresentation.pdf
 
Requirements Engineering - "Ch2 an introduction to requirements"
Requirements Engineering - "Ch2 an introduction to requirements"Requirements Engineering - "Ch2 an introduction to requirements"
Requirements Engineering - "Ch2 an introduction to requirements"
 
GT STRUDL
GT STRUDLGT STRUDL
GT STRUDL
 
W4 lecture 7&8 - requirements gathering
W4 lecture 7&8 - requirements gatheringW4 lecture 7&8 - requirements gathering
W4 lecture 7&8 - requirements gathering
 
Mobile Broadband Wireless Access
Mobile Broadband Wireless AccessMobile Broadband Wireless Access
Mobile Broadband Wireless Access
 
Unit II- Hardware design & testing methods1 - Electronic Product Design
Unit II- Hardware design & testing methods1 - Electronic Product DesignUnit II- Hardware design & testing methods1 - Electronic Product Design
Unit II- Hardware design & testing methods1 - Electronic Product Design
 
TANK
TANKTANK
TANK
 
L02_RequirementEngineering.ppsx
L02_RequirementEngineering.ppsxL02_RequirementEngineering.ppsx
L02_RequirementEngineering.ppsx
 
IJSRED-V2I3P91
IJSRED-V2I3P91IJSRED-V2I3P91
IJSRED-V2I3P91
 
IJSRED-V2I3P91
IJSRED-V2I3P91IJSRED-V2I3P91
IJSRED-V2I3P91
 
Chap1 RE Introduction
Chap1 RE IntroductionChap1 RE Introduction
Chap1 RE Introduction
 
the-ieee-8021-standards.pptx
the-ieee-8021-standards.pptxthe-ieee-8021-standards.pptx
the-ieee-8021-standards.pptx
 
Sw Requirements Engineering
Sw Requirements EngineeringSw Requirements Engineering
Sw Requirements Engineering
 
Wireless Sensor Network
Wireless Sensor NetworkWireless Sensor Network
Wireless Sensor Network
 
Fpga asic technologies_flow
Fpga asic technologies_flowFpga asic technologies_flow
Fpga asic technologies_flow
 
DI-EMCS - Contro procedures, test procedures e test report
DI-EMCS - Contro procedures, test procedures e test reportDI-EMCS - Contro procedures, test procedures e test report
DI-EMCS - Contro procedures, test procedures e test report
 

More from Abdul Basit

Atlassian git cheatsheet
Atlassian git cheatsheetAtlassian git cheatsheet
Atlassian git cheatsheetAbdul Basit
 
Github git-cheat-sheet
Github git-cheat-sheetGithub git-cheat-sheet
Github git-cheat-sheetAbdul Basit
 
White box testing
White box testingWhite box testing
White box testingAbdul Basit
 
Testing the documentation
Testing the documentationTesting the documentation
Testing the documentationAbdul Basit
 
Testing software security
Testing software securityTesting software security
Testing software securityAbdul Basit
 
Testing fundamentals
Testing fundamentalsTesting fundamentals
Testing fundamentalsAbdul Basit
 
Test cases planning
Test cases planningTest cases planning
Test cases planningAbdul Basit
 
Software Testing
Software TestingSoftware Testing
Software TestingAbdul Basit
 
Software Compatibility testing
Software Compatibility testingSoftware Compatibility testing
Software Compatibility testingAbdul Basit
 
Black box testing
Black box testingBlack box testing
Black box testingAbdul Basit
 
Software Automated testing and tools
Software Automated testing and toolsSoftware Automated testing and tools
Software Automated testing and toolsAbdul Basit
 
Why test software
Why test softwareWhy test software
Why test softwareAbdul Basit
 
Git Developer Cheatsheet
Git Developer CheatsheetGit Developer Cheatsheet
Git Developer CheatsheetAbdul Basit
 
Static white box testing lecture 12
Static white box testing lecture 12Static white box testing lecture 12
Static white box testing lecture 12Abdul Basit
 
Software testing lecture 10
Software testing lecture 10Software testing lecture 10
Software testing lecture 10Abdul Basit
 
Software testing lecture 9
Software testing lecture 9Software testing lecture 9
Software testing lecture 9Abdul Basit
 
Software quality assurance lecture 1
Software quality assurance lecture 1Software quality assurance lecture 1
Software quality assurance lecture 1Abdul Basit
 
Software measurement lecture 7
Software measurement lecture 7Software measurement lecture 7
Software measurement lecture 7Abdul Basit
 

More from Abdul Basit (20)

Atlassian git cheatsheet
Atlassian git cheatsheetAtlassian git cheatsheet
Atlassian git cheatsheet
 
Github git-cheat-sheet
Github git-cheat-sheetGithub git-cheat-sheet
Github git-cheat-sheet
 
White box testing
White box testingWhite box testing
White box testing
 
Web testing
Web testingWeb testing
Web testing
 
Testing the documentation
Testing the documentationTesting the documentation
Testing the documentation
 
Testing software security
Testing software securityTesting software security
Testing software security
 
Testing fundamentals
Testing fundamentalsTesting fundamentals
Testing fundamentals
 
Test planning
Test planningTest planning
Test planning
 
Test cases planning
Test cases planningTest cases planning
Test cases planning
 
Software Testing
Software TestingSoftware Testing
Software Testing
 
Software Compatibility testing
Software Compatibility testingSoftware Compatibility testing
Software Compatibility testing
 
Black box testing
Black box testingBlack box testing
Black box testing
 
Software Automated testing and tools
Software Automated testing and toolsSoftware Automated testing and tools
Software Automated testing and tools
 
Why test software
Why test softwareWhy test software
Why test software
 
Git Developer Cheatsheet
Git Developer CheatsheetGit Developer Cheatsheet
Git Developer Cheatsheet
 
Static white box testing lecture 12
Static white box testing lecture 12Static white box testing lecture 12
Static white box testing lecture 12
 
Software testing lecture 10
Software testing lecture 10Software testing lecture 10
Software testing lecture 10
 
Software testing lecture 9
Software testing lecture 9Software testing lecture 9
Software testing lecture 9
 
Software quality assurance lecture 1
Software quality assurance lecture 1Software quality assurance lecture 1
Software quality assurance lecture 1
 
Software measurement lecture 7
Software measurement lecture 7Software measurement lecture 7
Software measurement lecture 7
 

Recently uploaded

The basics of sentences session 3pptx.pptx
The basics of sentences session 3pptx.pptxThe basics of sentences session 3pptx.pptx
The basics of sentences session 3pptx.pptxheathfieldcps1
 
On_Translating_a_Tamil_Poem_by_A_K_Ramanujan.pptx
On_Translating_a_Tamil_Poem_by_A_K_Ramanujan.pptxOn_Translating_a_Tamil_Poem_by_A_K_Ramanujan.pptx
On_Translating_a_Tamil_Poem_by_A_K_Ramanujan.pptxPooja Bhuva
 
This PowerPoint helps students to consider the concept of infinity.
This PowerPoint helps students to consider the concept of infinity.This PowerPoint helps students to consider the concept of infinity.
This PowerPoint helps students to consider the concept of infinity.christianmathematics
 
Basic Intentional Injuries Health Education
Basic Intentional Injuries Health EducationBasic Intentional Injuries Health Education
Basic Intentional Injuries Health EducationNeilDeclaro1
 
How to Add New Custom Addons Path in Odoo 17
How to Add New Custom Addons Path in Odoo 17How to Add New Custom Addons Path in Odoo 17
How to Add New Custom Addons Path in Odoo 17Celine George
 
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdf
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdfUnit 3 Emotional Intelligence and Spiritual Intelligence.pdf
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdfDr Vijay Vishwakarma
 
Philosophy of china and it's charactistics
Philosophy of china and it's charactisticsPhilosophy of china and it's charactistics
Philosophy of china and it's charactisticshameyhk98
 
21st_Century_Skills_Framework_Final_Presentation_2.pptx
21st_Century_Skills_Framework_Final_Presentation_2.pptx21st_Century_Skills_Framework_Final_Presentation_2.pptx
21st_Century_Skills_Framework_Final_Presentation_2.pptxJoelynRubio1
 
General Principles of Intellectual Property: Concepts of Intellectual Proper...
General Principles of Intellectual Property: Concepts of Intellectual  Proper...General Principles of Intellectual Property: Concepts of Intellectual  Proper...
General Principles of Intellectual Property: Concepts of Intellectual Proper...Poonam Aher Patil
 
Jamworks pilot and AI at Jisc (20/03/2024)
Jamworks pilot and AI at Jisc (20/03/2024)Jamworks pilot and AI at Jisc (20/03/2024)
Jamworks pilot and AI at Jisc (20/03/2024)Jisc
 
Spellings Wk 4 and Wk 5 for Grade 4 at CAPS
Spellings Wk 4 and Wk 5 for Grade 4 at CAPSSpellings Wk 4 and Wk 5 for Grade 4 at CAPS
Spellings Wk 4 and Wk 5 for Grade 4 at CAPSAnaAcapella
 
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptx
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptxHMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptx
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptxmarlenawright1
 
How to Add a Tool Tip to a Field in Odoo 17
How to Add a Tool Tip to a Field in Odoo 17How to Add a Tool Tip to a Field in Odoo 17
How to Add a Tool Tip to a Field in Odoo 17Celine George
 
Beyond_Borders_Understanding_Anime_and_Manga_Fandom_A_Comprehensive_Audience_...
Beyond_Borders_Understanding_Anime_and_Manga_Fandom_A_Comprehensive_Audience_...Beyond_Borders_Understanding_Anime_and_Manga_Fandom_A_Comprehensive_Audience_...
Beyond_Borders_Understanding_Anime_and_Manga_Fandom_A_Comprehensive_Audience_...Pooja Bhuva
 
Sensory_Experience_and_Emotional_Resonance_in_Gabriel_Okaras_The_Piano_and_Th...
Sensory_Experience_and_Emotional_Resonance_in_Gabriel_Okaras_The_Piano_and_Th...Sensory_Experience_and_Emotional_Resonance_in_Gabriel_Okaras_The_Piano_and_Th...
Sensory_Experience_and_Emotional_Resonance_in_Gabriel_Okaras_The_Piano_and_Th...Pooja Bhuva
 
Wellbeing inclusion and digital dystopias.pptx
Wellbeing inclusion and digital dystopias.pptxWellbeing inclusion and digital dystopias.pptx
Wellbeing inclusion and digital dystopias.pptxJisc
 
AIM of Education-Teachers Training-2024.ppt
AIM of Education-Teachers Training-2024.pptAIM of Education-Teachers Training-2024.ppt
AIM of Education-Teachers Training-2024.pptNishitharanjan Rout
 
Python Notes for mca i year students osmania university.docx
Python Notes for mca i year students osmania university.docxPython Notes for mca i year students osmania university.docx
Python Notes for mca i year students osmania university.docxRamakrishna Reddy Bijjam
 
How to Manage Global Discount in Odoo 17 POS
How to Manage Global Discount in Odoo 17 POSHow to Manage Global Discount in Odoo 17 POS
How to Manage Global Discount in Odoo 17 POSCeline George
 
On National Teacher Day, meet the 2024-25 Kenan Fellows
On National Teacher Day, meet the 2024-25 Kenan FellowsOn National Teacher Day, meet the 2024-25 Kenan Fellows
On National Teacher Day, meet the 2024-25 Kenan FellowsMebane Rash
 

Recently uploaded (20)

The basics of sentences session 3pptx.pptx
The basics of sentences session 3pptx.pptxThe basics of sentences session 3pptx.pptx
The basics of sentences session 3pptx.pptx
 
On_Translating_a_Tamil_Poem_by_A_K_Ramanujan.pptx
On_Translating_a_Tamil_Poem_by_A_K_Ramanujan.pptxOn_Translating_a_Tamil_Poem_by_A_K_Ramanujan.pptx
On_Translating_a_Tamil_Poem_by_A_K_Ramanujan.pptx
 
This PowerPoint helps students to consider the concept of infinity.
This PowerPoint helps students to consider the concept of infinity.This PowerPoint helps students to consider the concept of infinity.
This PowerPoint helps students to consider the concept of infinity.
 
Basic Intentional Injuries Health Education
Basic Intentional Injuries Health EducationBasic Intentional Injuries Health Education
Basic Intentional Injuries Health Education
 
How to Add New Custom Addons Path in Odoo 17
How to Add New Custom Addons Path in Odoo 17How to Add New Custom Addons Path in Odoo 17
How to Add New Custom Addons Path in Odoo 17
 
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdf
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdfUnit 3 Emotional Intelligence and Spiritual Intelligence.pdf
Unit 3 Emotional Intelligence and Spiritual Intelligence.pdf
 
Philosophy of china and it's charactistics
Philosophy of china and it's charactisticsPhilosophy of china and it's charactistics
Philosophy of china and it's charactistics
 
21st_Century_Skills_Framework_Final_Presentation_2.pptx
21st_Century_Skills_Framework_Final_Presentation_2.pptx21st_Century_Skills_Framework_Final_Presentation_2.pptx
21st_Century_Skills_Framework_Final_Presentation_2.pptx
 
General Principles of Intellectual Property: Concepts of Intellectual Proper...
General Principles of Intellectual Property: Concepts of Intellectual  Proper...General Principles of Intellectual Property: Concepts of Intellectual  Proper...
General Principles of Intellectual Property: Concepts of Intellectual Proper...
 
Jamworks pilot and AI at Jisc (20/03/2024)
Jamworks pilot and AI at Jisc (20/03/2024)Jamworks pilot and AI at Jisc (20/03/2024)
Jamworks pilot and AI at Jisc (20/03/2024)
 
Spellings Wk 4 and Wk 5 for Grade 4 at CAPS
Spellings Wk 4 and Wk 5 for Grade 4 at CAPSSpellings Wk 4 and Wk 5 for Grade 4 at CAPS
Spellings Wk 4 and Wk 5 for Grade 4 at CAPS
 
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptx
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptxHMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptx
HMCS Vancouver Pre-Deployment Brief - May 2024 (Web Version).pptx
 
How to Add a Tool Tip to a Field in Odoo 17
How to Add a Tool Tip to a Field in Odoo 17How to Add a Tool Tip to a Field in Odoo 17
How to Add a Tool Tip to a Field in Odoo 17
 
Beyond_Borders_Understanding_Anime_and_Manga_Fandom_A_Comprehensive_Audience_...
Beyond_Borders_Understanding_Anime_and_Manga_Fandom_A_Comprehensive_Audience_...Beyond_Borders_Understanding_Anime_and_Manga_Fandom_A_Comprehensive_Audience_...
Beyond_Borders_Understanding_Anime_and_Manga_Fandom_A_Comprehensive_Audience_...
 
Sensory_Experience_and_Emotional_Resonance_in_Gabriel_Okaras_The_Piano_and_Th...
Sensory_Experience_and_Emotional_Resonance_in_Gabriel_Okaras_The_Piano_and_Th...Sensory_Experience_and_Emotional_Resonance_in_Gabriel_Okaras_The_Piano_and_Th...
Sensory_Experience_and_Emotional_Resonance_in_Gabriel_Okaras_The_Piano_and_Th...
 
Wellbeing inclusion and digital dystopias.pptx
Wellbeing inclusion and digital dystopias.pptxWellbeing inclusion and digital dystopias.pptx
Wellbeing inclusion and digital dystopias.pptx
 
AIM of Education-Teachers Training-2024.ppt
AIM of Education-Teachers Training-2024.pptAIM of Education-Teachers Training-2024.ppt
AIM of Education-Teachers Training-2024.ppt
 
Python Notes for mca i year students osmania university.docx
Python Notes for mca i year students osmania university.docxPython Notes for mca i year students osmania university.docx
Python Notes for mca i year students osmania university.docx
 
How to Manage Global Discount in Odoo 17 POS
How to Manage Global Discount in Odoo 17 POSHow to Manage Global Discount in Odoo 17 POS
How to Manage Global Discount in Odoo 17 POS
 
On National Teacher Day, meet the 2024-25 Kenan Fellows
On National Teacher Day, meet the 2024-25 Kenan FellowsOn National Teacher Day, meet the 2024-25 Kenan Fellows
On National Teacher Day, meet the 2024-25 Kenan Fellows
 

Requirements documentation standards ieee830

  • 1. Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: IEEE 830-1998 Standard, Daniel Amyot 2008, Stéphane Somé 2008 Requirements Specification with the IEEE 830 Standard DRAFT SEG3101 (Fall 2010)
  • 2. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 2 Table of Contents • Requirements Specification Document • IEEE 830 Standard • Relationship of IEEE 830 and ISO/IEC 12207
  • 3. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 3 Requirements Specification Document (1) • Clearly and accurately describes each of the essential requirements (functions, performance, design constraints, and quality attributes) of the system / software and its external interfaces • Defines the scope and boundaries of the system / software • Each requirement must be described in such a way that it is feasible and objectively verifiable by a prescribed method (e.g., by inspection, demonstration, analysis, or test) • Basis for contractual agreements between contractors or suppliers and customers • Elaborated from elicitation notes Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 4. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 4 Requirements Specification Document (2) • Specifications are intended to a diverse audience • Customers and users for validation, contract, ... • Systems (requirements) analysts • Developers, programmers to implement the system • Testers to check that the requirements have been met • Project Managers to measure and control the project • Different levels of detail and formality is needed for each audience • Different templates for requirements specifications • e.g. IEEE 830 Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 5. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 5 Example Specification (1) • When the switch lever is moved down, then, within 0.1 seconds, the lamp illuminates. • When the switch lever is moved up, then, within 0.2 seconds, Appearance 12 cm lamp switch lever Causal relationship OutputInput Timing relationship Source: Bray 2004 Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 6. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 6 Example Specification (2) • Extract from the requirements specification • R1: The system shall provide illumination of at least 500 candela. • R2: The system shall fit within a cube with maximum width of 15cm. • R3: The illumination can be switched on and off by a human operator. • R4: The system shall respond to operator input within 0.5 seconds. • R5: The system shall have a built-in power supply which should be capable of maintaining continuous illumination for at least 4 hours. • etc . . . . . . . • Several alternative designs could satisfy these requirements Source: Bray 2004 Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 7. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 7 IEEE 830-1998 Standard • Title of Standard • « IEEE Recommended Practice for Software Requirements Specifications » • Describes the content and qualities of a good software requirements specification (SRS) • Presents several sample SRS outlines Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 8. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 8 IEEE 830-1998 Standard – Objectives • Help software customers to accurately describe what they wish to obtain • Help software suppliers to understand exactly what the customer wants • Help participants to: • Develop a template (format and content) for the software requirements specification (SRS) in their own organizations • Develop additional documents such as SRS quality checklists or an SRS writer’s handbook Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 9. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 9 IEEE 830-1998 Standard – Benefits • Establish the basis for agreement between the customers and the suppliers on what the software product is to do • Reduce the development effort • Forced to consider requirements early  reduces later redesign, recoding, retesting • Provide a basis for realistic estimates of costs and schedules • Provide a basis for validation and verification • Facilitate transfer of the software product to new users or new machines • Serve as a basis for enhancement requests Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 10. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 10 IEEE 830-1998 Standard – Considerations • Section 4 of IEEE 830 (how to produce a good SRS) • Nature (goals) of SRS • Functionality, interfaces, performance, qualities, design constraints • Environment of the SRS • Where does it fit in the overall project hierarchy • Characteristics of a good SRS • Generalization of the characteristics of good requirements to the document • Evolution of the SRS • Implies a change management process • Prototyping • Helps elicit software requirements and reach closure on the SRS • Including design and project requirements in the SRS • Focus on external behavior and the product, not the design and the production process (describe in a separate document) Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 11. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 11 IEEE 830-1998 Standard – Structure of the SRS • Section 5 of IEEE 830 • Contents of SRS • Introduction • General description of the software product • Specific requirements (detailed) • Additional information such as appendixes and index, if necessary Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 12. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher • Title • Table of Contents • 1. Introduction • 1.1 Purpose • 1.2 Scope • 1.3 Definitions. Acronyms, and Abbreviations • 1.4 References • 1.5 Overview • 2. Overall Description • 3. Specific Requirements • Appendices • Index IEEE 830-1998 Standard – Section 1 of SRS •Describe purpose of this SRS •Describe intended audience •Identify the software product •Enumerate what the system will and will not do •Describe user classes and benefits for each •Define the vocabulary of the SRS (may reference appendix) •List all referenced documents including sources (e.g., Use Case Model and Problem Statement; Experts in the field) •Describe the content of the rest of the SRS •Describe how the SRS is organized Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 13. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher IEEE 830-1998 Standard – Section 2 of SRS • Title • Table of Contents • 1. Introduction • 2. Overall Description • 2.1 Product Perspective • 2.2 Product Functions • 2.3 User Characteristics • 2.4 Constraints • 2.5 Assumptions and Dependencies • 3. Specific Requirements • 4. Appendices • 5. Index •Present the business case and operational concept of the system •Describe how the proposed system fits into the business context •Describe external interfaces: system, user, hardware, software, communication •Describe constraints: memory, operational, site adaptation •Describe and justify technical skills and capabilities of each user class •Summarize the major functional capabilities •Include the Use Case Diagram and supporting narrative (identify actors and use cases) •Include Data Flow Diagram if appropriate •Describe other constraints that will limit developer’s options; e.g., regulatory policies; target platform, database, network software and protocols, development standards requirements Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 14. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher IEEE 830-1998 Standard – Section 3 of SRS (1) • … • 1. Introduction • 2. Overall Description • 3. Specific Requirements • 3.1 External Interfaces • 3.2 Functions • 3.3 Performance Requirements • 3.4 Logical Database Requirements • 3.5 Design Constraints • 3.6 Software System Quality Attributes • 3.7 Object Oriented Models • 4. Appendices • 5. Index Specify software requirements in sufficient detail to enable designers to design a system to satisfy those requirements and testers to verify requirements State requirements that are externally perceivable by users, operators, or externally connected systems Requirements should include, at a minimum, a description of every input (stimulus) into the system, every output (response) from the system, and all functions performed by the system in response to an input or in support of an output (a) Requirements should have characteristics of high quality requirements (b) Requirements should be cross-referenced to their source. (c) Requirements should be uniquely identifiable (d) Requirements should be organized to maximize readability Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 15. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher • … • 1. Introduction • 2. Overall Description • 3. Specific Requirements • 3.1 External Interfaces • 3.2 Functions • 3.3 Performance Requirements • 3.4 Logical Database Requirements • 3.5 Design Constraints • 3.6 Software System Quality Attributes • 3.7 Object Oriented Models • 4. Appendices • 5. Index IEEE 830-1998 Standard – Section 3 of SRS (2) •Detail all inputs and outputs (complement, not duplicate, information presented in section 2) •Examples: GUI screens, file formats •Include detailed specifications of each use case, including collaboration and other diagrams useful for this purpose •The main body of requirements organized in a variety of possible ways: a) Architecture Specification b) Class Diagram c) State and Collaboration Diagrams d) Activity Diagram (concurrent/distributed) •Include: a) Types of information used b) Data entities and their relationships •Should include: a) Standards compliance b) Accounting & Auditing procedures Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 16. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 16 IEEE 830-1998 Standard – Templates • Annex A of IEEE 830 • Section 3 (Specific Requirements) may be organized in many different ways based on • Modes • User classes • Concepts (object/class) • Features • Stimuli • Organizations Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 17. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 17 Relationship of IEEE 830 and ISO/IEC 12207 (1) • 12207 • Common framework for « Software life cycle processes » • ISO/IEC 12207 = IEEE/EIA 12207 • IEEE 830-1998 and IEEE/EIA 12207.1-1997 both place requirements on documents describing software requirements • Annex B of IEEE 830 explains the relationship between the two sets of requirements for those who want to produce documents that comply with both standards simultaneously • Such compliance may be required by customers when requesting proposals or issuing call for tenders Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207
  • 18. SEG3101 (Fall 2009). Requirements Specification with the IEEE 830 Standard. © 2009 Gunter Mussbacher 18 Relationship of IEEE 830 and ISO/IEC 12207 (1) Requirements Specification Document IEEE 830 Standard Relationship of IEEE 830 and ISO/IEC 12207