At PunNet, all projects follow a well-defined project life cycle. We follow standard software development methodology, which helps us to provide very cost-effective and efficient solutions. The following are the various phases of software development life cycle followed at PunNet, which commensurate with internationally accepted standards.

This is the first phase for every project when we meet the client to understand the course, design, and platform requirements. These are brainstorming sessions that help determine the overall business objectives and marketing goals. The initial scope of the project is then defined in terms of cost, effort, schedule, and deliverables and functional specifications are generated. Extensive feasibility study is done and after that, a proposal agreement is signed with client.

The Project Manager and the Software Engineering Team analyzes the client’s requirements and their implications on product development. Based on the analysis, a Software Requirements Specification (SRS) document is prepared. This document is the Engineering’s response to the Product Requirements Document. Along with this the System Test Cases are developed to address each requirement.

This phase involves design activities that progress from architecture to high-level design to low design. The Software Engineering Team works thru these different phases of design to create a Software Design Document (SDD), Unit Test Plan (UTP) and Integration Test Plan (ITP).

This is the stage where the project is actually off the ground. PunNet builds the application in progressive phases. First the prototype is created, which is functionally complete and runs on the actual platform envisaged or different prototyping techniques are used. Once the client approves the design and the prototype, the team starts the development process. Testing begins right at the prototype phase and continues through various project milestones.

Once the system goes into production mode, comprehensive training is extended to the end-users; not only to administer and maintain it, but also to make them understand the underlying technology and development tools. The end-users are trained to use the application effectively. Follow-up action in terms of close monitoring of the system and applications ensures immediate response to issues.