Business Systems Analysis - Part II

Business Systems Analysis

Overview Part II

by Vinil Gupta

Vinil Gupta Business Systems Analysis Part II 2

Two aspect of UML

Static Structure

Dynamic Behaviour


UML Diagrams OverviewDiagram

Structure Diagram

BehaviourDiagram

Component Diagram

Class Diagram

Object Diagram

Profile Diagram

Composite Structure Diagram

Deployment Diagram

Package Diagram

Activity Diagram

Use Case Diagram

Interaction Diagram

State Machine Diagram

Interaction Overview Diagram

Timing Diagram

Communication Diagram

Sequence Diagram

UML Diagrams Overview


Use CasesUse Cases, Business Use Cases, Systems

Use Cases – OOAD Use Case ID Use Case Description Pre and Post Conditions Assumptions Main flow or Basic Flow Alternate Flows Exception Flows Business Rules Issues and Risks


Object Constraint Language (OCL) OCL is used for applying constraints

and business rules.


Unified Modelling Language (UML) OOAD Project Scope – user goals and system

interaction Use Case Diagram – Actors, Uses, Extends Class Diagram – Business Object Models

Associations, Attributes, Operations, Generalization, Constraint Rules, Aggregation and Composition


Unified Modelling Language (UML) Sequence Diagram Collaboration Diagrams Package Diagrams State Diagrams Activity Diagrams Deployment Diagrams


UML: Associations Description of a set of link

between objects A change to a thing affects the

semantics of a dependent thing One element is a specialisation

of another; substituted more general element

One classifier specifies a contract that the other classifier guarantees to carry out

Association

Dependency

Generalisation

Realisation


Class Name

Class

Class Name

Attribute: Type = initialValue

Operation(arg list): return type

Class A Class Arole A

role B

Association

Multiplicities

Class

Class

Class

Class

1

*

0..1

Exactly one

Many (zero or more)

Optional (zero or one)

Numerically specified

m..n

Class

Class

Class

aggregation

composition

{ordered} * ordered role

Generalization

Supertype

Subtype 1 Subtype 2

discrimnator


Class

Qualified Association

qualifer

Navigability

Source Targetrole name

Class A Class B

Dependency

Constraint{description of constraint}

Stereotype<<stereotype name>>

note text

Note

Object

object name: Class Name


Class Diagram: Interfaces

Abstract Class{abstract}

Implementing Class

<<interface>>Type

Client of Type

Client Classdependency

Interface Name

Implementing Class


Class Diagram: Parameterized Class

Set

Ttemplate class

Set<Integer>

bound element

Association Class

Class Class

AssociationClass


Activity Activity

Activity Activity

Activity

[Condition 1]

[Condition 2]

* [for all thingies]

[synchronization condition]

Activity Diagram


Package Name

Class 1

Class 2

Class 3

Package Name

dependency

Package Diagram


Use Case Diagram

Use Case

<<Includes>>

<<extends>>


an Object

new Object

message

create

Self-delegation

return

delete

Sequence Diagram


Node

Component 2

Component 1

Deployment Diagram


object name: class

: class

1: simple message()

role name

object namerole name

1.1*: iteration message()1.2: [condition] message ()

asynchronous message

Collaboration Diagram


Superstate Name

Concurrent State

State State

State State


Superstate Name

State Name

Variable:Type = initial value

Entry / Actiondo / activityexit / action

event / action (arguments)

State Name

event(arguments)[condition]/ action

State Diagram


UML Common MechanismUML has four common mechanism

1. Specifications2. Adornments3. Common divisions4. Extensibility mechanism


1.SpecificationSpecifications are the meat of the UML model.

They provide the semantic backplane of the model. UML model has at least two dimensions

1. Graphic dimensions – diagram

2. Textural dimensions – specifications textual descriptions of the semantics of an element


1.Specification

UML models may be: Elided – some elements from diagrams to

simplify the view Incomplete – some elements may be

missing entirely Inconsistent – model may contain

contradictions

BankAccount

nameaccountNumber

deposite()withdraw()calculateInterest()

Icon or modelling element

Semantic BackplaneClass Specification

Use Case specification

Dependency specification

Deposit


Questions and Answers

Documents

Business Systems Analysis - Part II