(Re-)Engineering a Software Requirements Specification
From Foss2Serve
(Difference between revisions)
m |
|||
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | If the whole set of activities for the [ | + | If the whole set of activities for the [[Requirements Engineering, CSU Long Beach, Penzenstadler|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 stakeholders (Activity)]] | ||
| Line 7: | Line 8: | ||
* [[(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]] | ||
| + | [[Category:SE Requirements Engineering]] | ||
Latest revision as of 13:46, 15 October 2018
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
