Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
9Activity
0 of .
Results for:
No results containing your search query
P. 1
UML Tutorial

UML Tutorial

Ratings: (0)|Views: 2,466|Likes:
Published by api-3704649
Apostila.
Apostila.

More info:

Published by: api-3704649 on Oct 15, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

\ue000Product Info

Enterprise Architect (EA)
EA Download
EA Pricing

ExyBar
\ue000Related Info
Links
UML Tutorial
\ue000Tech Support

Support
Report a Bug (HTML)
Report a Bug (user forum)
Request-A-Feature (HTML)
Request-A-Feature (forum)

UML Tutorial - part 1

The Unified Modelling Language has quickly become the de-facto standard for building Object-Oriented software.\ue000This short tutorial provides a very high level introduction to UML, and suggests some further reading.

But first... What is UML?
TheOMG specification states:
"The Unified Modeling Language (UML) is a graphical language

for visualizing,
specifying, constructing, and documenting the artifacts of a
software-intensive system.
The UML offers a standard way to write a system's blueprints,
including conceptual
things such as business processes and system functions as well as
concrete things such
as programming language statements, database schemas, and
reusable software
components."

The important point to note here is that UML is a 'language' for
specifying and not a method or procedure. The UML is used to
define a software system; to detail the artifacts in the system, to
document and construct - it is the language that the blueprint is
written in. The UML may be used in a variety of ways to support a
software development methodology (such as the Rational Unified
Process) - but in itself it does not specify that methodology or
process.

UML defines the notation and semantics for the following domains:

The User Interaction or Use Case Model - describes the
boundary and interaction between the system and users.
Corresponds in some respects to a requirements model. (see

q
UML Tutorial
http://www.sparxsystems.com.au/UML_Tutorial.htm (1 of 2) [10/9/2001 11:08:37 AM]
The Use Case Model)

The Interaction or Collaboration Model - describes how
objects in the system will interact with each other to get work
done.

q

The Dynamic Model - State charts describe the states or
conditions that classes assume over time. Activity graphs
describe the workflows the system will implement. (seeThe

Dynamic Model)
q
The Logical or Class Model - describes the classes and
objects that will make up the system. (see The Class Model)
q

The Physical Component Model - describes the software (and
sometimes hardware components) that make up the system.
(see The Component Model)

q

The Physical Deployment Model - describes the physical
architecture and the deployment of components on that
hardware architecture. (see The Physical Model)

q

The UML also defines extension mechanisms for extending the UML to meet specialised needs (for example Business Process Modeling extensions)

Part 2 of this tutorial expands on how you use the UML to define
and build actual systems.
For some further reading see the following white papers (in PDF
format):
Business Process Modelling
q
The Use Case Model
q
The Logical Model
q
Component Model
q
Dynamic Model
q
If you have any suggestions or comments on the material here,

please forward your thoughts tosparks@sparxsystems.com.au.
\ue000
\u00a9 2000-2001 Sparx Systems Pty Ltd, All rights reserved.

Please direct your comments tosparks@sparxsystems.com.au
UML Tutorial
http://www.sparxsystems.com.au/UML_Tutorial.htm (2 of 2) [10/9/2001 11:08:37 AM]
\ue000Product Info

Enterprise Architect (EA)
EA Download
EA Pricing

ExyBar
\ue000Related Info
Links
UML Tutorial
\ue000Tech Support

Support
Report a Bug (HTML)
Report a Bug (user forum)
Request-A-Feature (HTML)
Request-A-Feature (forum)

Use Case Model
The Use Case Model describes the proposed functionality of the new system. A Use Case represents a discrete unit of
interaction between a user (human or machine) and the system. A Use Case is a single unit of meaningful work; for example
login to system, register with systemand create order are all Use Cases. Each Use Case has a description which describes the
functionality that will be built in the proposed system. A Use Case may 'include' another Use Case's functionality or 'extend'
another Use Case with its own behaviour.
Use Cases are typically related to 'actors'. An actor is a human or machine entity that interacts with the system to perform
meaningful work.
\ue000
A Use Case description will generally include:
General comments and notes describing the use case;
1.
Requirements - Things that the use case must allow the user to do, such as <ability to update order>, <ability to modify
2.
Use Case Model
http://www.sparxsystems.com.au/use_case_model.htm (1 of 5) [10/9/2001 11:09:05 AM]

Activity (9)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
rajaramansuresh liked this
Santanu Debnath liked this
abensur liked this
logpramz liked this
peeyushthebest liked this
best1065328 liked this
Nitheesh liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->