C3_SPWB System Process White Box Viewpoint
| Domain | Aspect | Maturity |
|---|---|---|
| Conceptual | Process & Behavior |  proposed |
Purpose
The C3_SPWB System Process White Box Viewpoint supports the specification of the internal functional realization of the System of Interest (SoI) through the collaboration of its constituent Conceptual Systems.
It provides a white-box perspective on the SoI, complementing the black-box perspective of the C3_SPRO System Process Viewpoint.
The viewpoint refines the internal realization of the SoI while preserving its externally visible functional behaviour.
Applicability
The System Process White Box Viewpoint supports the “Conceptualize the system architecture” activity included in the “System Architecture Definition Process” activities of the INCOSE SYSTEMS ENGINEERING HANDBOOK 2023 [§2.3.5.4] and contributes to the artifacts “System interface definition”, “System architecture description”, “System Viewpoints, views and models”, and “System element description”.
Supported Processes
Supported Information Items
Presentation
An activity diagram featuring the ordered execution of SAF_FunctionActions. The activity diagram swim lanes (partitions) represent the Conceptual Systems constituting the System of Interest (SoI). The activity diagram shows the allocation of SAF_SystemFunctions to the Conceptual Systems and the functional flows between Conceptual Systems and between Conceptual Systems and the system boundary represented by activity parameter nodes. Note: In order to improve the clarity of presentation it may be appropriate to use several activity diagrams for one System Process.
A tabular representation listing the Conceptual Systems contained in the SoI and the SAF_Functions allocated to each Conceptual System.
Stakeholder
- Acquirer
- Customer
- Hardware Developer
- IV&V Engineer
- Operator
- Project Manager
- Safety Expert
- Security Expert
- Software Developer
- Supplier
- System Architect
- User
Concern
- How are the functional responsibilities allocated among the Conceptual Systems?
- How do the Conceptual Systems collaborate to realize the functional behaviour of the System of Interest?
- How is the functional behaviour of the System of Interest realized internally?
- Is the internal functional realization consistent with the externally visible functional behaviour of the System of Interest?
- Which Conceptual Systems are involved in the realization of the functional behaviour?
- Which Conceptual Systems participate in interactions between the System of Interest and the system boundary?
Exposed Concepts
The Diagram shows the concepts exposed by the viewpoint, and related concepts if necessary.
The Table shows the concepts exposed by the viewpoint, and related concepts if necessary.
| Concept | Documentation |
|---|---|
| Conceptual System | Describes a conceptual system as specification for an implementation of a system. It is used in both functional and logical architectures on any hierarchy level. |
| Conceptual Internal Role | Specifies the fact that a Conceptual System may consist of Conceptual Systems (a white box perspective on a conceptual system). |
| General Functional Usage | Specifies a General Usage of a General Function within one or more other General Functions. |
| System Function | Specifies 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. |
| System Function in System Process | Specifies the fact that a System Function is used in a System Process. |
| General Functional Exchange | Specifies the fact that an General Functional Exchange between General Function Usage Exchange Points Parameters is taking place. |
| System Function in System Function | Specifies that a System Function is decomposed into a subordinate system functions |
Realization of exposed Concepts
The Diagram shows the realization of exposed concepts.
The Table shows the realization of exposed concepts.
Related Viewpoints
Required Viewpoints
Recommended Viewpoints
- System Functional Breakdown Structure Viewpoint
- System Internal Exchange Viewpoint
- System Internal Interaction Viewpoint
Example
No examples available.