1 / 15

UML Introduction

UML Introduction. 7 September 2010. Analysis techniques. IDEF0 DFD ER NIAM IDEF1x State diagrams OO UML. Information system design with UML. Having knowledge of the visual modelling language UML in the field of ICT.

lonna
Download Presentation

UML Introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UML Introduction 7 September 2010

  2. Analysis techniques • IDEF0 • DFD • ER • NIAM • IDEF1x • State diagrams • OO • UML

  3. Information system design with UML • Having knowledge of the visual modelling language UML in the field of ICT. • Gain a clear understanding of applying this knowledge for specifying, constructing, visualizing and documenting software-intensive systems.

  4. Information system design with UML • Having knowledge of the visual modelling language UML in the field of ICT. • Gain a clear understanding of applying this knowledge for specifying, constructing, visualizing and documenting software-intensive systems.

  5. What is the UML? The Unified Modelling Language (UML) is the successor to the wave of object-oriented analysis and design (OOA&D) methods that appeared in the late ’80s and early ’90s. It unifies the methods of Booch, Rumbaugh (OMT), and Jacobson (3 amigo’s).

  6. Data and Processes • Traditional, the division between data and processes • were structured separately, • and functions made use of data • For OO • an object contains data and processes • encapsulation • information hiding • avoiding domino effect adaptations • more simple and cheaper maintenance

  7. UML is for visualizing • An explicit model facilitates communication. • UML symbols are based on well-defined semantics.

  8. UML is for specifying and constructing • Specifying means building models that are precise, unambiguous and complete. • UML addresses the specification of all the important analysis, design, and implementation decisions made in developing and deploying a software system. • UML models are related to OO programming languages.

  9. UML is for documenting • UML addresses the documentation of a systems architecture and all of its details.

  10. UML is a language • UML is a visual language for software blueprints • with a vocabulary and rules for communication; • and a focus on conceptual and physical representations.

  11. UML: graphical notations

  12. UML Models, Views and Diagrams • A diagram is a view into a model • presented from the aspect of a particular stakeholder • and provides a partial representation of the system

  13. UML Views Component view Logical view Use Case view Concurrency view Deployment view

  14. Structure diagram Class diagram Object diagram Component diagram Deployment diagram Package diagram Behaviour diagram Use Case diagram Activity diagram Interaction diagram Sequence diagram Collaboration diagram UML Diagrams

  15. References • Sommerville, Ian (2001) Software Engineering, 6th edition http://www.software-engin.com • Timothy Lethbridge & Robert Laganière (2005) Object-Oriented Software Engineering, 2nd edition http://www.lloseng.com • Martin Fowler (2000, 2004) Object-Oriented Software Engineering, 2nd edition; 3rd edition

More Related