distinguish between allocation of usage and allocation of definition allocate function to Logical Element

ConceptDocumentation
System Use CaseThe System Use Cases are a table of content of the services provided by the System of Interest to its System Actors. A System Use Case is only the abstract of the depicted System behavior and represents the purpose. While the main System of Interest interaction actors participating in this Use Case are identified, the behavior itself is specified by a Use Case Activity, Note: The intended use (and also misuse in so called "black use cases") of the System of Interest is captured in free text; story telling at a coarse level of detail which is understandable to Customers (non engineering stakeholders in general).
SUCincludingSUCSpecifies the fact that a System Use Case includes other System Use Cases. The included use case is then no longer a full System Use Case, but a partial System Use Case.
SUCsynthesizingSFNSpecifies the fact that a System Function is used in a System Use Case, e.g., as a Trigger, Action, or Task. Note: This is a derived relationship.
System FunctionSpecifies the fundamental action or task that have to take place in the System in accepting and processing the inputs and in processing and generating the outputs. A System Function * accepts input from the System boundary * exposes its output at the System boundary * changes the System's State * is dependent on System's State Note: A System Function does not need to expose observable output, when it changes the System's state in a way that is observable by other system functions. Furthermore, a System Function does not need to accept any input from the system boundary, when it is dependent on the System State, which in turn is changeable by other System Functions.
GFUEPreceivingINPUTSpecifies the Input of a Functional Usage.
GFUEPsendingOUTPUTSpecifies the Output of a Functional Usage.
General Function Usage Exchange PointA parameter of a System or Context Function.
General Functional UsageSpecifies a General Usage of a General Function within one or more other General Functions.
General Functional ExchangeSpecifies the fact that an General Functional Exchange between General Function Parameters is taking place.
GFEbeingPartOfGFNUSpecifies the fact that a Functional Exchange appears within a general Functiona Usage.
GFEfromGFUEPSpecifies the fact that a General Functional Exchange is coming from a General Functional Usage Exchange Point.
GFEtoGFUEPSpecifies the fact that a General Functional Exchange is going to a General Functional Usage Exchange Point.
GFNcontrolledAFTERSpecifies a sequential execution of Functions.
System ProcessSpecifies the fact that a System Process captures system behavior as a specific sequence of actions or tasks, and system exchanges including information, materials, energy, etc.
SPSrefiningSUCSpecifies the fact that a System Use Case is refined by one System Process.
System Partial FunctionSpecifies the fact that a System Partial Function is a decomposed part of a System Function and defines details of the System Function it belongs to.
Context FunctionSpecifies the fact that a fundamental action or task is expected to be carried out by an External Entity. Note: The intention is to capture the expectations and to explicitly dissect the functionality. This must not be interpreted as an attempt for a behavior specification of an External Entity. Capturing this valuable information is the basis to reach agreement on the functionality at the System boundary by clarifying the expectations about what is performed by Context Elements.
SUCsynthesizingCFNSpecifies the fact that a Context Function is used in a System Use Case, e.g., as a Trigger, Action, or Task. Note: This is a derived relationship.
General FunctionSpecifies a General Function. It is used as base Class for specific System or Context Functions, or Partial Functions.
System Capability1) A System Capability is an operation or task that performs an action to produce a specific performance-based outcome. NOTE that a system capability represents the potential to perform an action. In contrast, an operational capability may integrate several physical system capabilities to produce a specific outcome to achieve a mission objective. [Wasson2006, SystemAnalysis+Design+Development] 2) System Capabilities, as system assets, characterize the mechanical, electrical, optical, or processing features that enable a system to function, process mission resources, make decisions, and achieve a required level of success based on performance. A system capability is broader in scope than simply a functional element (and performance bounding elements), especially in large, complex ecosystems. It represents a physical potential - strength, ability, endurance - to perform an outcome-based action for a given duration under a specified set of operating environment conditions. [Wasson2006, SystemAnalysis+Design+Development] Aliases: UAF::Capability NAF4::Capability
SPSenablingSCYSpecifies the fact that a System Process contributes to the provision of one or more System Capabilities in the field.
System Function IN System ProcessSpecifies the fact that a System Function is used in a System Process.
Context Function IN System ProcessSpecifies the fact that a Context Function is used in a System Process.
General Function Exchange PointA Exchange Point of a Function Usage
GFNsendingOUTPUTSpecifies the Output of a General Function.
GFNreceivingINPUTSpecifies the Input of a General Function.
GFEPrelatedToGFUEPspecifies that a General Functional Exchange Point is related to a General Function Usage Exchange Point
System Partial Function in System FunctionSpecifies that a System Partial Function is used in a system function