communication and confrence media
TRANSCRIPT
-
8/9/2019 communication and confrence media
1/62
1
-
8/9/2019 communication and confrence media
2/62
INDEXS.No Topics Page NO
1. Abstract 01
2. Problem Statement 02
3. Proposed Statement 03
4. Introduction to UML 04
5. Software Requirement Specification 08
6. Class Diagram 46
7. Use Case Diagram 48
8. Sequence Diagram 51
9. Collaboration Diagram 52
10. Activity Diagram 54
11. Activity Diagram with Swin lane Diagram 56
12. State Chart Diagram 57
13. Component Diagram 59
14. Deployment Diagram 61
ABSTRACT
2
-
8/9/2019 communication and confrence media
3/62
COMUNNICATION AND CONFRENCE
Communication:
Communication is a process of transferring information from one
entity to another. Communication processes are sign-mediated interaction
between at least two agents which share a repertoire of signs and semiotic
rules. Communication is commonly define as the important or interchange
of thoughts, opinions or information by speech, writing or signs. Although
there is such a thing as one-way communication, Communication can be
perceived better as a two way process in which there is a exchange and
progression of thoughts, feeling or ideas towards a mutually accepted goal or
direction
PROBLEM STATEMENTIn the process of running large industrial business or when people are stayed
in different countries wants to conduct the meetings. It is highly impossible
for them to exchange this information at a time by many people from many
countries. They can use cell phones, telephones but it is costly therefore if
there is a gap in the communication it will directly effects on the business.
PROPOSED SYSTEMSThe Communication and conference media provides a best solution for
conference meetings collected by the companies with their clients and their
employees. The person who wants to communicate should have to register
first then he should send a request for inviting them and then he is able to
Communicate or join a conference.
COMMUNICATION AND CONFRENCE MEDIA
Communication processes are sign-mediated interaction between at least two
agents which share a repertoire of signs and semiotic rules. Communication
3
-
8/9/2019 communication and confrence media
4/62
is commonly define as the important or interchange of thoughts, opinions
or information by speech, writing or signs. Although there is such a thing
as one-way communication.1. Introduction
1.1 Purpose
1.2 Scope1.3 Definitions, acronyms and abbreviations1.4References1.5 Overview
2. Overall Description2.1 Product perspective2.2 Product functions2.3 User characteristics2.4 Constraints2.5 Assumptions and dependencies
3. Specific Requirements3.1 Interface Requirements
3.1.1 User interfaces3.1.2 Hard interfaces3.1.3 Software interfaces
3.1.4 Communication interfaces
3.2 Functional Requirements3.2.1 Information flows3.2.2 Process description3.2.3 Data construct specification
3.3 Performance requirements
3.4 Logical data base requirements3.5 Quality attributes3.6 Organizing the specific requirements
1. Introduction:1The introduction of an communication identifies the purpose, scope, definitions,acronyms, abbreviation, references and overview of the requirements of thedocuments.
4
-
8/9/2019 communication and confrence media
5/62
Communication processes are sign-mediated interaction between at least twoagents which share a repertoire of signs and semiotic rules. The purpose the oftransferring information from one entity to another.
Purpose
The purpose of communication is to exchange their thought between oneanother. Communication is commonly define as the important or interchange ofthoughts, opinions or information by speech, writing or signs. Although there issuch a thing as one-way communication, Communication can be perceivedbetter as a two way process in which there is a exchange and progression ofthoughts, feeling or ideas towards a mutually accepted goal or direction
ScopeThe scope of communication identifies the software product to be produced, thecapabilities, objectives and applications etc.The software product to be produced is communication and conference the main
objective of this system is to allow access of an employee of a firm to differentsections of the premises.It is an independent application which can run on windows operating system.-Keeping in touch with all known-Keeping the status check on the subscriber-Allow subscriber to make a chat, call, conference etc while not in the homemarket.-The system can even share the file between subscribers.-The system maintain the subscribers profile through which new friends can beadded.
1.3 Definitions, Acronyms and AbbreviationsUser : A person who had an account in that system.SRS Software Requirements SpecificationStd StandardIEEE Institute of Electrical and Electronic EngineersJVM Java Virtual MachinePHP Hyper Text Preprocessor
1.4 References
IEEE std. 830-1993, IEEE Recommended practice for software requirementsspecifications.Software engineering- A practitioners Approach By Rogers Pressman.
1.5 Overview
5
-
8/9/2019 communication and confrence media
6/62
This section provides the road map for the SRS. The other part of the SRScontains the product functions, the constraints on the system which includesassumptions and redundancies.The SRS also contain the details of process and data requirements.Communication and conference provide interface to the user and also contains
scanners to scan id-card, fingerprints, retina and heartbeat also contains the database of the employees working in the firm.
2. Overall DescriptionThe main functions associated with this project are described in this section ofthe SRS. The characteristics of a user for this project are indicated. Theassumptions, constraints and dependencies are described in this section.
2.1 Product PerspectiveThe communication and conference system is an interactive tool for anyorganization. It is intended to be used by both the user and the end-user toaccess different sections in the communication.2.2 Product Functions
This communication and conference system is helpful for people assure theorganization to interact with each other. It is an important service to theorganization and it saves the time and overhead involved in communicating witheach other.
2.3 User CharacteristicsThe users of communication and conference system should be authorized users.The user will need to understand and use the system effectively. The user musthave basic knowledge of windows environment and must be familiar to with PC.
2.4 ConstraintsThis system developed will be user friendly and easy to use by novices as wellas professionals.The system requires a minimum hardware for running windows OS.
2.5 Assumptions and DependenciesThe system is dependent on JVM enabled operating system with a properdatabase and other hardware devices like microphone and speakers.3. Specific RequirementsThis section of the SRS provides a description of the observable of a softwaresystem. It also includes a description of the entire system.
3.1 Interface Requirements
3.1.1 User InterfacesThe user interface will be a java enabled window and also interfaces are alsopresent for different scanners.
3.1.2 Hard InterfacesIn hardware interfaces the logical characteristics of each interface betweensoftware and hardware on which the software can run are specified. Theproposed system can use the existing hardware specifications of communicationand conference system.
6
-
8/9/2019 communication and confrence media
7/62
3.1.3 Software InterfaceJava Development Kit (JDK 1.5) or above from Sun Micro Systems, SQL
Database.
3.1.4 Communication InterfacesThe system has a interface with touch enabled display to perform the required
operations.
3.2 Functional Requirements3.2.1 Information flowsData flow diagrams describe the process of availing the services by the system.
3.2.2 Process DescriptionA sample process description based on the process information (input, actionoutput) is given below.Inputs: register to account, enter the id and password.Action: Verify the id and passwordOutput: gives the series of action that is give the communicating operations.
3.2.3 Data Construct SpecificationData constructs are prepared for each piece of data referenced in the data flowdiagrams and process descriptions.
3.3Performance RequirementsThe proposed system provides any number of simultaneous users to access thesystem. But ensures that the actions taken are atomic and leaves the databaseof system in a consistent state. There are no such criteria of priority of the arrival.
Logical Database Requirements
All the data is given to perform the action that is call option video option share
the files ect.
3.4Quality Attribute
Issues such as security, availability, reliability, maintainability are truly maintained toa maximum extent in this system.
3.6 Organizing Specific Attributes
Every major activity of the system will have a Dataflow Diagram (DFD
UNIFIED MODELING LANGUAGEIntroduction:
7
-
8/9/2019 communication and confrence media
8/62
The unified modeling language(UML)is a standard language for writing software blue
prints.The UML is a language for
Visualizing Specifying
Constructing
Documenting
The artifacts of a software system:
UML is a language that provides vocabulary and the rules for combing words in thatvocabulary for the purpose of communication.
A modeling language is a language whose vocabulary and rules focus on the concept
and physical representation of a system.
Vocabulary and rules of a language tell us how to create and real well formedmodels, but they dont tell you what mode you should create and when should create
them.
VISUALIZING
The UML is more than just a bunch of graphical symbols. In UML each symbol has well
defined semantics. In this manner one developer can write a model in the UML and
another developer or even another tools can interpret the model unambiguously.
SPECIFYING
UML is used fro specifying means building models that are precise, unambiguous andcomplete.
UML addresses the specification of all the important analysis, design and implementation
decisions that must be made in developing and deploying a software intensive system.
CONSTRUCTING
UML is not a visual programming language but its models can be directly connected to avariety of programming languages.
This means that it is possible to map from a model in the
UML to a programming language such as java, c++ or Visual Basic or even to tables in a
relational database or the persistent store of an object-oriented database.This mapping permits forward engineering. The generation
of code from a UML model into a programming language.
The reverse engineering is also possible you canreconstruct a model from an implementation back into the UML.
DOCUMENTING
8
-
8/9/2019 communication and confrence media
9/62
UML is a language for Documenting. A software organization produces all sorts of
artifacts in addition to raw executable code. These artifacts includeRequirements,Architecture,Design,Sourcecode,Project plans,Test,Prototype,Release.
Such artifacts are not only the deliverables of a project,they are also critical in
controlling,measuring and communicating about a system during its development andafter its deployment.
Conceptual model of the UML:
To understand the UML, we need to form a conceptual model of the language and this
requires learning three major elements.
The UML Basic Building Blocks.The Rules that direct how those building blocks may be put together.
Some common mechanisms that apply throughout the UML.
As UML describes the real time systems it is very important to make a conceptual modeland then proceed gradually. Conceptual model of UML can be mastered by learning the
following three major elements:
UML building blocks
Rules to connect the building blocks
Common mechanisms of UML
This chapter describes all the UML building blocks. The building blocks of UML can be
defined as:
Things Relationships
Diagrams
Things:
Things are the most important building blocks of UML. Things can be:
Structural
Behavioral
Grouping
Annotational
Structural things:The Structural things define the static part of the model. They represent physical and
conceptual elements. Following are the brief descriptions of the structural things.
Class:
9
-
8/9/2019 communication and confrence media
10/62
Class represents set of objects having similar responsibilities.
Interface:
Interface defines a set of operations which specify the responsibility of a class.
Collaboration:
Collaboration defines interaction between elements.
Use case:
Use case represents a set of actions performed by a system for a specific goal.
Component:
10
-
8/9/2019 communication and confrence media
11/62
Component describes physical part of a system.
Node:
A node can be defined as a physical element that exists at run time.
Behavioral things:
Abehavioral thing consists of the dynamic parts of UML models. Following are the
behavioral things:
Interaction:
Interaction is defined as a behavior that consists of a group of messages exchanged
among elements to accomplish a specific task.
State machine:
11
-
8/9/2019 communication and confrence media
12/62
State machine is useful when the state of an object in its life cycle is important. It defines
the sequence of states an object goes through in response to events. Events are external
factors responsible for state change.
Grouping things:Grouping things can be defined as a mechanism to group elements of a UML modeltogether. There is only one grouping thing available.
Package:
Package is the only one grouping thing available for gathering structural and behavioral
things.
Annotational things:
Annotational things can be defined as a mechanism to capture remarks, descriptions, and
comments of UML model elements. Note is the only one Annotational thing available.
Note:
A note is used to render comments, constraints etc of an UML element.
RELATIONSHIP IN UML
12
-
8/9/2019 communication and confrence media
13/62
Relationship is another most important building block of UML. It shows how elements
are associated with each other and this association describes the functionality of an
application.There are four kinds of relationships available.
Dependency:
Dependency is a relationship between two things in which change in one element also
affects the other one.
Association:
Association is basically a set of links that connects elements of an UML model. It alsodescribes how many objects are taking part in that relationship.
Generalization:
Generalization can be defined as a relationship which connects a specialized element with
a generalized element. It basically describes inheritance relationship in the world ofobjects.
Realization:
Realization can be defined as a relationship in which two elements are connected. One
element describes some responsibility which is not implemented and the other one
implements them. This relationship exists in case of interfaces.
UML DIAGRAMS:
13
-
8/9/2019 communication and confrence media
14/62
UML diagrams are the ultimate output of the entire discussion. All the elements,
relationships are used to make a complete UML diagram and the diagram represents asystem.
The visual effect of the UML diagram is the most important part of the entire process. All
the other elements are used to make it a complete one.UML includes the following nine diagrams and the details are described in the following
chapters.
Class diagram
Object diagram
Use case diagram
Sequence diagram
Collaboration diagram
Activity diagram
Statechart diagram
Deployment diagram
Component diagram
We would discuss all these diagrams in subsequent chapters of this tutorial.
ARCHITECTURE OF UML
Any real world system is used by different users. The users can be developers, testers,business people, analysts and many more. So before designing a system the architecture
is made with different perspectives in mind. The most important part is to visualize the
system from different viewer.s perspective. The better we understand the better we makethe system.
UML plays an important role in defining different perspectives of a system. These
perspectives are:
Design
Implementation
Process
Deployment
And the centre is the Use Case view which connects all these four. A Use case representsthe functionality of the system. So the other perspectives are connected with use case.
Design of a system consists of classes, interfaces and collaboration. UML provides classdiagram, object diagram to support this.
14
-
8/9/2019 communication and confrence media
15/62
Implementation defines the components assembled together to make a complete
physical system. UML component diagram is used to support implementation
perspective.
Process defines the flow of the system. So the same elements as used inDesign are also
used to support this perspective.
Deployment represents the physical nodes of the system that forms the hardware. UML
deployment diagram is used to support this perspective.
CLASS DIAGRAMOverview:
The class diagram is a static diagram. It represents the static view of an application. Classdiagram is not only used for visualizing, describing and documenting different aspects of
a system but also for constructing executable code of the software application.
The class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the modellingof object oriented systems because they are the only UML diagrams which can be
mapped directly with object oriented languages.The class diagram shows a collection of classes, interfaces, associations, collaborationsand constraints. It is also known as astructural diagram.
Purpose:
The purpose of the class diagram is to model the static view of an application. The class
diagrams are the only diagrams which can be directly mapped with object orientedlanguages and thus widely used at the time of construction.
The UML diagrams like activity diagram, sequence diagram can only give the sequence
flow of the application but class diagram is a bit different. So it is the most popular UML
diagram in the coder community.So the purpose of the class diagram can be summarized as:
Analysis and design of the static view of an application.
Describe responsibilities of a system.
Base for component and deployment diagrams.
Forward and reverse engineering.
15
-
8/9/2019 communication and confrence media
16/62
How to draw Class Diagram?Class diagrams are the most popular UML diagrams used for construction of softwareapplications. So it is very important to learn the drawing procedure of class diagram.
Class diagrams have lot of properties to consider while drawing but here the diagram will
be considered from a top level view.Class diagram is basically a graphical representation of the static view of the system and
represents different aspects of the application. So a collection of class diagrams represent
the whole system.The following points should be remembered while drawing a class diagram:
The name of the class diagram should be meaningful to describe the aspect of the system.
Each element and their relationships should be identified in advance.Responsibility (attributes and methods) of each class should be clearly identified.
For each class minimum number of properties should be specified. Because unnecessary
properties will make the diagram complicated.
Use notes when ever required to describe some aspect of the diagram. Because at the end
of the drawing it should be understandable to the developer/coder.Finally, before making the final version, the diagram should be drawn on plain paper and
rework as many times as possible to make it correct.Now the following diagram is an example of an Order System of an application. So it
describes a particular aspect of the entire application.
First of all Orderand Customerare identified as the two elements of the system and theyhave a one to many relationship because a customer can have multiple orders.
We would keep Orderclass is an abstract class and it has two concrete classes
(inheritance relationship) SpecialOrderandNormalOrder.
The two inherited classes have all the properties as the Orderclass. In addition they haveadditional functions like dispatch () and receive ().
So the following class diagram has been drawn considering all the points mentionedabove:
16
-
8/9/2019 communication and confrence media
17/62
Where to use Class Diagrams?
Class diagram is a static diagram and it is used to model static view of a system. Thestatic view describes the vocabulary of the system.
Class diagram is also considered as the foundation for component and deployment
diagrams. Class diagrams are not only used to visualize the static view of the system but
they are also used to construct the executable code for forward and reverse engineering ofany system.
Generally UML diagrams are not directly mapped with any object oriented programminglanguages but the class diagram is an exception.Class diagram clearly shows the mapping with object oriented languages like Java, C++
etc. So from practical experience class diagram is generally used for construction
purpose.
So in a brief, class diagrams are used for:
Describing the static view of the system.
Showing the collaboration among the elements of the static view.
Describing the functionalities performed by the system.
Construction of software applications using object oriented languages.
OBJECT DIAGRAM
Object diagram shows a set of objects and there relationships.Object diagramrepresents static snapshot of instances of the things found in class diagram.
These diagrams addresses static design view or static process view of a system.
17
-
8/9/2019 communication and confrence media
18/62
USE CASE DIAGRAM
Overview:
To model a system the most important aspect is to capture the dynamic behaviour. To
clarify a bit in details, dynamic behaviourmeans the behaviour of the system when it isrunning /operating.
So only static behaviour is not sufficient to model a system rather dynamic behaviour is
more important than static behaviour. In UML there are five diagrams available to modeldynamic nature and use case diagram is one of them. Now as we have to discuss that theuse case diagram is dynamic in nature there should be some internal or external factors
for making the interaction.
These internal and external agents are known as actors. So use case diagrams are consistsof actors, use cases and their relationships. The diagram is used to model the
system/subsystem of an application. A single use case diagram captures a particular
functionality of a system.So to model the entire system numbers of use case diagrams are used.
Purpose:
The purpose of use case diagram is to capture the dynamic aspect of a system. But this
definition is too generic to describe the purpose.
Because other four diagrams (activity, sequence, collaboration and Statechart) are alsohaving the same purpose. So we will look into some specific purpose which will
distinguish it from other four diagrams.
Use case diagrams are used to gather the requirements of a system including internal andexternal influences. These requirements are mostly design requirements. So when a
18
-
8/9/2019 communication and confrence media
19/62
system is analyzed to gather its functionalities use cases are prepared and actors are
identified.
Now when the initial task is complete use case diagrams are modelled to present theoutside view.
So in brief, the purposes of use case diagrams can be as follows:
Used to gather requirements of a system. Used to get an outside view of a system.
Identify external and internal factors influencing the system.
Show the interacting among the requirements are actors.
How to draw Component Diagram?
Use case diagrams are considered for high level requirement analysis of a system. So
when the requirements of a system are analyzed the functionalities are captured in use
cases.
So we can say that uses cases are nothing but the system functionalities written in an
organized manner. Now the second things which are relevant to the use cases are theactors. Actors can be defined as something that interacts with the system.
The actors can be human user, some internal applications or may be some externalapplications. So in a brief when we are planning to draw an use case diagram we should
have the following items identified.
Functionalities to be represented as an use caseActors
Relationships among the use cases and actors.
Use case diagrams are drawn to capture the functional requirements of a system. So after
identifying the above items we have to follow the following guidelines to draw anefficient use case diagram.The name of a use case is very important. So the name should be chosen in such a way so
that it can identify the functionalities performed.
Give a suitable name for actors.Show relationships and dependencies clearly in the diagram.
Do not try to include all types of relationships. Because the main purpose of the diagram
is to identify requirements.Use note when ever required to clarify some important points.
The following is a sample use case diagram representing the order management system.
So if we look into the diagram then we will find three use cases (Order, SpecialOrder and
NormalOrder) and one actor which is customer.The SpecialOrderandNormalOrderuse cases are extended from Orderuse case. So they
have extends relationship. Another important point is to identify the system boundary
which is shown in the picture. The actorCustomerlies outside the system as it is anexternal user of the system.
19
-
8/9/2019 communication and confrence media
20/62
INTERACTION DIAGRAMWe have two types of interaction diagrams in UML. One is sequence diagram and theother is a collaboration diagram. The sequence diagram captures the time sequence of
message flow from one object to another and the collaboration diagram describes the
organization of objects in a system taking part in the message flow.
So the following things are to identified clearly before drawing the interaction diagram:
Objects taking part in the interaction.
Message flows among the objects.
The sequence in which the messages are flowing.
Object organization.
Following are two interaction diagrams modeling order management system. The first
diagram is a sequence diagram and the second is a collaboration diagram.
The Sequence Diagram:
The sequence diagram is having four objects (Customer, Order, SpecialOrder and
NormalOrder).
The following diagram has shown the message sequence forSpecialOrderobject and thesame can be used in case ofNormalOrderobject. Now it is important to understand the
time sequence of message flows. The message flow is nothing but a method call of an
object.
20
-
8/9/2019 communication and confrence media
21/62
The first call issendOrder () which is a method ofOrderobject. The next call is confirm() which is a method ofSpecialOrderobject and the last call isDispatch () which is a
method ofSpecialOrderobject. So here the diagram is mainly describing the methodcalls from one object to another and this is also the actual scenario when the system is
running.
The Collaboration Diagram:
The second interaction diagram is collaboration diagram. It shows the object organization
as shown below. Here in collaboration diagram the method call sequence is indicated by
some numbering technique as shown below. The number indicates how the methods are
called one after another. We have taken the same order management system to describe
the collaboration diagram.The method calls are similar to that of a sequence diagram. But the difference is that the
sequence diagram does not describe the object organization where as the collaborationdiagram shows the object organization.
Now to choose between these two diagrams the main emphasis is given on the type of
requirement. If the time sequence is important then sequence diagram is used and iforganization is required then collaboration diagram is used.
21
-
8/9/2019 communication and confrence media
22/62
Where to use Interaction Diagrams?
We have already discussed that interaction diagrams are used to describe dynamic nature
of a system. Now we will look into the practical scenarios where these diagrams are used.
To understand the practical application we need to understand the basic nature of
sequence and collaboration diagram.The main purposes of both the diagrams are similar as they are used to capture the
dynamic behaviour of a system. But the specific purposes are more important to clarify
and understood.Sequence diagrams are used to capture the order of messages flowing from one object to
another. And the collaboration diagrams are used to describe the structural organizations
of the objects taking part in the interaction. A single diagram is not sufficient to describethe dynamic aspect of an entire system so a set of diagrams are used to capture is as a
whole.
The interaction diagrams are used when we want to understand the message flow and the
structural organization. Now message flow means the sequence of control flow from oneobject to another and structural organization means the visual organization of the
elements in a system.
In a brief the following are the usages of interaction diagrams:
To model flow of control by time sequence.
To model flow of control by structural organizations.
For forward engineering. For reverse engineering.
22
-
8/9/2019 communication and confrence media
23/62
STATE CHART DIAGRAM
Overview:
The name of the diagram itself clarifies the purpose of the diagram and other details. Itdescribes different states of a component in a system. The states are specific to a
component/object of a system.
A Statechart diagram describes a state machine. Now to clarify it state machine can bedefined as a machine which defines different states of an object and these states are
controlled by external or internal events.
Activity diagram explained in next chapter, is a special kind of a Statechart diagram. AsStatechart diagram defines states it is used to model lifetime of an object.
Purpose:
Statechart diagram is one of the five UML diagrams used to model dynamic nature of asystem. They define different states of an object during its lifetime. And these states are
changed by events. So Statechart diagrams are useful to model reactive systems. Reactivesystems can be defined as a system that responds to external or internal events.
Statechart diagram describes the flow of control from one state to another state. States aredefined as a condition in which an object exists and it changes when some event is
triggered. So the most important purpose of Statechart diagram is to model life time of an
object from creation to termination.Statechart diagrams are also used for forward and reverse engineering of a system. But
the main purpose is to model reactive system.
Following are the main purposes of using Statechart diagrams:
To model dynamic aspect of a system.
To model life time of a reactive system. To describe different states of an object during its life time.
Define a state machine to model states of an object.
How to draw Component Diagram?
Statechart diagram is used to describe the states of different objects in its life cycle. So
the emphasis is given on the state changes upon some internal or external events. Thesestates of objects are important to analyze and implement them accurately.
Statechart diagrams are very important for describing the states. States can be identifiedas the condition of objects when a particular event occurs.
Before drawing a Statechart diagram we must have clarified the following points:
Identify important objects to be analyzed.
Identify the states.
Identify the events.
23
-
8/9/2019 communication and confrence media
24/62
The following is an example of a Statechart diagram where the state ofOrderobject is
analyzed.
The first state is an idle state from where the process starts. The next states are arrived forevents likesend request, confirm request, and dispatch order. These events are
responsible for state changes of order object.
During the life cycle of an object (here order object) it goes through the following statesand there may be some abnormal exists also. This abnormal exit may occur due to some
problem in the system. When the entire life cycle is complete it is considered as the
complete transaction as mentioned below.The initial and final state of an object is also shown below.
Where to use Interaction Diagrams?
From the above discussion we can define the practical applications of a Statechart
diagram. Statechart diagrams are used to model dynamic aspect of a system like other
four diagrams disused in this tutorial. But it has some distinguishing characteristics formodeling dynamic nature.
Statechart diagram defines the states of a component and these state changes are dynamic
in nature. So its specific purpose is to define state changes triggered by events. Events are
internal or external factors influencing the system.
Statechart diagrams are used to model states and also events operating on the system.When implementing a system it is very important to clarify different states of an object
during its life time and statechart diagrams are used for this purpose. When these statesand events are identified they are used to model it and these models are used during
implementation of the system.
If we look into the practical implementation of Statechart diagram then it is mainly usedto analyze the object states influenced by events. This analysis is helpful to understand
the system behaviour during its execution.
24
-
8/9/2019 communication and confrence media
25/62
So the main usages can be described as:
To model object states of a system.
To model reactive system. Reactive system consists of reactive objects. To identify events responsible for state changes.
Forward and reverse engineering.
ACTIVITY DIAGRAMOverview:
Activity diagram is another important diagram in UML to describe dynamic aspects ofthe system.
Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system.So the control flow is drawn from one operation to another. This flow can be sequential,
branched or concurrent. Activity diagrams deals with all type of flow control by using
different elements like fork, join etc.
25
-
8/9/2019 communication and confrence media
26/62
Purpose:
The basic purposes of activity diagrams are similar to other four diagrams. It captures thedynamic behaviour of the system. Other four diagrams are used to show the message
flow from one object to another but activity diagram is used to show message flow from
one activity to another.Activity is a particular operation of the system. Activity diagrams are not only used for
visualizing dynamic nature of a system but they are also used to construct the executable
system by using forward and reverse engineering techniques. The only missing thing inactivity diagram is the message part.
It does not show any message flow from one activity to another. Activity diagram is some
time considered as the flow chart. Although the diagrams looks like a flow chart but it is
not. It shows different flow like parallel, branched, concurrent and single.So the purposes can be described as:
Draw the activity flow of a system.
Describe the sequence from one activity to another.
Describe the parallel, branched and concurrent flow of the system.How to draw Component Diagram?
Activity diagrams are mainly used as a flow chart consists of activities performed by thesystem. But activity diagram are not exactly a flow chart as they have some additional
capabilities. These additional capabilities include branching, parallel flow, swimlane etc.
Before drawing an activity diagram we must have a clear understanding about theelements used in activity diagram. The main element of an activity diagram is the activity
itself. An activity is a function performed by the system. After identifying the activities
we need to understand how they are associated with constraints and conditions.
So before drawing an activity diagram we should identify the following elements:
Activities
Association Conditions
Constraints
Once the above mentioned parameters are identified we need to make a mental layout of
the entire flow. This mental layout is then transformed into an activity diagram.The following is an example of an activity diagram for order management system. In the
diagram four activities are identified which are associated with conditions. One important
point should be clearly understood that an activity diagram cannot be exactly matchedwith the code. The activity diagram is made to understand the flow of activities and
mainly used by the business users.
The following diagram is drawn with the four main activities:
Send order by the customer Receipt of the order
Confirm order
Dispatch orderAfter receiving the order request condition checks are performed to check if it is normal
or special order. After the type of order is identified dispatch activity is performed and
that is marked as the termination of the process.
26
-
8/9/2019 communication and confrence media
27/62
Where to use Interaction Diagrams?
The basic usage of activity diagram is similar to other four UML diagrams. The specific
usage is to model the control flow from one activity to another. This control flow does
not include messages.
The activity diagram is suitable for modeling the activity flow of the system. An
application can have multiple systems. Activity diagram also captures these systems anddescribes flow from one system to another. This specific usage is not available in other
diagrams. These systems can be database, external queues or any other system.Now we will look into the practical applications of the activity diagram. From the above
discussion it is clear that an activity diagram is drawn from a very high level. So it gives
high level view of a system. This high level view is mainly for business users or anyother person who is not a technical person.
This diagram is used to model the activities which are nothing but business requirements.
So the diagram has more impact on business understanding rather implementation details.
Following are the main usages of activity diagram:
Modeling work flow by using activities.
Modeling business requirements. High level understanding of the system's functionalities.
Investigate business requirements at a later stage.
27
-
8/9/2019 communication and confrence media
28/62
COMPONENT DIAGRAMOverview:
Component diagrams are different in terms of nature and behaviour. Componentdiagrams are used to model physical aspects of a system.
Now the question is what are these physical aspects? Physical aspects are the elements
like executables, libraries, files, documents etc which resides in a node.So component diagrams are used to visualize the organization and relationships among
components in a system. These diagrams are also used to make executable systems.
28
-
8/9/2019 communication and confrence media
29/62
Purpose:
Component diagram is a special kind of diagram in UML. The purpose is also different
from all other diagrams discussed so far. It does not describe the functionality of the
system but it describes the components used to make those functionalities.So from that point component diagrams are used to visualize the physical components in
a system. These components are libraries, packages, files etc.
Component diagrams can also be described as a static implementation view of a system.Static implementation represents the organization of the components at a particular
moment.
A single component diagram cannot represent the entire system but a collection ofdiagrams are used to represent the whole.
So the purpose of the component diagram can be summarized as:
Visualize the components of a system.
Construct executables by using forward and reverse engineering.
Describe the organization and relationships of the components.
How to draw Component Diagram?
Component diagrams are used to describe the physical artifacts of a system. This artifact
includes files, executables, libraries etc.So the purpose of this diagram is different, Component diagrams are used during the
implementation phase of an application. But it is prepared well in advance to visualize
the implementation details.
Initially the system is designed using different UML diagrams and then when the artifactsare ready component diagrams are used to get an idea of the implementation.
This diagram is very important because without it the application cannot be implementedefficiently. A well prepared component diagram is also important for other aspects likeapplication performance, maintenance etc.
So before drawing a component diagram the following artifacts are to be identified
clearly:
Files used in the system.
Libraries and other artifacts relevant to the application.
Relationships among the artifacts.
Now after identifying the artifacts the following points needs to be followed:
Use a meaningful name to identify the component for which the diagram is to be
drawn.
Prepare a mental layout before producing using tools.
Use notes for clarifying important points.
The following is a component diagram for order management system. Here the artifactsare files. So the diagram shows the files in the application and their relationships. In
actual the component diagram also contains dlls, libraries, folders etc.
In the following diagram four files are identified and their relationships are produced.Component diagram cannot be matched directly with other UML diagrams discussed so
far. Because it is drawn for completely different purpose.
29
-
8/9/2019 communication and confrence media
30/62
So the following component diagram has been drawn considering all the points
mentioned above:
Where to use Component Diagrams?
We have already described that component diagrams are used to visualize the static
implementation view of a system. Component diagrams are special type of UML
diagrams used for different purposes.These diagrams show the physical components of a system. To clarify it, we can say that
component diagrams describe the organization of the components in a system.
Organization can be further described as the location of the components in a system.These components are organized in a special way to meet the system requirements.
As we have already discussed those components are libraries, files, executables etc. Now
before implementing the application these components are to be organized. Thiscomponent organization is also designed separately as a part of project execution.
Component diagrams are very important from implementation perspective. So the
implementation team of an application should have a proper knowledge of the componentdetails.
Now the usage of component diagrams can be described as:
Model the components of a system.
Model database schema.
Model executables of an application.
Model system's source code.
30
-
8/9/2019 communication and confrence media
31/62
DEPLOYMENT DIAGRAM
Overview:
Deployment diagrams are used to visualize the topology of the physical components of asystem where the software components are deployed.
So deployment diagrams are used to describe the static deployment view of a system.
Deployment diagrams consist of nodes and their relationships.
Purpose:
The nameDeploymentitself describes the purpose of the diagram. Deployment diagrams
are used for describing the hardware components where software components aredeployed. Component diagrams and deployment diagrams are closely related.
Component diagrams are used to describe the components and deployment diagramsshows how they are deployed in hardware.
UML is mainly designed to focus on software artifacts of a system. But these two
diagrams are special diagrams used to focus on software components and hardwarecomponents.
So most of the UML diagrams are used to handle logical components but deployment
diagrams are made to focus on hardware topology of a system. Deployment diagrams areused by the system engineers.
The purpose of deployment diagrams can be described as:
Visualize hardware topology of a system.
Describe the hardware components used to deploy software components.
Describe runtime processing nodes.
How to draw Component Diagram?
Deployment diagram represents the deployment view of a system. It is related to the
component diagram. Because the components are deployed using the deployment
diagrams. A deployment diagram consists of nodes. Nodes are nothing but physicalhardwares used to deploy the application.
Deployment diagrams are useful for system engineers. An efficient deployment diagram
is very important because it controls the following parameters
Performance
Scalability
Maintainability
Portability
31
-
8/9/2019 communication and confrence media
32/62
So before drawing a deployment diagram the following artifacts should be identified:
Nodes
Relationships among nodesThe following deployment diagram is a sample to give an idea of the deployment view of
order management system. Here we have shown nodes as:
Monitor Modem
Caching server
ServerThe application is assumed to be a web based application which is deployed in a
clustered environment using server 1, server 2 and server 3. The user is connecting to the
application using internet. The control is flowing from the caching server to the clusteredenvironment.
So the following deployment diagram has been drawn considering all the points
mentioned above:
Where to use Deployment Diagrams?
Deployment diagrams are mainly used by system engineers. These diagrams are used to
describe the physical components (hardwares), their distribution and association.To clarify it in details we can visualize deployment diagrams as the hardwarecomponents/nodes on which software components reside.
Software applications are developed to model complex business processes. Only efficient
software applications are not sufficient to meet business requirements. Business
requirements can be described as to support increasing number of users, quick responsetime etc.
32
-
8/9/2019 communication and confrence media
33/62
To meet these types of requirements hardware components should be designed efficiently
and in a cost effective way.
Now a day's software applications are very complex in nature. Software applications canbe stand alone, web based, distributed, mainframe based and many more. So it is very
important to design the hardware components efficiently.
So the usage of deployment diagrams can be described as follows: To model the hardware topology of a system.
To model embedded system.
To model hardware details for a client/server system.
To model hardware details of a distributed application.
Forward and reverse engineering.
UML NOTATIONS
UML notations are the most important elements in modeling. Efficient and appropriate
use of notations is very important for making a complete and meaningful model. The
model is useless unless its purpose is depicted properly.So learning notations should be emphasized from the very beginning. Different notations
are available for things and relationships. And the UML diagrams are made using the
notations of things and relationships. Extensibility is another important feature whichmakes UML more powerful and flexible.
33
-
8/9/2019 communication and confrence media
34/62
The chapter describes the UML Basic Notations in more details. This is just an extension
to the UML buildling block section I have discussed in previous chapter.
Structural Things:
Graphical notations used in structural things are the most widely used in UML. These are
considered as the nouns of UML models. Following are the list of structural things.
Classes Interface
Collaboration
Use case
Active classes
Components
Nodes
Class Notation:
UML class is represented by the diagram shown below. The diagram is divided into
four parts.
The top section is used to name the class.
The second one is used to show the attributes of the class.
The third section is used to describe the operations performed by the class.
The fourth section is optional to show any additional components.
Classes are used to represent objects. Objects can be anything having properties and
responsibility.
Object Notation:
The objectis represented in the same way as the class. The only difference is the namewhich is underlined as shown below..
34
-
8/9/2019 communication and confrence media
35/62
As object is the actual implementation of a class which is known as the instance of a
class. So it has the same usage as the class.
Interface Notation:
Interface is represented by a circle as shown below. It has a name which is generally
written below the circle.
Interface is used to describe functionality without implementation. Interface is the just
like a template where you define different functions not the implementation. When aclass implements the interface it also implements the functionality as per the requirement.
Collaboration Notation:
Collaboration is represented by a dotted eclipse as shown below. It has a name written
inside the eclipse.
35
-
8/9/2019 communication and confrence media
36/62
Collaboration represents responsibilities. Generally responsibilities are in a group.
Use case Notation:
Use case is represented as an eclipse with a name inside it. It may contain additional
responsibilities.
Use case is used to capture high level functionalities of a system.
Actor Notation:
An actor can be defined as some internal or external entity that interacts with the system.
Actor is used in a use case diagram to describe the internal or external entities.
Initial State Notation:Initial state is defined show the start of a process. This notation is used in almost all
diagrams.
36
-
8/9/2019 communication and confrence media
37/62
The usage of Initial State Notation is to show the starting point of a process.
Final State Notation:
Final state is used to show the end of a process. This notation is also used in almost all
diagrams to describe the end.
The usage of Final State Notation is to show the termination point of a process.Active class Notation:
Active class looks similar to a class with a solid border. Active class is generally used to
describe concurrent behaviour of a system.
Active class is used to represent concurrency in a system.
Component Notation:
A component in UML is shown as below with a name inside. Additional elements can beadded wherever required.
Component is used to represent any part of a system for which UML diagrams are made.
Node Notation:
37
-
8/9/2019 communication and confrence media
38/62
A node in UML is represented by a square box as shown below with a name. A node
represents a physical component of the system.
Node is used to represent physical part of a system like server, network etc.
Behavioural Things:
Dynamic parts are one of the most important elements in UML. UML has a set of
powerful features to represent the dynamic part of software and non software systems.
These features include interactions andstate machines.Interactions can be of two types:
Sequential (Represented by sequence diagram)
Collaborative (Represented by collaboration diagram)
Interaction Notation:
Interaction is basically message exchange between two UML components. The following
diagram represents different notations used in an interaction.
38
-
8/9/2019 communication and confrence media
39/62
Interaction is used to represent communication among the components of a system.
State machine Notation:
State machine describes the different states of a component in its life cycle. The notationsare described in the following diagram.
State machine is used to describe different states of a system component. The state can be
active, idle or any other depending upon the situation.
Grouping Things:
Organizing the UML models are one of the most important aspects of the design. In UML
there is only one element available for grouping and that is package.
Package Notation:
Package notation is shown below and this is used to wrap the components of a system.
39
-
8/9/2019 communication and confrence media
40/62
Annotational Things:
In any diagram explanation of different elements and their functionalities are veryimportant. So UML has notes notation to support this requirement.
Note Notation:
This notation is shown below and they are used to provide necessary information of asystem.
Relationships
A model is not complete unless the relationships between elements are described
properly. TheRelationship gives a proper meaning to an UML model. Following are the
different types of relationships available in UML.
Dependency
Association
Generalization
Extensibility
Dependency Notation:
Dependency is an important aspect in UML elements. It describes the dependent
elements and the direction of dependency.
Dependency is represented by a dotted arrow as shown below. The arrow head representsthe independent element and the other end the dependent element.
Dependency is used to represent dependency between two elements of a system.
40
-
8/9/2019 communication and confrence media
41/62
Association Notation:
Association describes how the elements in an UML diagram are associated. In simpleword it describes how many elements are taking part in an interaction.
Association is represented by a dotted line with (without) arrows on both sides. The two
ends represent two associated elements as shown below. The multiplicity is alsomentioned at the ends (1, * etc) to show how many objects are associated.
Association is used to represent the relationship between two elements of a system.
Generalization Notation:
Generalization describes the inheritance relationship of the object oriented world. It isparent and child relationship.
Generalization is represented by an arrow with hollow arrow head as shown below. One
end represents the parent element and the other end child element.
Generalization is used to describe parent-child relationship of two elements of a system.
Extensibility Notation:
All the languages (programming or modeling) have some mechanism to extend its
capabilities like syntax, semantics etc. UML is also having the following mechanisms to
provide extensibility features.Stereotypes (Represents new elements)
Tagged values (Represents new attributes)
Constraints (Represents the boundaries)
41
-
8/9/2019 communication and confrence media
42/62
Extensibility notations are used to enhance the power of the language. It is basically
additional elements used to represent some extra behaviour of the system. These extra
behaviours are not covered by the standard available notations.
Abstraction Relationship
An abstraction relationship is a dependency between model elements that represents thesame concept at different levels of abstraction or from different viewpoints. You can add
abstraction relationships to a model in several diagrams, including use-case, class, and
component diagrams.
Activity edges
In activity diagrams, an activity edge is a relationship between two activity nodes thatyou can use to represent the control flow or object flow in an activity diagram.
Aggregation relationships
An aggregation relationship depicts a classifier as a part of, or as subordinate to, anotherclassifier.
Association relationships
In UML models, an association is a relationship between two classifiers, such as classes
or use cases, that describes the reasons for the relationship and the rules that govern the
relationship.
Binding relationships
In UML models, a binding relationship is a relationship that assigns values to template
parameters and generates a new model element from the template.
Communication paths
In UML modeling, a communication path is a type of association between nodes in adeployment diagram that shows how the nodes exchange messages and signals.
42
http://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cactedges.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/caggreg.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cassn.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cbind.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/ccommpath.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/caggreg.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cassn.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cbind.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/ccommpath.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cactedges.html -
8/9/2019 communication and confrence media
43/62
Composition relationships
A composition relationship, which was named composition association relationship inUML 1.4, represents wholepart relationships and is a form of aggregation. A
composition relationship specifies that the lifetime of the part classifier is dependent on
the lifetime of the whole classifier.
Dependency relationships
In UML modeling, a dependency relationship is a relationship in which changes to onemodel element (the supplier) impact another model element (the client). You can use
dependency relationships in class diagrams, component diagrams, deployment diagrams,
and use case diagrams.
Deployment relationships
In UML modeling, deployment relationships specify that a particular node type supports
the deployment of an artifact type.
Directed association relationshipsIn UML models, directed association relationships are associations that are navigable in
only one direction.
Generalization relationships
In UML modeling, a generalization relationship is a relationship in which one model
element (the child) is based on another model element (the parent). Generalizationrelationships are used in class, component, deployment, and use case diagrams.
Implementation relationships
In UML modeling, an implementation relationship is a specialized type of realization
relationship between a classifier and a provided interface. The implementation
relationship specifies that the realizing classifier must conform to the contract that theprovided interface specifies.
Include relationships
In UML modeling, an include relationship is a relationship in which one use case (the
base use case) includes the functionality of another use case (the inclusion use case). The
include relationship supports the reuse of functionality in a use case model.
Manifestation relationships
In UML modeling, a manifestation relationship shows which model elements, such as
components or classes, are manifested in an artifact. The artifact manifests, or includes, aspecific implementation for, the features of one or several physical software components.
Realization relationships
In UML modeling, a realization relationship is a relationship between two model
elements, in which one model element (the client) realizes the behavior that the other
model element (the supplier) specifies. Several clients can realize the behavior of a single
43
http://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/ccompasn.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cdepend.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cdeploy.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cdirasn.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cgeneral.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cimplement.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cinclude.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cmanifestn.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/creal.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/ccompasn.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cdepend.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cdeploy.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cdirasn.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cgeneral.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cimplement.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cinclude.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cmanifestn.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/creal.html -
8/9/2019 communication and confrence media
44/62
supplier. You can use realization relationships in class diagrams and component
diagrams.
Usage relationships
In UML modeling, a usage relationship is a type of dependency relationship in which one
model element (the client) requires another model element (the supplier) for fullimplementation or operation.
Common Mechanisms In UML
Specifications
textual statement of syntax & semantics
diagrams give view of specification
Adornments
elements in UML - unique graphical notation
adornments - added information about class
Common Divisions
general property vs. specific instanceclass vs. object
use case vs. use case instance
UML syntax: underline name of instanceseparation of interface & implementationinterface - contract
implementation - concrete realization of contract
Extensibility Mechanisms
stereotype
allows creation of new kinds of building blocks from existing ones
tagged value
allows creation of new information in specification
constraint
allows addition of new rules & modification of existing rules
44
http://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cusage.htmlhttp://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/topic/com.ibm.xtools.modeler.doc/topics/cusage.html -
8/9/2019 communication and confrence media
45/62
Rules Of UML specify what model should look like
semantic rules for
names
scope
visibility
integrity
execution
Common properties of models
elided - hide some elements for simplicity
incomplete
inconsistent
rules of UML make it easier to address these problems
TERMS AND CONCEPTS
UML 2.2 has 14 types ofdiagrams divided into two categories.[10] Seven diagram types
represent structural information, and the other seven represent general types of behavior,
including four that represent different aspects of interactions. These diagrams can be
categorized hierarchically as shown in the following class diagram:
UML does not restrict UML element types to a certain diagram type. In general, every
UML element may appear on almost all types of diagrams; this flexibility has been
partially restricted in UML 2.0. UMLprofiles may define additional diagram types orextend existing diagrams with additional notations.
In keeping with the tradition of engineering drawings, a comment or note explaining
usage, constraint, or intent is allowed in a UML diagram.
Structure diagrams
Structure diagrams emphasize what things must be in the system being modeled:
Class diagram: the class diagrams describes the structure of a system by showing
the system's classes, their attributes, and the relationships among the classes.
Component diagram: depicts how a software system is split up into componentsand shows the dependencies among these components.
Composite structure diagram: describes the internal structure of a class and the
collaborations that this structure makes possible.
Deployment diagram: serves to model the hardware used in system
implementations, and the execution environments and artifacts deployed on the
hardware.
45
http://en.wikipedia.org/wiki/Category:UML_diagramshttp://en.wikipedia.org/wiki/Unified_Modeling_Language#cite_note-9%23cite_note-9http://en.wikipedia.org/wiki/Class_diagramhttp://en.wikipedia.org/wiki/Profile_(UML)http://en.wikipedia.org/wiki/Class_diagramhttp://en.wikipedia.org/wiki/Component_diagramhttp://en.wikipedia.org/wiki/Composite_structure_diagramhttp://en.wikipedia.org/wiki/Deployment_diagramhttp://en.wikipedia.org/wiki/Category:UML_diagramshttp://en.wikipedia.org/wiki/Unified_Modeling_Language#cite_note-9%23cite_note-9http://en.wikipedia.org/wiki/Class_diagramhttp://en.wikipedia.org/wiki/Profile_(UML)http://en.wikipedia.org/wiki/Class_diagramhttp://en.wikipedia.org/wiki/Component_diagramhttp://en.wikipedia.org/wiki/Composite_structure_diagramhttp://en.wikipedia.org/wiki/Deployment_diagram -
8/9/2019 communication and confrence media
46/62
Object diagram: shows a complete or partial view of the structure of a modeled
system at a specific time.
Package diagram: depicts how a system is split up into logical groupings byshowing the dependencies among these groupings.
Profile diagram: operates at the metamodel level to show stereotypes as classes
with the stereotype, and profiles as packages with the stereotype. The extension relation (solid line with closed, filled
arrowhead) indicate what metamodel element a given stereotype is extending.
Since structure diagrams represent the structure they are used extensively in documentingthe architecture of software systems.
Behavior diagrams
Behavior diagrams emphasize what must happen in the system being modeled:
Activity diagram: represents the business and operational step-by-stepworkflows of components in a system. An activity diagram shows the overallflow of control.
State machine diagram: standardized notation to describe many systems, from
computer programs to business processes.
Use case diagram: shows the functionality provided by a system in terms ofactors, their goals represented as use cases, and any dependencies among
those use cases.
Since behavior diagrams illustrate the behaviour of a system, they are used extensively todescribe the functionality of software systems.
46
http://en.wikipedia.org/wiki/Object_diagramhttp://en.wikipedia.org/wiki/Package_diagramhttp://en.wikipedia.org/w/index.php?title=Profile_diagram&action=edit&redlink=1http://en.wikipedia.org/wiki/Software_Architecturehttp://en.wikipedia.org/wiki/Activity_diagramhttp://en.wikipedia.org/wiki/UML_state_machinehttp://en.wikipedia.org/wiki/Use_case_diagramhttp://en.wikipedia.org/wiki/Object_diagramhttp://en.wikipedia.org/wiki/Package_diagramhttp://en.wikipedia.org/w/index.php?title=Profile_diagram&action=edit&redlink=1http://en.wikipedia.org/wiki/Software_Architecturehttp://en.wikipedia.org/wiki/Activity_diagramhttp://en.wikipedia.org/wiki/UML_state_machinehttp://en.wikipedia.org/wiki/Use_case_diagram -
8/9/2019 communication and confrence media
47/62
CLASS DIAGRAMThe class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the modellingof object oriented systems because they are the only UML diagrams which can be
mapped directly with object oriented languages.
The class diagram shows a collection of classes, interfaces, associations, collaborationsand constraints. It is also known as astructural diagram.
Contents:Class diagrams commonly contain the following things
Classes
Interfaces
Collaborations
Dependency,generation and association relationships
Fig: Class Diagram
Class Diagram for Communication and Conference
User
User name
User Id
User password
User address
enter id & password()
select a friend()
send a request()
chat()
call()
abort()
Server
server name
server idconfiguration
provide parallel communication()
Enduser
User name
User id
User address
accept or deny request()
chat()
call()
* .....1
47
-
8/9/2019 communication and confrence media
48/62
USE CASE DIAGRAM
Use case diagrams are used to gather the requirements of a system including internal and
external influences. These requirements are mostly design requirements. So when asystem is analyzed to gather its functionalities use cases are prepared and actors are
identified.
Now when the initial task is complete use case diagrams are modelled to present theoutside view.
So in brief, the purposes of use case diagrams can be as follows:
Used to gather requirements of a system.
Used to get an outside view of a system.
Identify external and internal factors influencing the system.
Show the interacting among the requirements are actors.
Fig: Use Case Diagram
48
-
8/9/2019 communication and confrence media
49/62
USE CASE DIAGRAM FOR THE COMMUNICATION AND
CONFRENCE
Find a friend
Send a requestUser
Open application
Enter login id & password
Reply to a request
Chat
Call
Abort
Logout
Close application
End User
49
-
8/9/2019 communication and confrence media
50/62
INTERACTION DIAGRAM
That is why sequence and collaboration diagrams are used to capture dynamic nature butfrom a different angle.
So the purposes of interaction diagram can be describes as:
To capture dynamic behaviour of a system.
To describe the message flow in the system.
To describe structural organization of the objects.
To describe interaction among objects.
Fig:Sequence Diagram
50
-
8/9/2019 communication and confrence media
51/62
Fig: Collaboration Diagram
51
-
8/9/2019 communication and confrence media
52/62
SEQUENCE DIAGRAM FOR THE COMMUNICATION
AND CONFRENCE
UserUser
ServerServer
EnduserEnduser1: enter id and password
2: verify
3: display home page()
4: select enduser
5: forward
6: start communication
7: send request for conference call
8: accept/deny
9: start conference if accepted
10: end call
Fig: Sequence Diagram
52
-
8/9/2019 communication and confrence media
53/62
COLLABORATION DIAGRAM FOR THE DISTANCE
EDUCATION SYSTEM
User Server
Enduser
2: verify
1: enter id and password4: select enduser
3: display home page()
5: forward6: start communication8: accept/deny
7: send request for conference call9: start conference if accepted
10: end call
Fig: Collaboration Diagram
53
-
8/9/2019 communication and confrence media
54/62
ACTIVITY DIAGRAM
Activity diagram is another important diagram in UML to describe dynamic aspects of
the system.Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system.
So the control flow is drawn from one operation to another. This flow can be sequential,branched or concurrent. Activity diagrams deals with all type of flow control by using
different elements like fork, join etc.
54
-
8/9/2019 communication and confrence media
55/62
ACTIVITY DIAGRAM FOR THE COMMUNICATION AND
CONFRENCE SYSTEM
perform
registration
get id &
password
login
verify
home page
select a friend
chat call videocall conference
abort
logout
close
application
1
\
Fig: Activity Diagram for the communication and conference system
55
-
8/9/2019 communication and confrence media
56/62
Branching
A branch specifies alternate paths takes based on some Boolean expression
Branch is represented by diamondBranch may have one incoming transition and two or more outgoing one on each
outgoing transition,you place a Boolean expression shouldnt overlap but they should
cover all possibilities.
Forking and Joining
ForkA fork represents the splitting of a single flow of control into two or more concurrent
Flow of control.
A fork may have one incoming transition and two or more outgoing transitions, each ofwhich represents an independent flow of control.
Below fork the activities associated with each of these path continues in parallel.
JoinA join represents the synchronization of two or more concurrent flows of control.A join may have two or more incoming transition and one outgoing transition.
Above the join the activities associated with each of these paths continues in parallel.
Swimlane:Swimlanes are useful when we model workflows of business processes to partition the
activity states on an activity diagram into groups.Each group representing the business organization responsible for those activities,thesegroups are called swimlanes.
56
-
8/9/2019 communication and confrence media
57/62
SWIMLANE DIAGRAM FOR THE COMMUNICATION AND
CONFRENCE SYSTEM
57
-
8/9/2019 communication and confrence media
58/62
STATE CHART DIAGRAMA state chart diagrams a state machine, emphasizing the flow of control from state tostate.
Contents
State chart diagrams commonly contain
Simply state and composite states
Transitions, including events and actions
Common use
They are use to model the dynamic aspects of a system.
Event ordered behavior of any kind of objects, to model reactive objects.
58
-
8/9/2019 communication and confrence media
59/62
COMPONENT DIAGRAM
Component diagrams are different in terms of nature and behaviour. Component
diagrams are used to model physical aspects of a system.
Now the question is what are these physical aspects? Physical aspects are the elements
like executables, libraries, files, documents etc which resides in a node.So component diagrams are used to visualize the organization and relationships among
components in a system. These diagrams are also used to make executable systems.
Fig: Component Diagram
59
-
8/9/2019 communication and confrence media
60/62
COMPONENT DIAGRAM FOR COMMUNICATION AND
CONFRENCE SYSTEM
communication andconfrence.exe
.net
java
php
Fig: Component Diagram
DEPLOYMENT DIAGRAM
Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.
So deployment diagrams are used to describe the static deployment view of a system.Deployment diagrams consist of nodes and their relationships.
Purpose:
The nameDeploymentitself describes the purpose of the diagram. Deployment diagramsare used for describing the hardware components where software components are
deployed. Component diagrams and deployment diagrams are closely related.Component diagrams are used to describe the components and deployment diagramsshows how they are deployed in hardware.
60
-
8/9/2019 communication and confrence media
61/62
Fig: Deployment Diagram
61
-
8/9/2019 communication and confrence media
62/62
DEPLOYMENT DIAGRAM FOR THE COMMUNICATION AND
CONFRENCE SYSTEM
Fig: Deployment Diagram