Integral processes configuration management

Requirements, design/ architecture and coding S/W lifecycle products Translation process -requirements to design to code Verification Integral proeesses (Configuration Management and Quality Assuranee)... 

This section explores two of the integral processes of the SAV Ufecycle configuration management and SAV QA. While neither of these processes directly provide much information about the SAV product, they do contribute substantially to the trustworthiness of all of the other product evidence provided. 

B9.2 S/W Quality Assurance SAV QA is the process for providing adequate assurance that the SAV products and processes in the lifecycle conform to their specified requirements and adhere to their established plans. It establishes that the evidence for demonstrating requirements validity, satisfaction and traceability was derived from processes agreed with the certihcation authority. Like SAV configuration management, SAV QA is an integral process and cannot be performed retrospectively. SAV quality cannot be built in at the end of a program. 

Integral Process Records - describe the results of SAV configuration management and QA process activities. 

For an integration with AHEAD, the communication process during a cooperation is to be seen independent of the process models of the other IMPROVE subprojects in the first step. The communication process extends the C3 model of communication and cooperation possibilities. To do so, detailed information about synchronous communication for certain tasks is provided. This is achieved by using a layered model (see Sect. 3.3) of communication relationships. This model is connected to the model of AHEAD to offer the possibility to model multimedia conferences as separate management tasks, for enabling KomPaKt to get configuration information from AHEAD etc. 

Due to these features, AHEAD is ahead of state of the art systems for project, workflow, or document management. In particular, these systems cover only parts of the managerial configuration and do not integrate the managerial with the technical level. Common workflow management systems lack the support of dynamic changes within the task structure, which occur frequently in development processes. 

---