Unit-2: Introduction To The UML Language: Standards. Elements of

Unit-2
Introduction to the UML Language
Introduction to the UML Language: Standards. Elements of

the language.
General description of various models. The process of Object

Oriented software development. Description of Design
Patterns. Technological Description of Distributed Systems.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition
Copyright © 2015 John Wiley & Sons, Inc. All rights reserved.
The Unified Process
 A specific methodology that maps out when and how to use
the various UML techniques for object-oriented analysis and
design
 A two-dimensional process consisting of phases and
workflows
 Phases are time periods in development
 Workflows are the tasks that occur in each phase
 Activities in both phases & workflows will overlap
The Unified Process
Unified Process Phases
Inception
Feasibility analyses performed
Workflows vary but focus is on business modeling &
requirements gathering
Elaboration
Heavy focus on analysis & design
Other workflows may be included
Construction: Focus on programming
(implementation)
Transition--Focus on testing & deployment
Engineering Workflows
 Business modeling
 Requirements
 Analysis
 Design
 Implementation
 Testing
 Deployment
Supporting Workflows
 Project management
 Configuration and change management
 Environment
 Operations and support*
 Infrastructure management*
* Part of the enhanced unified process
Extensions to the Unified
Process
The Unified Process does not include:
 Staffing
 Budgeting
 Contract management
 Maintenance
 Operations
 Support
 Cross- or inter-project issues
Extensions to the Unified
Process (cont.)
Add a Production Phase to address issues after
the product has been deployed
New Workflows:
 Operations & Support
 Infrastructure management
Modifications to existing workflows:
 Test workflow
 Deployment workflow
 Environment workflow
 Project Management workflow
 Configuration & change management workflow
Basic Building Blocks of UML
• Three kinds of building blocks -

