Software development process implementation phase

The principal components of this software development process are presented in Fig. 21.25. Together they form the waterfall life cycle model (Royce, 1970,1987). In actual implementations of the waterfall model variations in the number of phases may exist, naming of phases may differ, and who is responsible for what phase may change. 

To better understand the tool features and functionality, a concise introduction to IT security development process is needed. All secured IT hardware or software products and systems are called Target of Evaluation (TOE) which are created on the basis of the security requirements specifications Security Target (ST)—an implementation-dependent and Protection Profile (PP)—an implementation-independent. Development process (Figure 1) consists of 4 (3 for PP) phases and transitions rationales ... 

FIGURE 8.1 The V-Model covers the entire process for software development from the business requirements to the implementation of the software in its intended operational environment. The process starts with a statement of work that defines the effort reqnired for the design, engineering, development, production, and test, and prototyping of a software system. The software documentation process covers user requirements, functional, and technical aspects of the software development. After development, different test phases are performed to verify installation, operation, and performance of the software. A business acceptance from the customer finally leads to implementation of the software. 

In order to develop a software architectural design both software safety requirements as well as all non-safety-related requirements are implemented. Hence in this sub-phase safety-related and non-safety-related requirements are handled within one development process. 

Figure 3 shows the software development life cycle which is divided into the three phases of concept confirmation, implementation and testing. The concept confirmation phase includes the processes of requirements development and software design. The software requirements will be derived from the system requirements and the system design. They include functional, performance and interface requirements. Inputs for the software requirements are ... 

Implement, which is organized across three sub-phases — create, develop, and deploy. From current best practices and applications and knowledge of techniques that work, business processes are established in detail and mapped to software package capabilities. Business scenarios are written for use during development to configure and customize software according to the firm s actual needs, particularly in relation to what key customers have indicated would be the most beneficial CRM features. 

In order to develop the software for the station, the actions of each piece of equipment are defined. The implementation fell into two phases definition of part type and specific assembly sequences. After completion of an assembly, the robot waits for notification of the next part type to be processed by the station. This notification comes from the cell controller. After receiving the next part type the robot controller notifies the microcomputer monitor of the part type requested. The microcomputer compares the requested part type to the current part and downloads the new program to the controller if necessary. A separate program for each part type... 

---