(Re-)Engineering a Software Requirements Specification
(Difference between revisions)
m |
|||
| Line 7: | Line 7: | ||
* [[(Re-)Engineering use cases (Activity)]] | * [[(Re-)Engineering use cases (Activity)]] | ||
* [[(Re-)Engineering Quality requirements (Activity)]] | * [[(Re-)Engineering Quality requirements (Activity)]] | ||
| + | |||
| + | -------------------- | ||
| + | {{License CC BY SA}} | ||
| + | |||
| + | [[Category:Requirements_Engineering]] | ||
Revision as of 13:06, 24 July 2017
If the whole set of activities for the Requirements Engineering course seems to much, for example because you have a trimester instead of a semester, here is a reduced set of activities that together will lead to a complete software requirements specification.
- (Re-)Engineering stakeholders (Activity)
- (Re-)Engineering goals (Activity)
- (Re-)Engineering a system vision (Activity)
- (Re-)Engineering a domain model (Activity)
- (Re-)Engineering use cases (Activity)
- (Re-)Engineering Quality requirements (Activity)
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License
