Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.


Share this Page URL
Help

Chapter 14 - Modeling Cross-Cutting Rela... > 14.7 Connecting Functional Flow with... - Pg. 358

358 CHAPTER 14 Modeling Cross-Cutting Relationships with Allocations If a standard activity partition is used without the «allocate» keyword, the part or block rep- resented by the partition retains responsibility for execution of all behavior nodes in the partition (see Chapter 9, Section 9.11.1). This does not employ the SysML allocate relationship, but instead tightly couples the behavior definition to the structural definition. For example, if an action in a standard activity partition is a call behavior action, then the modeling method/tool may automatically make the activity called by the action an owned behavior of the block that represents the partition. In particular, a block's operation can call this activity as its method, as described in Chapter 7, Section 7.5 and Chapter 9, Section 9.11.2. 14.7 CONNECTING FUNCTIONAL FLOW WITH STRUCTURAL FLOW USING FUNCTIONAL FLOW ALLOCATION Flow between activities can either be control flow or object flow as described in Chapter 9, Section 9.5 and 9.6. The following sections address allocating object flow as represented on activity diagrams. Allocation of control flow may be depicted in a similar way as allocation of object flow. Flow allo- cation is typically an allocation of usage because items that flow between model elements are usually specified in the context of their usage.