Analysing a Use Case

1. Analysing a Use Case E.Barker@intrallect.com

2. General Principles • This method of analysis should be considered before use cases are gathered • Methods of analysis differ and must depend on the purpose of the project • E.g if the aim is to get requirements for a software product may want to produce a complete set of use cases which customer can understand and agree with • E.g if aim is to gather sector requirements want to extract information from use case

3. Approaches for systems design • The following methods may be of use in systems design • Combining use cases together: • Creating UML diagrams:

4. Approaches used for Large Scale Business Analysis • Determining if sector covered • Analysis of primary actors and aims • Consultation to check all primary actors and aims covered.

5. Large Scale Business Analysis 2 2. Extracting requirements • Construct an extra column next to success scenario and extensions • Write down any implied requirements from each sentence • Sort requirements under headings and note repeated requirements • Note that this requires interpretation from person analysing use cases • Example

6. Approach for DRM study • Analysed from point of view of determining DRM requirements of FE and HE sectors • Requirements which came up frequently were considered in more depth in the final report

7. Reflections • The approach did determine the areas which were important to the sector and I would recommend using the same approach for similar projects. • Not always possible to determine exactly what was meant by use case authors • Can be difficult to group requirements under headings