– Things
– Relationships
– Diagrams
psg/9
Basic Building Blocks of UML - Things
• Things
– The abstractions that are first-class citizens in a model.
– There are four kinds of things in the UML
1. Structural
2. Behavioral
3. Grouping
4. Annotational
psg/10
Basic Building Blocks of UML – Things -
Structural
• Structural
– These are nouns of UML models which are static parts represent
elements that are either conceptual or physical.
– There are seven kinds of structural things in the UML
1. class
2. interface
3. collaboration
4. Use case
5. Active class
6. Component
7. node
psg/11
Basic Building Blocks of UML – Things –
Structural – Class, Interface
• Class
– Description of as set of objects that share same attributes,
operations, relationships, and semantics.
– Graphically, a class is rendered as a rectangle.
• interface
– A collection of operation that specify a service of a class or
component.
– Describes externally visible behavior of a class or component or
only a part of that behavior.
– Defines set of operation specifications
– Graphically, an interface is rendered as a circle.
psg/12
Structural – Collaboration
• Collaboration
– Defines an interaction and is a society of classes, interfaces and
other elements work together to provide some cooperative
behavior.
– A given class might participate in several collaborations
– Represents the implementation of patterns that make up a system
– Graphically, a collaboration is rendered as an ellipse with dashed
line, usually including only its name.
psg/13
Structural – Use case
• Use case
– It is a description of set of sequence of actions that a system
performs that yields an observable result of value to a particular
actor.
– It is used to structure the behavioral things in a model.
– It is realized by a collaboration.
– Graphically, a use case is rendered as an ellipse with solid line,
usually including only its name.
psg/14
Structural – Active class, Component
• Active Class
– The objects of active class own one or more processes or threads
so initiate control activity.
– Graphically, an active class is rendered as a rectangle with heavy
lines.
• Component
– It is a physical and replaceable part of a system that conforms to
and provides the realization of a set of interface.
– Graphically, a component is rendered as a rectangle with tabs,
usually including only its name.
psg/15
Structural – Node
• Node
– It is a physical element that exists at run time.
– It represents a computational resource.
– It has some memory and often processing capabilities.
– Graphically, a node is rendered as a cube, usually including only
its name.
psg/16
Behavioral
• Behavioral
– These are dynamic parts of UML model.
– These are verbs of a model.
– Represents behavior over time and space.
– There are two primary kinds of behavioral things
1. Interaction
2. State machine
psg/17
Behavioral - Interaction
• Interaction
– It comprises a set of messages exchanged among set of objects
within a particular context to accomplish a specific purpose.
– It includes messages, action sequences, and links.
– Graphically, a message is rendered as a directed line, usually
including name of its operation.
psg/18
Behavioral – State Machine
• State Machine
– It is a behavior that specifies the sequence of state an object or an
interaction goes through during its lifetime in response to events,
together with its responses to those events.
– It includes events and activities.
– Graphically, a state is rendered as a rounded rectangle, usually
including its name and its substates.
psg/19
• Grouping
Grouping
– These are the organizational parts of UML model.
– There is one primary kind of grouping thing, namely, packages.
– Package
– It is a general purpose mechanism for organizing element into
groups.
– Structural, behavioral and grouping things may be placed in a
package.
– Graphically, a package is rendered as a tabbed folder, usually
including only its name and sometimes its contents.
psg/20
Annotational
• Annotational
– These are the explanatory parts of UML model.
– These are the comments.
– There is one primary kind of annotational thing, called a note.
– Note
– It’s a symbol for rendering constraints and comments attached to
an element or a collection of elements.
– Graphically, a note is rendered as a rectangle with a dog-eared
corner, together with a textual or graphical comment.
psg/21
Basic Building Blocks of UML –
Relationships
• Relationships
– It tie things together.
– There are four kinds of relationships in the UML.
1. Dependency
2. Association
3. Generalization
4. realization
psg/22
Relationships - Dependency
• Dependency
– It is a semantic relationship between two things in which a change
to one thing may affect the semantics of the other things.
– Graphically, a dependency is rendered as a dashed line, possibly
directed, and occasionally including a label.
psg/23
Relationships - Association
• Association
– It is a structural relationship that describes a set of links, a link
being a connection among objects.
– Aggregation is a special kind of association representing a
structural relationship between a whole and its parts.
– Graphically, an association is rendered as a solid line, possibly
directed, occasionally including a label, and often containing
multiplicity and role names.
psg/24
Association
1 Guides *
Teacher Student
Aggregation
1 *
Institute Department
psg/25
• An association is a bi-directional connection between classes
– An association is shown as a line connecting the related classes
• An aggregation is a stronger form of relationship where the relationship is between
a whole and its parts
– An aggregation is shown as a line connecting the related classes with a diamond
next to the class representing the whole
• A dependency relationship is a weaker form of relationship showing a relationship
between a client and a supplier where the client does not have semantic knowledge
of the supplier
• A dependency is shown as a dashed line pointing from the client to the supplier
psg/26
Relationships - contd..
 An association class is an association that also has class
properties(or a class has association properties)
 A constraint is a semantic relationship among model elements that
specifies conditions and propositions that must be maintained as
true: otherwise, the system described by the model is invalid
 An interface is a specifier for the externally visible operations of a
class without specification of internal structure. An interface is
formally equivalent to abstract class with no attributes and methods,
only abstract operations.
 A qualifier is an attribute or set of attributes whose values serve to
partition the set of instances associated with an instance across an
association.
psg/27
Association
1 Guides *
Teacher Student
Guide RS
Navigation
Aggregation
1 *
Institute Department
psg/28
Aggregation Vs Composition
1 *
Page Frame
Window
Menu Header Slider
psg/29
Dependency
uses
Window Button
access
Employee Salary
psg/30
Association Classes
1 Teaches *
Teacher Course
Offering
No of students
Venue
Slot number
1 employs *
Company Employee
Job
Designation
Salary
psg/31
Relationships - Generalization
• Generalization
– It is a specialization/generalization relationship in which objects
of the specialized elements are substitutable for objects of the
generalized element.
– The child share the structure and the behavior of the parent.
– Graphically, a generalization is rendered as a solid line with a
hollow arrowhead pointing to the parent.
psg/32
Generalization/Specialization
Superclass, Subclass, or Inheritance comes into picture in

