1. Introduction to UML: Why use UML | Explained in Hindi| UML Made Easy

The video describes UML- its need, history and importance.

Object Modelling Using UML UML is a modelling language.  Not a system design or development methodology Used to document object-oriented analysis and design results. Independent of any specific design methodology.

UML Origin OOD in late 1980s and early 1990s:  Different software development houses were using different notations.  Methodologies were tied to notations. UML developed in early 1990s:  To standardize the large number of object- oriented modelling notations that existed.

UML Lineology Based Principally on:  OMT [Rumbaugh 1991]  Booch’s methodology[Booch 1991]  OOSE [Jacobson 1992]  Odell’s methodology[Odell 1992]  Shlaer and Mellor [Shlaer 1992]

Different Object Modeling Techniques in UML UML Booch’s Methodolog y OOSE OMT

UML as A Standard Adopted by Object Management Group (OMG) in 1997. OMG is an association of industries Promotes consensus notations and techniques UML also being used outside software development area:  Example car manufacturing

History of UML Industrialization Standardization Unification Fragmentation Other methods Booch'91 OMT-1 OOSE Booch'93 OMT-2 UML 0.9 & 0.91 Unified method 0.8 UML 0.9 & 0.91 UML 1.1 public feedback UML 2.0

Developments to UML • UML continues to develop: – Refinements – Making it applicable to new contexts UML 1.X UML 1.0 UML 2.0 Application to embedded systems 1997 2003

Why are UML Models Required? Modelling is an abstraction mechanism:  Capture only important aspects and ignores the rest.  Different models result when different aspects are ignored.  An effective mechanism to handle complexity. UML is a graphical modelling tool Easy to understand and construct

Why do we model • Models help us to visualize a system as it is or as we want it to be. • Models permit us to specify the structure or behavior of a system. • Models give us a template that guides us in constructing a system. • Models document the decisions we have made.

UML Diagrams Nine diagrams in UML1.x :  Used to capture 5 different views of a system. Views:  Provide different perspectives of a software system. Diagrams can be refined to get the actual implementation of a system.

UML Model Views Views of a system:  User’s view  Structural view  Behavioral view  Implementation view  Environmental view

UML Diagrams User’s View - Use Case Diagram Structural View - Class Diagram - Object Diagram Implementation View - Component Diagram Environmental View - Deployment Diagram Behavioural View - Sequence Diagram - Collaboration Diagram - State-chart Diagram - Activity Diagram Diagrams and views in UML

UML 2.0 Diagrams UML 2.0 Diagram Behavior Diagram Structure Diagram Class Diagram Composite Structure Diagram Object Diagram Activity Diagram Use Case Diagram State Machine Diagram Interaction Diagram Component Diagram Deployment Diagram Package Diagram Sequence Diagram Communication Diagram Interaction Overview Diagram Timing Diagram

Structural Diagrams • Class Diagram – set of classes and their relationships. • Object Diagram – set of objects (class instances) and their relationships • Component Diagram – logical groupings of elements and their relationships • Deployment Diagram – set of computational resources (nodes) that host each component.

Behavioral Diagrams • Use Case Diagram – high-level behaviors of the System, user goals, external entities: actors • Sequence Diagram – focus on time ordering of messages • Collaboration Diagram – focus on structural organization of objects and messages • State Chart Diagram – event driven state changes of system • Activity Diagram – flow of control between activities
Quotable Quotes on Using UML • “UML is a large and growing beast, but you don’t need all of it in every problem you solve…” – Martin Fowler • The Unified Modeling Language is described as a language for “specifying, visualizing, constructing, and documenting the artifacts of software systems” and for business modeling (OMG UML V1.x documents). The UML reflects some of the best experiences in object- oriented modeling, thus it has the potential to become a widely-used standard object-oriented modeling language. • Robert France, Bernhard Rumpe

Are All Views Required for Developing A Typical System? NO For a simple system:  Use case diagram, class diagram and one of the interaction diagrams only. State chart diagram:  when class has significant states.  When states are only one or two, state chart model becomes trivial Deployment diagram:  In case several hardware components used to develop the system.

• In groups: – History of: OMT, OOSe, Odell’s Methodology Shlaer & Mellor, Limitations and advantages of UML Everyone individually: • Current version of uml • Tools used for UML by various vendors

Видео 1. Introduction to UML: Why use UML | Explained in Hindi| UML Made Easy канала Preeti Mishra