Project Execution Cycle

The standard Project Execution Cycle that we follow and propose for your project is as under and is open to your suggestions:

1. Preliminary Investigation
   Client initiates the inquiry or the requirement and contacts the company. Project manager responds to the inquiry either with the company profile or a proposal. Proposal includes Objective, Overview, Features, Quote, Payment terms, Deliverables and Milestones. In this phase, system and design is studied by Project manager in as an overall system and does not go into the detail of modules. A general view of the system is accomplished.
   Document: Project Proposal
   
   
2. Requirement Analysis
   During this phase of the Project Management Cycle, Project Manager and Software Engineer is in constant contact with the client where they use the fact finding techniques to get the specific details of the Client's Requirements. Understanding the requirements of the client is the key to a successful completion of the project. A document is associated with this phase, which will be provided to the client for approval. This document also develops a trust that there is clear understanding about the requirements of the client.
   Document: System Requirement Specification (SRS)
   
   
3. System Design
   Once the requirement analysis is finished and common ground is developed, Project Manager, Software Engineer and Project Leader gets involved with the designing of the project. Designing includes System Architecture, Database Design and Functional document. System Architecture involves detailed description of the flow of the information in the project and software programming languages that will be used. Database Design includes in depth planning of the tables and its relationships and interaction with the rest of the development of the project. Database is primarily used for storing critical information. A Functional document is provided by which a complete flow of the project will be given to the client. Once the approval is received from the client Detail Design and Coding of the project can begin.
   Document: Functional Document
   
   
4. Detail Design
   This is a complete internal phase of the Project. Client's approved Functional Document is used to develop modules and assign modules for programming. For the easy of programmer's point of view a detail Program Specification Document is created. Also Test Scripts are generated to perform test on modules and the whole product about integration.
   
   
5. Coding
   Programmers use the Program Specification Document for programming the individual modules. Project Manager maintains the schedule of programming and Project Leader handles the technical assistance of the project.
   
   
6. Integration and System Testing
   Integration of the individual modules programmed by different programmers is accomplished and also the Quality Assurance (QA) Team does complete testing of the product. Also Installation Manual Document is given to the user for easy installation procedure and guidance. Preparation for Deployment is done simultaneously. Deployment preparation can include getting some space on the server (in case of Websites) or getting a proper platform set at the client' premises for the product to work.
   
   
7. Deployment
   Project is loaded on the server (in case of Website) or a Computer at the Client's Premises. User Manual is also prepared and provided to the client at the end of this phase, which will help users use the product successfully.
   
   
8. Acceptance Testing
   Client uses the User Manual to test the finished product and gives any positive or negative feedback to the Project Manager.
   
   
9. Support
   A grace period is always given to the Client for requesting minor changes depending on the contractual terms.
   
   
10. Sign Off
    End of the Grace period and the implementation of the suggested minor changes suggest that the project is successfully completed.