![]() |
![]() |
![]() |
|
| Annex 2 | |||
| 2.5 The complex Methods SA and SA/RT |
SA/RT - Structured Analysis with Real-time-Extensions
Contents
|
|
|---|
1 Brief Description
Both SA and SA/RT have several versions that are also found in the tools. For SA, the versions according to /DeMarco, 1978/ and /Gane, 1979/are relevant, the relevant versions for SA/RT are the descriptions in /Ward, 1985/ and /Hatley, 1987/. The following brief description refers to the works of DeMarco and Hatley/Pirbhai the way they are described in /Hatley, 1987/; the differences to the other authors are small and will be explained in chapter 5.
SA or SA/RT support the main activities SD1 - System Requirements Analysis to SD3 - SW/HW Requirements Analysis, i. e. all three levels of the requirements analysis. While SA is not restricted to a special scope of application, SA/RT is predominantly applied in technical, real-time-oriented applications. The components of the complex method SA are:
In addition, the complex method SA/RT contains the following components:
2 Tabular Comparison
Note:
The right column of the table contains the names of several authors. This has to be interpreted in such a way that an application of SA or respectively SA/RT is possible according to any one of these authors.
3 Specification of the Allocation
| Method | Corresponding Component in SA | Explanation |
|---|---|---|
|
FCTD Functional Decomposition |
Process Hierarchy /Hatley, 1987/ chap. 12.1, /Gane, 1979/ chap. 4 /Ward, 1985/ volume 2, chap. 5 and 6 | If the data flow model with its hierarchical process structure is generated prior to a function tree (according to FCTD), a function tree can still be generated by extracting the processes from the data flow model and recording to them as separate tree. This tree can then be used as the basis for a function tree. This function tree is frequently upgraded by additional functions (e. g. organizational functions or manual activities) that are essential for the corresponding project. |
4 Information about individual Components
SA and SA/RT cooperate with a central data-dictionary for all items identified in connection with modeling processes. However, in connection with the data only data flows and stores are decomposed into individual parts, the interrelation of the data is not taken into consideration. Today, this disadvantage can be compensated with the application of the E/R modeling-in particular in connection with the development of information systems. Even though E/R is not a component of the complex method SA or respectively SA/RT it makes sense to model the SA or SA/RT data with the E/R data model. The data structures are then a result of the E/R modeling process (compare basic method ER).
The data management itself is predominantly the task for a tool. The specification of certain notation forms for the data definition must also be considered as beyond the regulation by the Methods Standard.
Control flow diagrams merely illustrate which processes are interacting via control flows and if a control flow has the character of an input or output value. The control specification is generally a finite automaton with output. Control flows are thus the input and output information controlling the participating processes, depending on the system states.
A number of representations are possible for finite automata with output, the description of the basic method STM contains a corresponding list. In case the number of states degenerates to 1, it is a combinatorial automaton. The common way to represent combinatorial automata is the decision table (see basic method DTAB). The automata themselves can be linked with each other, with regard to a control specification of a higher complexity (e. g. the process activation table according to /Hatley, 1987/.) This way, however, the representation of the RT model can be simplified.
The time efficiency requirements are part of the control specification. The RT model knows two types of external time requirements:
5 Further Information
The definition of SA in Gane/Sarson /Gane, 1979/ differentiates mainly with regard to the notation of the one in DeMarco. The meaning of the representation elements process, store, data flow, external item is identical in both approaches.
Differences:
The method description for SA/RT listed in this annex is based on the works of /Hatley, 1987/. An alternative approach for an RT upgrade can be found in /Ward, 1985/.
While in /Hatley, 1987/, CFM and the process specification are representing the RT upgrade, /Ward, 1985/ introduces
The event flows are similar to the data flows of the DFM. They are different from the control flows of the CFM because an event flow can only transport a constant value, i. e. an event flow rather corresponds to a switch than to a control channel with possibly variable information.
5.2 Further Development of SA and SA/RT
Today, the terms "Modern Structured Analysis" /Yourdon, 1989/, "Advanced Structured Analysis" /Peters, 1988/ etc. refer to a number of publications about the further development of SA and SA/RT.
/Yourdon, 1989/, e. g. summarizes the know-how and experience with regard to the structured analysis since the publication of /DeMarco, 1978/. Though a new method is not really propagated, SA and SA/RT are seen in the entire SW engineering environment. In this connection, the interrelation of individual methodical components as well as the transition to the SW design play an important role. Furthermore, it is considered as state of the art to apply method E/R together with SA or respectively SA/RT within the scope of information modeling.
6 Literature
![]() |
![]() |
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
![]() |