-
Key: SYSML11-132
-
Legacy Issue Number: 12222
-
Status: closed
-
Source: No Magic, Inc. ( Darren Kelly)
-
Summary:
Experience modelling a wide range of heterogeneous systems has proven that the representation of logical channels as information flows across connections between flowports nested within standard ports is a very useful idiom. It would help if this possibility is explicitly stated in both 9.3.2.3 FlowPort, 9.3.2.7 Standard Port, and illustrated in specification figures. Example: a software application acquires encoded signals representing physical positon and rotation via a high-level software API to a low-level A./D card in a computer. The software application is connected to an A/D module subject to a contract represented by an Interface provided by a standard port (subject ot a protocol). The flow of information corresponding to logical acquired channels can be well represented as flowports nested within the standard port of the A/D module. This example is illustrated in detail at: http://school.nomagic.com/node/194 It is marked as 'significant' because without this idiom of nesting flowports on standard ports it is impossible or very difficult to model a wide range or real-world systems.
-
Reported: SysML 1.0 — Thu, 14 Feb 2008 05:00 GMT
-
Disposition: Resolved — SysML 1.1
-
Disposition Summary:
No Data Available
-
Updated: Sun, 8 Mar 2015 18:08 GMT
SYSML11 — 09.Ports and Flows: 9.3.2.3 FlowPort, 9.3.2.7 Standard Port
- Key: SYSML11-132
- OMG Task Force: SysML RTF