IEEE ; CS Project Documentation, by Bouchier, Brewster, Fischer, Herschbach, Nina; Project submissions from CS Page 1. Page 2. Page 3. Page 4. Page 5. Page 6. Page 7. Page 8. Page 9. Page Page Page Page Page Page Page Page Page A software requirements specification (SRS) is a description of a software system to be . — IEEE Recommended Practice for Software Requirements Specifications. doi/IEEESTD ISBN

Author: Vizil Mushura
Country: Libya
Language: English (Spanish)
Genre: Literature
Published (Last): 1 January 2013
Pages: 272
PDF File Size: 18.41 Mb
ePub File Size: 13.46 Mb
ISBN: 955-4-49896-653-9
Downloads: 34752
Price: Free* [*Free Regsitration Required]
Uploader: Vorn

Software requirements specification

But I guess it’s because the whole method on how we specify requirements has changed drastically in recent years. Again, I guess this document was “superseeded” because today, we have a bit of chaos around requirements specification: On how it is actually done in the industry today: I found a copy of it on our uni’s internal site though.

I can’t find how it was superseeded even with IEEE’s advanced search: I found this in the IEEE site: There are so-called “executable” specifications, which are formalsince they are essentially domain-specific languages DSLs for testing. There is 830-199 single authority who is able to tell you: The software requirements specification document lists sufficient and necessary requirements for the 380-1998 development. But what if you want to stick with the old methods, eg.


Aadaam 1, 7 Home Questions Tags Users Unanswered. Following the idea of code smellsthe notion of requirements smell has been proposed to describe issues in requirements specification where the requirement is not necessarily wrong but could be problematic.

This is a not-so-bad example on how one looks like it’s not a standard! It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle.

Software requirements specification establishes the basis for an agreement between customers and contractors or suppliers on how the software product should function in a market-driven project, these roles may be played by the marketing and development divisions. Computer science Computer engineering Project management Risk management Systems engineering. How do you find what standard superseded another, and ueee one took ‘s place? Computer programming Requirements engineering Software deployment 80-1998 design Software maintenance Software testing Systems analysis Formal methods.

Strohm Apr 15 ’13 at In other projects Wikimedia Commons.

documentation – What standard superseded ? – Software Engineering Stack Exchange

Time to lose some sleep Sign up using Email and Password. By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies.

In particular, the requirements smell: This page was last edited on 26 Decemberat Data modeling Enterprise architecture Functional specification Modeling language Orthogonality Programming paradigm Software Software archaeology Software architecture Software configuration management Software development methodology Software development process Software quality Software quality assurance Software verification and validation Structured analysis.


The SRS 830-9198 be one of a contract deliverable Data Item Descriptions [4] or have other 380-1998 of organizationally-mandated content. Post Your Answer Discard By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies.

Bart van Ingen Schenau This is because of iterative development, only a handful of features are specified informally for each cycle of weeks. They have their own standards, recommended best practices, etc.

Software requirements specification – Wikipedia

The specific goals of the SRS are:. A renowned book is User Stories Applied. Try expanding upon your answer with some details about what is contained inside of your link. It should isee provide a realistic basis for estimating product costs, risks, and schedules.

Views Read Edit View history.