120 likes | 143 Views
UML Notation Overview. by Brian Lawler Brian.Lawler@JHU.edu. Each of these symbols is from a model for a communications system Basic options are: Round Top and Round Sides Flat Top and Round Sides Flat Sides with Round Corners Flat Sides with Sharp Corners 3D Rectangle The shape conveys:
E N D
UML Notation Overview by Brian Lawler Brian.Lawler@JHU.edu
Each of these symbols is from a model for a communications system Basic options are: Round Top and Round Sides Flat Top and Round Sides Flat Sides with Round Corners Flat Sides with Sharp Corners 3D Rectangle The shape conveys: High-level vs. Low-level Logical vs. Physical Behavior vs. Structure vs. State Shape Counts Deliver Messages Verify Password Idle CommunicationsController Server Brian.Lawler@JHU.edu
Solid Lines versus Dashed Lines Meaning depends upon diagram Line Style Counts Brian.Lawler@JHU.edu
Compare “open” to “closed” arrows Compare “half” to “full” arrows Arrow Style Counts Brian.Lawler@JHU.edu
Name Server Name Fill Counts Brian.Lawler@JHU.edu
Italics font has a specific meaning This is subtle and easy to miss Other mechanisms can convey the exact same ideas more clearly Other design choices can be easier to understand Bank Account {abstract} Bank Account Savings Account Checking Account Savings Account Checking Account Savings Account Checking Account Font Counts << interface >>Bank Account Brian.Lawler@JHU.edu
Meaning of the diamond shape depends upon the diagram. Context Counts Brian.Lawler@JHU.edu
Cash Register Scale Scanner Monitor Transaction Shapes Count <<boundary>>Scale <<entity>>Transaction <<control>>Cash Register <<boundary>>Scanner <<boundary>>Monitor Brian.Lawler@JHU.edu
In UML, color is has no meaning. Users/Projects may choose to use color for some purpose but: Use cautiously Define in legend Color Doesn’t Count Don’t use color to indicate that this process is performed by a certain part of the system. Use the swim lanes variant of this diagram. - BL [condition 1] [condition 2] Brian.Lawler@JHU.edu
UML is intentionally based upon simple notational elements Symbols have precise meanings Symbols can be hand-drawn Models can be defined with text UML is a purposeful notation: Simple symbols have meaning Symbols combine to complex ideas Clip Art Can dilutes the clarity of the model Creates confusion about whether diagrams are designs or cartoons UML versus Clip Art Brian.Lawler@JHU.edu
Unified Modeling Language(not Unified Drawing Language) You don’t have to draw anything. Your model can be entirely in text using the UML vocabulary. CASE tools store model information in a database. Class: Customer Attributes: Name, Address, Phone Use Case: Sell Stuff Scenario: Successfully Place Order Participants: Customer, Order Taker and Order Fulfillment Scenario: Customer submits order with Order Taker Order Taker places order with Order Fulfillment Order Taker acknowledges order with Customer Brian.Lawler@JHU.edu
Patient Record <<entity>> Patient Record Notation Supports Simple Alternatives Window Company Frame has Department <<subsystem>>Billing <<Component>>Call Handling - or - <<Package>>Billing Most notations in the UML downgrade relatively gracefully into simple but meaningful block diagrams with simple but meaningful text descriptors. Brian.Lawler@JHU.edu