Back to Software Engineering

Study notes

Qwestrum Engineering360 · IT & Software · Software Engineering

UML and Design Modelling

UML is a standard visual notation for modelling software: structural diagrams (class, component) show what the system is made of, while behavioural diagrams (use case, sequence, state) show how it behaves.

Exam tip: keep SI units consistent end-to-end, write the governing relation symbolically before substituting, and sanity-check magnitude and sign.

Key formulas & points

Skim these first — then read the full notes below.

Aggregation is weak ownership; composition is strong ownership
A state machine models an object’s lifecycle
A component diagram shows deployable modules

Topic details

Introduction

This Sommerville topic covers design modelling with UML. You draw and interpret class diagrams with relationships and multiplicities, model interactions with sequence diagrams, capture user goals with use cases, and represent object lifecycles with state machines.

Key relations & formulas

Formulas (Indian textbook notation)

$class diagram: attributes, methods, associations and multiplicity$

Formulas (Indian textbook notation)

$sequence diagram: lifelines with time-ordered messages$

Formulas (Indian textbook notation)

$use case: actor → system boundary → use cases$

Notation and sign conventions

Relation 1 —

class diagram: attributes, methods, associations and multiplicity

Formulas (Indian textbook notation)

$class diagram: attributes, methods, associations and multiplicity$

Write this relation with symbols exactly as in Software Engineering — Roger Pressman before substituting numbers. Examiners award partial marks for a correct setup even when arithmetic slips.

Relation 2 —

sequence diagram: lifelines with time-ordered messages

Formulas (Indian textbook notation)

$sequence diagram: lifelines with time-ordered messages$

Write this relation with symbols exactly as in Software Engineering — Roger Pressman before substituting numbers. Examiners award partial marks for a correct setup even when arithmetic slips.

Relation 3 —

use case: actor → system boundary → use cases

Formulas (Indian textbook notation)

$use case: actor → system boundary → use cases$

Write this relation with symbols exactly as in Software Engineering — Roger Pressman before substituting numbers. Examiners award partial marks for a correct setup even when arithmetic slips.

Concept in depth

UML gives a shared vocabulary so designers can communicate structure and behaviour before writing code. Class diagrams capture the static picture — classes, their attributes and operations, and relationships whose multiplicity constrains how many objects associate. The distinction between aggregation and composition encodes ownership: composition means the part cannot outlive the whole (a room and its building), aggregation is a looser has-a. Behavioural diagrams complement this: sequence diagrams show the time-ordered messages between objects for a scenario, use cases frame the system from the actor’s goals, and state machines describe how an object reacts to events over its lifetime. Together they let design flaws surface cheaply on paper.

Assumptions and validity limits

State assumptions explicitly before using any relation for uml and design modelling — steady state, uniform properties, linear elastic material, ideal gas, incompressible flow, etc., as applicable.

Wrong assumptions invalidate the entire solution even when the formula is correct. In Software Engineering viva and GATE descriptive questions, listing valid assumptions often earns separate marks.

Step-by-step problem approach

1. Read the question and list given data with SI units (common in Software Engineering papers).
2. Draw a neat labelled diagram where applicable — examiners in Indian universities award diagram marks even when arithmetic slips.
3. Identify which relation from this topic applies to uml and design modelling.
4. Use equation 1:

class diagram: attributes, methods, associations and multiplicity

.
5. Use equation 2:

sequence diagram: lifelines with time-ordered messages

.
6. Substitute values, compute, and verify units and sign (direction).
7. State conclusion in one line — e.g. safe/unsafe, stable/unstable, feasible/infeasible.

Applications & exam relevance

UML and Design Modelling appears in product teams and IT services. In Indian it software curricula this topic is tested because it connects theory to SDLC, requirements, and quality.

GATE and semester exams often combine uml and design modelling with earlier units — revise prerequisites before attempting mixed problems.

Industry interview panels sometimes ask: "Where did you use uml and design modelling?" — answer with a lab, mini-project, or plant visit example if possible.

Common mistakes in exams

Students confuse aggregation with composition, misread multiplicities, and mix up structural (class) with behavioural (sequence) diagrams. Treating a use-case diagram as a flowchart of steps rather than a set of actor goals is common.

Quick revision checklist

Before attempting uml and design modelling problems, confirm you can:

1. Aggregation is weak ownership; composition is strong ownership
2. A state machine models an object’s lifecycle
3. A component diagram shows deployable modules

Revise the solved examples in Software Engineering — Roger Pressman and one previous-year GATE or university paper for this unit.

Worked examples

Try the problem first — open the solution when you are ready to check.

Aggregation versus composition

Problem

Model the relationship (a) a University and its Departments and (b) a Playlist and its Songs. Which is composition?

Solution

(a) University–Department is composition (a department cannot exist without its university). (b) Playlist–Song is aggregation, since a song can exist independently and belong to many playlists.

Conceptual check — UML and Design Modelling

Problem

In a Software Engineering semester or GATE paper you are asked: "State the main assumption, the governing relation, and one practical consequence of uml and design modelling." What should a complete answer include?

📖 Standard books (India)

Software Engineering — Roger Pressman
Read: Syllabus unit
SDLC, Agile, and software metrics

Explore related topics

See real it & software careers

After exams and interviews, see how engineers actually built careers — milestones and decisions from people in the field.

Browse IT & Software journeys Plan your path