Overview and history of UML
•
Concepts and contributions of the object model
•
The position of UML with regard to methods
•
The UML definition process
•
UML model quality
•
UML strong and weak points
•
The future of UML
The 9 UML diagrams
•
Static diagrams
- Rules for use and limitations
- Class diagrams, package diagrams, deployment diagrams and
component diagrams
- Dynamic diagrams
- Sequence diagrams, collaboration diagrams, state diagrams and
activity diagrams
•
Use diagrams
- Use case diagrams
Refreshers on the development process
•
Phases, cycles, activities, products and supplies,
...
The 9 UML diagrams
•
Objectives
•
Tools (models) used
•
Organization:
- Link with users
- Organization of workshops and meetings
- Documentation
- Validation
Defining the dictionary
•
Objectives
•
The project dictionary
•
The project structure
•
Content of descriptions
•
Structuring
•
Traceability
Defining requirements
•
Language
•
Structuring
•
Functional requirements
•
Non-functional requirements
•
Validation rules
•
Traceability
Defining the business process
•
Formalism: the activity diagram
•
Structuring
•
Link with use cases
•
Validation rules
Defining the company model
•
Formalism: the collaboration diagram
•
Validation rules
Defining the information model
•
Formalism: the class diagram
•
Prominent concepts
•
Validation rules |
Defining the use case model
Identifying system actors
•
UML definition and formalism
•
Primary and secondary actors
•
Users versus roles
•
Questions to ask oneself
•
Description of actors
Identifying use cases
•
Rules for identifying first-level use cases (fundamental
needs)
•
Functional and non-functional needs taken into account
•
Use cases versus the functional approach
•
Structuring use cases
•
Textual description of use cases
•
Links between use cases and the GUI
•
Use cases for validation
•
Limitations in what use cases can express
•
Cost model based on use cases
Fine-tuning use cases
•
UML formalism
•
Advantages and disadvantages of the use case approach
Identifying scenarios
•
Objectives
•
Links with use cases
•
Textual scenarios, sequence and activity diagrams
•
Rules for writing scenarios
•
Criteria for selecting scenarios
•
The "Happy Day" scenario
•
Secondary scenarios
Traceability
•
Objectives
•
Means implemented
•
Traceability matrix
Validating use case models
•
Validation rules
•
Metrics
Environmental constraints
•
Objectives
•
Component diagrams
•
Deployment diagrams
Links to analysis
•
Link with the needs expression phase
•
Traceability with regard to use cases
Developing the software acceptance document
Developing the user manual
Document types
Managing evolutions
|
