ARCH-2: UML 101 - From Design to Implementation using UML

ARCH-2: UML 101 - From Design to Implementation using UML

Frank Beusenberg Senior Technical Consultant

© 2006 Progress Software Corporation2ARCH-2: UML 101 - From Design to Implementation using UML

Theory vs. Practice

The difference between The difference between theory and practice is that, in theory and practice is that, in theory, there is no difference theory, there is no difference between theory and practice.between theory and practice.


Shu-Ha-Ri

ShuShu - Learning- LearningHaHa - Understanding- UnderstandingRiRi - Be creative- Be creative


Agenda

Introduction UML 2.0 Diagrams Use Case View Logical View Dynamic View Implementation View Demonstration Q&A


UML = Unified Modeling Language First UML spec in 1997 Current version = 2.0

• Object Management Group (OMG) Graphical language

• Object Oriented in nature• Has syntax rules• Can be extended using stereotypes

NOT a methodology!

Introduction

What is UML? Facts


Introduction

What is UML?


Manage complexity Mitigate risk Facilitate communication

Modeling provides ability to visualize entire systems, assess options and designs• Software has grown from do-it-yourself into highly

complex systems• Software is integral part of business process, so has to

be well planned• Software has become capital equipment that cannot

just be removed/changed

Introduction

Why model?


Specify, visualize, and document models of software systems• Current and new systems

• Structure and design

• Behavior and interaction

De facto standard (Tool Support!) Unambiguous and consistent notation Documentation

Introduction

Why use UML?


Agenda



UML 2.0 Diagrams

UML 2.0 Types of Diagrams – Behavior Diagrams


UML 2.0 Behavioral Diagrams

Describes the functional requirements of the system

UML Use Case Diagram



Describe procedural logic, business processes and workflow

UML Activity Diagram



Describes the message flow between objects in chronological order

UML Sequence Diagram

sd Serv ice Manager - Component Creation

«interface»

Interfaces::IServiceManager

Component::Component«interface»

Interfaces::ISecurityManager

System

(from Actors)

«interface»

Interfaces::IComponentFactory

alt Component Started

[No]

alt Authorized

[TRUE]

Reference= startService(logicalName,componentType)

Authorized= isAuthorized()

Reference= Check Local Cache for Component

Reference= createInstance(componentName,componentType)

Create


UML 2.0 Diagrams

UML 2.0 Types of Diagrams – Structure Diagrams


UML 2.0 Structural Diagrams

Captures logical structure of system

UML Class Diagram

cd Ev aluate Testdriv e

Class Name

- Private Attribute: integer+ Public Attribute: character# Protected Attribute: logical~ Package Attribute: decimal

- Private Operation(character, logical) : void+ Public Operation() : void# Protected Operation() : void~ Package Operation() : void



Illustrates the pieces of software that will make up a system.

UML Component Diagram



Shows how and where the system will be deployed.

UML Deployment Diagram


UML Modeling

Use Case View

Logical View

Dynamic View

Implementation View

Deployment View

ud Manage Employees

AutoEdge System

Manager

(from Actors)

Browse Employees

Update Employee

Create Employee

Delete Employee

Create User«extend»

«include»

«use»

«use»

cd Users

Architecture Entities::User

- UserEmail: CHARACTER- UserLogin: CHARACTER- UserPassword: CHARACTER

Architecture Entities::UserGroups

- UserGroupDescription: CHARACTER- UserGroupName: CHARACTER

Business Entities::Employee

+ Address: CHARACTER+ City: CHARACTER+ email: CHARACTER- EmployeeLanguage: CHARACTER+ employmentEndDate: DATETIME-TZ+ employmentStartDate: DATE+ FirstName: CHARACTER+ LastName: CHARACTER+ MobilePhoneNumber: CHARACTER+ Notes: CHARACTER+ PhoneNumber: CHARACTER+ Position: CHARACTER+ PostCode: CHARACTER

+ createEmployee() : void+ deleteEmployee() : void+ findEmployee() : void+ isAvailable() : LOGICAL+ updateEmployee() : void+ validateEmployee() : void

Architecture Entities::Language

- Description: CHARACTER- Language: CHARACTER

0..*

1

11

0..* 1

sd Login

Client

(from Architecture Components)

Server Gateway


Security


Session Context


Request("Security", "Login", ...)

isValidUser(Login, password)

ValidUser

