Week 6- Use Case Modelling

OO Models:
- Class/Domain model: definition of system comoments
- Use case diagrams/ descriptions: show user roles and how they use the system; graphical models that summarise information about actors and use cases; use event table to identify major uses
- System Sequence Diagrams: define inputs, outputs and sequence of interactions between user and system for a use case
- Statechart diagrams: describe object state
- Activity diagram: describe user activities

CRUD analysis:
- Create, Read/Report, Update, Delete
- An IE technique used to identify event table events/ develop use case diagram
- Three levels of detail: brief, intermediate and fully developed

Activity Diagrams:
- Used to document work flow of business process activities for each use case scenario
- Standard UML diagram

SSD notation:
- Actor = stick figure
- Object = rectangle
- Message = arrow (not sure, my notes are a bit scribbled)
- Lifeline = verticle line under object (passage of time)
- dashed verticle line (creation and deletion of thing isnt important to the scenario)
- long narrow rectangles (activation lifelines- object is active only during this part of scenario)

The Domain Class Diagram:
- Provides definition of system components
- Contains important class structure information for implementation with OO programming
- Conceptual data model to describe classes for database definition