8.2.7 SWMM Concept (SWMMC)
The SWMM Concept contains regulations about how the System can be transferred into the state where it can be used, which organizational measures must be taken for the later SWMM, and which resources will be required.
1. General Information
2. Marginal Conditions
2.2. Reference Documents
2.4. Specifications for the SWMM Organization
3. System Description
4. Evaluation with Regard to SWMM
5. SWMM Organization
5.1. Organizational Structure
5.2. Tasks and Responsibilities
6. SWMM Process
7.2. Technical Prerequisites
8. Making SWMM Ready to Work
9. Transition to Utilization
See schema 1. General Information.
This contains a description of the application scope for the SWMM Concept, of the application conditions to be taken into consideration, and how update is to be handled.
This chapter contains a list of the reference documents for the SWMM Concept.
This contains definitions of terms that are newly introduced with the SWMM Concept and that are essential for the understanding of the product.
This contains specifications of marginal conditions with regard to staff, training, organization, infrastructure, logistics and programming languages. It is necessary to refer to existing logistical procedures.
General aspects like place of operation, time/time span and putting into operation have to be described.
Special characteristics with regard to
have to be stated.
It is necessary to state for the individual system parts whether SWMM is to be realized or if it might become required or if no SWMM will be required at all. The responsibility for the SWMM has to be allocated to the corresponding organizations (e. g. authority, industry). Special characteristics of the system parts must be described together with their effects on the SWMM (e. g. SW quality, programming languages, documentation, use of standards).
The SWMM organization is described here. It is described how the SWMM team is set up (which departments, instances), how tasks and responsibilities have to be allocated to this organization, and which interfaces have to be considered.
All departments are listed that carry out activities within the scope of SWMM.
This is where the tasks and responsibilities of the participating departments are established.
Communication interfaces with internal and external parties (customer, subcontractor, partner, bodies and committees, admission boards) are defined here. It is documented who is getting which type and form of information (technical or administrative, in writing or verbally) when (set date, periodically, event-driven) by whom or to whom he is going to pass it on.
The SWMM realization process (e. g. application, analysis and classification of modifications, evaluation of modifications, configuration management, distribution on data media, and installation) has to be described.
- requirements for availability,
- security and reliability criteria,
- interoperability, and
- dependencies on other systems
In particular, the procedure with regard to off-the-shelf-products has to be described.
The required personnel and technical resources are listed.
The personnel requirements for SWMM are determined. It must be stated how far the personnel requirements can be covered by internal staff or if the realization of SWMM measures should be placed with external contractors. The required know-how of the required staff has to be documented.
The prerequisites with regard to the realization of SWMM measures have to be defined. These include
It must be planned how SWMM is made ready to work. This includes
- required development documentation,
- development and assessment environment,
- IT security (e. g. cryptographic equipment, radiance protection), and
It must be documented here, how the System is to be transferred to the SWMM organization. While doing so, the following has to be taken into consideration:
- creating personnel and technical prerequisites,
- training, and
- measures accompanying the development (e. g. in order to obtain the necessary qualification for the realization of SWMM measures during use within the scope of system development).
- time schedule,
- method of transition,
- data stocks.
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster