At the successful completion of system Development the system will be sent for commissioning and implementation. At the implementation stage also, system will pass through the rigorous QA tests.

While implementing the system, the minimum following points will be considered:

1. Installation and configuration audit (adhering to the Installation test as specified)
2. System Installation Results / Reports
3. Real time system test and performance monitoring

The requirements study and System Design shall be completed as explained below.

Analysis of Existing System

This will be an important phase in the life cycle of system, as the new system has to incorporate/built on the required functionalities of the existing system. The study, analysis and design for the existing system would require special attention, as the final understanding of the requirements for new system (vis-à-vis existing system) will determine the approach to be implemented for the new system development and implementation. All the involved functional areas of the existing system will be studied and observed to define the development path for the new system.

The analysis of the existing system will also involve the critical analysis of the existing system so as to determine the approach for enhancements for the components and also the data interfacing required with the external systems.

Based on the information gathered through analysis and Client's visions, Caldiatech consultants will work with client to identify business objectives with respect to the scope of the project. These objectives shall be documented and will be used throughout the life cycle of project.

As the functionality and data of the existing system has to be preserved in the new system also, the first step towards evolving the system will be to study, understand and analyze the existing system. The basic purpose of this whole exercise will be to finally come out with complete understanding of the existing system in view of the different tasks specified for it. The outcome of this study would enable us to design and develop a robust and optimized system. The existing system would require attention and special treatment keeping the following points in perspective:

• Functional aspects of the existing system to be preserved in the new system
• Use of Data of existing systems in the new system (if required)

In order to analyze and understand the existing system, complete information would be required regarding the existing system in the mentioned manner:

• Complete requirement specification of existing system
• Complete functional specifications of the existing system

The new system will be defined with special attention paid to analysis of the existing system and business objectives. The new system will be defined keeping the following points in perspective:

• Immediate as well as the future needs/work load of the system
• Use the existing data of different functional subsystems
• Functional objectives of the new system
• Business objectives of the new system
• Implementation of robust security mechanism for the secure transfer of data flowing between the systems/sub-systems across the components/network.
• Specific needs of the components/subsystems involved in data interfacing with the external systems

The scope of this document is to provide a detailed understanding of the business goals, functional requirement, Understanding of the Existing system and propose new system. The design and development process will start only after the approval of Analysis document by the client. Necessary changes will be implemented as per the feedback from the client.

This is an important aspect in the project lifecycle as this reflects the complete understanding of existing system, system goals of the proposed system. The system design will involve the following steps:

• Defining the system design
• Defining system requirements
• Define processing steps
• Define test requirements

All the areas such as required for the successful implementation of the proposed system will be defined.

Define system requirements

The expected behavior of the system, subsystem and modules shall be defined in this stage of implementation schedule. The main objective of this step is to collect, tighten, refine and document requirements specifications from user. The new system shall be defined in this phase. The following documents shall be drafted during this phase:

• Functional requirements document
• Technical requirements document

The Technical Solution process area relies on the specific practices in the Verification process area to perform design verification and peer reviews during design and prior to final build. The new system needs to ensure that all functionalities of existing systems are preserved.

During this phase all the test requirements and the QA procedures to be followed during the project life cycle shall be defined. The project team shall define the test parameters and the step-by-step procedures of the test. This will take the test, functional, and technical requirements and implement into a coordinated effort to demonstrate each and every task, capability or option. This is to include the expected range of data and failure responses. Document the expected response for each input and include the proper verification steps.

The following documents will be drafted during this phase:

• Test requirements document
• Test plan / Procedure
• Inventory item
• Defect report
• Change request
• Quality Assurance check list and signoff sheet

This will involve the following steps:

• Develop project plan
• Define project team members
• Define tasks and responsibility
• Define System Development Schedule
• Identify functional milestones
• Define target release dates
• Define risks based on assumptions
• Deliver System specifications

This is an important step in project lifecycle of the project where the requirement understanding of the development team and the requirement specification by the client are matched and reviewed. This will be Project Specification approval.

Senior management from the development team and the client will review the requirement specifications defined. The specification review is carried out based on these documents:

• Analysis and design document
• Requirement specification document
• Functional specification document

Any changes suggested during the course of review will be implemented and the changes will be reflected in the above-mentioned documents, test plan, QA plan.

This is an important step, as the requirements will be frozen after Project specification approval from the client. A final copy of approved project specification will be maintained with client and the development team.

After this step the design for system will be frozen.

Changes to Design Specifications

Any changes done for Requirements Specification shall be reflected in the design of the system if needed. Theses changes shall reflect in all the concerned documents.

Design Specifications Review

Senior management and the client will review the Design specifications defined. The specification review is carried out based on these documents:

• Analysis and design document (Updated if required)
• Requirement specification document (Updated if required)
• Functional specification document (Updated if required)

Any changes suggested during the course of review will be implemented and the changes will be reflected in the above-mentioned documents, test plan, QA plan.

This is an important step, as System design will be frozen after Project Design specification approval from the client. A final copy of approved project Design specification will be maintained with client and the development team.

