The Webel Images slideshow (ViewsSlideshow version)

[book] Submitted by webel on Fri, 20/03/2009 - 20:45

WARNING: this large images slideshow may be CPU and bandwidth intensive !

This version uses Drupal's Views Slideshow module and JQuery image rotation.
Select or click on an image to navigate to its description page, where you can see it full size.
Hover mouse pointer over an image to pause the slideshow. Move pointer to resume slideshow.
If the slideshow seems stuck, move the mouse pointer OUTSIDE the entire image display region !

The Webel logos

The Webel logos

DranceWare: SysML mockup of PureData synthesis patches

Drancel RGB accelerometer LED lights prototype

Drancel RGB model as nested UML instances

The RGB LEDs of a Drancel

A composite JSyn software component that performs real-time audio synthesis with AM or VFO

A triaxial accelerometer as used in the original Drancing sensor suit

DAQSource

DAQcard

DranceWare with JSyn audio synthesis: multi-column treetable parameter control GUI

Drancing Java visuals base in UML

Drancing JSyn UML: Overview

Top level UML Composite Structure Diagram of Drancing and DranceWare JSyn

A representation of the 5 triaxial accelerometers used by Drancing as a subsystem (component)

Drancing_java3d.uml

Drancing_swing.uml

Java GUI with multi-column TreeView for DranceWare MIDI (circa 2002)

DranceWare: Java3D: accelerometer interaction demo (snapshot)

DranceWare: Java3D: UML: accelerometer interaction demo

DranceWare Java accelerometer monitor

UML of DranceWare Java accelerometer monitor

Java Swing accelerometer signal view

A simplified representation of a triaxial accelerometer (vector acceleration sensor)

Sample Triggering in JSyn

In the press: "Drancing past the keyboard"

UML diagram of a Drancel LED RGB accelerometer light show unit

The vision: a Drancer with wireless data telemetry of accelerometer signals

Alternative strategies for concealing cables in the Drancing accelerometer suit

DranceWare: Java3D: "body star" accelerometer suit interaction animation

DranceWare: Java: UML of simple accelerometer sensor monitor

Drancing suit 2002: 5 accelerometer "body star" pattern

Drancing suit accelerometer magnitude signals with drum triggers

Photo of the original Drancing accelerometer suit

Drancing "The amazing musical motion sensing suit"

Previously data transmission was via cable with plug and socket connection between a DAQ card and the Drancing sensor suit

Snapshot from a Java3D animation of the MOST radiotelescope

1.2.0. The Java 3D API.jpg

1.4.1. A Simple Recipe for Writing Java 3D Programs

1.3.0. Building a Scene Graph

1.3.0.a. A Java 3D scene graphs is constructed of Node objects in parent-child relationships forming a tree structure.

1.3.0.b. Group vs. BranchGroup_ API notes

1.3.0.c. Each scene graph has a single VirtualUniverse.

1.9.0.a. Adding Animation Behavior In Java 3D

2.2.2 Node Components

1.3.1. High Level Java 3D API Class Hierarchy

1.3.0.d. Each scene graph path in a Java 3D scene graph completely specifies the state information of its leaf

1.3.0.e. Graphic representations of a scene graph can serve as design tool and_or documentation for Java 3D programs

1.4.0. Recipe for Writing Java 3D Programs

1.5.0. Some Java 3D Terminology

1.6.0.a. Simple Recipe Example_ HelloJava3Da

1.6.0.b. Note there is no start the renderer step in either the basic or simple recipes

1.7.1 Combination of Transformations Example_ HelloJava3Db

AMacc3D.pd

AccWavetable2x3.pd

Circles.pd

Compressor.pd

Condition.pd

DSP.pd

DarwiinRemoteOSC accelerometer signal plots

DarwiinRemoteOSC accelerometer signal plots

DranceWare.pd

Drancel.pd

Drancing.pd

DrumSamples.pd

DrumTrig.pd

Drums.pd

FilterCh.pd

Filters.pd

Global.pd

