- UML : United Modeling Language
- ER : Entity Relationship
- SDL: Specification and Description Language
- UML 2.0 has MDA and MDD to produce Program code directly. (MDA Model Driven Architecture , MDD Model Driven Development)
- UML Profile ? Helps to define UML for specific environment and needs.
- OCL ? Object Constraint Language and UML Profile helps to directly generate program code.
- Package diagram: Depicts to model a system and its subsystems.Can show dependency. Similar to class diagram.
-
A package diagram can also show dependency using dotted arrow key with
blocked arrow key.
- Example [Inventory System]<------[Order]<------[Sales]
-
Class Diagram: Depicts a the static design of the system; Can show
Attributes, State and Behavioral Constraints
- Inheritance: A completed non-filled triangle arrow head pointing to super class.
-
Association:
- If both class is aware of the association: A line with no arrows between one class to another.
- If only one is aware: A line with open arrow head ____>
- Object Diagram: Depicts the facts and functions of the resources.
-
Component Diagram: To show relationship and dependency between various
software components at its relationship at its implementation stage.
- Example: [EDI] [EJB]_____>(filled triangle arrow)[Database]
-
Deployment Diagram: Uses to show the hardware architecture of the system and
its relationship at its implementation stage.
- Example: [Mobile] or [Browser] 0..* ---------- 1 [Middleware server]
- Combined Component/Deployment Diagram.
- Composite Structure Diagram: To display internal structure of a classifier.
-
Use Case Diagram
- Shows behavioral relationship.
- Generalization is inheritance relationship between cases or actors.
- Association is interaction between actors and use cases.
- <<include>> unconditional relationship. Included in the execution of another use case.
- <<extend>> one use case affects the execution of another use case.
-
Interaction Diagrams: Depicts messages that are sent between various objects
to perform a task.
- Examples: Sequence, Communication, Interaction Overview and Timing Diagrams
-
Sequence Diagram: Contains objects life line,
synchronous, asynchronous messages, self-reference, return, activation
and suspension.
- Synchronous message is shown using closed arrow head.
- Communication Diagram: A numbered way of showing sequential interactions between objects.
- Interaction Overview diagram: Similar to Flowchart
- Timing Diagram: Changing states of an activity with an emphasis on time.
-
State Diagram: To show the states of different objects in an application.
- State Machine Diagram
- Activity Diagram
-
Use Case Scenario: Contains Use Case Diagram, Narrative, Scenario
- Show what users wants from system and vice verse.
- Scope of a project(line of business, system & single sub-system or component) helps to derive a use case.
- Use Case SCenarion helps to define the Requirement, features, end-user goals and implementation mechanism
- 3 types of Actors: Primary (end users), Supporting actors, Offstage actors.
- Actors describes both traceability and generalizations.
TrackBacks[0]
Comments[3]
Posted by balajidl on 30 October 2006 09:39:17 CET
Reply |
Permalink
Re: UML Notes..
sr i want inventory system
Comment from supi on 18 January 2007 17:16:32 CET
On personal opinion, I find this very helpful.
Guys, I have also posted some more relevant info further on this, not sure if you find it useful: http://www.bidmaxhost.com/forum/
Comment from guanhua on 05 April 2007 15:25:22 CEST
Hello sir i have to learn the uml.pls send complete notes...
Comment from Krishnan on 29 August 2008 13:30:09 CEST
TrackBack to http://radio.javaranch.com/balajidl/addTrackBack.action?entry=1162197557001