This section describes the methodology to be used for Project Management, Monitoring and Control. This methodology provides a framework for software development and software maintenance teams to develop their project plans.

Periodical reviews are conducted by the Project lead and Senior Management.

The purpose is to track all major project variables - cost, time, scope, and quality of deliverables. The overall objectives of the process are to:

• Track and review actual project accomplishments and results to project plans
• Revise the project plan to reflect accomplishments thus far, and to revise the plan for remaining work, if needed
• Provide visibility into progress as the project proceeds, so that the team and management can take corrective action early when project performance varies significantly from original plans

This role of the project management is multi-faceted:

• Planning tasks and allocating resources
• Risk management
• Issues management
• Time management
• Financial management
• Working in teams
• Quality management
• Monitoring and reporting
• Documentation and record keeping

Mechanisms for progress reporting and inter/intra team communication are identified in this stage. All project communication will be carried out using by any or all of the following means:

• E-mails
• Conference calls
• Chat/Skype

This stage shall be the longest in the entire life cycle of the System development. It shall encompass the development of the system in conformance with the approved Requirement specification and Design specification.

The system to be developed will be as per the set design and standards for the proposed System. Each stage of development will be monitored closely with the set milestones for each sub-system/sub-element/module. Each successful accomplishment will be followed by the required round of testing. The following tasks shall be carried out:

• UI and display logic development
• Business Logic Component development
• Data handling components
• Creation of data/general information validation components

System quality team will consist of a technical team of computer and Information Technology specialists that will perform a variety of activities that support the proposed system development environment. In order to provide a high quality system and services, each support team will adhere to processes, procedures and standards. It involves reviewing and auditing the system and activities to verify that they comply with the applicable procedures and standards, and assuring the appropriate visibility for the results of the reviews and audits.

Develop QA test Plan

This Quality Assurance Plan (QAP) describes the standards, processes and procedures that will be used to support the consistent delivery of a high-quality professional application and services provided in the support of the System.

Before we release our hardware, software, Portal, or internal application, we need to know (and ensure that) it's free from bugs, glitches, and oversights. Our quality assurance (QA) testing involves the painstaking, step-by-step verification that you need to be confident that your users have the experience they are supposed to.

During QA Testing the following shall be evaluated:

• Functionality
• Compatibility
• Interoperability
• Multi-tier Issues

User Acceptance testing shall be carried out at the client's site. The test criteria for UAT shall already be defined when requirement specifications are defined. Any changes or possible defects shall be rectified after verification of the same with the Requirement specification and Design Specification.

UAT Sign Off

After the completion of UAT the client shall send testing and approval of UAT, Signoff for system. A copy of it shall be maintained with the client and the development team.

At the successful completion of QA testing the system will be sent for pre-production commissioning and implementation. At the pre-production stage also, system will pass through the rigorous QA tests.

System Launch

The system shall be launched after UAT approval.

System commissioning at the client shall take place after the Approval of UAT for of the system. This is an important stage after the successful implementation of the system at the client place. It will equip the different user's of the system to use and manage the system successfully. User Training and Administrator training shall be provided for the system.

Everyone involved in interacting with the system shall receive training. The need for training users from different areas of the system shall be catered for.

The outcome of this phase will be:

• Determine training needs, develop plan
• Develop training presentation material

User specific training will be designed for normal end users of System.

Administrator Specific

Administration specific training will be designed for system administrator, network engineer, Database administrator. Accordingly the training slides and documentation will be prepared. The modules under which this training shall be covered are:

• Systems software
• Network Management
• Database Administration
• Security Configuration and Administration

Developer training will be focused for the maintenance staff of the system at the client site. Developer specific training will be covered in following modules:

• System workflow training
• System troubleshooting

Develop training material

Document preparation will be undertaken before, during or after the application development (as applicable, depending on the document required). The list of documents to be provided is as under:

o System Administration documentation
o User/Operator Manual
o Application Software Documentation

Effective training requires coordinating many elements of instruction, engaging each participant in a way that promotes learning, and facilitating sharing of ideas between participants. The training will be conducted at the client site. The training material will consist of slides and /or documentation as required by the training module.

After the system is commissioned it will be ready for the System Acceptance (based on the commissioning results).

As per the requirement and agreement the period for support and system warranty will be for a period of 6 months after the Acceptance Date.

Resolve operational problems

All the postproduction operational problems reported are logged in postproduction defect log. Test plans are prepared for the proposed changes to be done for the code. The impact of changes is carefully studied and then senior management approves the changes after the consent of the client. Required changes in QA and project documentation shall be carried out as required.

Install software upgrades

Versioning system is implemented for System release. All the required documentation will be changed along with the system upgrades.

The System will have adequate and suitable documents for the system to be developed. All the documents prepared will be simple, comprehensive and detailed (wherever possible the target user will be considered as a non-technical person). All required documents for the System would follow appropriate standards concerning content and format. When industry standards are not available, the QA team, along with input from the project team, will develop the standards or adapt documents developed by other groups to use as standards within the project. Standards will be identified and followed for all required project documentation.