GlobalAM.pd

GlobalScale.pd

GlobalTrig.pd.2

GlobalVFO.pd

Meters.pd.2

Monitor.pd

MonitorWin.pd

MonoToStereoPanned.pd

PlaySample.pd

Record.pd

StereoEcho.pd

StereoOutput.pd

Strips.pd

VFO.pd

VFOacc3D.pd

WiiOSC.pd

Drancel RGB PureData/GEM accelerometer monitors

Drancel RGB monitors: PureData/GEM: (low intensity)

Atom

Baryon

Element

Gauge Boson

Flavor change

Beta decay

W- decay

Forces

Hadron

Lepton

Meson

The Standard Model

Muon

Particle

Quantum Chromodynamics (QCD) in UML

Quark

Statistics

Electroweak Theory

W and Z

Snapshot of a video of a Drancel RGB accelerometer-driven LED light show

Drancel RGB LED accelerometer light show: mini video 1

Drancel RGB LED accelerometer light show: mini video: 3

Drancel RGB LED accelerometer light show: mini video: 4

Drancel RGB LED accelerometer light show: mini video 5

Drancel RGB LED accelerometer light show: mini video 6

Drancel RGB LED accelerometer light show: mini video 7

Drancel RGB LED accelerometer light show: mini video 8

Drancing Wii iSight header image

Powered by MySQL (image, unlinked)

UML logo (image, unlinked)

SysML logo (image, unlinked)

banner left

banner right

home buttons

home buttons

home buttons

home buttons

home buttons

home buttons

HERA particle accelerator: electron Beam Loss Monitor lifetime disruption plots

BLME data analysis extract, for header

TEST CCK ImageField in CustomImage appears ok in teaser

Zone button

Xmas 2008: David Jones, Sydney, shop-front animatronic puppet display

Xmas 2008: Martin Place, Sydney

TEST: BookMadeEasy: CustomImage created as direct child of "BookMadeEasy" Gallery

TEST: TaxonomyRouter: FAILS

TEST CustomImage under private upload

Example of numerical integation and visualisation of a differential equation in the Maple symbolic algebra system

Maple 3d plot animation example

Maple symbolic animation example: the Webel logo

Maple example: symbolic algebra equation and numerical solution

HERA particle accelerator: custom data analysis application

CT scan slice: visualisation example: 1

CT scan slice: visualisation example: 2

JUNG example application: a semantic network with clustering

JUNG: 0. introduction and overview

JUNG: 3.user data: 1.class extension

JUNG: 3.user data: 2.JUNG annotation

JUNG: 3.user data: 3.Copying User Data

JUNG: 3.user data: 4.Decorators, Indexers, and Labellers

JUNG: 5.algorithms: 0. Algorithms

JUNG: 5.algorithms: 1. Graph Matrix Operations

JUNG: 5.algorithms: 2. Clustering

JUNG: 5.algorithms: 3. Topology, Paths, and Flows

JUNG: 5.algorithms: 4. Importance

JUNG: 5.algorithms: 6. Statistics

JUNG: 6.filtering: 0. Filtering

JUNG: 7.visualisation: 0. Visualization

JUNG: 8.utilities: 0. Utilities

MOST radiotelescope: Java3D animation: flyby (4.5M)

MOST radiotelescope: Java3D animation: steering (9.8M)

Snapshot from a JSP web application for the MOST radiotelescope

Figure 1: MOST radiotelescope "skymap" from observation of a strong point source at field centre

Figure 2: A diagram of MOST with the numbering system used in this thesis report (1988)

Figure 3: MOST radiotelescope: A diagram of the coordinate system used in the report (1988)

Reverse-engineering into UML of the TJDO database table structure for the MOST radiotelescope information system application (2004)

Figure 5: The MOST radiotelescope centre fan-beam with field centre at meridian (from 1988)

Figure 10: the MOST radiotelescope synthesised beam

00: cover and title

00: cover and title

02: abstract

03: contents

04: introduction

MOST: UML: synthesis

