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):||20 December 2011|
|PDF File Size:||8.41 Mb|
|ePub File Size:||5.56 Mb|
|Price:||Free* [*Free Regsitration Required]|
Computer science Computer engineering Project management Risk management Systems engineering. Post as a guest Name. Why don’t you show me standards instead?
But I guess it’s because the whole method on how we specify requirements has changed drastically in recent years. The specific goals of the SRS are:.
I know thatand probably 8301998are probably just fine for use. What standard superseded ? 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. Sign up using Facebook. I have been looking into how to document software projects more formally, and I have learned about IEEE Home Questions Tags Users Unanswered.
I found this in the IEEE site: Applied software project management. P P P P P Time to lose some sleep Views Read Edit View history.
Computer programming Requirements engineering Software deployment Software design Software maintenance Software testing Systems analysis Formal methods. Email Required, but never shown.
This is because of iterative development, only a handful of features are specified informally for each cycle of weeks. This is achieved through detailed and continuous communications with the project team and customer throughout the software development process. Aadaam 1, 7 Retrieved 19 December A renowned book is User Stories Applied.
Also, specification by software engineers was superseeded by UX designincluding information architecture and interaction design, so it’s not done by people who can actually code nowadays, which can lead to conflict sometimes.
Retrieved from ” https: Sign up using Email and Password.
They have their own standards, recommended best practices, etc. 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.
80-1998 is a not-so-bad example on how one looks like it’s not a standard! However, if nothing else, I would like to know what standard has superseded it.
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.
All articles with unsourced statements Articles with unsourced statements from May