In Search of Excellent Requirements - 1 views
-
Consequently, it is not reasonable to expect us to make sound business or technical decisions on behalf of the customers, or to resolve conflicting requirements supplied by different end users, or to set priorities for the many requirements that might be collected.
-
We have finally reached the state where if no project champion can be found to see that the right system is built, we cancel the project.
-
The consequence of not explicitly discussing these quality tradeoffs is a surprise upon delivery, when the customer finds that his implicit quality attribute requirements have not been achieved
- ...3 more annotations...
-
One way to reach an appropriate middle ground in the specification process is to conduct formal inspections of the SRS. A structured document like the IEEE SRS is readily inspected by the design team, the project champions, other representative users, and other software engineers who are not directly involved with the project
-
A prototype is intended to answer specific questions about functionality or interaction styles. If you don't have any questions, don't bother with a prototype
-
Even in a small software group, a focus on accurately and completely capturing, documenting, and modeling the user requirements is a major contributor to building high quality information systems