MOST: UML: Reflector

MOST: UML: Circularly polarised ring Antenna

MOST: UML: Feed

MOST: UML: Waveguide

MOST: UML: Module

MOST: UML: Bay

MOST: UML: Arm

MOST: UML: top-level

JSyn: UML: com.softsynth.jsyn

JSyn: UML: SynthSound with Ports

JSyn: UML: SynthUnit: audio idioms

JSyn: UML: SynthCircuit

JSyn: UML: SynthNote

JSyn: UML: SynthUnit: audio idioms

JSyn: UML: SynthUnit: bus

JSyn: UML: SynthUnit: filters

JSyn: UML: SynthUnit: in out

JSyn: UML: SynthUnit: maths

JSyn: UML: SynthUnit: noise

JSyn: UML: SynthUnit: oscillators

JSyn: UML: SynthUnit: response

JSyn: UML: envelopes

JSyn: UML: samples

JSyn: UML: overview

JSyn: UML: misc

org.myorg.systemproperties.AllPropsNode

org.myorg.systemproperties.OnePropNode

org.myorg.systemproperties:actions

org.myorg.systemproperties:nodes

org.openide.nodes

Spacecraft and exploration of our solar system

Mars exploration

Asteroid

Earth

Jupiter

Mars

Mercury

Moon

Neptune

Planet

Pluto

Saturn

Uranus

Star

Sun

Stellar system

Solar system

Venus

collections and sets

field

function

group

number

operator

Lie group

binary operator

Rules of Algebra

value

relation

space

Overview of Webel seminar props, with coloured team mats, containers, and a variety of classes and objects

Exploring composite structure and state of properties with context containers and coloured instances

156. Exploring composite structure and states of properties with context containers and coloured instances

141. coloured team labels (instances of the TeamLabel class)

127. a set of coloured plastic balls as instances of the Ball class

113: set of plastic lotus flowers with subtle variation as instances of the LotusFlower class

098. playful toy pegs used as Actors (can be easily clipped onto other model elements)

094. white and grey mice as binary states of the Mouse actor

