Ten sessions of UML modelling with StarUML or ArgoUML, then implementing class diagrams and associations in C++ or Java and mapping classes to tables.
Objectives
Do not copy. Read for understanding and the viva- Draw different UML diagrams for specified systems
- Implement the UML diagrams in code
- Do mapping of classes into database tables
Sessions
| Session | Topic | Questions |
|---|---|---|
| Session 1 | Class and object diagrams | Q1 to Q3 |
| Session 2 | Use case diagrams | Q4 to Q5 |
| Session 3 | Sequence diagrams | Q6 to Q8 |
| Session 4 | Collaboration (communication) diagrams | Q9 to Q11 |
| Session 5 | Activity diagrams | Q12 to Q13 |
| Session 6 | State chart diagrams | Q14 to Q15 |
| Session 7 | Component and deployment diagrams | Q16 to Q18 |
| Session 8 | Implementing class diagrams in code | Q19 to Q20 |
| Session 9 | Implementing associations | Q21 to Q22 |
| Session 10 | Mapping classes to database tables | Q23 |
Before the first session
Do not copy. Read for understanding and the viva- For every exercise, write a problem description of 300 to 500 words and list the assumptions before drawing.
- Use a UML tool: StarUML, ArgoUML, draw.io or PlantUML all produce acceptable diagrams. Keep the exported image and the description together in the record.
- Name every class, actor, message and state; unnamed elements lose marks.