 |

Engagement model
The following constitutes the SDLC of a typical enterprise project in Servion. A project manager works with the technical team members who are allotted from various practices to deliver a work product. A member of software quality assurance team performs an umbrella activity of ensuring that proper application of quality metrics is carried out across all phases of the project.
Requirements
A member from the consulting team along with the project manager carries out a detailed analysis of the customer’s business and understands his requirements. It is during this phase that best practices that are followed in the industry are projected to the customer by the analyst. Discussions on how best practices can be applied to a customer’s business requirement happen during this phase and they get documented. Once the customer signs off this phase, the project goes to the next phase.
Design
The analyst presents the requirements to the technical team comprising of architects, integration specialists and other team members in the project. A detailed discussion on design is then carried out between them and documented. Several design alternatives are discussed, debated with pros and cons of each and finally the best design for that solution is arrived at. This design is then reviewed and signed off by the head of the technical group.
Once the design is signed off, unit and integration level test cases are prepared by the developers and reviewed by the technical leads.
Development
The design document forms the base for the development activity. Developers are coached to adhere to the best practices while coding. Test driven development approach is followed in this phase. Once the development is complete, the code is reviewed by the technical leads.
Testing
- Unit testing – where the developers tests individual modules assigned to them and ensure that it yields desired results based on the test cases written
- Integration testing – this is an application level testing wherein the whole solution is tested for meeting desired results in terms of customer requirements and load factors
- System testing – the process of testing end-to-end of a system to verify that it meets specified requirements. It attempts to discover defects that are present in the entire system rather than of its individual components. In a way, this phase impersonates customer testing.
Implementation
Once system testing certifies the solution for implementation, the solution is deployed at the customer’s premise. A round of full-blown test is carried out integrating with the actual hosts/backend systems.
User Acceptance Testing
Once the implementation team completes their onsite testing, the solution is released to the customer for user acceptance testing. The customer performs tests on this system and provides a sign off to move the system to production.
Production support
Once the system is moved to production, the implementation team will monitor the solution for a defined period of time and hand over the same to the regional services team for ongoing maintenance and support
|
|
|