![]() |
![]() |
![]() |
![]() |
![]() |
Scope of the SOMT Method
The primary focus of the SOMT method is on system development using object oriented analysis and SDL design, with extra support for interface definitions in other notations like ASN.1 [23]. Nevertheless, an important issue in SOMT is the possibility to use the analysis part of SOMT together with design using other notations. Some examples:
- The system to be built is composed of several different parts, where some parts are not suitable to design using SDL. A simple example might be where the system includes a window based user interface that is easier to design using a special purpose tool.
- Another example is when the system includes a data base component. The analysis of the data is suitable to perform using object oriented analysis, but the data base component is preferably designed and implemented using a commercial data base tool.
- Different parts of the system may be designed in different parts of the world and for some reason there has been a choice to use SDL-based development for some parts and other methods for other parts.
The scope of the support given by SOMT when using a design notation other than SDL is, as can be seen in Figure 614, basically:
- The requirements and system analysis of the system are still valid.
- Parts of the system design activity are still supported by SOMT.
- The SDL-based design of components is of course supported.
How much of the system design part that is supported by SOMT is of course very much depending on the "XYZ" method used (see Figure 614). However, the support given by SOMT when using "external" components is at least the definition of the interface of the "external" components. This includes definitions of both static and dynamic aspects as will be seen in System Design.
http://www.ibm.com/rational |
![]() |
![]() |
![]() |
![]() |