[if Valid User]: createSession

sessionID

[if valid user]: sessionID

id Business Entity (Client)

«Program»

proSIproxy.p

- NEW GLOBAL SHARED VARIABLE ghttProxySIproc: HANDLE

+ fetchWhere(CHARACTER, HANDLE, DATASET-HANDLE*) : void+ saveChanges(CHARACTER, HANDLE, CHARACTER*) : void

«Program»

ClientXxx.p

«Include»

proSIproxyStart.i

- NEW GLOBAL SHARED VARIABLE ghProxySIproc:

«Include»

dsXxx.i

- DEFINE DATASET <dataset-def>:

«Include»

etXxx.i

«include»

ttContext.i«includes»

includes

includes

«includes»

«realize PERSISTENT»

includes

dd Integration

HQ System

Sonic

Dealer System 1

Sonic

Dealer System 2

Sonic

Dealer System 3

Sonic

Dealer System n

Sonic


Model-Driven Architecture (MDA)


Agenda



AutoPark - Use Case View

Describing system functionality

Gathering requirements• Functional & non-functional requirements

Document functional requirements• UML Use Case Diagram

• Use Case Description Documents

Identify actor(s) and association to use case Create different levels of use cases (re-use!)


AutoPark - Use Case Viewud Use Case Package Diagram - Auto Park

AutoPark System

Testdrive Car Pool Maintenance

+ Manage Cars

+ Print l ist of testdrive cars

Testdrive Appointment Maintenance

+ Manage test drive appointments

+ Print and send testdrive invitation

+ Print l ist of testdrive appointments

+ Process evaluation form

+ Process TestDrive Request

+ Request TestDrive

Testdrive Person Maintenance

+ Manage Customers

+ Print l ist of testdrive persons

Use Case Packages


AutoPark - Use Case Viewud Testdriv e Appointment Maintenance

AutoPark Testdrive Maintenance

Administrativ e Person

(from Actors)

Sales Person

(from Actors)

Print and send testdriv e inv itation

Print list of testdriv e

appointments

Process ev aluation form

Manage test driv e appointments

Customer

(from Actors)

Request TestDriv e

Process TestDriv e Request

(from Testdrive Person Maintenance)

Manage Customers«extend»

Use Case Diagram



Describing use case scenario(s)

Scenario = Use Case Activity Flow

Basic Scenario Alternate Scenario(s)

UML Activity Diagram• Describe what happens, now how!



Activity Diagram

ad Activ ity Diagram - Process TestDrive Request

Process TestDrive Request Start

Display List of Requests

«UserActivity»Select Request to process

and rev iew

Delete Request

Process Request

Process TestDrive Request

[Action = REJECT]

[Action = PROCESS]

ad Activ ity Diagram - Process Request

Process Request Start

Validate User

Create TestDriv eAppointment

Business Request?

Create TestDriv e RequestXML File

Process Request End

[BusinessRequest = YES][Business Request = NO]



Creating Test Scenarios

Identify paths in activity diagram

Create minimal test-scenarios (using each path once)

Create all possible test-scenarios (combining all paths to create unique scenarios)


Agenda


cd Logical View

Ev aluation

- EvalCustomer: name- EvalDate: date- EvalScore: number 1-10

+ validateEvaluation() : void

Testdriv e

- TestdriveDate: date- TestdriveCustomer: customer- TestdriveEmployee: employee- TestdriveCar: car


AutoPark - Logical View

Designing The System Structure

Identify entities/things used in use case• Identify attributes

• Identify operations

• Identify entity relations

• Identify multiplicity

Create class diagram



Class Diagramcd Logical Data Model - Process TestDriv e Requests

Request TestDriv e::Request

- FirstName: CHARACTER- LastName: CHARACTER- Email: CHARACTER- PhoneNumber: CHARACTER- BirthDate: DATE- LicenseDate: DATE- Brand: CHARACTER- Model: CHARACTER- Version: CHARACTER- Engine: CHARACTER- Business: LOGICAL

+ createRequest() : LOGICAL+ deleteRequest() : LOGICAL+ readRequest() : CHARACTER+ findRequest() : CHARACTER

Manage TestDriv e Appointments::TestDriv e

- Date: DATE- EvalForm: LOGICAL- currentCar: Car- currentPerson: Person

