Timeline for Writing a Software Requirement Specification
Current License: CC BY-SA 2.5
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 24, 2015 at 19:02 | comment | added | Dunk | Your examples aren't requirements, they are design. The specifics on how the requirement is to be accomplished is a design decision, not a requirement. Thus, "two buttons" is a design decision. It becomes obvious when you realize there are many other valid ways to accomplish the same goal (Start or Stop something). Thus, to make it more of a requirement you would say "The UI shall provide a means to Start and Stop something". But I'd go further, because using a UI is also a design decision. So for the system requirement it would be "The system shall provide a means to Start and Stop something" | |
| Nov 9, 2010 at 0:47 | history | answered | AShelly | CC BY-SA 2.5 |