UML Diagrams

& the AD Lifecycle

Chris Boultwood

All images Mat Wright

IT Strategy & Architecture

December 23, 2015

Agenda
1. UML a brief reminder
2. The British Councils AD Lifecycle
3. So what?

IT Strategy & Architecture

December 23, 2015

OMG! The UML

http://www.uml.org/

http://www.omg.org/
http://www.uml.org/
IT Strategy & Architecture

December 23, 2015

Lucky Thirteen
Systems have both static and dynamic aspects:
there UML diagrams that describe structure and behaviour
Activity

Behavioural

describes the business and operational step-by-step workflows of components in a

system

Class

Structural

describes the structure of a system by showing the system's classes, their attributes,
and the relationships among the classes

Communication
Component

Interaction
Structural

shows the interactions between objects or parts in terms of sequenced message

describes how a software system is split up into components and shows the
dependencies among these components

Composite Structure

Structural

describes the internal structure of a class and the collaborations that this structure
makes possible

Deployment

Structural

describes the hardware used in system implementations and the execution

environments and artifacts deployed on the hardware

Interaction Overview
Object

Interaction
Structural

provides an overview in which the nodes represent communication diagrams

shows a complete or partial view of the structure of an example modeled system at a
specific time

Package

Structural

describes how a system is split up into logical groupings by showing the dependencies
among these groupings

Sequence
State Machine
Timing
Use Case

Interaction
Behavioural
Interaction
Behavioural

shows how objects communicate with each other in terms of a sequence of messages
describes the states and state transitions of the system
a specific type of interaction diagram where the focus is on timing constraints
describes the functionality provided by a system in terms of actors, their goals
represented as use cases, and any dependencies among those use cases

IT Strategy & Architecture

December 23, 2015

Activity Diagram

IT Strategy & Architecture

December 23, 2015

Class Diagram

IT Strategy & Architecture

December 23, 2015

Component Diagram

IT Strategy & Architecture

December 23, 2015

Deployment Diagram

IT Strategy & Architecture

December 23, 2015

Package Diagram

IT Strategy & Architecture

December 23, 2015

Sequence Diagram

IT Strategy & Architecture

December 23, 2015

10

State Diagram

IT Strategy & Architecture

December 23, 2015

11

Use Case Diagram

IT Strategy & Architecture

December 23, 2015

12

The British Council AD Lifecycle

IT Strategy & Architecture

December 23, 2015

13

SDLC - Service Development Lifecycle

IT Strategy & Architecture

December 23, 2015

14

Application Development Lifecycles

IT Strategy & Architecture

December 23, 2015

15

Generic Lifecycle Model

IT Strategy & Architecture

What,
no architecture?

December 23, 2015

16

UML Diagrams by AD Lifecycle Phase

UML Diagram

Type
Reqts

AD Lifecycle Phase
Design
Logical Physical Build

Description
Test

Use Case

Behavioural C

na

describes the functionality provided by a system in terms of actors, their goals

represented as use cases, and any dependencies among those use cases

Package

Structural

na

na

na

describes how a system is split up into logical groupings by showing the dependencies
among these groupings

Class

Structural

na

na

Component

Structural

na

na

na

Activity
State Machine
Sequence

Behavioural C
Behavioural C
Interaction na

U
U
na

R
R
C

R
R
R

R
R
na

Deployment

Structural

na

describes the structure of a system by showing the system's classes, their attributes,
and the relationships among the classes
describes how a software system is split up into components and shows the
dependencies among these components
describes the business and operational step-by-step workflows of components in a
system
describes the states and state transitions of the system
shows how objects communicate with each other in terms of a sequence of messages
describes the hardware used in system implementations and the execution
environments and artifacts deployed on the hardware

CRUD chart: C=Create R=Read U=Update D=Delete

Diagrams will often be elaborated as more detail is required at each successive phase
There may be multiple passes through Requirements & Design phases at different levels of abstraction
There may be multiple passes through all phases depending on waterfall vs iterative lifecycle

IT Strategy & Architecture

December 23, 2015

17

So what?
Formal notation is the only way to disambiguate requirements
UML provides a common language and an industry standard notation
Supports better working with contractors and third parties
Approach to tool support and a shared repository identified
No strategy, plan or funding for broad implementation

Furthermore
Heroic model of development vs engineering model
Scalable development needs a standard lifecycle (inc Work Products)
Much broader than patchy, ad hoc adoption of UML

IT Strategy & Architecture

December 23, 2015

18