Chapter1 UML Overview

Chapter1 UML Overview - Formal System Design Process with...

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

View Full Document Right Arrow Icon
Use a formal process & tools to facilitate and automate design steps: Requirements Specification System architecture Coding/chip design Testing Formal System Design Process with UML Text: Chapter 1.4
Background image of page 1

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

View Full DocumentRight Arrow Icon
Unified Modeling Language (UML) Developed by Grady Booch et al. Version 1.0 in 1997 (current version 2.0) Maintained by Object Management Group (OMG) – www.omg.org Resources (tutorials, tools): www.uml.org Goals: object-oriented (OO); visual; useful at many levels of abstraction; usable for all aspects of design. Encourage design by successive refinement Don’t rethink at each level CASE tools assist refinement/design
Background image of page 2
Emphasis of OO Design Describe system/design as interacting objects Object = state + methods. State defined by set of “attributes” each object has its own identity. Methods provide an abstract interface to the object attributes. Objects map to system HW/SW elements Also model the outside world (users, machines, environment) interactions with the system
Background image of page 3

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

View Full DocumentRight Arrow Icon
UML Elements Model elements objects, classes, interfaces, components, use cases, etc. Relationships associations, generalization, dependencies, etc. Diagrams class diagrams, use case diagrams, interaction diagrams, etc. constructed of model elements and relationships
Background image of page 4
UML Diagram Types Use-case : help visualize functional requirements (user- system interaction) Class : types Object: specific instances of classes Interaction diagrams (dynamic) Sequence: how sequences of events occur (message-driven) Collaboration: focus on object roles Statechart : describe behavior of system/objects Activity : flow of activities in a process (flowchart) Component : physical view of system (code, HW)
Background image of page 5

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

View Full DocumentRight Arrow Icon
Structural vs. Behavioral Models Structural: describe system components and relationships static models objects of various classes Behavioral describe the behavior of the system, as it relates to the structure dynamic models
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 41

Chapter1 UML Overview - Formal System Design Process with...

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

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