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.

Can be used to describe how actors in a use case are interacting.
Human and proactive system actors (the primary actors) should be on the left most side of the diagram.
Reactive system actors (the supporting actors) are on the right most side of the diagram.