4/11/2011                      State DiagramStatechart Diagram   The Statechart describes the life of an object in terms ...
4/11/2011State Diagrams   Depicts object behavior across use cases   State: collection of values of attributes   State-...
4/11/2011Defining Internal Events and ActivitiesWhen to Draw State Diagrams   State diagrams are good at describing the  ...
4/11/2011State Diagrams Help CompleteSystem Design   State diagrams often reveal use cases    overlooked in earlier analy...
4/11/2011Package Diagram Notation   Folder: Package   Dotted arrow between folders: dependency    link   Two variations...
4/11/2011  Package dependencyThe dependency relationship means that at least one class in a package hasto communicate with...
4/11/2011The Component Diagram   The Component diagram models the physical    implementation of the software.(Deployment ...
4/11/2011Component stereotypes   <<executable>>: A component that runs on a processor   <<library>>: A set of resources ...
Upcoming SlideShare
Loading in …5
×

Tp uml 4_year

352 views
308 views

Published on

Short overview on UML

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • Statechart Diagram
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
352
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
7
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

Tp uml 4_year

  1. 1. 4/11/2011 State DiagramStatechart Diagram The Statechart describes the life of an object in terms of the events that trigger changes in the object’s state. It identifies both the external events and internal events that can change the object’s state. Next, contrast the scope of the Statechart with that of the Sequence diagram. The scope of the Statechart is the entire life of an object. The scope of the Sequence diagram is a single scenario. Consequently, it is possible to derive a Statechart from the set of Sequence diagrams that use the object. 1
  2. 2. 4/11/2011State Diagrams Depicts object behavior across use cases State: collection of values of attributes State-behavior relationship  state is updated by some behavior carried out Notation  States: rounded rectangles  Arrows: state transitions  Labels on Arrows: event/action/use caseExample 1:Book in a Library System start Reserved release New reserve borrow Borrowed activate return Available 2
  3. 3. 4/11/2011Defining Internal Events and ActivitiesWhen to Draw State Diagrams State diagrams are good at describing the behavior of an object across several use cases Use state diagrams only for those classes that exhibit interesting behavior, often the main classes of the system 3
  4. 4. 4/11/2011State Diagrams Help CompleteSystem Design State diagrams often reveal use cases overlooked in earlier analyses of the system State diagrams provide hints on which attributes are necessary for a given classPackage Diagrams Systems are often large  Can be divided into subsystems  In object-oriented contexts, subsystems are packages; packages are groups of classes Package diagrams depict  grouping  dependencies between packages 4
  5. 5. 4/11/2011Package Diagram Notation Folder: Package Dotted arrow between folders: dependency link Two variations  Abbreviated: name in folder  Detailed: name on folder tab, rectangles representing classes in folder area Every subsystem package must have at least one public interface (that is, at least one class with a public interface). 5
  6. 6. 4/11/2011 Package dependencyThe dependency relationship means that at least one class in a package hasto communicate with at least one class in the other package. 6
  7. 7. 4/11/2011The Component Diagram The Component diagram models the physical implementation of the software.(Deployment diagram models the physical architecture of the hardware) The purpose of the Component diagram is to define software modules and their relationships to one another Each component is a chunk of code that resides in memory on a piece of hardware. Each component must define an interface, which allows other components to communicate with that component. The interface and the internal implementation of the component are encapsulated in the classes that make up the component.Defining the Notation for Componentsand Component Dependencies 7
  8. 8. 4/11/2011Component stereotypes <<executable>>: A component that runs on a processor <<library>>: A set of resources referenced by an executable during runtime <<table>>: A database component accessed by an executable <<file>>: Typically represents data or source code <<document>>: A document such as a page inserted into a Web pageComponent interfaces 8

×