0% found this document useful (0 votes)
52 views6 pages

An Effective Analysis of Visualizing Software Architecture Using Unified Modeling Language

This document provides an overview of Unified Modeling Language (UML) and its applications in software design. It discusses: 1) UML's origins and its use for visualizing software architecture through diagrams. 2) The main categories of UML diagrams - structural and behavioral - and examples of each. 3) Several literature references that apply UML to domains like embedded systems, agent design, and software comprehension. 4) The need for UML modeling to provide structure for problem solving and manage complexity.

Uploaded by

Chetan Chauhan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
52 views6 pages

An Effective Analysis of Visualizing Software Architecture Using Unified Modeling Language

This document provides an overview of Unified Modeling Language (UML) and its applications in software design. It discusses: 1) UML's origins and its use for visualizing software architecture through diagrams. 2) The main categories of UML diagrams - structural and behavioral - and examples of each. 3) Several literature references that apply UML to domains like embedded systems, agent design, and software comprehension. 4) The need for UML modeling to provide structure for problem solving and manage complexity.

Uploaded by

Chetan Chauhan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

AN EFFECTIVE ANALYSIS OF VISUALIZING SOFTWARE

ARCHITECTURE USING UNIFIED MODELING LANGUAGE


ABSTRACT
Unified Modeling Language (UML) refers to a general-purpose modeling language in software
engineering designed to offer a customary approach to visualize the design of a software system.
Proposed and developed by rady !ooch" #var $acobson and $ames %umbaugh at %ational
&oftware" later it was adopted as a standard by the 'b(ect Management roup ('M). )inally"
the UML was globally accepted and recognized by the #nternational 'rganization for
&tandardization (#&') as an accepted #&' standard. &ince then it has been periodically revised to
cover the latest revision of UML.

*he Unified Modeling Language (UML) provides a mode for
visualization of the blueprints of software using different diagrams" including elements including
activities ((obs)" individual components of the system" the way in which they can interact with
other software components as well as +,ternal user interface. *his manuscript highlights various
aspects of unified modeling language in terms of its applications and scope in different domains.
*he term paper proposal will finally consist of different dimensions of unified modeling
language alongwith the case study and most appropriate literature.
Keywords - Unified Modeling Language" &oftware -esign Methodologies" &oftware
.rchitecture
INTRODUCTION
*he UML was designed as a graphical notation for use with ob(ect-oriented systems and
applications. !ecause of its popularity" now it is emerging in the field of embedded systems
design as a modeling language. *he UML notation is useful in capturing the re/uirements"
documenting the structure" decomposing into ob(ects and defining relationships between ob(ects.
#t is a notational language that is very useful in modeling the real-time embedded systems 012.
UML DIAGRAMS
.ny comple, system can be e,plained and best understood with the diagrams or pictorial
representations. &uch diagrams are having an effective vision on the understanding. UML
diagrams are prepared to understand and a system in better and easy way. UML covers different
types of diagrams to envelope the multiple aspects of a system.
*here are two e,tensive categories of the diagrams divided further sub-categories3
&tructural -iagrams
!ehavioral -iagrams
*he term paper shall include all these diagrams including the e,amples and case scenarios for a
particular industrial application.
LITERATURE REVIEW
.man 4aur (5665) 012 - *his paper portraits the re/uirements and investigation modeling of a
real-time embedded system related to a control system for platform stabilization using 7'M+*
method of design with UML notation. *hese applications involve designing of electromechanical
systems that are controlled by multi-processors.
&ellappan Palaniappan and Louis Ling (5668) 052 - *his paper propose and presents a prototype
web based 7.&+ tool which supports the automated rendering of UML models by enabling team
members who are geographically distributed to wor9 together. &oftware modelers specify their
software systems using a set of triplets for each UML diagram and the tool uses the triplets to
automatically render high-/uality &: graphics" thus eliminating the need for manual
diagramming. *he current version supports three UML diagrams3 7lass" Use 7ase and &e/uence.
*he tool is implemented using .ctive &erver Page (the Microsoft;s server-side scripting engine)
and :!&cript (the Microsoft;s :isual !asic &cripting Language) and can be accessed on the
<eb.
M. .. 4holy (5611) 0=2 > #n this wor9" the author presents a proposal for the &ystematic
.pproach of .gent -esign with the use of Unified Modeling Language (UML) diagram. #n this
wor9" the authors illustrate notions for the behavior of an agent using and e,tending UML class
diagrams. )ocus on representing the agent migration from ta9e re/uests and between other hosts.
#n a case study the authors e,plain one variant of notation that is the most suitable for given
scenario. .nd show that it is easier to design agent applications based on agent UML" by develop
software for the case study generated by UML software pac9age.
?ader #. (566@) 0@2 - *his wor9 focus on the conception of UML diagrams. -uring the research
presented in this paper" data was gathered from the wor9 of two groups. roup 1 consisted of 1=
senior computer science students who wor9ed in five teams. *he students were as9ed to trace
and analyze the process by which they retrieved information from UML diagrams of a given
system. roup 5 consisted of @5 senior computer science students who were re/uested to
complete a /uestionnaire in which they were as9ed to ran9 different types of UML diagrams
according to their importance. *he section on data analysis discusses strategies adopted by the
novices in their attempt to reveal the meaning of a set of UML diagrams" as well as their attitudes
towards the different diagrams. 'ne of the interesting observations is that although each team
had its own preferences with respect to the usefulness of each specific type of diagrams" the
overall use of each diagram type is very similar across the teams.
%. Aolfaghari (561=) 0B2 > *he classical wor9 suggested a method for converting the UML
description designing software to Cueuing networ9s model (CD) model" which provides the
application of using the UML in designing software with high performanceE in other words it
putting the performance in designing software and a high /uality software is designed. #n order
to modeling the parts of system the authors in this manuscript use deployment diagram for
allocating software components to hardware resources and activity diagrams to model software
behavior" and use case diagrams to model wor9loads with the performance profile and .n
algorithm is provided for automatic production of the CD performance model from the
FML(+,tensible Mar9up Language) documents .used diagrams with performance
profiles(stereotype" label and limitation)" using the +,portFM# software rational rose.
performace model load to software tool for performance analysis" so as the designer can test the
fulfill of performance goals of his design according to type of different performance parameters
and changing in value and chooses the best option in designing.
RECENT DOMAINS OF RESEARCH IN UML
1. +nterprise %esource Planning
5. !an9ing and )inance
=. Mar9eting and ?uman %esource
@. +nterprise information systems
B. *elecommunications.
G. *ransportation
H. -efense
8. %etail &ector
I. Medical and ?ealth &ciences
16. &cience and %esearch.
11. -istributed <eb-based services.
NEED OF UML MODELING
*o provide the e,plained and detailed structure for problem solving.
Multiple solutions are obtained which are re/uired in problem solving
Manage the comple,ity of systems before actually starting development wor9.
UML shows the clear views of system thus reducing time-to-mar9et for business problem
solutions.
#f we model the problem before its actual development there are lesser chances that the
development plan will go wrong" thus decreasing development costs.
%eduction in the ris9s and failures
Com!r!"#$e A%!&ys#s o' UML Too&s
*he following UML tools shall be analyzed based on different parameters including
programming language used" open source" platform" dependency and many others. )ollowing is
the list of prominent UML tools which are used in industry and in the interest of our term paper.
UML Too& (ror#e"!ry OR Oe% So)r*e Too&
.gile$ &tructure:iews Proprietary
.rgoUML 'pen &ource
astah Proprietary
.*L 'pen &ource
!'UML Proprietary
7ase7omplete Proprietary
7oncept-raw P%' Proprietary
7reately for UML Proprietary
-ia 'pen &ource
+clipse UML5 *ools 'pen &ource
+nterprise .rchitect Proprietary
Lucid7hart Proprietary
Magic-raw Proprietary
Microsoft :isio Proprietary
Modelio 'pen &ource
My+clipse Proprietary
D7lass 'pen &ource
Det!eans 'pen &ource
'b(ecteering Proprietary
ob(ecti) Proprietary
'pen Model&phere 'pen &ource
Papyrus 'pen &ource
Poseidon for UML Proprietary
Power-esigner Proprietary
Prosa UML Modeller Proprietary
%ational %hapsody Proprietary
%ational %ose F-+ Proprietary
%ational &oftware .rchitect Proprietary
%ational &oftware Modeler Proprietary
%ational &ystem .rchitect Proprietary
%#&+ Proprietary
%eal *ime -eveloper &tudio Proprietary
&oftware #deas Modeler Proprietary
&tarUML 'pen &ource
Umbrello UML Modeller 'pen &ource
UMLet 'pen &ource
UModel Proprietary
:isual Paradigm for UML Proprietary
y+d Proprietary
REFERENCES
012 4aur" .man" and %a(eev .rora. J.pplication of UML in real-time embedded systems.J
International Journal of Software Engineering and Applications (IJSEA) =" no. 5 (5615)3 BI-H6.
052 Palaniappan" &ellappan" and Louis Ling. J<eb-!ased 7.&+ *ool for .utomated %endering
of UML Models.J IJCSNS 8" no. 8 (5668)3 1@G.
0=2 .l-4holy" Momtaz" .hmed 4halifa" and Mohamed +l-&aied. J. &ystematic .pproach for
.gent -esign !ased on UML.J Int. Arab J. e-Technol. 5" no. 5 (5611)3 16B-111.
0@2 ?adar" #rit" and 'rit ?azzan. J'n the contribution of UML diagrams to software system
comprehension.J Journal of b!ect Technolog" =" no. 1 (566@)3 1@=-1BG.
0B2 Aolfaghari" %ahmat. J7onverting UML -escription of &oftware .rchitecture to CDM and
Performance +valuation.J

You might also like