8 Copyright IBM Corporation, 2006. All Rights Reserved. This publication may refer to products that are not currently available in your country. IBM makes no commitment to make available any products referred to herein. An Introduction to the Unified Modeling Language Omar E. Pérez, PMP [email protected]
47
Embed
An Introduction to the Unified Modeling Language · Jacobson, Rumbaugh, and Booch – The first UML specification was ratified in 1997 – The current UML version is 2.0, which was
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
8 Copyright IBM Corporation, 2006. All Rights Reserved.This publication may refer to products that are not currently available in your country. IBM makes no commitment to make available any products referred to herein.
• A classifier is a category of UML elements that have some common features, such as attributes or operations– Can sometimes be used to refer to a class
• Types of UML classifiers– class– component– data type– interface– node– signal– subsystem– use case
• Provide an extensibility mechanism to UML• Allows tagging existing modeling elements to create new ones• Stereotypes must be defined
– Within the model– By reference to external document
• You can stereotype both classes and relationships• Each model element can have zero to many stereotypes• Graphically rendered as a name enclosed between guillemets
• Use case diagrams consist of– Stick figures that represent actors– Ovals that represent the use cases– Connectors that indicate relationships
• The goals of use case diagrams are– Document important aspects of the system– Give a big picture view of the system– Facilitate requirement prioritization
• Activities are a collection of nodes connected by edges
• Three categories of nodes– Action node – discrete units of work that are atomic with the activity– Control node – control the flow through the activity (branching)– Object node – represent objects used in the activity (data)
• Two categories of edges– Control flow – represent the flow of control through the activity– Object flow – represent the flow of objects through the activity
• Tokens are moved from a source node to a target node across an edge
• The Unified Modeling Language is a standardized set of abstractions for object-oriented software design– Can be adapted to model business and other processes
• The UML consists of diagrams. We covered:– Use Case Diagrams (behavior)– Activity Diagrams (behavior)– Interaction Diagrams– Class Diagrams (structure)
• The initial node is a small filled circle with an edge coming out of it• Control flow is represented by arrows called edges or flows• A rectangle with rounded corners is an action node• Connector nodes are labeled circles that have only either incoming or
outgoing flows, not both• Nodes can have guard conditions, indicated by parenthetical phrases
on edges• Preconditions and postconditions are represented as UML notes• Decision and merge nodes are represented by diamonds• Forks and joins are horizontal bars that represent parallel behavior• Rectangles used to show who or what is responsible for an activity are
8 IBM Corporation 1994-2007. All rights reserved.References in this document to IBM products or services do not imply that IBM intends to make them available in every country.
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
Rational is a trademark of International Business Machines Corporation and Rational Software Corporation in the United States, other countries, or both.Intel, Intel Logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered
trademarks of Intel Corporation or its subsidiaries in the United States and other countries.Linux is a trademark of Linus Torvalds in the United States, other countries, or both.Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the United States and other countries.Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.Other company, product or service names may be trademarks or service marks of others.
Information is provided "AS IS" without warranty of any kind.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.
Information concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute an endorsement of such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the supplier of those products.
All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller for the full text of the specific Statement of Direction.
Some information addresses anticipated future capabilities. Such information is not intended as a definitive statement of a commitment to specific levels of performance, function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here to communicate IBM's current investment and development activities as a good faith effort to help with our customers' future planning.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here.
Photographs shown are of engineering prototypes. Changes may be incorporated in production models.
Trademarks and Disclaimers
AS/400 e-business on demand i5/OSAS/400e IBM OS/400eServer IBM (logo) System i5