![]() |
![]() |
![]() |
![]() |
![]() |
Textual Requirements
Conventional textual requirements are in most development projects an important input and result of the requirements analysis. In SOMT, the textual requirements model is simply one or more text documents. It is however important to include them within the scope of SOMT to get a possibility to create implinks from them to the other models in SOMT, and thus make it possible to trace the implementation of the requirements.
The source of the requirements may in some cases be the customers in which case the textual requirements form one of the inputs to the requirements analysis. In other cases the textual requirements are created by the development team as part of the requirements analysis.
Non-functional requirements are an example of a type of requirements that are important to capture, but may be difficult to formulate using the other models in the requirements analysis. The non-functional requirements may express properties about for example:
- Performance issues like response time or number of transactions per second.
- Reliability like the mean time between failure.
This type of requirements are most easily expressed in natural language and entered into the textual requirements model.
It is important to not only write down the requirements but also to analyze them. One aspect of this analysis is to mark all important concepts in the requirements that can be useful later when identifying objects and use cases.
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |