UML_Lecture - EEL5881 Software Engineering I UML Lecture Yi...

Info iconThis preview shows pages 1–13. Sign up to view the full content.

View Full Document Right Arrow Icon
    EEL5881 Software Engineering I UML Lecture Yi Luo
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    About myself Yi Luo TA for EEL5881 3 rd  Year Phd student in CpE Email:  samprasluo@hotmail.com Office hour:  Wednesday 3:00PM-5:00PM in HEC-365
Background image of page 2
    Acknowledgements Slides material are taken from different  sources including: the slides of Mr. Shiyuan Jin’s UML class, EEL 4884, Fall 2003. Object-Oriented and Classical Software Engineering,  Sixth  Edition, WCB/McGraw-Hill, 2005 Stephen R. Schach UML resource page  http://www.uml.org/
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    Outline What is UML and why we use UML? How to use UML diagrams to design  software system? What UML Modeling tools we use  today?
Background image of page 4
    What is UML and Why we use UML? UML → “Unified Modeling Language” Language: express idea, not a methodology Modeling: Describing a software system at a high level of abstraction Unified: UML has become a world standard Object Management Group (OMG): www.omg.org
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    What is UML and Why we use UML? More description about UML: It is a industry-standard graphical language for specifying, visualizing, constructing, and documenting the artifacts of software systems The UML uses mostly graphical notations to express the OO analysis and design of software projects. Simplifies the complex process of software design
Background image of page 6
    What is UML and Why we use UML? Why we use UML? Use graphical notation: more clearly than natural language (imprecise) and code (too detailed). Help acquire an overall view of a system. UML is not dependent on any one language or technology. UML moves us from fragmentation to standardization .
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    What is UML and Why we use UML? 1997: UML 1.0, 1.1 1996: 1995: Unified Method 0.8 Other methods Booch ‘91 Booch ‘93 OMT - 2 OMT - 1 Year Version 2003: UML 2.0 2001: UML 1.4 1999: UML 1.3
Background image of page 8
    How to use UML diagrams to  design software system? Types of UML Diagrams: Use Case Diagram Class Diagram Sequence Diagram Collaboration Diagram State Diagram This is only a subset of diagrams … but are most widely used
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    Use-Case Diagrams A use-case diagram is a set of use cases A use case is a model of the interaction between External users of a software product (actors) and The software product itself More precisely, an actor is a user playing a specific role describing a set of user scenarios capturing user requirements contract between end user and software developers
Background image of page 10
    Use-Case Diagrams Library System Borrow Order Title Fine Remittance Client Employee Supervisor Boundary Actor Use Case
Background image of page 11

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
    Use-Case Diagrams Actors: A role that a user plays with respect to the system, including human users and other systems. e.g., inanimate physical objects (e.g. robot); an external system that needs some information from the current system. Use case:
Background image of page 12
Image of page 13
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/25/2011 for the course EEL 5881 taught by Professor Staff during the Spring '09 term at University of Florida.

Page1 / 40

UML_Lecture - EEL5881 Software Engineering I UML Lecture Yi...

This preview shows document pages 1 - 13. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online