24-03-2012, 02:50 PM
OBJECT ORIENTED ANALYSIS AND DESIGN
37923576-CS1402OOADLabManual.doc (Size: 738.5 KB / Downloads: 197)
UML NOTATION
• Unified Modeling Language.
• Set of notations and conventions used to describe and model an application.
• Universal language for modeling systems.
• Standard notation for OO modeling systems.
• Does not specify methodology to develop an application.
UML DIAGRAMS
• Class Diagram
• Use Case Diagram
• Behavioral Diagram
Interaction Diagram
Sequence Diagram
Collaboration Diagram
State Chart Diagram
Activity Diagram
• Implementation Diagram
Component Diagram
Deployment Diagram
CLASS DIAGRAM
• Shows the static structure of the model.
• Collection of static modeling elements such as classes and their relationships
connected as a graph.
• Provides visual representation of objects, relationships and their structures
USE CASE DIAGRAM
• Set of use cases enclosed by system boundary, communication association between actors and use cases, and generalization among use cases.
Actors:-
• External factors that interacts with the system from the user's perspective.
SEQUENCE DIAGRAM:
• Describes the behavior of the system through interaction between the system and the environment in time sequence.
• Two dimensions:
Vertical dimension – represents time.
Horizontal dimension – represents objects.
• Life line – Object's existence during the interaction.
STATECHART DIAGRAM
• Models the dynamic behavior of individual classes or any other kind of object.
• Shows the sequences of states, events, and actions.
ACTIVITY DIAGRAM
• Used for modeling the sequence of activities in a process
• Special case of a state machine in which most of the states are activities and most of the transitions are implicitly triggered by completion of the actions in the source activities.
COMPONENT DIAGRAM
• Models the physical components in the design.
• A graph of the design’s components connected by dependency relationships.
• Includes concept of packages.
• Package is used to show how classes are grouped together.