Sponsor Software Engineering The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th...  Home/Search
Context Related
| csri.utoronto.ca/~...ESTD8301998.pdf Cached: PS.gz PS PDF This document uses CoBlitz to cache paper downloads. If your firewall is blocking outgoing connections to port 3125, you can use these links to download local copies.
Image Update HelpPS.gz PS PDF From: csri.utoronto.ca/~sme/CSC...index (more) (Enter author homepages) |
Rate this article:      (best)Comment on this article |
Abstract: : The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products. Guidelines for compliance with IEEE/EIA 12207.1-1997 are also provided. Keywords: contract, customer, prototyping, software requirements specification, supplier,... (Update)
Context of citations to this paper: More
.... of the model, followed by an improvement of the model based 1 The IEEE RecommendedPractice for Software Requirements Specifications [10] lists eight characteristics of a quality Software Requirements Specification: that it is correct, unambiguous, complete, and consistent,...
Cited by: More
Verifying Model Oriented Specifications through Animation - Kazmierczak, Winikoff, Dart (Correct)
Similar documents (at the sentence level):
6.2%: Revision of IEEE Std 829-1983) - Sponsor Software Engineering (Correct)
Similar documents based on text: More All
0.4: Applying the IEEE 1471-2000 Recommended Practice to a Software.. - Land (Correct)
0.3: A Comparison of IEEE/EIA 12207, ISO/IEC 12207, J-STD-016, and.. - Gray (1999) (Correct)
0.2: Unknown - (1999) (Correct)
BibTeX entry: (Update)
Software Engineering Standards Commitee of the IEEE. IEEE Recommended Practice for Software Requirements Specifications. IEEE, 1993. http://citeseer.ist.psu.edu/429289.html More
@misc{ standards93ieee,
author = "S. Standards and C. of",
title = "the IEEE. IEEE Recommended Practice for Software Requirements Specifications",
text = "Software Engineering Standards Commitee of the IEEE. IEEE Recommended Practice
for Software Requirements Specifications. IEEE, 1993.",
year = "1993",
url = "citeseer.ist.psu.edu/429289.html" }
Citations (may not include all citations):1 IEEE RECOMMENDED PRACTICE FOR 30 Copyright 1998 IEEE (context) - Std - 1998
1 The specic content requirements for an SRD in IEEE/EIA 12207 (context) - Compliance, content et al. - 1997
1 The purpose of the SRD is: IEEE/EIA 12207.1-1997, subclause .. (context) - of, is et al.
1 of this recommended practice shall be evaluated considering .. (context) - specied, requirements et al. - 1996
Documents on the same site (http://www.csri.utoronto.ca/~sme/CSC2106S/index.html): More
Requirements Engineering: A Roadmap - Nuseibeh, Easterbrook (2000) (Correct)
CSC2106S Requirements Engineering - Prof Steve Easterbrook (Correct)
Automated Consistency Checking of Requirements Specifications - Heitmeyer, Jeffords, Labaw (1996) (Correct)
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC