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 or section
Like this
132Activity

Table Of Contents

0 of .
Results for:
No results containing your search query
P. 1
Labmanual_full

Labmanual_full

Ratings:

2.5

(2)
|Views: 33,798 |Likes:
Published by Selva Kanmani

More info:

Published by: Selva Kanmani on Apr 10, 2011
Copyright:Attribution Non-commercial

Availability:

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

08/21/2014

pdf

text

original

 
Ex.no: 1 STUDY OF UML DIAGRAMSDate:UML DIAGRAMS
There are three classifications of UML diagrams:
Behavior diagrams.
A type of diagram that depicts behavioral features of asystem or business process. This includes activity, state machine, and use casediagrams as well as the four interaction diagrams.
Interaction diagrams.
A subset of behavior diagrams which emphasize objectinteractions. This includes communication, interaction overview, sequence, andtiming diagrams.
Structure diagrams.
A type of diagram that depicts the elements of aspecification that are irrespective of time. This includes class, compositestructure, component, deployment, object, and package diagrams.
DiagramDescriptionLearningPriorityActivity Diagram
Depicts high-level business processes, includingdata flow, or to model the logic of complex logicwithin a system.High
Class Diagram
Shows a collection of static model elements such asclasses and types, their contents, and theirelationships.High
CommunicationDiagram
Shows instances of classes, their interrelationships,and the message flow between them.Communication diagrams typically focus on thestructural organization of objects that send andreceive messages. Formerly called a CollaborationDiagram.Low
ComponentDiagram
Depicts the components that compose andapplication, system, or enterprise. The components,their interrelationships, interactions, and thei public interfaces are depicted.Medium
CompositeStructure Diagram
Depicts the internal structure of a classifier(such asa class, component, or use case), including theinteraction points of the classifier to other parts of the system.Low
DeploymentDiagram
Shows the execution architecture of systems. Thisincludes nodes, either hardware or softwareexecution environments, as well as the middlewareconnecting them.Medium
InteractionOverview Diagram
A variant of an activity diagram which overviewsthe control flow within a system or business process. Each node/activity within the diagram canrepresent another interaction diagram.Low
 
Object Diagram
Depicts objects and their relationships at a point intime, typically a special case of either a classdiagram or a communication diagram.Low
Package Diagram
Show how model elements are organized into packages as well as the dependencies between packages.Low
Sequence Diagram
Models the sequential logic, in effect the timeordering of messages between classifiers.High
State MachineDiagram
Describes the states an object or interaction may bein, as well as the transitions between states.Formerly referred to as a state diagram, state chartdiagram, or a state-transition diagram.Medium
Timing Diagram
Depicts the change in state or condition of aclassifier instance or role over time. Typically usedto show the change in state of an object over timein response to external events.Low
Use Case Diagram
Shows use cases, actors, and theiinterrelationships.Medium
USE CASE DIAGRAM:
A
use case diagram
is a type of behavioral diagram defined by the
UnifiedModeling Language
(UML). Its purpose is to present a graphical overview of thefunctionality provided by a system in terms of 
actors
, their goals- represented as
usecases
- and any dependencies between those use cases.
Use case diagram depict:
Use cases.
A use case describes a sequence of actions that provide something of measurable value to an actor and is drawn as a horizontal ellipse.
Actors.
An actor is a person, organization, or external system that plays a role inone or more interactions with your system. Actors are drawn as stick figures.
Associations.
Associations between actors and use cases are indicated in use casediagrams by solid lines. An association exists whenever an actor is involved withan interaction described by a use case. Associations are modeled as linesconnecting use cases and actors to one another, with an optional arrowhead onone end of the line. The arrowhead is often used to indicating the direction of theinitial invocation of the relationship or to indicate the primary actor within the usecase. The arrowheads are typically confused with data flow and as a result I avoidtheir use.
System boundary boxes (optional).
You can draw a rectangle around the usecases, called the system boundary box, to indicate the scope of your system.
 
Anything within the box represents functionality that is in scope and anythingoutside the box is not. System boundary boxes are rarely used, although onoccasion I have used them to identify which use cases will be delivered in eachmajor release of a system.
Packages (optional).
Packages are UML constructs that enable you to organizemodel elements (such as use cases) into groups. Packages are depicted as filefolders and can be used on any of the UML diagrams, including both use casediagrams and class diagrams. I use packages only when my diagrams becomeunwieldy, which generally implies they cannot be printed on a single page, toorganize a large diagram into smaller ones. 
RELATIONSHIPS IN USE CASE DIAGRAM:Three relationships
among use cases are supported by the UML standard, whichdescribes graphical notation for these relationships.
Include
In one form of interaction, a given use case may
include
another. The first usecase often depends on the outcome of the included use case. This is useful for extractingtruly common behaviors from multiple use cases into a single description. The notation isa dashed arrow from the including to the included use case, with the label“<<include>>”. This usage resembles a macro expansion where the included use case
List ItemsView ItemEdit ItemCreate ItemDelete ItemActor 

Activity (132)

You've already reviewed this. Edit your review.
himetoo liked this
1 hundred thousand reads
priyankaAGM added this note
its very useful
priyankaAGM liked this
dharanimanickam liked this
sureshsugan liked this
mike61969 liked this
Sharmila Nathan liked this
1 thousand reads
1 hundred reads

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)//-->