Auriga's intent is to provide a general overview of our Software V & V process as part of the Strategic Plans. Each of the above Sections are composed of several tasks to ensure each activity is implemented correctly, completely, consistently, and with accuracy. While Auriga is confident our process is consistent with those that are implemented according to industry's best practices, we continuously seek feedback from our customers and business partners on how to further improve our current methodology.

INTRODUCTION

This Section provides a brief overview of Auriga's Software Verification and Validation process. Auriga's Software Verification and Validation (V & V) process is accomplished through a series of activities and tasks that are planned and executed at various stages of the software development life cycle. These tasks may be one time occurrences or may be iterated many times, depending on the life cycle model used and the scope of changes made as the software project progresses.

Auriga's software life cycle model covers the software from its inception to its retirement. Verification and Validation activities in the Auriga's software life cycle model include the following:

• Quality Planning
• System Requirements Definition
• Software Design Specification
• Construction or Coding
• Testing
• Installation and Checkout
• Operation and Support
• Maintenance and Retirement

In the remaining sections, we will discuss "typical" tasks that could support activities that are implemented in our software life cycle model. For each of the software life cycle activities, there are certain, typical tasks that support a conclusion that the software is verified and validated. Please note, depending on the complexity and application risks, all tasks outlined below may not be implemented. However, Auriga will consider each task, define, and document which tasks are or are not appropriate for the specific application.

ACTIVITIES AND TASKS

Quality Planning

At the foundation of the Auriga's Verification and Validation process is quality planning. The quality planning process identifies necessary tasks, procedures for anomaly reporting and resolution, necessary resources, and management review requirements, including formal design reviews.

System Requirements Definition

This V&V activity addresses software requirements analysis of the functional and performance requirements, interfaces external to the software, and requirements for qualification, safety and security, human factors engineering, data definitions, user documentation for the software, installation and acceptance, user operation and execution, and user maintenance. In addition, we clearly state the software requirements and it's intended use or application. During this activity, Auriga will develop a Detailed Software Requirements Specification.

Software Design Specification

During this activity, Auriga, translates the Detailed Software Requirements Specification into a logical and physical representation of the software to be implemented. The Software Design Specification is a description of what the software should do and how it should do it.

Construction or Coding

Auriga has very mature Quality Control guidelines that established policies and procedures related to the software coding process. Our procedures dictate that modules ready for integration and test have documentation of compliance with coding guidelines and any other applicable quality policies and procedures.

Testing

Testing includes software unit testing, software integration testing, software qualification testing, system integration testing, and system qualification testing. Auriga's objective of the Test V&V activity is to ensure that the software requirements and system requirements allocated to software are verified and validated by execution of integration, system, and user acceptance tests.

Installation and Checkout

During this activity, Auriga installs the application and performs applicable tests in the target environment. The objective of Installation and Checkout V&V is to verify and validate the correctness of the software installation in the target environment. This activity is the final stage of the user acceptance criteria.

Operation and Support

In this activity, Auriga evaluates the impact of changes in the operating environment; assesses the effect on the system of any proposed changes; evaluates operating procedures for adherence with the intended use; and analyzes risks affecting the user and the system.

Maintenance and Retirement

The scope of this V&V activity is initiated and determined by the customer. In the past, for large mission critical and complex applications, Auriga has addressed and supported activities in the Maintenance and Retirement V & V category. The Auriga's team has a proven track record in the following areas of expertise:

• modifications (i.e., corrective, adaptive, or perfective changes)
• migration (i.e., the movement of software to a new operational environment); and
• retirement (i.e., partial or total replacement by a new application)