Fuzone e-system follows a unique engagement model that ensures the success of each client project. At the core of the model is our proven
Quality Management Process
At FUZONE, project management is our expertise. For efficient and cost effective project management and project execution, we have put a quality process in place
A complete process driven software development life cycle is followed to execute a project. Currently, two models are followed in the majority of the software industry
1. The V model of SDLC
2. The waterfall model of SDLC.
We at FUZONE have chosen the waterfall model. The entry criteria for each phase is planned and decided. The exit criteria for each phase are decided in terms of deliverables. The most important feature of each phase of project execution at FUZONE is phase end review that is conducted after each phase. The phase end review is done with the team members and in some cases with the customer to iron out the differences and problem experienced in the past phase so that they are not repeated in the next phase. This is the way we keep improving our process cycle.
The following section describes the key phases of the SDLC at FUZONE
Request for proposal from the customer
The project generally starts with the request for proposal from the customer. This is taken as an input for the proposal from FUZONE.
Development of Proposal
For starting the project, FUZONE provides detail of the understanding of the project and cost in terms of a document that is reviewed and accepted by the customer. This is an input to the contract. This marks the beginning of the next phase.
The project planning is done to provide the detail of planning of the project in terms of resources, schedules and milestones. This is the document that is studied and followed by all team members.
Study and Requirement Specification
The requirement phase is started after completion of proposal phase. The requirements elicitation phase consists of requirement identification based on the inputs of the customer in the statement of work or the contract. The requirement document is reviewed by the FUZONE team as well as the customer. Once the requirements are freezed in a document format, the same is taken as an input to the design phase.
High-level design followed
The high level design involves brain-storming, discussions and documentation of the design in high level of the solution proposed to the customer. The documentation is reviewed internally and is put as an input to the low-level design phase.
Low-level design followed by review
The low-level design involves designing of the low level details of the modules. The documentation includes the design till the level of coding. The same goes through the review process.
Coding followed by review
The coding is done using the tools identified during the project-planning phase. Version management tools like CVS are used during this phase to maintain multiple versions of the code.
A 3-tier strategy is developed for the testing phase. The following sub-phases are planned and executed.
Unit testing: Unit Test Plan Execution
Unit Test Plans are made to validate the code written against the requirements and design. "Units" are identified, which may be at the function / sub-routine level. Unit Testing stubs are made to test the functionality of each unit. This test plan is executed over the "Units" to be tested to form the Unit Test reports containing the results of this phase.
SSI Testing: SSI Test plan Execution
The SSI test plan is developed to test the integration of various sub-modules. At FUZONE, we endeavor to follow the incremental SSI method in which the modules developed are integrated incrementally. However, in larger systems, the SSI is done simultaneously on various modules and the resulting modules of SSI are integrated incrementally. The SSI Test plan is developed to cover all functional requirements of the software modules under SSI. The SSI Test reports are the output of this module.
SI Testing: SI Test Plan Execution
The System Integration Test Plan is executed on a target system or a prototype. The System Integration results in the final software system that can go for factory testing.
At the end of each phase a deliverable is identified and produced. For e.g., at the end of high-level design phase a high-level document will be generated. The team reviews this internally and formal defect logs are generated over that HLD document. The comments from these defect logs are discussed with the inspector or the producer of the defect log and then they are incorporated in the document before it is finally released to the customer. The source code is also reviewed in the same manner.
The defect density for each project deliverable is maintained and these are used to decide the company wide defect density targets.
At FUZONE, we follow Quantitative Project Management.