 |
 |
 |
|
 |
|||
| SSD07 - Supporting Modeling of Information Flows |
LSE07 - Modellierung der Informationsflüsse unterstützen
1 Allocation to V-Model and Methods Allocation
V-Model
SD1.1 - Recording of Actual Status and Analysis
SD1.2 - Description of Application System
SD1.5 - User-Level System Structure
SD2.1 - Technical System Design
SD3.2 - Specification of Requirements for External Interfaces of SW/HW Unit
SD3.3 - Definition of Requirements for the Functionality
Method
DFM - Data Flow Modeling
CFM - Control Flow Modeling
2 Brief Characteristics
This service unit defines the requirements for tools applied
- to model data flows between objects (processes, data stores, terminators) and
- to complete these data flows by control elements in the sense of Control Flow Modeling.
3 Requirements
3.1 Requirements for Interfaces
| SSD07.I.1 | Granularity | The exchange of control parameters with SWFM01 - Workflow Management is possible for individual closed function packages of the tool by means of a disclosed, documented interface. |
| SSD07.I.2 | Input interface to SSD05 - Supporting Function Structure |
Functions from function structures collected with SSD05 are transferred without further transformation from the object management to be automatically integrated into the data flow diagrams. The functions defined in SSD05 correspond to the processes used in the data flow diagrams. |
| SSD07.I.3 | Output interface to SSD09 - Supporting Information Structuring |
It is possible to transmit processes, data flows, and data stores from data flow diagrams via the object management to SSD09 as reference points for the definition of information structures. The functions defined in SSD09 correspond to the processes used in the data flow diagrams. |
| SSD07.I.4 | Output interface to SQA15 - Supporting Dynamic Assessments | It is possible to transmit data flow diagrams and control flow diagrams via the object management without transformation to SQA14 in order to generate test cases. |
3.2 Requirements for the Methods Support
| SSD07.M.1 | DFM - Data Flow Modeling | |
| SSD07.M.1.1 | Symbols | |
| SSD07.M.1.1.1 | Processes | Symbols are available for the representation of processes. |
| SSD07.M.1.1.2 | Terminators | Symbols are available for the representation of terminators. |
| SSD07.M.1.1.3 | Data Flows | Symbols are available for the representation of data flows. |
| SSD07.M.1.1.4 | Data Stores | Symbols are available for the representation of data stores. |
| SSD07.M.1.2 | Data flows | |
| SSD07.M.1.2.1 | Terminators and data stores | It is guaranteed that no data flows are specified between terminators and data stores. |
| SSD07.M.1.2.2 | Data flows between terminators | It is guaranteed that no data flows are specified between terminators. |
| SSD07.M.1.2.3 | Trigger | It is possible to document a trigger at each data flow. |
| SSD07.M.1.2.4 | Splitting up or Combining | It is possible to split up or to combine data flows. |
| SSD07.M.1.2.5 | Redirection | It is possible to turn the direction of a data flow around. |
| SSD07.M.1.2.6 | Rerouting | It is possible to reroute data flows. |
| SSD07.M.1.3 | Hierarchy | |
| SSD07.M.1.3.1 | Hierarchical refinement | It is possible to hierarchically refine the processes utilized in the data flow diagrams. |
| SSD07.M.1.3.2 | Automatic display | In- and outgoing data flows of a process are automatically displayed on the next lower hierarchy level. |
| SSD07.M.1.4 | Opening data flow diagrams | |
| SSD07.M.1.4.1 | Next lower level | It is possible to open from a data flow diagram a data flow diagram on the next lower level in the tree structure. |
| SSD07.M.1.4.2 | Next higher level | It is possible to open from a data flow diagram a data flow diagram on the next higher level in the tree structure. |
| SSD07.M.2 | CFM - Control Flow Modeling | |
| SSD07.M.2.1 | Symbols | |
| SSD07.M.2.1.1 | Control flows | Symbols are available for the representation of the control flows. |
| SSD07.M.2.1.2 | Control stores | Symbols are available for the representation of the control stores. |
| SSD07.M.2.1.3 | CSPEC interface | A symbol for the interface to the control specification (CSPEC interface) is available for each control flow diagram. This way it is possible to illustrate if a process is activated or deactivated depending on CSPEC or if an activated process works as an input value in the CSPEC. |
| SSD07.M.2.1.4 | Processes | Symbols are available for the representation of processes. |
| SSD07.M.2.1.5 | Terminators |
Symbols are available for the representation of terminators. By using the above mentioned symbols it is possible to set up a control flow diagram analogous to a data flow diagram. A control flow diagram merely displays control flows instead of data flows. However, the processes of a control flow diagram do not symbolize the processing of the incoming control flows. They only force the control flow to follow the same refinement structure as the data flow. |
| SSD07.M.2.2 | Hierarchy | |
| SSD07.M.2.2.1 | Hierarchical refinement | It is possible to hierarchically refine the processes used in the control flow diagrams. |
| SSD07.M.2.2.2 | Automatic display | Incoming and outgoing control flows of a process are automatically displayed on the next lower hierarchy level. |
| SSD07.M.2.3 | Opening of control flow diagrams | |
| SSD07.M.2.3.1 | Next lower level | It is possible to open from a control flow diagram a control flow diagram of the next lower level in the tree structure. |
| SSD07.M.2.3.2 | Next higher level | It is possible to open from a control flow diagram a control flow diagram of the next higher level in the tree structure. |
3.3 Requirements for Functions
none
3.4 Other Requirements
| SSD07.O.1 | Upward Compatibility | It must be possible that objects generated with an older release of the tool can also be processed with the new release without suffering a loss of information and functionality. |
| SSD07.O.2 | Procedural command language | The tool has a procedural command language that can be applied by the user to generate and run macros or procedures. |
| SSD07.O.3 | Complexity | There is no limitation of the complexity caused by the tool itself. |
|
|
|
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
|