+ createTestDrive() : LOGICAL+ deleteTestDrive() : LOGICAL+ readTestDrive() : CHARACTER+ updateTestDrive() : LOGICAL+ findTestDrive() : CHARACTER+ validateTestDrive() : LOGICAL

Manage Cars::Car

- Brand: CHARACTER- Model: CHARACTER- Version: CHARACTER- Color: CHARACTER- Engine: CHARACTER- Fuel: CHARACTER- Description: CHARACTER- AvailForTD: LOGICAL- DateAdded: DATE

+ createCar() : LOGICAL+ deleteCar() : LOGICAL+ readCar() : CHARACTER+ updateCar() : LOGICAL+ findCar() : CHARACTER+ validateCar() : LOGICAL

Manage Customers::Person

- FirstName: CHARACTER- LastName: CHARACTER- PhoneNumber: CHARACTER- BirthDate: DATE- LicenseDate: DATE

+ createCustomer() : LOGICAL+ deleteCustomer() : LOGICAL+ updateCustomer() : LOGICAL+ readCustomer() : CHARACTER+ findCustomer() : CHARACTER+ validateCustomer() : LOGICAL

0..*

1

0..*

1



Patterns

"A pattern is a proven solution to a problem in a context."


Agenda

Introduction UML 2.0 Diagrams Requirements Logical View Dynamic View Implementation View Demonstration Q&A


AutoPark - Dynamic View

Describing Behavior

Identify objects involved

Identify interactions (messages)• Use public operations

Describe how things work


AutoPark - Dynamic View

Describing Behaviorsd Sequence Diagram - Process TestDrive Request (Client)

Client Server

Administrative Person

(from Actors)

Viewer Control Entity Request BE

alt valid request

[true]

[false]

«interface»

Process TestDriveRequest::IProcessTDRequest

listRequests

showSelectScreen

getRequests

getRequests

selectRequest

showRequestDetails

getRequestDetails

getRequestDetails

acceptRequest(request)

processRequest(request)

processRequest(request)

deleteRequest(request)

rejectRequest(request)




Agenda



AutoPark - Implementation Viewid Manage Customers

«Program»

proSIproxy.p

- NEW GLOBAL SHARED VARIABLE ghttProxySIproc: HANDLE

+ fetchWhere(CHARACTER, HANDLE, DATASET-HANDLE*) : void+ saveChanges(CHARACTER, HANDLE, CHARACTER*) : void

«Include»

proSIproxyStart.i

- NEW GLOBAL SHARED VARIABLE ghProxySIproc:

«Include»

dsPerson.i

- DEFINE DATASET Person:

Manage Customers::CustomerMaintenanceView

«Include»

etPerson.i

CustomerMaintenanceControl «include»

ttContext.i

CustomerMaintenanceModel

CustomerMaintenanceControl.p

+ onValueChangedBrwsCustomer() : void+ onChooseBtnAdd() : void+ onChooseBtnModify() : void+ onChooseBtnDelete() : void+ onChooseButtonOK() : void+ onChooseBtnCancel() : void+ onChooseBtnHelp() : void+ onChooseBtnDone() : void

CustomerMaintenanceModel.p

+ addCustomer() : void+ deleteCustomer() : void+ modifyCustomer() : void+ commitCustomer() : void+ getCustomer() : void

CustomerMaintenanceView.w

«includes»

«realize»

«includes»«includes»

«includes»

«realize»

«realize»

«realize PERSISTENT»

includes

Name:Package:Version:Author:

Manage CustomersManage Customers1.0Frank Beusenberg


Agenda



Demonstration


In Summary

Model & Design• Manage complexity

• Minimize risk

• Facilitate communication

Use UML• De facto standard

• Unambiguous

• Documentation


For More Information, go to…

ARCH-6: UML Modeling with Enterprise Architect

Relevant Exchange Sessions



Object Management Group• http://www.omg.org

Hillside.net Patterns Library• http://hillside.net/patterns

Relevant Web Resources



Addison-Wesley Object Technology Series

UML Distilled Third Edition• Martin Fowler – ISBN 0-321-19368-7

Use Case Driven Object Modeling with UML• Doug Rosenberg – ISBN 0-201-43289-7

Developing Software with UML• Bernd Oestereich – ISBN 0-201-75603-X

Relevant Literature


Questions?


Thank you foryour time

ARCH-2: UML 101 - From Design to Implementation using UML

Documents

Transcript of ARCH-2: UML 101 - From Design to Implementation using UML