![]() The requirements document has a diverse set of users (stakeholders), ranging from the senior management of the organization that is paying for the system to the engineers responsible for developing the software. However, in our opinion, it is still useful to write a short supporting document that defines the business and dependability requirements for the system it is easy to forget the requirements that apply to the system as a whole when focusing on the functional requirements for the next system release. ![]() For business systems where requirements are unstable, this is a viable approach. The user then prioritizes requirements for implementation in the next increment of the system. Rather than a formal document, approaches such as Extreme Programming (XP) or Scrum collect user requirements incrementally and write these on cards as so-called user stories. ![]() However, some of the software development methodologies (i.e., agile methods) argue that requirements change so quickly that a requirements document is out of date as soon as it is written, therefore the effort spent with its preparation is largely wasted. ![]() Requirements documents are essential when an outside contractor is developing the software system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |