Difference between revisions of "Analysis"
From Suhrid.net Wiki
Jump to navigationJump to search (→Intro) |
|||
| Line 10: | Line 10: | ||
* UML modeling can be used to analyse requirements. | * UML modeling can be used to analyse requirements. | ||
* Use cases (Are these part of UML ?) - to define functional requirements. | * Use cases (Are these part of UML ?) - to define functional requirements. | ||
| − | * Static Structure Diagrams - To model object and relationships. [TODO : Isnt this design ?] | + | * Static Structure Diagrams - To model object and relationships. [TODO : Isnt this stepping into design ?] |
| + | * Dynamic behavior diagrams - to model interaction and sequencing. | ||
| + | * There are also UML analysis patterns which help reuse existing models. These are usually domain specific. | ||
| + | ** Note: this is ''different'' from a design pattern. | ||
| + | |||
[[Category:REQE]] | [[Category:REQE]] | ||
Revision as of 12:12, 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 stepping into design ?]
- Dynamic behavior diagrams - to model interaction and sequencing.
- There are also UML analysis patterns which help reuse existing models. These are usually domain specific.
- Note: this is different from a design pattern.
