Development Methodology |
| Pranava is strictly adhering to Software Development Live Cycle (SDLC) using Structured Systems Analysis and Design Methods. Effective project Reviews, Code walk through, complying to pre-set standards makes the projects and products of Pranava very quality rich and adhere to international quality standards. |
Domain Expertise in Pranava |
| Pranava has rich exposure to various domains such as Manufacturing, Logistics, Transportation sectors including Aviation related domains like Crew Scheduling, Crew pairing, Flight Scheduling, Flight Dispatch, Trading etc and also has expertise in SIEBEL-CRM. |
Project Execution Methodology at Pranava |
Software process automation will be used to restructure the organization on a continuous basis. Formal techniques will be increasingly applied to all stages of life cycle. During the execution of the project, the project development team will follow the best current practices, which will ensure the quality of the product and its timely delivery of the client.
Pranava will identify a project leader with relevant skills for the project. The project leader will be responsible for the delivery of the project. The following are the different stages in the project. |
Requirement Analysis |
| Pranava develops the functional requirements of the application system after understanding the same from the end users during the system study. A final sign off
Will be taken from the client for the development process to continue. |
Designing |
| The project leader along with the team which did the system study will prepare the design documents for the complete requirement analysis. The design documents are further approved by the client for proceeding further with coding. |
Construction |
In this stage, the project leader will verify the detailed ‘program specification’ for its completeness, before handing over this to the team members for coding. Incase, if there are any clarifications required on these specifications, the project leader will interact with the client and hand over the ‘program specifications document ’ to the member developers for the coding purposes.
The team members will do the following
- Code the program based on the specifications document
- Prepare unit test cases and test plans
- Perform unit testing
Before starting the unit testing of the source code, the project leader will review the source code for its functionality and give the comments to the team members. The team will then incorporate these comments and proceed with unit testing of the source code. |
Source Code Review |
| The unit-tested code is then handed over to the review team for code review. The review team will review the code in terms of coding standards, understandability, documentation of the code etc., and handover its comments to the respective team members and project leader. Then the team members will incorporate the review team’s comments on the source code and the related unit test cases will be performed to ensure that the modifications are tested thoroughly. |
Integration Testing |
| When all the programs pertaining to a sub-system are passed through the above two stages, then the sub-system is considered to be ready for integration testing. The project leader and the corresponding team will perform the integration tests on the source code of the module. Then the team will fix the bugs, which are identified in this stage. |
Version Control of the Software |
The development team will use the necessary version control tools like the Visual Source Safe for proper version control of the source code, during all the stages of project development. The development team will be assisted by a ‘source librarian’ who will be responsible for
Maintaining the list of all the source programs in the project
Maintaining the status of the source programs on weekly basis
Assisting the development team for maintaining the source programs |
Change Control Procedure |
| While the project is underway or under maintenance any changes to the agreed functionality or any request for addition of new functionality is handled by change control procedures. The change control Request Form, which is used in this procedure, can be the Pranava’s standard form or a mutually agreed form. |
Evaluating changes |
| The changes requested by the Client/ Project Leader are assessed and evaluated by the project leader in terms of the effort, time, cost and impact on the current project schedule, if it has to be incorporated along with the on-going project schedules. This information is provided to the client for approval. The client has the option for rejecting, deferring or approving this change. If approved, the Change Request is moved to the next step. Otherwise the change request is closed. |
Implementing Changes |
| After the client approves the estimate, time and cost implications, the change is implemented after retrieving the proper version of the software and is implemented by the project Leader. |
| |
