The document discusses Unified Modeling Language (UML) and object-oriented methodology. It introduces UML, describing it as the standard language for visualizing and modeling software systems. It outlines the main UML diagram types including use case diagrams, class diagrams, sequence diagrams, collaboration diagrams, state machine diagrams, activity diagrams, component diagrams, and deployment diagrams. The document also discusses key concepts of object-oriented methodology such as classes, objects, attributes, and methods.
4. Introduction To UML
What is Unified Modeling Language?
•The UML is the standard language for visualizing,
specifying, constructing, and documenting the
artifacts of a software-intensive system.
•It can be used with all processes, throughout the
development life cycle, and across different
implementation technologies.
•The standard for OO systems
5. Introduction To UML
What is UML Represent ?
The UML combines the best of the best
from:-
• Data Modeling concept
(Entity Relationship Diagrams)
• Business Modeling
(work flow)
• Object Modeling
• Component Modeling
6. Introduction To UML
The Value Of Unified Modeling Language
• Is an open standard.
• Supports the entire software development
lifecycle.
• Supports diverse applications areas.
• Is based on experience and needs of the user
community.
• Supported by many tools.
7. Introduction To UML
UML Usage ….
• Define the boundaries of a system & its major functions.
• Illustrate use cases.
• Define the static structure of a system.
• Model the behavior of objects.
• Document the physical implementation architecture.
• Provide for growth.
8. Introduction To UML
Design Method Evolution …..
1997 OOAD with UML
1990 OOAD
1986 CASE
1986 OOP
1980 4GL
1980 Data Modeling
1980 Structured Analysis
1975 Structured Design
1970 Structured Programming
9. Introduction To UML
UML Support………..
Relationships
ORDBMS
Oracle Business Objects
large scale system
Classes
Objects
Use Cases
Components
Microsoft Scenarios
application partitioning
CORBA
OMG
ActiveX/COM
Microsoft
Business Process
11. Object-Oriented Methodology
Hint To know About ……
•A program will typically consist of objects that
cooperate to solve a task.
•An object will typically have attributes (data) and
methods (behavior), this defines the state of the
object and the manner in which the object operate.
•Objects communicate by sending messages to each
other. Sending a message to an object is the same
as calling a method of the object.
12. Object-Oriented Methodology
Hint To know About ……
- Class: A description of a set of objects that share
the same attributes, operations, relationships, and
semantics.
- Object: A concrete manifestation of an
abstraction; an entity with a well defined boundary
and identity that encapsulates state and behavior;
an instance of a class.
15. UML Diagram Classifications
Diagrams Classifications ……..
State
State
Diagrams
Class
Use Case Diagrams
Use Case Diagrams State
Use Case Diagrams
Use Case State
Use Case Diagrams Diagrams
Object
Diagrams
Sequence Diagrams Diagrams
Diagrams Diagrams
Diagrams
Scenario State
Scenario State
Diagrams
Collaboration Diagrams
Component
Diagrams Models Diagrams
Diagrams Diagrams
Scenario Component
Scenario Component
Diagrams
Deployment
Diagrams
State machine Diagrams
Diagrams Diagrams
Diagrams Activity
Diagrams
Static
Dynamic
16. UML Diagram Classifications:-
Classification Of UML …..
• Use Case Diagrams
– Requirements
• Activity Diagrams
– Generally what, not who - good to detect parallelism
• Interaction Diagrams
– Sequence Diagrams (timeline)
– Collaboration Diagrams (object centered)
17. UML Diagram Classifications:-
Classification Of UML …..
• Static Structure Diagrams
– Objects/Classes/Packages
• State Chart Diagrams
– States of objects with interesting lifecycles
• Implementation Diagrams
– Component Diagrams
– Deployment Diagrams