1. ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager

2. 2© 2005 Progress Software Corporation ARCH-05 UML 101 Agenda n History and goals of UML n Why learn UML n Types of diagrams n Diagramming in detail n Applying use cases n Summary and conclusions

3. 3© 2005 Progress Software Corporation ARCH-05 UML 101 History of UML n Diagrams became a part of software engineering practice –Flow charts –Data flow diagrams –State transition diagrams n Modern languages and design emerge (1980s) n More formal and structured modeling techniques (early 1990s) –OMT, Booch, State Charts n UML –Booch + OMT + Others

4. 4© 2005 Progress Software Corporation ARCH-05 UML 101 The Result n Full view of application –Fundamental views n Architecture, behavior, collaboration –System/application states n State chart, activity diagram –Interactions and physical structures n Sequence, component, deployment –Why multiple diagrams?

5. 5© 2005 Progress Software Corporation ARCH-05 UML 101 Goals of UML n Provide a visual way of building and exchanging models n Provide ways to extend the core concepts n Be independent of programming language and development processes n Provide a formal basis for working with models n Support higher-level development concepts –Frameworks, patterns and components n Integrate best practices

6. 6© 2005 Progress Software Corporation ARCH-05 UML 101 Agenda Slide n History and goals of UML n Why learn UML n Types of diagrams n Diagramming in detail n Applying use cases n Summary and conclusions

7. 7© 2005 Progress Software Corporation ARCH-05 UML 101 Why Learn About Modeling? n Promotes better communication earlier –Within the development team –With customers n Enables architects and designers to think about solving the business problem –Implementation details don’t impede solution n Can produce software that better meets customers’ needs

8. 8© 2005 Progress Software Corporation ARCH-05 UML 101 Why Learn UML in Particular? n Becoming the de facto standard for modeling n Provides for formal modeling –Models can be proven consistent and correct –Models can be tested –Accurate code generation is possible n Can connect the business problem to the technology solution

9. 9© 2005 Progress Software Corporation ARCH-05 UML 101 Agenda Slide n History and goals of UML n Why learn UML n Types of diagrams n Diagramming in detail n Applying use cases n Summary and conclusions

10. 10© 2005 Progress Software Corporation ARCH-05 UML 101 Types of Diagrams n Use case diagrams –Shows the relationship among actors and cases n Class diagrams –Show class structure and contents n Interaction diagrams –Sequence diagrams n display the time sequence of component interactions –Collaboration diagrams n display components and their links to one another

11. 11© 2005 Progress Software Corporation ARCH-05 UML 101 Types of Diagrams n State diagrams –Shows the sequences of states an application goes through n Activity diagrams –Focuses on flows driven by processing n Physical diagrams –Component diagrams n shows the high level structure of the code itself –Deployment diagrams n shows the configuration of elements at runtime

12. 12© 2005 Progress Software Corporation ARCH-05 UML 101 Agenda Slide n History and goals of UML n Why learn UML n Types of diagrams n Diagramming in detail n Applying use cases n Summary and conclusions

13. 13© 2005 Progress Software Corporation ARCH-05 UML 101 Use Case Diagrams n Using use case diagrams –Visualizing functional requirements n How to draw use case diagrams –Actors and cases

14. 14© 2005 Progress Software Corporation ARCH-05 UML 101 Class Diagrams n Class diagrams – describe types of components in a system and their relationships –Consist of a name, attributes, and operations

15. 15© 2005 Progress Software Corporation ARCH-05 UML 101 Interaction Diagrams n Sequence diagrams and collaboration diagrams are used to demonstrate the interaction of components in a use case n Sequence diagrams –Components and messages/data

16. 16© 2005 Progress Software Corporation ARCH-05 UML 101 Interaction Diagrams n Collaboration diagram –Relationships between components –Ordering of messages

17. 17© 2005 Progress Software Corporation ARCH-05 UML 101 State Diagrams n State diagrams – notes changes of state in the system –Adds state, activity, and transition

18. 18© 2005 Progress Software Corporation ARCH-05 UML 101 Activity Diagrams n Activity diagrams –Workflow and behavior –Think of the old dataflow diagram

19. 19© 2005 Progress Software Corporation ARCH-05 UML 101 Physical Diagrams n Physical diagrams are used when development is complete –Descriptions of physical information –Component and deployment diagrams n Component diagrams –Dependencies among code components

20. 20© 2005 Progress Software Corporation ARCH-05 UML 101 Physical Diagrams n Deployment diagram –Contains nodes and connections n The two diagrams are often combined

21. 21© 2005 Progress Software Corporation ARCH-05 UML 101 Common Questions on UML n Why multiple diagram types? –Different views into the same application –Mostly orthogonal –Needed to represent very different systems n Are they all necessary? –Not for most applications –Concentrate on the ABCs n Architecture, Behavior, Collaboration

22. 22© 2005 Progress Software Corporation ARCH-05 UML 101 Agenda Slide n History and goals of UML n Why learn UML n Types of diagrams n Diagramming in detail n Applying use cases n Summary and conclusions

23. 23© 2005 Progress Software Corporation ARCH-05 UML 101 Applying UML n Always start with your use cases –Help you determine what to build –Establish effective communication with users n An auto dealership application

24. 24© 2005 Progress Software Corporation ARCH-05 UML 101 Define the Architecture n Class diagrams – How will the application be structured? –The data structure of the auto customer

25. 25© 2005 Progress Software Corporation ARCH-05 UML 101 Look at Application Behavior n Activity diagram –Steps in requesting a test drive

26. 26© 2005 Progress Software Corporation ARCH-05 UML 101 Study Collaboration Between Components n Collaboration diagrams show interactions –How the auto dealer application components work together

27. 27© 2005 Progress Software Corporation ARCH-05 UML 101 Applying UML n You have enough to get started coding –Involve other diagrams when different views are needed –Don’t hesitate to modify or add a view if the situation requires n These are living diagrams n The purpose is to communicate

28. 28© 2005 Progress Software Corporation ARCH-05 UML 101 In Summary n Using UML helps create applications that achieve important business goals –Better meet customer needs –Higher quality application –Better communication between designers, developers, and customers

29. 29© 2005 Progress Software Corporation ARCH-05 UML 101 Questions?

30. 30© 2005 Progress Software Corporation ARCH-05 UML 101 Thank you for your time!

31. 31© 2005 Progress Software Corporation ARCH-05 UML 101