When software is embedded in some larger system, such as medical equipment, then issues beyond those identified in this standard may have to be addressed. This recommended practice describes the process of creating a product and the content of the product.
The product is a software requirements specification. This recommended practice can be used to create such software requirements specification directly or can be used as a model for a more specific standard. This recommended practice does not identify any specific method, nomenclature, or tool for preparing an SRS. Purpose: This recommended practice describes recommended approaches for the specification of software requirements.
It is divided into five clauses. Clause 1 explains the scope of this recommended practice. Clause 2 lists the references made to other standards. Clause 3 provides definitions of specific terms used.
Clause 4 provides background information for writing a good SRS. I know that , and probably even , are probably just fine for use. However, if nothing else, I would like to know what standard has superseded it. 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 line , in this case.
Short answer : is not a standard, it is a recommended best practice on how to write SRS in the style of But I guess it's because the whole method on how we specify requirements has changed drastically in recent years. 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 Architectures , a surprisingly good book is the old iconix book , and an old classic is Cockburn's Writing Effective Use Cases.
Truth to be told, formal project documentation, especially requirements documentation was killed off mostly in the age of Agile , as the Agile Manifesto discourages formal documentation. There is no one, single, large formal specification, but instead, there are so called user stories , product backlogs and such.
This is because of iterative development, only a handful of features are specified informally for each cycle of weeks. A renowned book is User Stories Applied. There are so-called "executable" specifications, which are formal , since they are essentially domain-specific languages DSLs for testing. Also, specification by software engineers was superseeded by UX design , including information architecture and interaction design, so it's not done by people who can actually code nowadays, which can lead to conflict sometimes.
This is a not-so-bad example on how one looks like it's not a standard! They have their own standards, recommended best practices, etc. Again, I guess this document was "superseeded" because today, we have a bit of chaos around requirements specification: there are many-many viewpoints on how it should be done.
There is no single authority who is able to tell you: "this is how specifications should be made". There are best practices , and I tried to provide you with a representative list of documents and directions , albeit by no means complete, and perhaps personally biased.
At the end of the day, what matters is wether the document you create is able to fulfill all the goals all the people who ever read it have with it : what people want to see, what people need to know in order to understand the requirements are pretty well described in these books, and these are best practices on their own right, albeit in much smaller communities than a single, undivided IT community what we had perhaps in 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.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. What standard superseded ? Ask Question. Asked 9 years, 5 months ago. Active 6 years, 1 month ago. Viewed 11k times. TLDR: How do you find what standard superseded another, and which one took 's place?
Improve this question. Add a comment.
0コメント