generalization/Specialization.
psg/33
Generalization/Specialization..Continued
Bees and grasshoppers are specialized versions of an insect
psg/34
Relationships - Realization
• Realization
– It is a semantic relationship between classifier, wherein one
classifier specifies a contract that another classifier guarantees to
carry out.
– Realization encounter in two places –
• Between interfaces and the classes or components that realize them
• Between use cases and the collaborations that realize them.
psg/35
Realization
<interface>
Iaccount
AccountImpl
Deposit()
withdraw()
psg/36
Basic Building Blocks of UML – Diagrams
• Diagrams
– It is the graphical presentation of a set of elements, most often
rendered as a connected graph of vertices (things) and arcs
(relationships).
– UML includes nine different diagrams.
psg/37
Summary
• All systems development projects follow essentially the
same process, called the system development life cycle
(SDLC)
• System development methodologies are formalized
approaches to implementing SDLCs
• The systems analyst needs a variety of skills and plays
a number of different roles
• Object-oriented systems differ from traditional systems
Summary
Object-Oriented Systems Analysis and Design
(OOSAD) uses a use-case-driven, architecture-
centric, iterative, and incremental information
systems development approach
The Unified Process is a two-dimensional systems
development process described with a set of phases
and workflows
The Unified Modeling Language, or UML, is a
standard set of diagramming techniques
Standards
Design Patterns
 Pattern is simply a useful group of collaborating patterns that

provide solutions to a common problem
 Patterns provide solution to a common problem, they are
reusable
Singleton
Factory
Adapter
Why study design patterns
• Experts in software architecture and design are highly paid, because they
know how to create designs that are flexible, elegant, and reusable.
• You become an expert through experience, reusing solutions that worked for
you before.
• Patterns describe solutions to design problems that occur over and over
again.
• Patterns also record design decisions, alternatives, and trade-offs gained

from experience.
• Once you know the pattern, many design decisions follow.
• Knowing patterns helps you get designs right faster.
• Knowing the vocabulary surrounding patterns helps communication between

designers, and can ease the documentation effort.
Singleton
Singleton pattern: Ensures that only one
instantiation is created and avoids creating
multiple instances of the same object.
Factory
 Delegates object creation to the factory class so it hides the
creation logic.
Adapter
 Adapter pattern works as a bridge between two
incompatible interfaces. This type of design pattern
comes under structural pattern as this pattern combines
the capability of two independent interfaces.
Distributed System
 A distributed system is a collection of Independent computers
that appears to its users as a single system
Examples: Internet, LAN, WAN, Intranets, Mobile Computing,
Ubiquitous computing, Pervasive Systems

Unit-2: Introduction To The UML Language: Standards. Elements of

Uploaded by

Copyright:

Available Formats

Unit-2: Introduction To The UML Language: Standards. Elements of

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unit-2: Introduction To The UML Language: Standards. Elements of

Uploaded by

Copyright:

Available Formats

Unit-2

Introduction to the UML Language

Introduction to the UML Language: Standards. Elements of

General description of various models. The process of Object

* Part of the enhanced unified process

• Three kinds of building blocks -

Menu Header Slider

Superclass, Subclass, or Inheritance comes into picture in

Bees and grasshoppers are specialized versions of an insect

 Pattern is simply a useful group of collaborating patterns that

• Patterns also record design decisions, alternatives, and trade-offs gained

• Once you know the pattern, many design decisions follow.

• Knowing patterns helps you get designs right faster.

• Knowing the vocabulary surrounding patterns helps communication between

Examples: Internet, LAN, WAN, Intranets, Mobile Computing,

Ubiquitous computing, Pervasive Systems

You might also like