|
-
Systems modelling
- The need for modelling and modelling standards
- Models of the Unified Modeling Language (UML)
- Interaction of selected UML models
- Validating and verifying models
-
Modelling Functionality
- Modelling user requirements
- Use cases
- Actors and the system boundary
- Use case diagrams
- Generalising actors and use cases
- Use case descriptions - template of the description, including pre-conditions and post-conditions
- Use case descriptions - defining the main and alternative flows
- <<include>> and <<extend>>
- Using activity diagrams to model use case descriptions
- Activity diagrams - notation
- Using activity diagrams to model processing
- Using activity diagrams to model use case descriptions
-
Static modelling
- Analysis class modelling
- Objects and classes
- Class diagrams and object diagrams
- Representing classes: name, attributes and operations
- Defining attributes: adornments
- Abstraction and encapsulation
- Associations
- Naming associations
- Defining multiplicities (minimum and maximum)
- Multiple associations
- Reflexive associations
- Constraints in associations
- Association classes
- Generalisation and inheritance
- Modelling generalisation
- Private, public and protected attributes
- Concept of polymorphism
-
Dynamic modelling
- Use case realisation
- Sequence diagrams
- Lifelines
- Focus
- Message notation
- Populating the class diagram
- Using opt, alt and loop in the sequence diagram
- Communication diagrams - an introduction
-
Modelling in context
- The Unified Process
- Phases of the Unified Process
- Workflows of the Unified Process
- The relationship of models to the Unified Process
- Monitoring analysis against business objectives and system requirements
- The bridge to design, software package selection and development
|
|