|1 Objective and Application of the Functional Tool Requirements|
In other words, while the V-Model specifies the activities and products of the software development and the Methods Standard defines the methods to be applied to realize the activities, the functional tool requirements offer criteria for the evaluation of the functionality of tools that have to be taken into consideration when selecting tools for software projects. The functional tool requirements thus directly support the objectives of the V-Model and the Methods Standard. Apart from that they assist in achieving the following objectives in connection with project realizations in the German Federal Armed Forces:
Increase and guarantee for the software quality:
Minimizing the software costs for the whole lifecycle:
Improvement of the communication between the different parties as well as a reduced dependence of the customer on the contractor:
The Functional Tool Requirements do not contain any technical-organizational requirements (e. g. a regulation of a certain architecture or infrastructure) since these aspects depend very much on the corresponding environment where the assessed tool is to be applied. Technical-organizational requirements must be individually specified-depending on the corresponding operation environment1.
Since both functional and technical-organizational requirements must be taken into consideration when selecting a tool, but the standardized criteria catalogue only contains the functional requirements, it is obvious that the standardized criteria catalogue cannot be the only basis for the selection of a tool environment. In particular it is not possible for the standardized criteria catalogue to specify which tools are actually to be applied in a certain environment.
Apart from the individual functional requirements, the present GD 252 defines the logical structure of an SDE within the scope of an SDE reference model. This structured frame is to guarantee that only equally suitable items are compared with each other, i. e. in each tool assessment it will be exactly specified which functionality is actually meant. With regard to the structure, the SDE reference model generated in the following is therefore predominantly based on the established ECMA reference model as de-facto standard .
One of the most important tasks at the beginning of the activities in an actual operation environment includes the specification of those service units required for the realization of the tasks in this operation environment. For any further steps only those requirements are taken into consideration that are part of the service units identified here.
Figure 1.1: Procedure for the Selection of Tools
|Step 2||The term "application conditions" refers to those influence factors that are the cause that certain functional requirements of the standardized criteria catalogue are considered irrelevant. In the case where an actual project forms the operation environment, these influence factors can be found in the project manual. Otherwise they have to be separately documented in order to justify the selection of a certain tool.
It is essential for the application of the standardized criteria catalog that either
|Step 3||The summary of the functional and technical-organizational requirements into an operational criteria catalogue must be homogeneous and free of inconsistencies.|
|Step 4||Based on a tool profile (see section 1.3.2) or based on a tool description, each individual tool in question will be compared with the operational criteria catalogue. The results of these comparisons are used as a basis for the selection of appropriate tools for the planned application.|
Since the above described tool evaluation might have serious and long-term consequences, all evaluation results must be carefully confirmed.
The listed information about the degree to which the requirements are met is valid for each tool, i.e. provided there are no modifications (e. g. new version/release). The described tool profile is utilized in the tool selection for certain operation environments, according to 1.3.1.
General Directive No. 252 is used as a basis. It contains relevant requirements that are then analyzed with regard to the tool characteristics. Thus it can be ascertained which of the requirements cannot be met. When these analyses are available for several tools it is advisable to compare them with each other. A possible result could be a list of tool requirements that are hardly ever or never met. This list can then be used as a stimulus for the individual manufacturers to improve their tools or to upgrade the functionality of their tools.
|GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster|