Home
About us
News & Events
Awards
Quality
Analytical Instruments
Technology Services
OEM Services
Contact Us

Search
Overview
Focus Areas
Knowledge Domain
Software Services
Engineering Services
Relationship Model
Business Model
Quality
Security
Infrastructure
Process Methodologies
Case Studies
FAQ
  Enquiry



Software Life Cycle Model

A standardized software development methodology enables ELICO to provide low-cost business solutions to meet the exact requirements of the client. This methodology is adapted to suit the specific requirements of each customer.

Project Planning and Requirements Analysis

This stage comprises of project planning and understanding of nature of the system to be built. Requirements for both the system and the software are documented and reviewed with the customer. The outputs of the Project plan and Requirements Analysis Phase is


Project Plan
Software Requirement Specification (SRS)

If it is necessary, qualified technical consultants can be assigned to the client's site to study their business process and requirements.

Design

Based on the SRS, ELICO's analysts draw up a design of the Technical Architecture for the proposed application. A project specific work plan, test plan and configuration management plan are prepared. The outputs of Design Phase are

Design Document
Work Plan
Test Plan
Configuration Management

Application Development

ELICO's project teams generally follow the incremental model of development, wherein the application is built in progressive phases or increments. Incremental delivery permits the Client to monitor and provide an improved focus to the project team, at each stage of the project. This also allows the organization, management and project team to focus on delivering results.

Testing

Testing is carried out in 4 Phases

Unit or Module Level
Integration Testing
System Testing
Acceptance Testing

^

One or all of these methods are used depending on the size and complexity of the project.

"Testing Methodology"

The quality process starts from the project initiation stage. The project plan is prepared by the Project Manager and is reviewed by the Project Deciding Committee.

The test engineer designs a test plan for the project. This contains the testing objectives for the project, the testing approach adopted, success/failure criteria for tests, test deliverables, pre-requisites for testing and the testing schedule, which is dependent on project milestones.

The developers prepare unit test cases before the start of application development. On completion of coding, peer-to-peer code review is done. After correction of faults observed in the peer-to-peer code review, the application is tested against the unit test cases. Subsequent to successful unit testing, the application is submitted to the testing team for Integration and system level testing.

Testing team is responsible for Bug Tracking, Design of test cases and prepares test case documents for module level, integration and acceptance testing. This occurs in parallel with the development team's coding work.

Implementation & Maintenance

Upon successful completion of testing, the application is prepared for deployment and implementation.
Upon successful implementation of the project and receipt of the client's acceptance certificate, the project and related documentation are handed over to the support team/client.


^