Static Modelling with UML Flashcards
functional requirements
Functional requirements are described by use cases. Use cases are the core of object-oriented
analysis and design.
Levels and Types of Requirements
Business requirements,System requirements,Internal requirements.
Challenges of Writing Requirements
Problem Domain Complexity
Person-to-person Communication
Constant Change
Writing Requirements
Types of Roles
Primary,secondary and external
Primary
A person in this role directly uses the system to enter, view process or extract information.
Secondary
A person in this role does not directly use the system, but uses or generates data for the system.
External
Any system that receives or generates data for the system.
How to Deal with Hundreds of Use Cases
The key is to organise the use cases so the team can understand them. One specific technique is to organise the use cases into
groups or packages.
Three types of use case
-Brief use case
-Casual use case
-Fully dressed
Brief use case
It has one paragraph summary and is normally used for main success scenarios.
Casual use case
It is an informal paragraph which has multiple paragraphs that cover various scenarios
Fully dressed
This is the most comprehensive case that shows all the steps and variations. It has supporting sections, such as preconditions and success guarantees. However, a detailed discussion about a fully dressed use
case is beyond the scope of this syllabus.
Include relationship
Typically where a set of use cases each includes some common functionality that is expressed in one shared subuse case;
Extend
Where the functionality of a use case is extended by referencing other use cases;
Generalisation
Where several use cases share something similar.