081. set of coloured pens as instances of the Pen class (match each Team's colour)

089. coloured paper clips as instances of PaperClip class (good for marking value state)

039. coloured sticker notes (can indicate value, team ownership, and direction)

004. coloured sticker notes (can indicate value, team ownership, and direction)

174. the blue team's BlueFactory basket (records the history of product creation in AbstractFactory pattern lessons)

180. the pink team's PinkFactory basket, with pink Boxes as containers and the team's ContextMat (records the history of product creation in AbstractFactory pattern lessons, and SysML value state)

138. coloured strings: used as Relationships (Dependency, Association, Connectors) for each team

Neutron Scattering: a primer

TEST: REMOTE: cck image and imagecache

TEST: webel: tiny image remote

TEST: webel: tiny image remote

02. Neutron Man: classes

02. Neutron Man: communication diagram

04. xrays vs neutrons: classes

Shibboleth: sequence diagram: request secure federated document

Shibboleth: pseudo-animation of a request for a secure federated document: artefacts

Shibboleth: pseudo-animation of a request for a secure federated document: UML1.x collaborations

3.1 Players

3.1.a The following names are used in this document for the various functions

3.2.1 Basic SAML Domain Model: classes and subsystems

3.2.1 Basic SAML Domain Model: collaboration

3.2.2 Basic Shibboleth Domain Model

3.2.3 Other SAML-Shibboleth Differences

3.3.1 Origin

3.3.2 WAYF (Where Are You From)

3.3.3 Target

3.4 The Role of Sessions

3.5 Identifying the User

3.5.1 Collaboration: Identifying the User (via WAYF)

3.7 Glossary

OAI Marc reversed

OAI Identifier

OAI-PMH

X3D Schema: reverse engineering to UML in the MagicDraw UML tool (from 2007)

UKeduPerson schema (from 2004)

About the MARC Standards (from 2004)

UML as a hub between software engineering technologies

The UML can be used in combination with any software development process !

The UML Parsing Analysis meta-process may be represented as stereotypes (from 2005)

ExecutionSemantics

Introspection

Lightweight RTC

Robotics Technology Component (RTC)

0. Magicdraw UML content diagrams as executable UML2.0 animation sequencer

1. Homer is enjoying a beer watching tv peacefully in the lounge room

2. Bart rides skateboard over Homer, mocks him and laughs

3. Homer drinks beer in one shot and strangles Bart

4. Lisa laughs at both Homer and Bart then plays jazz on sax

5. Marge comes in to stop them making noise by waving a rolling pin

Animated UML: The Simpsons: overview of Classes (with closed Interfaces)

Animated UML: The Simpsons: overview of Classes (with open Interfaces)

007. Fundamental attitudes

009-010. Hindu Tantra

010-014. Tantra equates the human body with the cosmos

010.a. The two divinities generate around themselves devatas

010.b. The devata are all human in shape

059. Mantra and yantra

061. Mantra

Auxliary diagram: Wikipedia: Chakra

Field (physics)

Lagrangian

Stress-Energy Tensor

Figure 01: Convention and notation for Class/Interface pairs and associated wrapper Component.

Figure 02: Flowport notation for mapping UML2 to Java

Figure 03: Example: neutron beam instrument flowports and blocks for UML2

Figure 04: ExampleBlock convention for block wrapper components and organisation of engineering elements

Figure 05: Example: UML2 composite structure diagram (systems engineering view) of a fictitious neutron beam conditioning bunker.

Figure 06: Example: wrapped class diagram (software engineering view) of a fictitious neutron beam conditioning bunker

Figure 07: Model: Top-level UML2 composite structure diagram (systems engineering view) for the Platypus Reflectometer

Figure 08: Model: Bunker shield assembly for the the Platypus reflectometer as UML2 composite structure diagram with flowport notation.

Figure 09: Model: bunker shield assembly for the Platypus reflectometer as "wrapped block" class diagram.

Figure 11: Model: UML2 composite structure diagram of the monochromator assembly

Figure 10: Model: UML2 composite structure diagram for the monochromation beam stage of the neutron diffractometers of the OPAL NBIs.

Figure 12: Model: UML2 composite structure diagram of the monochromator stage assembly with motorised goniometer rotation, tilt, and translation stages, which are driven by encoded devices.

Figure 13: Model: wrapped block class diagram (software engineering view) for the entire monochromation beam ("logical") stage.

Figure 14: SWT TableTree ModelClient showing an instance of the Platypus reflectometer model.

Figure 15: Simplified SysML version of the Platypus neutron reflectometer model.

UML analysis models of the JIRA system, with custom issue types for feature-oriented software process

UML State Machine Diagram analysis of a JIRA OmniTracker BUG issue workflow

Abstraction of "resolvable" JIRA issue types as UML stereotypes

UML State Machine Diagram analysis of the workflow of a JIRA Feature issue type

Representation of a feature-oriented software process as UML stereotypes corresponding to JIRA issue types

UML State Machine Diagram analysis of the workflow of a custom 'recordable' JIRA issue type

Custom 'recordable' JIRA issue types represented as UML stereotypes

UML State Machine Diagram analysis of the workflow of a custom 'jRequirement' JIRA issue type

Custom 'jRequirement' and 'feature' JIRA issue types represented as UML stereotypes combined with the SysML Requirement approach

Overview of UML and SysML stereotypes for a feature-oriented development process for JIRA issues

'Shape is all the geometrical information that remains when location, scale and rotational effects are filtered out from an object.'

A shape whose points belong all [in] the same plane is called a plane figure..jpg

In geometry a polygon .. is traditionally a plane figure that is bounded by a closed path or circuit, composed of a finite sequence of straight line segments (i.e., by a closed polygonal chain)

These segments are called its edges or sides, and the points where two edges meet are the polygon's vertices or corners.

An equilateral polygon is a polygon which has all sides of the same length.

A regular polygon is a polygon which is equiangular (all angles are equal in measure) and equilateral (all sides have the same length).

A triangle is one of the basic shapes of geometry_ a polygon with three corners or vertices and three sides or edges which are line segments

A quadrilateral is a polygon with four 'sides' or edges and four vertices or corners.

A diagonal can refer to a line joining two nonconsecutive vertices of a polygon or polyhedron

Convex quadrilaterals are further classified as follows:

Parallelogram_ both pairs of opposite sides are parallel

Rhombus or rhomb: all four sides are of equal length.

Trapezium .. two opposite sides are parallel.

Square (regular quadrilateral)_ all four sides are of equal length (equilateral), and all four angles are right angles

In mathematics, a locus (Latin for place, plural loci) is a collection of points which share a property

A circle is the locus of points from which the distance to the center is a given value, the radius.

In mathematics, a conic section (or just conic) is a curve obtained by intersecting a cone (more precisely, a circular conical surface) with a plane.

In the Cartesian coordinate system, the graph of a quadratic equation in two variables is always a conic section, and all conic sections arise in this way

Standpoint: A circle is a kind of ellipse

Standpoint: A circle is a distinct conic

PHP logo (unlinked)

KDE3.5: Desktop Pager: floating widget with overview of desktops and window positions

KDE3.5: window list with multiple desktop structure

KDE3.5: easy to move a window from one desktop to another using top-left corner window menu

KDE3.5: moving window from one desktop to another using KPager mini-app view

KDE 3.5: mini pager in KPanel, with (optionally) named desktops

KDE3.5: ALT TAB gives nice vertical list with rows indicating the application by icon and the window title as text

KDE3.5: active Application (taskbar) icon+title buttons with window stacks in KPanel

Screenshot of time2exercise Drupal CMS web site developed by Webel

Screenshot: PLAY: a musing project: Drupal Ubercart digital music eCommerce demo with PayPal

Snapshot: ethical eMarket affiliate marketing site

PLAYlogo.pd

PLAYlogo.pd: synthesised PLAY logo together with top-level Puredata patch

PLAYtext.pd

PLAY logo: SoundCircles.pd

PLAY logo: LCircle.pd

PLAY logo: StereoEnv~.pd

PLAYlogo: ExpCircleWav.pd

PLAYlogo: DiscCircle.pd

PLAYlogo: RingCycle~.pd

PLAYlogo: FanEnv~.pd

PLAYlogo: PanPong~.pd

Screenshot of a professional services Drupal CMS site developed by Webel

Screenshot of the original MagicDraw UML & SysML online school (2008)

2. Understanding Java Platform, Enterprise Edition

Overview of Enterprise Applications

Tiered Applications

The client tier consists of a client program that makes requests to the middle tier (nested Property version)

The client tier consists of a client program that makes requests to the middle tier (associative version)

The client tier consists of a client program that makes requests to the middle tier (composite version)

In a multi-tiered application, the functionality of the application is separated into isolated functional areas, called tiers

Typically, multi-tiered applications have a client tier, a middle tier, and a data tier (often called the enterprise information systems tier).

The middle tier's business functions handle client requests and process application data, storing it in a permanent datastore in the data tier.

The middle tier's business functions handle client requests and process application data, storing it in a permanent datastore in the data tier: NESTED PROPERTY FORM

Java EE application development concentrates on the middle tier to make enterprise application management easier, more robust, and more secure.

The Client Tier

*Application_Tiered_typical

The client tier consists of application clients that access a Java EE server and that are usually located on a different machine from the server.

The clients make requests to the server

The server processes the requests and returns a response back to the client.

Many different types of applications can be Java EE clients, and they are not always, or even often Java applications.

Clients can be a web browser, a standalone application, or other servers, and they run on a different machine from the Java EE server.

The Web Tier

The web tier consists of components that handle the interaction between clients and the business tier.

Its primary tasks are the following:

Dynamically generate content in various formats for the client

Collect input from users of the client interface and return appropriate results from the components in the business tier.

Collect input from users of the client interface and return appropriate results from the components in the business tier (as composite structure)

Control the flow of screens or pages on the client.

Maintain the state of data for a user's session

Perform some basic logic and hold some data temporarily in JavaBeans components.

Java EE Technologies Used in the Web Tier

Java programming language classes that dynamically process requests and construct responses, usually for HTML pages

Java programming language classes that dynamically process requests and construct responses, usually for HTML pages (port version)

Java programming language classes that dynamically process requests and construct responses, usually for HTML pages (composite structure)

Text-based documents that are compiled into servlets and define how dynamic content can be added to static pages, such as HTML pages.

A tag library that encapsulates core functionality common to JSP pages

Objects that act as temporary data stores for the pages of an application

A user-interface component framework for web applications that allows you to include UI components (such as fields and buttons) on a page, convert and validate UI component data, save UI component data to server-side data stores, and maintain component st

Facelets applications are a type of JavaServer Faces applications that use XHTML pages rather than JSP pages.

A set of standard tags used in JSP and Facelets pages to refer to Java EE components

The Business Tier

The business tier consists of components that provide the business logic for an application

Business logic is code that provides functionality to a particular business domain, like the financial industry, or an e-commerce site

In a properly designed enterprise application, the core functionality exists in the business tier components.

In a properly designed enterprise application, the core functionality exists in the business tier components (composite structure diagram)

Java EE Technologies Used in the Business Tier

The Enterprise Information Systems Tier

The enterprise information systems (EIS) tier consists of database servers, enterprise resource planning systems, and other legacy data sources, like mainframes

These resources typically are located on a separate machine than the Java EE server, and are accessed by components on the business tier

Java EE Technologies Used in the EIS Tier.

Java EE Servers

A Java EE server is a server application that the implements the Java EE platform APIs and provides the standard Java EE services.

Java EE servers are sometimes called application servers, because they allow you to serve application data to clients, much as how web servers serve web pages to web browsers.

Java EE servers host several application component types that correspond to the tiers in a multi-tiered application

The Java EE server provides services to these components in the form of a container

Java EE Containers

The Web Container

Java EE containers are the interface between the component and the lower-level functionality provided by the Java EE platform to support that component

The web container is the interface between web components and the web server.

A web component can be a servlet, a JavaServer Faces Facelets page, or a JSP page.

The container manages the component's lifecycle, dispatches requests to application components, and provides interfaces to context data, such as information about the current request.

The Application Client Container

The application client container is the interface between Java EE application clients, which are special Java SE applications that use Java EE server components, and the Java EE server.

The application client container runs on the client machine, and is the gateway between the client application and the Java EE server components that the client uses.

The application client container runs on the client machine, and is the gateway between the client application and the Java EE server components that the client uses (connected).

The EJB Container

The EJB container is the interface between enterprise beans, which provide the business logic in a Java EE application, and the Java EE server.

The EJB container runs on the Java EE server and manages the execution of an application's enterprise beans.

3. Creating Your First Java EE Application

This chapter gives an overview of the example application and step-by-step instructions on coding the example application.

Clone of This chapter gives an overview of the example application and step-by-step instructions on coding the example application.

Architecture of the Example Application

The example application consists of three main components: DukesAgeResource, a JAX-RS RESTful web service; DukesBirthdayBean, an enterprise bean; and firstcup, a web application created with JavaServer Faces Facelets technology.

DukesAgeResource is a JAX-RS resource that calculates the age of Duke, the Java mascot.

Java EE 6 Tutorial: Types of Enterprise Beans

DukesBirthdayBean is a stateless session bean that calculates the difference between the user's age and Duke's age.

The firstcup web application is a JavaServer Faces Facelets application that accesses DukesAgeResource to display Duke's age, reads in a date provided by the user, accesses DukesBirthdayBean to calculate who is older, and then displays the difference ..

The firstcup web application is a JavaServer Faces Facelets application that accesses DukesAgeResource to display Duke's age, reads in a date provided by the user, accesses DukesBirthdayBean to calculate who is older, and then displays the difference Act.

The firstcup web application consists of the following:

greeting.xhtml: An XHTML page that uses the JavaServer Faces Facelets tag libraries.

Representing structure: the SysML Block, Ports, Connectors

Mathematical Constraints analysis in SysML

SysML extends UML2 Activities and Activity Diagrams

Control as data: control values and control operators.

Probability

[Advanced] Activities as Classes and “Activity decomposition”.

Why you should always (and I really mean always) use explicit Pins on Activities

SysML1.0 adds no additional stereotypes to UML2 StateMachines

Using SysML Requirements

The normative SysML Requirement

Deriving one Requirement from another with SysML DerivedReqt

Refining descriptions of Requirements with other element types using SysML Refine

The SysML Satisfy relationship: tracing fulfillment of Requirements

The SysML Verify relationship, TestCase, and VerdictKind

[Non-standard] on applying the SysML «requirement» Stereotype to UML2 Components.

HOWTO elicit SysML Requirements and how to relate them to other elements.

HOWTO callout SysML requirements metadata into UML notes in MagicDraw UML

HOWTO use hyperlinks and related elements in MagicDraw to trace between source

Allocation in SysML

Allocation, AllocateFrom, AllocateTo

HOWTO «allocate» form one element to another element in MD SysML

Example: decomposing a complex flow using allocations

Using SysML for Project Management

Tracking human resources and working groups using Actors

Generating model reports using MagicDraw UML and MD SysML

Modelling development process with Activities

Hyperlinking from Artifacts to external documents and resources

Stereotype driven development process

Recording the status of elements and test results as “tagged values”

Relating Actor elements to other model elements

People vs. Roles

TIP: Use a BlockPackage or BlockModel to group a Block and supporting elements

Exploit the powerful hyperlinking and diagram icon facilities of MagicDraw for easy cross-navigation between elements, packages, models and diagrams

Watch out for module Dependencies !

On combining UML and SysML to get the best of both worlds in SysML tools

The MD SysML BeerMachine with value state and other fun and interesting examples

Limitations of SysML views and viewpoints (and why Dr Darren claims his wrapper Components are better).

From engineering documents in natural language to understandable SysML models.

To make the recipe work you need the UML2 Component (not officially in SysML)

The SysML Parsing Analysis recipe (currently) works best in the MagicDraw UML and MD SysML tools.

The UML2 Component as logical and graphical «wrapper»

Ownership and the UML2 Component

“To steal, or not to steal ownership; that is the tool vendor question”

Hyperlinked “focus diagrams” for «wrapper» Components

HOWTO trace participation in logical «wrapper» Components: "unwrapping"

HOWTO nest «wrapper» Components to reflect source text paragraph structure

HOWTO separate parsing analysis elements and «source» text «wrapper» Components in Models from systems elements in Packages

Protecting modularisation: On the issue of Relationships from packaged systems elements to source text wrapper Components in "focus diagrams"

People who could benefit from this course:

Scientists interested in graphical associative analysis, modelling, and simulation of systems such as scientific beam instruments, complex natural systems, and taxonomies.

Why graphical, associative, port-based, and patch-based "synthesis engineering" is (potentially) so powerful.

What SysML is and why you should consider it for your systems engineering projects.

Anatomy of the SysML Block element

Dr Darren's SysML Block reference "poster"

Overview of the SysML Diagrams (and the UML Diagrams they are adapted from).

Some example systems used in this course:

Example: the SysML specification's Hybrid Sports Utility Vehicle (HSUV)

Example: port-based engineering example: a modular home entertainment system

Example: MagicDraw UML and MD SysML: the MagicCastle system.

Example: the participants' own domain-specific workshop case study.

Ownership of Elements: Packages, Models, and Components as Namespaces.

UML Classes, UML Properties, and Class Diagrams.

UML Properties as “attributes” of a Class and as Association ends.

UML Ports, Connectors, and the EncapulatedClassifier