Sitemap
Front page
Books
Books at Webel IT Australia.
-
IT zone
- Arduino zone
- C++ zone
- Drupal zone
- Java zone
- PHP zone
-
Pure Data zone (patch-based synthesis)
- GEM zone (visual synthesis for Pure Data)
-
Gallery: PureData+GEM example: The PLAY logo animation: synchronised video and audio synthesis
- PLAY logo: LCircle.pd
- PLAY logo: SoundCircles.pd
- PLAY logo: StereoEnv~.pd
- PLAYlogo.pd: synthesised PLAY logo together with top-level Puredata patch
- PLAYlogo.pd: top-level control patch
- PLAYlogo: DiscCircle.pd as workaround for bad aliasing
- PLAYlogo: ExpCircleWav.pd
- PLAYlogo: FanEnv~.pd
- PLAYlogo: PanPong~.pd
- PLAYlogo: RingCycle~.pd
- PLAYtext.pd
- Video: The PLAY synthesised light-sound circles logo (Pure Data + GEM)
- SQL zone
- Symbolic Algebra zone
-
SysML zone
-
TRAIL: Webel's ultimate guide to Systems Modeling Language with MagicDraw/Cameo
- 00:00: [STUB] Why SysML? Why Model-Based Systems Engineering?
- 01:01: [STUB] SysML Overview
-
01:02: UML 101 for model-based systems engineering with SysML
- Class compartments
- Generalization and VisibilityKind example
- Inherited Feature indicator
- Association and Property - some cases
- InstanceSpecifications with links and Slots
- Internal Structure Compartment vs Composite Structure Diagram
- BehavioredClassifier and provided and required Interfaces
- Required/Provided Interface notation: Ball-and-Socket "dependency wiring" [tool specific]
- UML2 simplified key metaclass hierarchy (excluding relationships) - ADVANCED REFERENCE ONLY
- UML2 simplified key "relationship" metaclasses hierachy - ADVANCED REFERENCE ONLY
- UML2 Activity Diagram - essential metaclasses - ADVANCED REFERENCE ONLY
- UML2 Actions - metaclasses - ADVANCED REFERENCE ONLY
- UML2 StateMachine - metaclasses - ADVANCED REFERENCE ONLY
- UML2 ValueSpecification - metaclasses - ADVANCED REFERENCE ONLY
-
01:03: UML Behavior: StateMachines quick start
- Behavior StateMachines can be used to specify any of the following
- StateMachines - simplified metaclass hierarchy
- UML Event types for triggering Transitions
- uml101 - StateMachines - NOTATION REFERENCE CARD
- Kinds of States
- State configurations
- Effect, Entry, Do, Exit
- Composite state entry and exit points
- Submachines: entryPoint and exitPoint
- Using submachines
- Pseudostates - initial, fork, join, terminate
- Pseudostates - junction
- Pseudostates - choice
- Pseudostates - deepHistory and shallowHistory
- Transitions
-
01:04: UML Behavior: Activities quick start
- uml101 - Activity Diagram - notation - REFERENCE CARD
- Activity example: send and catch Signal
- ActivityPartitions using “swimlane” notation
- Starting an Action that has an InputPin
- Starting an Action that has an InputPin with multiplicity
- Starting an Action that has a ControlPin
- Starting an Action that has a ValuePin - LIMITED SUPPORT
- Parameter vs ActivityParameterNode vs Pin
- ActivityParameterNode cases - REFERENCE CARD
- UML2 Types of Pins - metaclasses
- OR with DecisionNode and MergeNode
- AND with ForkNode and JoinNode
- ForkNode and JoinNode with optional ControlFlow guards - LIMITED SUPPORT
- INCORRECT InitialNode no implicit fork
- CORRECT InitialNode explicit fork
- OPTION double InitialNode
- ExecutableNode has implicit fork
- Loop: running example using DecisionNode and MergeNode
- LoopNode: basic running example
- LoopNode with loopVariable - ADVANCED REFERENCE
- LoopNode: running loopVariable example
- ExpansionRegion: running «iterative» example
- StructuredActitivityNodes (structured actions) - ADVANCED REFERENCE ONLY
-
08:01: The building Blocks of SysML
- ExampleBlock in a Block Definition Diagram (BDD)
- ExampleBlock in an Internal Block Diagram (BDD)
- REFERENCE CARD: Types of Block Properties and Block compartments
- REFERENCE CARD: Property cheat-sheet for Block
- Block, Generalization, Association: Home entertainment system
- SysML Part Property representations
- SysML "shared" Property example
- SysML Reference Property representations
- SysML "shared" Property challenge as objects
- More block Generalization examples: Home entertainment system
- Indicating inherited features: Home entertainment system
- Redefined Properties: Home entertainment system
- Examples of Dependency and Usage
- Dependency vs Usage vs Association vs Connector
- Association vs Connector - detailed
- Associative BDD view
- Useful "user-defined" stereotypes for Blocks: «system context», «system», «subsystem», «external», «domain»
-
08:02: The SysML ValueType, Unit, and using values
- SysML ValueType and QUDV overview
- UML DataType vs SysML ValueType
- Structured vs Primitive DataType
- SysML Complex ValueType
- Using Enumeration in SysML
- Instances with value-carrying Slots
- Instances with part-carrying Slots
- Block level :values and :properties compartments in IBD
- Table 8-1 - Graphical nodes defined in Block Definition diagrams - ValueType - MagicDraw SysML 19SP3
- 08:03: The SysML QuantityKind and Unit
-
08:04: Deep configuration using SysML context-specific values
- Values - BasicCamera with Sensor with pixels - BDD
- Values - BasicCamera with Sensor with pixels - IBD
- Values - CustomCamera with customised Sensor with pixels - BDD
- Values - CustomCamera with customised Sensor with pixels - IBD
- Values - SmartPhone with 2 PhoneCameras - BDD
- Values - SmartPhone with 2 PhoneCameras - IBD
- Values - LuxuryPhoneConfig - BDD
- Values - LuxuryPhoneConfig - IBD
- Context-specific values tree in SysML - DEMO OVERVIEW
- 09:01: Indicating flow on Associations and Connectors
- 09:02: Ports - The basics
- 09:03: Port conjugation in SysML is now Type-based
-
09:04: Ports and contracts
- Hybrid SUV example: Ports with required/provided Interfaces (Block Definition Diagram)
- Hybrid SUV example: Ports with required/provided Interfaces (Internal Definition Diagram)
- Hybrid SUV example: provided/required DirectedFeatures (Block Definition Diagram)
- Hybrid SUV example: provided/required DirectedFeatures (Internal Definition Diagram)
- UML provided/required Interfaces vs SysML DirectedFeatures on Ports
- 09:05: FlowProperty and Ports with flows
- 09:06: ProxyPorts and FullPorts
- 10:01: [STUB] ConstraintBlocks: equations, parametrics, and mathematics in SysML
- 11:01: [STUB] Activity modelling extensions in SysML
- 11:02: Activity Decomposition for functional allocation
- 12:01: Interactions [NOT COVERED]
- 13:01: StateMachines [see UML 101 section]
- 14:01: UseCases in SysML
-
15:01: The Allocate relationship
- Functional allocation of an Activity (definition level) in a BDD with callouts
- Functional allocation of a CallBehaviorAction (usage level) in an Activity Diagram to elements in a BDD
- Allocation of a CallBehaviorActionAction to a PartProperty via an AllocateActivityPartition "swimlane"
- Structural Allocation: USB - Progressive refinement using Allocations
- Allocation matrix in the MagicDraw/Cameo tool
- Allocation table in the MagicDraw/Cameo tool
- Allocation via swimlanes in usage allocation mode - DOs and DON'Ts
- Allocation via swimlanes in definition allocation mode - DOs and DON'Ts
-
16:01: Requirements engineering in SysML
- A most basic Requirement with a 'name', an 'id', and 'text'
- A basic Requirement is an AbstractRequirement
- Derived requirements and the DeriveReqt relationship
- Derived requirements and the DeriveReqt relationship - compartment styles
- Refining requirements
- Satisfying Requirements and the Satisfy relationship
- Requirements and the Trace relationship - metamodel
- Trace used for model element elicitation - callout style
- Trace used for model element elicitation - tagged value and element property styles
- TestCase and Verify metamodel
- TestCase and Verify example - callout style
- Composite (a.k.a. "compound") Requirements
- The Copy relationship
- MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block (all)
- MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block (relations only)
- MagicDraw/Cameo: Satisfy Requirement Matrix: Hybrid SUV vs Block and PartProperty (relations only)
- The non-normative extended requirements
- 17:01: Creating custom Comment stereotypes
-
18:01: Logical grouping with the ElementGroup comment
- The ElementGroup stereotype
- An ElementGroup used for basic Parsing Analysis model element elicitation: Example 1
- An ElementGroup used for basic Parsing Analysis model element elicitation: Example 2
- An ElementGroup in the model tree browser of MagicDraw/Cameo
- Extending the ElementGroup for the Webel Parsing Analysis recipe (a quick look)
- Customizing the ElementGroup extensions for the Webel Parsing Analysis recipe (simplified)
- 27:01: Views and Viewpoints
-
TRAIL: The SysML Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations)
-
Section: SysML-1.6: HSUV sample
- Figure D.1 - Establishing the User Model by importing and applying SysML Profile & Model Library (Package Diagram)
- Figure D.2 - Defining ValueTypes and Units to be used in the Sample Problem
- Figure D.3 - Establishing Structure of the User Model using Packages and Views
- Figure D.4 - Establishing the Context of the Hybrid SUV System using a User-Defined Context Diagram
- Figure D.5 - Establishing Top Level Use Cases for the Hybrid SUV
- Figure D.6 - Establishing Operational Use Cases for Drive the Vehicle
- Figure D.7 - Elaborating Black Box Behavior for the “Drive the Vehicle” Use Case
- Figure D.8 - Finite State Machine Associated with “Drive the Vehicle”
- Figure D.9 - Black Box Interaction for "StartVehicle", referencing White Box Interaction
- Figure D.10 - White Box Interaction for “StartVehicle”
- Figure D.11 - Establishing HSUV Requirements Hierarchy (containment)
- Figure D.12 - Establishing Derived Requirements and Rationale from Lowest Tier of Requirements Hierarchy
- Figure D.13 - Acceleration Requirement Relationships
- Figure D.14 - Requirements Relationships Expressed in Tabular Format (Table)
- Figure D.15 - Defining the Automotive Domain (Automotive Domain Breakdown)
- Figure D.16 - Defining Structure of the Hybrid SUV System (Hybrid SUV Breakdown)
- Figure D.17 - Internal Structure of Hybrid SUV
- Figure D.18 - Defining Structure of Power Subsystem (PowerSubsystem Breakdown)
- Figure D.19 - Internal Structure of the Power Subsystem (Internal Block Diagram)
- Figure D.20 - Blocks Typing Ports in the Power Subsystem (ICE Port Type Definitions)
- Figure D.21 - Initially Defining Flow Specifications for the CAN Bus (CAN Bus Flow Properties)
- Figure D.22 - Consolidating Connectors into the CAN Bus (CAN Bus Description)
- Figure D.23 - Elaborating Definition of Fuel Flow (Power Subsystem Fuel Flow Definition)
- Figure D.24 - Defining Fuel Flow Constraints (Parametric Diagram)
- Figure D.24 - Defining Fuel Flow Constraints (Parametric Diagram) [ANNOTATED]
- Figure D.25 - Detailed Internal Structure of Fuel Delivery Subsystem (Internal Block Diagram)
- Figure D.26 - Defining Analyses for Hybrid SUV Engineering Development (Block Definition Diagram)
- Figure D.27 - Establishing a Performance View of the User Model (Package Diagram)
- Figure D.28 - Defining Requirements and VnV viewpoints (Package Diagram)
- Figure D.29 - Requirements and VnV views exposing elements from the model (Package Diagram)
- Figure D.30 - The Requirements and VnV views with supporting views (Package Diagram)
- Figure D.31 - Defining Measures of Effectiveness and Key Relationships (Parametric Diagram)
- Figure D.32 - Establishing Mathematical Relationships for Fuel Economy Calculations (Parametric Diagram)
- Figure D.32 - Establishing Mathematical Relationships for Fuel Economy Calculations (VARIATION: labels inside)
- Figure D.33 - Straight Line Vehicle Dynamics Mathematical Model (Parametric Diagram)
- Figure D.34 - Defining Straight-Line Vehicle Dynamics Mathematical Constraints (Definition of Dynamics)
- Figure D.35 - Results of maximum Acceleration Analysis (Timing Diagram) [PLACEHOLDER]
- Figure D.36 - Behavior Model for “Accelerate” Function (Activity Diagram) {ELIDED PINS}
- Figure D.36 - Behavior Model for “Accelerate” Function (Activity Diagram) {EXPLICIT PINS}
- Figure D.37 - Decomposition of “Accelerate” Function (Activity and Object Flow Breakdown)
- Figure D.38 - Detailed Behavior Model for “Provide Power” {ELIDED PINS}
- Figure D.38 - Detailed Behavior Model for “Provide Power” {EXPLICIT PINS}
- Figure D.39 - Flow Allocation to Power Subsystem (Power Functional Allocation)
- Figure D.40 - Tabular Representation of Allocation from “Accelerate” Behavior Model to Power Subsystem (Table)
- Figure D.41 - Special Case of Internal Block Diagram Showing Reference to Specific Properties (serial numbers)
- Figure D.41 - Supporting InstanceSpecification tree for 'initialValues (context-specific values) in MagicDraw/Cameo
- INTERLUDE: we are half-way through the trail
- Section: SysML-1.6 specification diagrams: 04 Language and Architecture
-
Section: SysML-1.6 specification diagrams: 08 Blocks
- Figure 8-1: Nested property reference
- Figure 8-2: Abstract syntax extensions for SysML blocks
- Figure 8-3: Abstract syntax extensions for SysML properties
- Figure 8-4: Abstract syntax extensions for SysML value types
- Figure 8-5: Abstract syntax extensions for SysML property paths
- Figure 8-6: Abstract syntax extensions for SysML connector ends
- Figure 8-7: Abstract syntax extensions for SysML property-specific types
- Figure 8-9: Abstract syntax extensions for SysML adjunct properties and classifier behavior properties
- Figure 8-10: Model library for primitive value types
- Figure 8-11: Model library for Unit and QuantityKind
- Figure 8-12 - Block diagram for the Wheel Package (WheelHubAssembly)
- Figure 8-13: Internal Block Diagram for WheelHubAssembly
- Figure 8-14: Defining Value Types with units of measure from the International System of Units (SI)
- Figure 8-15: Vehicle decomposition
- Figure 8-16: Vehicle internal structure (BoundReference example)
- Figure 8-17: Vehicle specialization
- Figure 8-18: Example of Unit, QuantityKind and ValueType definitions
- Figure 8-22: Property-specific types in facility example
- Figure 8-23: Changes in classification over time due to property-specific types
-
Section: SysML-1.6 specification diagrams: 09 Ports and Flows
- Figure 9-1: Port Stereotypes
- Figure 9-2: Stereotypes for Actions on Nested Ports
- Figure 9-3: Stereotypes for Property Value Change Events
- Figure 9-4: Provided and Required Features
- Figure 9-5: Item Flow Stereotype
- Figure 9-6: Usage example of ports with provided and required features
- Figure 9-7: Usage example of proxy and full ports
- Figure 9-8: Water Delivery association block
- Figure 9-9: Internal structure of Water Delivery association block
- Figure 9-10: Two views of Water Delivery connector within House block
- Figure 9-11: Specializations of Water Client in house example
- Figure 9-12: Plumbing association block
- Figure 9-13: Internal structure of Plumbing association block
- Figure 9-14: Water Delivery association block with internal Plumbing connector
- Figure 9-15: Usage example of item flows in internal block diagrams
- Figure 9-16: Usage example of item flow decomposition
- Figure 9-17: Usage example of item flow decomposition
- Section: SysML-1.6 specification diagrams: 10 ConstraintBlocks
-
Section: SysML-1.6 specification diagrams: 11 Activities
- Figure 11-1: Block definition diagram with activities as blocks
- Figure 11-2: CallBehaviorAction notation with behavior stereotype
- Figure 11-3: CallBehaviorAction notation with action name
- Figure 11-4: Control flow notation
- Figure 11-5: Block definition diagram with activities as blocks associated with types of object nodes, variables, and parameter
- Figure 11-8: Abstract Syntax for SysML Activity Extensions
- Figure 11-9: Control values
- Figure 11-10: Continuous system example 1 {ELIDED PINS}
- Figure 11-10: Continuous system example 1 {EXPLICIT PINS}
- Figure 11-11: Continuous system example 2 {ELIDED PINS}
- Figure 11-11: Continuous system example 2 {EXPLICIT PINS}
- Figure 11-12: Continuous system example 3 {EXPLICIT PINS}
- Figure 11-13: Example block definition diagram for activity decomposition
- Figure 11-14: Example block definition diagram for object node types
- Section: SysML-1.6 specification diagrams: 12 Interactions
- Section: SysML-1.6 specification diagrams: 13 StateMachines
- Section: SysML-1.6 specification diagrams: 14 UseCases
-
Section: SysML-1.6 specification diagrams: 15 Allocations
- Figure 15-1: Abstract syntax extensions for SysML Allocation
- Figure 15-2: Abstract syntax expression for AllocateActivityPartition
- Figure 15-3: Generic Allocation, including /from and /to association ends
- Figure 15-4: Behavior Allocation
- Figure 15-5: Example of flow allocation from ObjectFlow to Connector
- Figure 15-6: Example of flow allocation from ObjectFlow to ItemFlow
- Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty
- Figure 15-8: Example of Structural Allocation
- Figure 15-9: Allocation Matrix showing Allocation for Hybrid SUV Accelerate Example
-
Section: SysML-1.6 specification diagrams: 16 Requirements
- Figure 16-1: Abstract Syntax for Requirements Stereotypes
- Figure 16-2: Requirements Derivation
- Figure 16-3: Links between requirements and design
- Figure 16.4: Requirement satisfaction in an internal block diagram
- Figure 16-5: Use of the copy dependency to facilitate reuse
- Figure 16-6: Linkage of a Test Case to a requirement (and Figure 16-7)
-
Section: SysML-1.6: HSUV sample
-
Webel's Best Practice policy notes for UML and SysML and the MagicDraw/Cameo tools
- Webel: First recommended style and project option steps for every UML and SysML project in MagicDraw/Cameo.
- Webel: Recommend maintain a basic black-and-white style file for starting new projects. Webel course attendees have access to a basic Webel.stl file (or clone and tune the 'OMG SysML style').
- "Trust the Metaclass or Stereotype" of an Element to indicate what type of element it is (you don't have to repeat it in the name)
- "Trust the Namespace" - DO NOT repeat information in names of owned elements that can be gleaned from the owner or ancestor (and is usually easily shown using display options). It is WET, it breaks the DRY principle!
- A common interpretation of composite Aggregation of a part property in SysML domain modelling is that if the owner Block is "destroyed" so is the child part property. Webel adopts these semantics always.
- AVOID "mixed" functional (behavioral) allocation levels! DO NOT Allocate from Usage level (Action) to Definition level (Block) or from Definition level (Activity) to usage level (part Property) - even if formally permitted in SysML.
- AVOID (where possible) SysML Unit names that are the same as unit symbols
- AVOID (where possible) SysML ValueType names that are the same as the name of units or unit symbols
- About the Single Source of Truth (SSOT) and Don't Repeat Yourself (DRY) principles
- Always consider including an abstract (sometimes intermediate) base Block in your domain modelling Generalization hierarchy.
- Always use either anonymous or 'lowerCamelCase' or 'tla' acronyms for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")!
- Associative BDDs are best used as staging diagrams for you (and SysML-fluent experts), IBDs usually make better presentations diagrams for a wider audience of general engineers and other stakeholders.
- Avoid mixing flow properties on the Type of a Port with directed features (operations and values); One distinguishes between "ports with flows" and "contract ports".
- Cameo/MagicDraw: The Classifier specification setting 'isAbstract' is (for reasons that beggar belief or engineering reason) not by default visible in the Element specification dialog. Enable expertise level 'All' (and for always everwhere).
- Colours: Strongly recommend (insist) use black symbol borders and no symbol fill (or white symbol fill) EXCEPT for special highlighting. DO NOT use the default VENDOR-SPECIFIC line and fill colours for symbols!
- Colours: Very strongly recommend (insist) DO NOT use shadows or gradient fill adornments on diagrams!
- Consider creating a "focus" Block Definition Diagram (or Class Diagram) for the each main Block (or Class) with expanded feature details and relationships to at least nearest neighbours
- Consider hiding the name of a named Port or Property in a Diagram if its Type is sufficient to indicate its role.
- DO NOT name the Type (Block or InterfaceBlock) of a Port with a flow the same as the name of the 'Stuff' that flows through it; use the Webel 'F_Stuff' convention!
- DO NOT use Connector names that are identical to the names of the Associations that type them!
- DO NOT use Property names that are identical to the names of the Classifier (Class, DataType, Block, ValueType) that type them!
- DO NOT use spaces in Property names or Class/Block names! If you want to communicate familiar names of elements within an organisation use a custom stereotype and tagged values (such as 'aka')!
- FlowProperty naming. Use anonymous or just 'i' for in, 'o' for out, and 'io' for inout. "Trust the Type". For conjugation ~InterfaceBlock use 'o' for in, 'i' for out, and 'oi' for inout.
- For SysML Blocks and InterfaceBlocks used to type Ports with contracts use the naming convention 'I_UpperCamelCase' [may be combined with acronymn conventions]
- For SysML Blocks and InterfaceBlocks used to type Ports with flows use 'F_UpperCamelCase' [may be combined with acronymn conventions]
- If an abstract Block or Class in a domain model has Associations to Blocks or Classes that are not also abstract, it's often a hint that you have not identified a correct abstraction layer.
- If instances of Blocks “communicate” with each other use an Association between them.
- If using "French style" post-adjective naming in English use a trailing underscore after the noun and before the adjective or qualifier: Vin_rouge, Cable_digital. Can be combined with TLA acronyms: Player_DVD.
- If you are using model queries (such as table and report extraction) you may not always be able to use anonymous Property names and anonymous instance level element names
- If you must name your Ports or Pins, name them simply 'i', 'o', or 'io' to indicate direction UNLESS you have to indicate a special role like 'iRole', 'oAuxiliary'. DO NOT use Port names like 'input', 'output', etc.
- In SysML diagrams, showing the context name and type in the diagram frame can lead to clutter and is not always clear to non-SysML stakeholders (although that is the style used in the specification samples)
- In general, the SysML DirectedFeature approach is more powerful and the notation is cleaner than UML provided/required Interfaces. Prefer SysML DirectedFeatures unless you have really a good reason to use Interfaces!
- In most Webel examples, the default is chosen to be 'out' if there is a single FlowProperty, so a Port with the type applied will act as a source. If an InterfaceBlock is used, then a Port typed by the conjugating ~InterfaceBlock will act as a sink.
- In the Webel recipe for SysML, DO use a "standard" Port until you have a truly compelling reason to commit to a FullPort or ProxyPort
- It is NOT true in SysML that you "should" always use a SysML FullPort or a SysML ProxyPort instead of a "standard" Port, and it's not even always a good idea (and the spec states this very clearly in multiple places)!
- Just because you can't see a Feature or some other aspect of a UML or SysML Element in a tool on a symbol does NOT mean it does not exist in the underlying model (repository)!
- MagicDraw/Cameo: Keep most elements out of the top-level of a project (i.e. not directly under the project Root). Have one top-level index/content/package diagram.
- MagicDraw/Cameo: On EVERY project of ANY kind set the Environment Perspective to Full-Featured and check the Expert box, even if you are a "novice".
- MagicDraw/Cameo: Set EVERY element properties and symbol properties filter to 'All' (yes, not just 'Expert', to 'All', even if you are a "novice" on your first project) in EVERY dialog and every project option setting. Use the dialog search filters!
- MagicDraw/Cameo: ValueType naming: The ISO-80000 libraries use 'lower case' (sometimes with spaces and/or with [scaling] indicated in square brackets).
- Prefer 'UpperCamelCase' (a.k.a. PascalCase) names for Behaviors such as Activities intended for use in CallBehaviorActions, or at least use a 'Capital first letter'; avoid 'all lower case' (as it leads to confusion with lower case Action names)
- Prefer anonymous Actions, or if they must be named, prefer 'lowerCamelCase' or completely 'lower case' (if you do absolutely insist on having spaces in action names, but please no other punctuation).
- Prefer not rename Properties when redefining unless indicating a clear change in role.
- Prefer the Name Display Mode 'both' on CallBehaviorAction symbols (rather than 'Show Action Name', 'Show Behavior Name', or 'Show Both or Behavior Name')
- Rule #1: A UML or SysML Element in a tool is NOT just an Element symbol in a diagram! A Note is not an Element (compare with a Comment).
- Style: use line width 2 or 3 on the border of the "focus" element in "focus" diagrams (such as the main Block or Class of a dedicated Block Definition Diagram or Class Diagram)
- SysML Blocks have lots of possible features and compartments, lots of capabilities, and are very powerful! But you don't have to use every aspect of a Block (or show every aspect in every diagram) at once on every project.
- SysML: Webel recommends use of an additional custom «requirementGroup» stereotype for compound Requirements that serve as owning Namespaces and are subject to the satisfaction policy that all child requirements must be satisfied.
- SysML: You don't need to call every ConstraintBlock a 'SomethingEquation'
- The Webel modelling style, naming conventions, and Best Practices for SysML are more consistent than most SysML specification diagrams. When following Webel courses please DO NOT use the spec sample diagrams as visual references!
- The default display of all tagged values on the comment symbol for an ElementGroup can make diagrams cluttered, but you can extend it with a custom stereotype and customise the default visible tagged values.
- Use 'UpperCamelCase' (a.k.a. PascalCase) names for Classifiers such as UML Classes and SysML Blocks) to avoid confusion with 'lowerCase' Property names [see however special naming conventions for acronyms and SysML contract and flow Blocks]
- Use of 'this-that' with a hyphen in Connector names is admissable (where 'this' and 'that' indicate Connector ends or their types)
- ValueType naming: The Webel convention is 'UpperCamelCase' (a.k.a. PascalCase).
- Verbose block property names and port names can help tracing participation of properties and ports in requirements relationships and play nicely with current SysML callout style.
- Webel has suggested that SysMLv2 should support verification of each individual claim of more than one Element helping to Satisfy a Requirement.
- Webel recommends (usually) display the header of a Package, Model, ModelLibrary, or Profile in the 'tab' (rather than 'top')
- Webel suggests using a verbose 'name' for leaf (child) Requirements but NO 'text' to prevent Single Source of Truth issues and for improved callout vs relationships (but this might not always work when syncing with external requirements management tools)
- Webel use editorial Sterotypes prefixed with ! and ? in and in CAPS in keywords such as: «!». «?», «!ERROR», «!ISSUE», «!CAUTION», «!WARNING», «!CAVEAT», etc.
- When domain modelling with SysML, Generalization, inheritance, and even multiple inheritance are not "evil" and can be used relatively freely. We are not doing code-oriented Decorator patterns - an implementation choice - we are doing domain modelling!
- When satisfying a Requirement with a Block, you need to ask whether the Block (all instances) satisfies the Requirement or whether only a particular usage of the Block (such as a part property) Satisfies the Requirement!
- When using acronyms in names of Classifiers either treat them as a word 'TlaLikeThis' or suffix with an underscore 'TLA_LikeThis', except at the end of the name 'LikeThisTLA' is admissable.
-
The Webel Parsing Analysis recipe for SysML
- Even relatively informal elicitation of model elements using the SysML ElementGroup and a Parsing Analysis approach is extremely powerful.
- Humans work well with natural language: Many stakeholders – including those who are not necessarily familiar with UML or SysML modelling symbols and diagrams - benefit enormously from having plain text in diagrams side-by-side with graphics.
- In Webel Parsing Analysis if you want to track implied model elements that have not been explicitly mentioned in source text you can introduce an Element-level custom tracking Stereotype with the keywords «implied» or «assumed».
- Not even the most experienced requirements engineers can easily state requirements perfectly in consistent requirements-friendly language first shot; requirements and constraints are often buried in the natural text of domain source documents.
- The Webel Parsing Analysis recipe for SysML does not use the ElementGroup directly, it extends it as a user-defined Snippet stereotype with keyword «snippet» and with MagicDraw Customization.
- The Webel Parsing Analysis recipe promotes a clearly scoped modelling workflow.
- The grouping of member elements by an ElementGroup is denoted here "logical" in the sense that it does not "steal ownership" of member elements (as opposed to "physical" ownership of elements in the model)
- Translating authoritative technical documents written in “natural” engineering language (snippet-by-snippet) into Webel Parsing Analysis diagrams creates consistent underlying systems models and can bridge easily to existing methodologies.
- Webel Parsing Analysis (with strict traceability of all elicited model elements) can be used side-by-side with "freestyle" modelling with incremental benefit the more it is used.
- Webel Parsing Analysis is a "meta-process" that can be applied to general domain source documents to elicit Requirements (and related model elements) or to a Requirements Specification itself as a special case of a domain source document!
- Webel Parsing Analysis «pa» diagrams are "scratchpads" used to elicit model elements traceably from text «snippets». While BDDs are a good initial choice, any kind of diagram can be used as a «pa» diagram.
- Webel Parsing Analysis «pa» diagrams are NOT intended as final presentation diagrams! They serve merely to traceably elicit model elements, which may then be shown in other (typically much tidier) presentation diagrams elsewhere.
- Webel Parsing Analysis: A Snippet (keyword «snippet») must have exactly one 'source' Document (keyword «document»).
- Webel Parsing Analysis: A custom Document stereotype (keyword «document») extends the UML standard profile Document that extends Artifact (which is NOT in the UML4SysML intersection). Such a Document may act as the 'source' of a «snippet».
- Webel Parsing Analysis: Create a top-level 'source' Package/Model SEPARATE from your project model. All source «document» elements and «snippet» comments and their related «pa» diagrams MUST be ultimately owned by that top-level Package/Model as ancestor!
- Webel Parsing Analysis: If you are processing lots of text from one source «document» create a STUB «snippet» with that «document» set as 'source' and just make copies of it in the model browser as needed. Big time saver!
- Webel Parsing Analysis: If you wish to show a «snippet» comment symbol (with its body text) in a presentation diagram (that is NOT a «pa» diagram) remove the '/members' tagged value from display so the only visible tagged value is 'source'.
- Webel Parsing Analysis: typically the quoted extract text (body) of a «snippet» is a short phrase, a sentence, or a couple of short sentences (but not dozens of sentences).
- MagicDraw SysML Plugin zone
-
Cameo Systems Modeler zone
-
Cameo Simulation Toolkit (CST) zone
- Action Language Helper (ALH) API
- HOWTO invoke an operation as a Transition guard in Cameo Simulation Toolkit
- HOWTO set a ValueSpecificationAction to use the * LiteralUnlimitedNatural to drive an 'insertAt' InputPin on an AddStructuralFeatureValueAction in Cameo Simulation Toolkit and Cameo Systems Modeler
-
HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study
- Figure 14.7 Composite State with two States
- Representing the telephone numbers as Signals
- Overview: Controller class (and its Activity), Dialer Class (and its StateMachine), Number class
- Activity: DialN(n:int)
- CatchDialN: Activity with AcceptEventAction for a SignalEvent and a CallBehaviorAction
- The Controller Activity (classifierBehavior of the Controller class)
- The Connect Activity
- StateMachine for the Dialer class
- StartDialTone and StopDialTone
- The number.append Activity as entry Behavior for the PartialDial State
- The append(n:int) operation and its Activity method Append
- The number.print Activity as exit Behavior for the PartialDial State
- The number validation guard
- The WhenValid Activity as effect Behavior
- A quick look at accessing an Operation on a Transition or ActivityEdge guard with Alf vs ALH
- Screencast: Mini tutorial: UML/SysML: Cameo Simulation Toolkit: StateMachine with doActivity and a Transition with a ChangeEvent trigger
- Screencast: Tutorial: UML/SysML: StateMachines vs Activities: Operation-driven Transition case study - UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit
-
Cameo Simulation Toolkit (CST) zone
-
TRAIL: Webel's ultimate guide to Systems Modeling Language with MagicDraw/Cameo
- Tools and Applications zone
- UML zone
- Web Ontology Language (OWL) zone
- Web technologies zone
- XML zone
-
Profile
- About Webel IT Australia
- About Dr Darren
- Dr Darren Kelly's model-based software and systems engineering résumé
- Dr Darren Kelly's web technologies résumé
-
Dr Darren Kelly's full-career Curriculum Vitae
- Career Profile
-
Record of education, employment, consultancy, and R & D activities
- IT Consultant: Model-Based Systems Engineering (MBSE) with SysML [construction]: Phase2
- SysML specification tracking
- Drupal CMS site migration [Drupal8]
- IT Consultant: Model-Based Systems Engineering (MBSE) with SysML [construction]: Phase1
- IT Training: OMG Systems Modeling Language (SysML) seminar course [construction]
- IT Consultant: Drupal CMS web site migration and PHP scripting for systems engineering resources web site [Drupal8]
- IT Consultant: Model-Based Systems Engineering (MBSE) with SysML [astronomy]
- IT Training: OMG Systems Modeling Language (SysML) seminar course [astronomy, instrumentation]
- IT Training: OMG Systems Modeling Language (SysML) seminar course [astronomy]
- IT Consultant: software architect, systems analyst, Enterprise Java web application developer, Drupal CMS web site developer (Phase6)
- IT Training: OMG Systems Modeling Language (SysML) seminar course [electronics]
- IT Training: OMG Systems Modeling Language (SysML) seminar course preparation and specification tracking [SysML1.5/1.6]
- R&D: Electronics patent development employing the Systems Modeling Language (SysML) and 3D modelling
- IT Consultant: software architect, systems analyst, Enterprise Java web application developer, Drupal CMS web site developer (Phase5)
- IT Consultant (OWL/FHIR) e-Health
- R&D: Drupal CMS developers web site: Drupal8
- IT Training: OMG Systems Modeling Language (SysML) seminar course preparation and specification tracking [SysML1.4/1.5]
- IT Consultant: Drupal CMS web site developer and administrator
- IT Consultant: software architect, systems analyst, Enterprise Java web application developer, Drupal CMS web site developer (Phase4)
- IT Consultant (OCL/UML/MDHT)
- IT Trainer (OCL/UML)
- IT Consultant: software architect, systems analyst, Enterprise Java web application developer, Drupal CMS web site developer (Phase3)
- IT Consultant: Senior Drupal CMS web developer, PHP programmer
- Drupal CMS contributed module development, PHP programming, UML modelling
- IT Consultant: software architect, systems analyst, Enterprise Java web application developer, Drupal CMS web site developer (Phase2)
- IT Consultant: Drupal CMS web site developer, PHP developer
- R&D: Drupal CMS developers web site with UML PHP models [Drupal7]
- IT Consultant: software architect, systems analyst, Enterprise Java web application developer, Drupal CMS web site developer (Phase1)
- IT Consultant: software engineer, systems analyst, Drupal CMS web developer
- IT Consultant: Drupal CMS web developer (multilingual site)
- IT Consultant: Drupal CMS web site development and PHP scripting for systems engineering resources web site
- IT Trainer: UML and SysML systems engineering education for the RAAF and DSTO
- Drupal CMS affiliate marketing web site development
- Drupal CMS eCommerce web site development
- Drupal CMS: Newsletter development and subscription database engineering
- IT Consultant: Drupal CMS video web site re-development
- Drupal CMS technical web site development
- Scientific IT Consultant: UML+Java developer (neutron science)
- R & D: NeXML: a generative XML Schema for the NeXus neutron science data format
- R & D: the Drancing accelerometer real-time music synthesis "air instrument" and Drancel body motion visuals
- OMG's SysML specification tracking [No Magic]
- IT Consultant and Trainer: Expert Advisor for Science, Engineering, and Education
- Computational Physicist: Scientific Software Architect
- Visiting research scientist and software architect
- Computational Physicist: Data Analysis Developer
- R & D: port-based UML, UML analysis, radio astronomy synthesis models
- Java and XML developer, and Unified Modeling Language (UML) architect
- Scientific IT Consultant and UML+Java developer (radioastronomy)
- Research assistant (computer visualisation)
- IT Lecturer
- Research and laboratory assistant, Java programmer, UML analyst
- IT Consultant: Perl programmer, dynamic web site developer
- R & D: the Drancing accelerometer music "air instrument"
- Perl Programmer
- Physicist, C++ programmer, scientific data analysis and visualisation
- Guest researcher/inventor (motion-controlled sound synthesis)
- Postdoctoral research scientist, particle accelerator physics (DESY, Hamburg)
- Postdoctoral mathematical assistant (Hilfsmathematiker)
- Postdoctoral researcher (astrophysics)
- PhD research student (astrophysics, computational data analysis)
- Guest PhD research student (astrophysics) [USA]
- Conference assistant and proceedings sub-editor
- Doktorand (PhD research student, astrophysics) [Germany]
- German language student
- University mathematics tutor
- PhD research student (astrophysics) [Sydney]
- Computational modeling for radioastronomy
- Student vacation employment: C-programmer: digital image analysis
- Student vacation employment: programmer and laboratory assistant
- Qualifications
- Scholarships, grants, and awards
-
Organisations
- Australian Astronomical Optics (AAO) Macquarie University
- Lendlease Digital Delivery
- University of Melbourne
- ANU Advanced Instrumentation and Technology Centre (AITC)
- Ultra Electronics (Avalon Systems)
- University of Tasmania
- National eHealth Transition Authority (NEHTA)
- Sitback Solutions
- Health Direct
- Technocrat
- GreenSoft Pty Ltd
- ecoSmart Building Pty Ltd
- Automatisering og Utvikling av Rutiner (AUR)
- Royal Australian Air Force (RAAF)
- Defence Science and Technology Organisation (DSTO)
- Project Performance International (PPI)
- Object Management Group™ (OMG™)
- No Magic Inc.
- ISIS pulsed neutron and muon source, Rutherford Appleton Laboratory
- Institute Laue-Langevin (ILL)
- NeXus International Advisory Committee (NIAC)
- Bragg Institute, Australian Nuclear Science and Technology Organisation (ANSTO)
- Macquarie University
- Macquarie E-Learning Centre Of Excellence (MELCOE)
- Centre for the Mind, University of Sydney
- International Institute of Business and Information Technology (IIBIT)
- Webel IT Australia
- Dot Communications Internet Service Provider (ISP)
- Danish Institute of Electroacoustic Music (DIEM)
- The European Organisation for Nuclear Research (CERN)
- Deutsches Elektronen Synchrotron (DESY)
- Bundesministerium für Forschung und Technik (German Ministry for Research and Technology)
- BASF The Chemical Company
- Vislab, University of Sydney
- Harvard-Smithsonian Centre for Astrophysics
- Monash University
- Astronomical Society of Australia
- Institute of Theoretical Astrophysics, University of Heidelberg, Germany
- University of Heidelberg (Karls-Ruprecht Universität)
- Goethe Institute, Freiburg
- Deutscher Akademischer Austauschdienst (DAAD) [German Academic Exchange Service]
- Goethe Institute, Sydney
- School of Mathematics and Statistics, University of Sydney
- Molonglo Observatory
- Commonwealth Scientific and Industrial Research Organisation (CSIRO)
- Department of Astrophysics, School of Physics, University of Sydney
- Department of Applied Physics, School of Physics, University of Sydney
- University of Sydney
- Anglo-Australian Observatory at Siding Spring
- Dubbo South High School
-
Publications, Reports, Articles
- An analysis of image formation by MOST (Molonglo Observatory Synthesis radioTelescope)
- Advancements in radiative hydrodynamic simulations of early phases of type II supernovae
- Radiation hydrodynamics of early stages of type II supernovae (PhD thesis)
- Radiation hydrodynamics of early stages of type II supernovae (journal article)
- Type II supernova test cases and breakout modelling with flux-vector splitting and adaptive gridding
- On the conditions for the existence of self-similar solutions of the 1D hydrodynamic equations
- On symbolic algebra interfaces to numerical initial value problems
- Why is mating disruption of Lobesia botrana ineffective above a particular damage threshold ?
- Mathematical considerations on modelling of emergence and death of Lobesia botrana Schiff.
- The role of beneficials in fungicide treatments of Lobesia botrana
- Mathematical modelling of the effect of mating disruption and xenobiotic treatments on the population dynamics of Lobesia botrana
- Characterisation of Lepton Beam Lifetime Behaviour in HERA
- Many-event lifetime disruption in HERA and DORIS
- The electron beam lifetime problem in HERA
- HERA electron beam lifetime machine studies Dec 1995: (I) Analysis of loss monitor data
- HERA electron-beam lifetime disruption machine studies and observations
- The effect of beam excitation on the HERA electron-beam lifetime disruption
- A catalogue of HERA Electron Loss Monitor observations: (I) 08 Dec 1995 - 18 Dec 1995
- A catalogue of HERA Electron Loss Monitor observations: (II) 28 May 1996 - 10 June 1996
- Dust in accelerator vacuum systems
- Comparison of the frequency of beam loss rate increases due to dust particles in HERA under ion-getter pump and NEG operation
- The effect of a static clearing field on trapped dust particles in the HERA electron ring
- The effect of transverse beam excitation and kicking on the HERA electron beam lifetime disruption
- NeXusBeans: object-oriented software components for the NeXus scattering science data format using Java, UML, and XML Schema technologies
- Port-based systems engineering of block models for control and simulation of Neutron Beam Instruments of the OPAL research reactor using UML/SysML
- NeXML: automating generation of an XML schema and EMF Java bindings from the XML templates
- The Instrument Control and Simulation Modelling Language (ICSML) proposal
- Proposal for a LogicalWrapper element for UML and SysMLv2
- About PLAY
-
IT Education and Training courses
-
UML and SysML training seminars and workshops
-
Course: Model-based systems engineering with the OMG's Systems Modeling Language (SysML®) and the SysML Plugin for MagicDraw® and Cameo™
- Topic outline for full 5-day workshop course version: Model-based systems engineering with the OMG's Systems Modeling Language (SysML®) and the SysML Plugin for MagicDraw® and Cameo™
- Topic outline for 3-day overview course version: Model-based systems engineering with the OMG's Systems Modeling Language (SysML®) and the SysML Plugin for MagicDraw® and Cameo™
- Course: UML-driven, model-based Java software engineering and XML Schema data engineering with MagicDraw
-
Course: Model-based systems engineering with the OMG's Systems Modeling Language (SysML®) and the SysML Plugin for MagicDraw® and Cameo™
-
UML and SysML training seminars and workshops
-
Services
- Service: Model-Based Systems Engineering with SysML
- Service: UML-based Analysis and Design
- Service: UML-driven Software Engineering
- Service: Data analysis, mapping, transformation, and visualisation
- Service: Drupal-driven Content Management System (CMS) web sites
- Service: Media: Video, Audio, Graphics
- Service: Synthesis, simulation, animation
- Service: Photography
-
R & D projects
-
The Drancel motion-driven real-time synthesis "atom"
-
The Drancel light synthesis system
- Video: 4K Drancel Chromæsthesia: The still colourful mind
- Video: 4K: Drancel Chromæsthesia: Swarovski study: Gallery space video mix: Part 1: “Temple of Heaven”
- Video: 4K: Drancel Chromæsthesia: Swarovski study: Gallery space video mix: Part 2
- Video: 4K: Drancel Chromæsthesia: ‘It’s a crystal world !’ Swarovski dedication: Part 2
- Video: 4K: Drancel Chromæsthesia: “Grand Vase”: Gallery space video mix
- Video: 4K: Drancel Chromæsthesia: “Macro Grand Vase”: Gallery space still mix
- Video: 4K: Drancel Chromæsthesia: “Morpheus' Grand Vase”
- Video: 4K: Drancel Chromæsthesia: “Spin Lily” study: Part 1: Gallery space video mix
- The Drancel sound synthesis system
- The Drancel visuals synthesis system
-
The Drancel light synthesis system
- [ARCHIVAL] Instrument ModelServer
- [ARCHIVAL] NeXML: a generative XML Schema with EMF Java bindings for the NeXus format
- [ARCHIVAL] The Drancing accelerometer sensor suit "air instrument"
-
The Drancel motion-driven real-time synthesis "atom"
-
Client showcase
-
GreenSoft zone
-
GreenDesk zone
- Video: Introduction to GreenDesk for Green Star Design & As Built
- Video: Getting Started with the GreenDesk for Green Star Design & As Built TRIAL for selected Materials credits
- Video: GreenDesk tutorial - Credit Criteria Web Worksheets and Submission Forms - Case: GBCA Green Star Design and As Built - Concrete
- Video: A GreenDesk mini-tutorial: Understanding login users and role-based access: Case: A ‘concrete’ user in GreenDesk for Green Star
- Video: A GreenDesk mini-tutorial: Terminology: Login User vs. Author (user profile) vs. Actor (human resource role)
- Video: A GreenDesk mini-tutorial: How to allocate Activities (tasks) to Actors (human resource roles) for project management [SILENT]
- Video: A GreenDesk mini-tutorial: How to target Credit points [SILENT]
- GreenSoft presents GreenDesk® for Green Star® Design and As Built
- The GreenDesk logo
- The GreenDesk animated logo
-
GreenDesk zone
- PPI zone
-
GreenSoft zone
Keywords
Use keywords to identify pages by topic and search by keyword tag
- 3D (2)
- 3rd party (2)
- abstraction (1)
- accelerometer (4)
- AcceptEventAction (1)
- Action Language Helper (6)
- air drums (1)
- air instrument (1)
- air music (1)
- air synth (1)
- Alf (9)
- ALH (5)
- animation (25)
- anonymous (2)
- Arduino (2)
- art (1)
- article (1)
- astronomy (32)
- astrophysics (4)
- Atlassian (1)
- audio (2)
- audio engineering (1)
- audio synthesis (11)
- backing bean (1)
- BalusC (1)
- beam disruption (3)
- beam lifetime (4)
- beam loss monitor (1)
- beam physics (3)
- BeanShell (1)
- Behavior (2)
- black box (7)
- Block (2)
- BREEAM (1)
- building (9)
- business requirement (1)
- C++ (7)
- Cameo Collaborator (1)
- Cameo Simulation Toolkit (50)
- Cameo Systems Modeler (167)
- Cascading Style Sheet (4)
- CDA (1)
- CDI (1)
- Clinical Document Architecture (1)
- CMS (1)
- coding (2)
- command line (1)
- computer visuals (19)
- constraint (1)
- construction (1)
- Content Management System (3)
- Contexts and Dependency Injection (1)
- continuous system (5)
- contract (3)
- control system (1)
- copyright (1)
- course (4)
- CSS (4)
- customer (1)
- Dart (1)
- data (8)
- data analysis (14)
- data format (1)
- data mapping (4)
- data modelling (1)
- data schema (1)
- data structures (1)
- data transformation (1)
- data visualisation (14)
- database (5)
- database schema (1)
- debugger (1)
- Decorator (1)
- Dedicated Server (1)
- deep configuration (6)
- defence (1)
- dependency injection (1)
- dependency matrix (3)
- derived relationships (4)
- Design Pattern (2)
- designer (1)
- DESY (4)
- diagram style (1)
- differential equation (2)
- discrete system (1)
- Docker (1)
- document-driven engineering (1)
- domain analysis (1)
- Domain Specific Language (1)
- Don't Repeat Yourself (1)
- drag-n-drop (4)
- Drancel (19)
- Drancing (1)
- Drumming-by-Dancing (1)
- Drupal (9)
- Drupal module (3)
- Drupal project (3)
- Drupal7 (2)
- Drupal8 (2)
- Drush (1)
- DRY (2)
- e-Health (1)
- Eclipse IDE (1)
- Eclipse Modeling Framework (3)
- education (7)
- electron (4)
- electron beam (2)
- electronics (4)
- embedded systems (1)
- EMF (2)
- energy (3)
- engineering analysis (1)
- Enterprise Java (7)
- enterprise web application (15)
- equation (21)
- error handling (2)
- ESD (2)
- execution (5)
- Extensible Stylesheet Language (2)
- external requirement (2)
- extract (1)
- Facelets (2)
- flow (5)
- flow allocation (2)
- forward-engineering (1)
- Foundational UML (3)
- framing (1)
- frequency (1)
- fUML (75)
- function (1)
- functional allocation (33)
- functional decomposition (5)
- functional requirement (1)
- GEM (19)
- gestural music (2)
- gestural synthesis (2)
- Giant Magellan Telescope (2)
- Git (1)
- graph (5)
- graphical engineering (12)
- graphical user interface (1)
- graphics (8)
- green building (9)
- Green Star (9)
- GreenDesk (11)
- GreenSoft (11)
- ground-based telescope (1)
- guard (1)
- GUI (1)
- hadron (2)
- hardware (2)
- health (1)
- health informatics (2)
- HERA (8)
- high resolution (1)
- hires (1)
- HTML (2)
- human (2)
- human resource (2)
- hyperlink (3)
- icon (1)
- IDE (2)
- IEC80000 (1)
- INCOSE Systems Engineering Handbook (1)
- information (1)
- infrared (2)
- infrared astronomy (4)
- inheritance (9)
- instrumentation (3)
- instruments (1)
- Integrated Development Environment (2)
- interactive worksheet (1)
- Interceptor (1)
- interface component (1)
- ISO-80000 (13)
- ISO/IEC/IEEE 15288 (1)
- ISO/IEC/IEEE 15288-2015 (1)
- issue (1)
- issue tracking (1)
- Jakarta EE (5)
- Java (29)
- Java Data Objects (1)
- Java EE (7)
- Java Persistence API (2)
- Java3D (16)
- JavaScript (2)
- JavaServer Faces (3)
- JavaServer Pages (1)
- JDO (1)
- JIRA (2)
- JPA (2)
- JSF (3)
- JSP (1)
- LEED (1)
- lepton (2)
- light show (11)
- light shows (1)
- light synthesis (10)
- logical decomposition (2)
- logical grouping (2)
- LogicalWrapper (1)
- logo (4)
- macro (1)
- macro photography (10)
- MagicDraw implied relationships (8)
- MagicDraw SysML (151)
- MagicDraw UML (77)
- Maple (6)
- Maplesoft (2)
- material (3)
- Mathematica (2)
- mathematics (31)
- matrix (1)
- MBSE (9)
- MD SysML (6)
- Measure of Effectiveness (8)
- media (2)
- megapixel (1)
- menu item (1)
- metachain navigation (4)
- micro-controller (3)
- model (1)
- model elicitation (2)
- model query (2)
- model-based development (3)
- Model-Based Systems Engineering (41)
- model-driven development (5)
- module (3)
- MOST (24)
- multiple inheritance (5)
- music (1)
- music synthesis (3)
- MySQL (8)
- NBI (3)
- NetBeans IDE (1)
- neutron (1)
- neutron beam (2)
- neutron beam instrument (4)
- neutron science (3)
- NeXML (2)
- NeXus (1)
- night photography (1)
- night-scape (1)
- non-normative (7)
- notation (1)
- numerical solution (4)
- numerics (4)
- Object Constraint Language (2)
- object database (1)
- Object Management Group (1)
- object-relational mapping (6)
- objectdb (1)
- objective function (3)
- OCL (9)
- ODBMS (1)
- office building (9)
- ontology (3)
- OPAL (1)
- open source (1)
- optical astronomy (2)
- optical telescope (2)
- optics (2)
- ORM (6)
- oscillator (3)
- OWL (3)
- pan (1)
- paper (1)
- parametrics (19)
- parsing analysis (31)
- Part Property (1)
- particle accelerator (11)
- particle accelerator physics (5)
- particle collider (5)
- particle physics (2)
- patch-based (10)
- patch-based programming (20)
- PD (22)
- performance (1)
- performance condition (1)
- persistence (1)
- photography (6)
- PHP (8)
- PhpStorm IDE (1)
- physical decomposition (2)
- physics (9)
- Platypus Reflectometer (1)
- PLAY (1)
- port-based engineering (1)
- positron (2)
- presentation option (2)
- primary/replica (2)
- PrimeFaces (1)
- primitive type (1)
- printing (1)
- probability distribution (1)
- profiler (1)
- programming (3)
- programming language (1)
- project management (1)
- Protégé (1)
- proton (2)
- publication (1)
- Pure Data (23)
- Qt (1)
- query (3)
- query matrix (1)
- query table (5)
- quote (1)
- radio astronomy (26)
- radio telescope (26)
- RDBMS (2)
- RDMBS (6)
- real-time synthesis (24)
- refactoring (1)
- reflectometer (1)
- reflectometry (1)
- relational database (9)
- relationship map (2)
- relationship matrix (1)
- report (3)
- report extraction (2)
- report generation (3)
- report table (4)
- repository (2)
- requirement elicitation (1)
- requirements analysis (12)
- requirements engineering (67)
- reverse-engineering (3)
- rich user interface (2)
- Sass (3)
- scattering (1)
- scattering science (3)
- science (32)
- scientific instrument (31)
- scientific unit system (22)
- screencast (3)
- screencast tutorial (1)
- screencast tutorial video (1)
- secondary stereotype (2)
- semantic web (3)
- seminar (6)
- SendEventAction (1)
- serialisation (1)
- service (8)
- SI (1)
- Signal (1)
- signal processing (3)
- simulation (28)
- Single Source of Truth (1)
- SKAMP (1)
- snippet (1)
- software (2)
- software analysis (1)
- software application (1)
- software architecture (2)
- software design (1)
- software development (1)
- software engineering (4)
- software repository (1)
- sound (1)
- sound editing (1)
- sound synthesis (12)
- spectrograph (1)
- SQL (2)
- SSoT (2)
- stakeholder (1)
- standard (3)
- state chart (4)
- State Chart XML (2)
- state machine (5)
- statistics (1)
- stereo (1)
- stereotype (2)
- structural allocation (2)
- Structured Query Language (2)
- supernova (2)
- sustainable development (9)
- symbolic algebra (7)
- symfony (1)
- synchrotron (5)
- Syntactically Awesome Stylesheets (3)
- synthesis (30)
- SysML (70)
- SysML Parametrics (1)
- SysML tool (1)
- system (1)
- system configuration (5)
- system requirement (1)
- systems (8)
- systems engineering (48)
- Systems Modeling Language (54)
- table (5)
- table query (4)
- telescope (29)
- telescopes (1)
- templating (1)
- test engineering (8)
- theming (1)
- time (3)
- TJDO (1)
- tool (1)
- toolkit (2)
- TopBraid (1)
- training (8)
- translucency (1)
- triaxial accelerometer (3)
- TWIG (1)
- UML (77)
- UML-2.5.1 (7)
- Unified Modeling Language (64)
- units (1)
- URI (2)
- URL (2)
- user interface (2)
- vacuum system (1)
- validation (2)
- validation engine (2)
- vendor-specific (1)
- version control (1)
- video (3)
- video editing (2)
- VIM3 (15)
- Virtual Private Server (1)
- virtualisation container (1)
- visual programming (2)
- visuals (17)
- visuals synthesis (18)
- VPS (1)
- water (2)
- We Enjoy Typing (1)
- web (2)
- web application (5)
- web component (3)
- web hosting (1)
- web language (1)
- Web Ontology Language (3)
- web service (1)
- web site (2)
- web technologies (1)
- web technology (3)
- web user interface (3)
- web worksheeet (2)
- Webel Best Practice (49)
- Webel Parsing Analysis (25)
- WET (1)
- white paper (1)
- Wiimote (1)
- Wolfram (1)
- Wolfram Language (1)
- workshop (6)
- WPA::«assumed» (1)
- WPA:«document» (13)
- WPA:«implied» (1)
- WPA:«pa» (9)
- WPA:«snippet» (13)
- Write Everything Twice (1)
- www (1)
- x-ray science (2)
- Xdebug (1)
- XHTML (2)
- XML (5)
- XML Schema (5)
- XSD (3)
- XSL (1)
- XSLT (1)
Video style
Categorise and search for videos by style/type
- 4K (15)
- animation (1)
- annotated (11)
- demonstration (1)
- gallery presentation (8)
- instructional (11)
- live video (1)
- logo (1)
- narrated (9)
- proposal (1)
- screencast (14)
- silent (14)
- tutorial (9)