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
|Published (Last):||12 July 2011|
|PDF File Size:||8.41 Mb|
|ePub File Size:||10.72 Mb|
|Price:||Free* [*Free Regsitration Required]|
Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. A moderately good book on formal documentation is Documenting Software Architecturesa surprisingly good book is the old iconix bookand an old classic is Cockburn’s Writing Effective Use Cases.
A renowned book is User Stories Applied. In other projects Wikimedia Commons. There are so-called “executable” specifications, which are formalsince they are essentially domain-specific languages DSLs for testing.
It should also provide a realistic basis for estimating product costs, risks, and schedules. From Wikipedia, the free encyclopedia. But what if you want to stick with the old methods, eg. P P P P P There are best practicesand I tried to provide you with a representative list of documents and directionsalbeit by no means complete, and perhaps personally biased. What standard superseded ?
Software requirements specification
Sign up using Email and Password.
I have been looking into how to document software projects more formally, and I have learned about IEEE Email Required, but never shown. In this case it may not matter, but if other standards are superseded for more technical things, I think it would be a good idea to link somewhere what standard superseded another if it is not another one in the same linein this case.
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. Bart van Ingen Schenau Post as a guest Name. The software requirements specification document lists sufficient and necessary requirements for the project development.
This is because 380-1998 iterative development, only a handful of features are specified informally for each cycle of weeks. Sign up or log in Sign up using Google.
Retrieved from ” https: Why do you recommend books? An example organization of an SRS is as follows: Retrieved 17 July Applied software project management. Retrieved 19 December However, if nothing else, I would like to know what standard has superseded it.
Software requirements specification – Wikipedia
A software requirements specification SRS is a description of a software system to be developed. I can’t tell you how much they charge, as the new corporate firewall does not allow their Buy page to work. So, from now on, I try to answer a bit of modified question: Recommended Practice for Software Requirements Specifications.
I can’t find how it was superseeded even with IEEE’s advanced search: There is no single authority who is able to tell you: Computer science Computer engineering Project management Risk management Systems engineering.
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. There is no one, single, large formal specification, but instead, there are so called user storiesproduct iree and such.
Strohm Apr 15 ’13 at Journal of Systems and Software. This is a not-so-bad example on how one looks like it’s not a standard! Data modeling Enterprise architecture Functional specification Modeling language Orthogonality Programming paradigm Software Software archaeology Software architecture Software iee management Software development methodology Software development process Software quality Software quality assurance Software verification and validation Structured analysis.
documentation – What standard superseded ? – Software Engineering Stack Exchange
How do you find what standard superseded another, and which one took ‘s place? However, as you can see from that link, it has been superseded.
This is a very complex kind of documentation, it’s mainly used for handovers, although it does contain the requirements mostly it’s chapter 7 in the new ISO style document A moderately good book on formal documentation is Documenting Software Architecturesa surprisingly good book is the old iconix bookand an old classic is Cockburn’s Writing Effective Use Cases.