|
Software Development methodology
WhiteHedge follows the Rational Unified Process (RUP) and Microsoft Solutions Framework (MSF) as the basis for our software development. A standardized software development methodology helps us to provide very cost-effective and efficient business solutions. If strict time lines are established for the project, WhiteHedge adopts Extreme Programming (XP) methodologies for Rapid Application Development (RAD) to meet the project deadlines.
Our Methodology and Models encompasses multiple processes and methodologies to take the surprises out of project and deliver measurable results for our customers
Common SDLC Model
WhiteHedge follows Spiral Model of Software Development Life Cycle for continual need to refine the requirements and estimates for a project. This model of development combines the features of the Prototyping Model and the Waterfall Model. The spiral model is favored for large, expensive, and complicated projects.
Following are the common phases within our delivery model:
- Envisioning Phase
- Planning phase
- Design Phase
- Development Phase
- Stabilizing Phase
- Deployment Phase
|
Envisioning Phase
Envisioning phase is the period during which the team, the customer, and the sponsors define the high-level business requirements and overall goals of a project.
The main purpose is to ensure a common vision and reach consensus among the team members that the project is both valuable to the organization and likely to succeed. During envisioning, you should focus on creating clear definitions of the problem. The envisioning phase culminates in the vision/scope approved milestone.
Planning Phase
During the planning phase, the team defines the solution: what to build, how to build it, and who will build it. During this phase the team prepares the functional specification, works through the design process, and prepares work plans, cost estimates, and schedules for the various deliverables.
Logical Design
In conceptual design, you describe the solution from the business and user perspectives. The next step is to describe the solution from the project team’s perspective. This is done in the logical design process.
Physical Design
Physical design is the last step in the planning phase. The project team proceeds to physical design after all members agree that they have enough information from the logical design to begin physical design. During physical design, the team applies technology considerations and constraints to the conceptual and logical designs. Because the physical design evolves from the conceptual and logical designs, its success depends on the accuracy of the previous two designs. The reliance of physical design on the conceptual and logical designs ensures that the team will be able to complete a physical design that meets the business and user requirements.
|
Incremental Development
This is the stage where the project is actually off the ground. Our team builds the application in progressive phases or increments. Incremental delivery permits experimentation of complex solutions during the course of development. This approach facilitates modifications through hands-on exposure to the delivered increment.
Stabilizing Phase
During the stabilizing phase, testing is conducted on a solution whose features are complete. Testing starts early in this process with activities such as defining the success criteria and the testing approach during the envisioning phase, and creating a testing plan during the planning phase. However, it is during the stabilizing phase that the Testing team completes the tasks and creates the deliverables that move the feature-complete build to a state in which the defined quality level is reached and the solution is ready for full production deployment.
Deployment Phase
At the end of the stabilizing phase, the release readiness approved milestone indicates the solution’s readiness for deployment into the production environment.
During the deploying phase, the team deploys the solution technology and components, stabilizes the deployment, moves the project to operations and support, and obtains final customer approval of the project. After the deployment, the team conducts a project review and a customer satisfaction survey. Stabilizing activities might continue during this period as the project components are transferred from a test or staging environment to a production environment.