 |
|
|
||
Exercise: your turn ! Create typed Ports that provide and require Interface contracts.
In MD UML one can drag-n-drop valid Types of Ports from the model browser onto Port symbols.
PortServer
Converting an end Property of an Association to an Attribute.jpg)
Converting an attribute Property to a Port
The Convert To Port menu item.jpg)
Viewing Ports in or on a Class in a class diagram
Related Elements > Display Ports
Select Ports.jpg)
Port-based server in Class diagram with boundary
Representing Usage of Interfaces
Client with usage Port class
Migration to graphical usage Port representation
PROBLEM: can't automatically wire-up usage Port to required Interface
Usage Port with manually created Usage relationship
Review of some relationships indicating "usage" 
Classifier-level Dependency Wiring of port-based systems
Port-based Composite Structure Diagrams
Composite Structure Diagram with provided "lollipops" and required "forks" Interface notation
ADVANCED TOPIC: The "Portface" recipe for encapsulated port-based Java engineering in UML2
The «portface» Class as abstract contract for a service provided by a Port
A service required via a Port of a «portface» Class
Basic Java Desktop Application example
NB: Make sure the Show Code Engineering Set option is active in the model browser
Create a new Java code engineering set
Message: choose option import only
Choose code engineering set name and import-only option
Edit code engineering set to select source
Message: Round Trip Set
Set code engineering source directory and add sources
Reverse entire code engineeering set
WARNING: reverse engineering changes can't be undone
Reverse Options: default
Reverse options: fine tuning
Create diagram for reverse engineering and choosing its name and location
After reverse always check the messages window to find any unresolved dependencies
Reversed elements: overview in containment browser
Delete unresolved elements in the Default package
HOWTO add a JAR to the Java ClassPath for the project to resolve unknown references
Repeating a reverse to fix unresolved references
Correctly resolved Classes after repeat reverse
Understanding and adapting reverse engineered diagrams
Creating navigable package diagrams and focus diagrams
Creating a "focus diagram" for each Class in a Package
Manually name a "focus" class diagram after its Class
Starting and hyperlinking a "focus" diagram
Always offer a way out of a focus diagram
.. one can use the Hyperinks/GoTo button (tiny arrow lower left) on a Class to navigate more widely ..
Navigation from a package overview diagram to focus diagrams (and beyond)
Analysing a Class and its nearest neighbours in a "focus" diagram
Convert an attribute into a Property end of an Association by "dragging it out" of its owner's symbol
Attribute converted to Property end of an Association
TIPS for display options of nearest neighbours
Graphical coupling when showing features of associated elements in a "focus" class diagram
Exploring nearest neighbours with Display Related Elements
The Display Related Elements dialog
Showing the Generalization supplier in a "focus" class diagram
Reversing from bytecode by reversing from classpath
Reverse from classpath: options dialog
Beware of graphical coupling when reversing classes with many features !
Displaying only selected attributes/fields and operations/methods using Edit Compartment
The Compartment Edit dialog
Compartment Edit dialog: selected operations
Improved focus diagram with only selected operations showing from related class
Exploring beyond the nearest neighbour in a "focus" diagram
Show crucial interfaces in a "focus" diagram for a class
The natural extent of a "focus" class diagram
Managing physical, logical, and graphical groupings of software model elements
Some pros and cons of text-like attributes vs. graphical associations
Using physical packaging to group Class symbols graphically
Using "wrapper" Components to logically group Classes (without stealing ownership)
Reverse engineering Java variables
Converting object reference attributes to graphical Property ends of Associations
Creating a "focus" Class diagram with immediate Associations
Improved Package Overview diagram
Logically grouping with UML2 Components as "wrappers" 
Java fields and methods as UML attributes and operations
One can show a Property as both an attribute and as a Property end of an Associat
Option [All] under Symbol Properties > Show Association Ends as Attributes
Reversing Java arrays, collection classes, and generics
Reversing Java collections
Collections with resolved generics
Collections with unresolved generics
To resolve or not to resolve collection generics
Template bindings and substitution
TemplateBinding: Dialog
Interface List: TemplateParameters
Using the Analysis options to create «virtual» Dependencies on reverse
Viewing «virtual» Dependencies between Packages using the Package Overview Diagram Wizard
Choose packages for package Dependency Diagram
Resulting Package Overview Diagram with «virtual» Dependencies
Viewing «virtual» dependencies between Packages using Display Paths
Viewing «virtual» Dependencies between Classifiers using Display Related Elements
Does the Analysis option to create Dependencies between Classifiers also catch local variables in methods ?
Reversing the implementation of an operation (Java method)
The Reverse Implementation wizard dialog
Selecting the operation to reverse
Selecting the classes to include
Result of sequence diagram reverse of a Java method
Sequence diagram reverse of static method Main.main()
Physical package overview diagrams
Showing elements related to the elements of a Package 
Avoiding elements external to a Package in its Package overview diagram and module
Modules > Export Module
You will given the opportunity to select additional Packages (which opportunity I'll ignore for now)
You will be asked whether you want to check Dependencies (you should)
Attempt to modularise a Package with graphical coupling
Architectural class collaborations (ThingSystem)
Reverse of LocalTest.Main() implementation to Sequence Diagram
UMLfriendlierTest
Architectural "ball and socket" Dependency wiring
Quantity
Dimension
Unit
UnitsML wrapper overview (manually constructed schema)
UnitType.xsd
EnumeratedRootUnit
ValueSlice
SysML value slice proposal: example of value assignment as BDD
Leaf BDD: manages own static (class-level) primitive default values for value properties
InnerAssembly: manages an «InitialValues» "vector" for the value properties its leaf:Leaf part
RootAssembly: manages «InitialValues» of two different InnerAssembly parts
ExampleValueSlice IBD
«ValueSlice»: manages «Values»owned by either a «ValueSliceModel» or a «ValueSlicePackage»
ModelValueSlice
Why «ValueSlice» has a root:Block attribute (a.k.a. "tag") ?
Explanation: A property path - not a Property - is the unique coordinate for the target of an "instance values" carrier
Meaning and limits of the illustrative «sets» Dependency
propagation of default values, property-specific initial values, and context-specific values
TheValueContext IBD
Drawing of propagation of default values, property-specific initial values, and context-specific values
ValueSlice example: "BeerMachine" in given value context
BeerMachine IBD
ValueContextForBeerMachine IBD
«Configuration» extension of «ValueSlice»
ALTERNATIVE: «ValuesPathPair»: Values/ValueSlice metamodel using decoupled mapping between Values and Property[*] path
ALTERNATIVE: Slot-based: root "instance values tree" at the «ValueSlice» and map to all parts within value context
Analysis of impact on "rooted instance values tree" of changing Block and Property structure
instance tree slots AFTER test structure changed
TypeA: leaf with value property
TypeB: leaf with value property
TypeC: assembly uses TypeA and TypeB
TypeD: reuses assembly TypeC and instance values from a «ValueSlice» for TypeC
TypeE: also resuses TypeC and instance values from a «ValueSlice» for TypeC
[Suggest show both part-specific values & static values "showing through" to part within a value context with static indicator]
"quantity kind" as a generalization/specialization hierarchy
*Dimension (quantity dimension, dimension of a quantity)
*Quantity (quantity) [INCUBATING]
*QuantitySystem (system of quantities)
*Unit (measurement unit, unit of measurement, unit)
base Quantity
derived Quantity
Dimensionless
kind of quantity
ordinal quantity
SI Base Quantities
SI base Units
VIM general and particular quantity examples
[quantity scale]
*DimensionedType
*FrameSpecification
*QuantityProperty
*UnitProperty
*ValueProperty
*ValueType (proposed)
NIST specific/particular quantity examples
Email: please use the contact form Tel: +61 (2) 9386-0090 Post: webel.com.au, PO Box 1816, Bondi Junction, NSW 1355, Australia. ABN: 67 677 268 579 
© Copyright 2000 - 2010 webel.com.au. All rights reserved.
Excluded: selected images from the MagicDraw™ UML and SysML eSchool as referenced by URL, which remain © Copyright 2008 No Magic Inc.
This web site contains educational examples of techniques for parsing text sources into UML™ analysis models.
Where possible explicit permission from authors of original sources has been sought; please report copyright conflicts here.
Text from Wikipedia articles parsed into UML™ analysis models is subject to copyleft under the GNU_Free_Documentation_License
Text from OMG™ specifications - parsed into UML™ analysis models and Drupal™ node titles - remains © Copyright The Object Management Group™.
Text from Java™ tutorials and documentation - parsed into UML™ analysis models and Drupal™ node titles - remains © Copyright Sun Microsystems Inc.
Excluded: selected images from the MagicDraw™ UML and SysML eSchool as referenced by URL, which remain © Copyright 2008 No Magic Inc.
This web site contains educational examples of techniques for parsing text sources into UML™ analysis models.
Where possible explicit permission from authors of original sources has been sought; please report copyright conflicts here.
Text from Wikipedia articles parsed into UML™ analysis models is subject to copyleft under the GNU_Free_Documentation_License
Text from OMG™ specifications - parsed into UML™ analysis models and Drupal™ node titles - remains © Copyright The Object Management Group™.
Text from Java™ tutorials and documentation - parsed into UML™ analysis models and Drupal™ node titles - remains © Copyright Sun Microsystems Inc.
With thanks to Volacci for the wonderful SEO Checklist module.
