NOT / AVERAGEWE CAN DO BETTER

UCS503 · SOFTWARE ENGINEERING

Understand the system
before you draw it.

Process models explain how the work moves. Requirements explain what the system must achieve. UML makes the behaviour, structure and deployment visible.

INTERACTIVE DIAGRAM STUDIO

Choose a system. Choose a scenario. Draw every connected view.

This is the complete lab built around Instagram, Spotify, Uber, Ola and other familiar systems. Change the scenario, then switch between Classroom, System Design and Near Exhaustive depth.

Open the complete studio
EXAM REVISION PATHStart with the module you need, then use a worked interaction to test the idea.
Start a 15-minute revision
MODULE 01

Process Models and Agile Software Development

Choose a way of working before you begin drawing the system.

Exam focus

Compare models through requirement change, risk, feedback and delivery constraints.

  1. L01
    guided interactive

    Introduction to Software Engineering

    Why is engineering software different from simply writing code?

    Learn
  2. L02
    guided interactive

    Software Engineering Basics

    What has to be true before a software solution can be trusted?

    Learn
  3. L03
    guided interactive

    Software Process Models

    Which process model fits the uncertainty in this project?

    Learn
  4. L04
    guided interactive

    Agile Model

    How does a team turn a backlog into a small, reviewable increment?

    Learn
  5. L05
    guided interactive

    User Stories and Cards

    Can a short story state a user goal without becoming vague?

    Learn
MODULE 02

Requirement Engineering and Analysis Modeling

Find the actual problem before choosing notation or technology.

Exam focus

Classify requirements, make them testable and trace them into models.

  1. L07
    guided interactive

    Requirement Engineering

    How do needs become requirements that can be checked?

    Learn
  2. L08
    guided interactive

    Requirement Gathering

    Which elicitation technique exposes the information you do not yet know?

    Learn
  3. L09
    guided interactive

    Requirement Modeling

    Which view makes the requirement easier to discuss?

    Learn
  4. L10
    full diagram studio

    Use Case and Activity Diagrams

    What does a user want, and what workflow makes that goal happen?

    Learn
  5. L11
    guided interactive

    Data Flow Diagrams: Level 0 and Level 1

    What data enters, changes, is stored and leaves the system?

    Learn
  6. L12
    full diagram studio

    Class Diagrams

    What stable objects and relationships support the selected scenario?

    Learn
  7. L13
    full diagram studio

    Case Studies: Use Case and Activity Diagram

    Can one scenario remain consistent when the view changes?

    Learn
  8. L14
    guided interactive

    Non-Functional Requirements

    How do you make a quality expectation measurable?

    Learn
MODULE 03

UML Modeling

Choose the diagram that answers the question in front of you.

Exam focus

Explain why one diagram is appropriate and identify what it must not contain.

  1. L10
    full diagram studio

    Use Case and Activity Diagrams

    What does a user want, and what workflow makes that goal happen?

    Learn
  2. L12
    full diagram studio

    Class Diagrams

    What stable objects and relationships support the selected scenario?

    Learn
  3. L15
    guided interactive

    Sequence and Collaboration Diagrams

    Do you need time order or object links to explain the interaction?

    Learn
  4. L15
    guided interactive

    State Diagrams

    How does one object change over time when events happen?

    Learn
  5. L15
    guided interactive

    Component and Deployment Diagrams

    What is the software split, and where does each part run?

    Learn
MORE DIAGRAMS

Continue beyond the connected UML studio.

These guided exercises cover data flow, object collaboration, state changes, components and deployment.

guided builder

DFD

Where does data enter, change and persist?

guided comparison

Collaboration

Which linked object owns each numbered message?

guided simulator

State

How does one object react to events?

guided explorer

Component and deployment

What is the software split, and where does it run?

CONNECTED DIAGRAM STUDIO

Use one scenario across five live diagrams.

Open the UML lab