1. UML

2. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test model

3. Model Types of model 1.Use case model  defines the outside (actors) & inside (use case) of the system’s behavior. 2.Domain model  maps real world object into the domain object model. 3.Analysis object model  how source code should be carried out & written. 4.Implementation model  represents the implementation of the system. 5.Test model  test plans, specifications & reports.

4. Model Model is an iterative process. It can represent static or dynamic situations. Model Static Dynamic Represents a system’s behaviors that, taken together, reflect its behavior over time. (e.g.) interaction & activity diagrams Provides a system’s parameters at rest or at a specific point in time. (e.g.) class diagram

5. Why modeling Blue print Clarity Familiarity Maintenance Simplification

6. Advantages of modeling Easy to express complex ideas Reduce complexity Enhance & reinforce learning and training Low cost Easy to change the model

7. UML Grady Booch, James Rumbaugh and Ivar Jacobson combine the best features into a unified method called: Unified Modeling Language (UML)

8. What is Unified Modeling Language (UML)? The UML is a graphical / standard language for visualizing, specifying, constructing & documenting the software system and its components.

9. History of UML 1980 – 1990  Many different methodologies 1.Booch method by Grady Booch 2.Object Modeling Technique (OMT) by Jim Rumbaugh 3.Object Oriented Software Engineering (OOSE) by Ivar Jacobson Each method had its strengths & weaknesses. 1.Booch was great in design 2.OMT & OOSE were great in analysis

10. History of UML UML 1.0 (January 1997) UML 1.1 (November 1997) UML 1.3 (Current Minor revision 1999) UML 1.4 (Planned Minor revision 2000) UML 2.0 (Planned Major revision 2004)

11. UML Concepts UML can be used to support your entire life cycle. 1.The interaction of your application with the outside world (use case diagram) 2.Visualize object interaction (sequence & collaboration diagrams) 3.The structure of your system (class diagram) 4.View the system architecture by looking at the defined package. 5.The components in your system (component diagram)

12. What are Diagrams ? Graphical presentation of model elements. A diagram is a graphical means to view a system’s parts

13. UML Diagrams 8 diagrams You will model the following 5 diagrams only: 1.Use case diagram 2.Activity diagram 3.Sequence diagram 4.Collaboration diagram 5.Class diagram The other UML diagrams that can be modeled in Rose are: 1.State chart diagram 2.Component diagram 3.Deployment diagram Interaction diagram

14. Behavior Diagram Sequence diagram Collaboration diagram State chart diagram Activity diagram Interaction diagram behavior diagram

15. UML Diagrams 1.Class diagram 2.Use case diagram 3.Activity diagram 4.Sequence diagram 5.Collaboration diagram 6.State chart diagram 7.Component diagram 8.Deployment diagram 9.Package Diagram

16. 1. Class diagram Class  a set of objects that share the same attributes, operations & relationships. It represented by a compartmented rectangle. It shows the structure of software. 3 compartments 1.Top  shows class name 2.Middle  shows class attributes 3.Bottom  shows class operation

17. 1.Attributes  defines the characteristics or structure of a class.  displayed in the middle of the compartmentalized rectangle. 2. Operation  the service provided by the class.  displayed in the bottom of the compartmentalized rectangle.

18. Class Diagram for ATM