Difference between revisions of "Analysis"
From Suhrid.net Wiki
Jump to navigationJump to search (→Intro) |
|||
| Line 1: | Line 1: | ||
| − | + | = Intro = | |
* Requirements Analysis is building models of requirements that can be evaluated. | * Requirements Analysis is building models of requirements that can be evaluated. | ||
| Line 5: | Line 5: | ||
* Formally modeling natural language requirements is hard ! also, requirements also conflict with multiple stakeholders. | * Formally modeling natural language requirements is hard ! also, requirements also conflict with multiple stakeholders. | ||
* Techniques used are: UML and SCR tables. | * Techniques used are: UML and SCR tables. | ||
| + | |||
| + | = Analysis using UML = | ||
| + | |||
| + | * UML modeling can be used to analyse requirements. | ||
| + | * Use cases (Are these part of UML ?) - to define functional requirements. | ||
| + | * Static Structure Diagrams - To model object and relationships. [TODO : Isnt this design ?] | ||
| + | |||
[[Category:REQE]] | [[Category:REQE]] | ||
Revision as of 12:08, 31 October 2011
Intro
- Requirements Analysis is building models of requirements that can be evaluated.
- It is also about identifying conflicts between requirements.
- Formally modeling natural language requirements is hard ! also, requirements also conflict with multiple stakeholders.
- Techniques used are: UML and SCR tables.
Analysis using UML
- UML modeling can be used to analyse requirements.
- Use cases (Are these part of UML ?) - to define functional requirements.
- Static Structure Diagrams - To model object and relationships. [TODO : Isnt this design ?]
