Our Software Development Process
Phase 1: Investigation
At the onset of a project, we work with you to establish a common understanding of the problem as well as the scope and requirements of the solution. This phase provides an opportunity and a mechanism with which to discuss and document stakeholder expectations.
Deliverables
• Vision and scope document - describes the overall scope and goals for the project
• Requirements specification - describes use cases as well as functional and non-functional requirements
• Project time and cost estimates - initial estimates for the entire project
Phase 2: Design
Development team leads and architects begin to translate project requirements into abstract representations that will be used as the basis for implementation of the application. At the same time, user interface designers create the initial design for the layout and controls through which users will interact with the application.
Deliverables
• Architectural design specification - describes abstract representations of the underlying architecture of the application
• User interface design specification - describes the layout and interactive components of the application
• Wireframes, mockups, and/or prototypes - visual representations of the user interface
• Architecture design artifacts - UML diagrams, stubbed code or interface specifications, etc.
Phase 3: Planning
Team leads and managers work with you to produce a strategic plan for the development, testing, documentation and release of the application. In addition, application components are evaluated and organized such that priority is given to those areas which pose the highest risk or represent fundamental application functionality.
Deliverables
• Strategic development plan - describes the schedule and the structure of development activities
• Strategic QA plan - describes black and white box testing strategies
• Initial estimates for application components
Phase 4: Development
Application development proceeds through a series of iterations as outlined in the strategic plan. Prior to each iteration, team members identify and evaluate tasks. Based upon your input, a set of tasks is selected for implementation within the iteration, and the resulting functionality is documented and tested. At the end of each iteration, a functioning release of the software is deployed for your evaluation.
Deliverables
• A functioning release at the end of each iteration - stakeholders are asked to evaluate and provide feedback
• Status reports - describe status of current tasks, issues discovered, testing results, etc.
Phase 5: Delivery
When you determine that a release satisfies project requirements, that version of the software is delivered in its entirety. Delivery may involve deployment as well as training in the use and administration of the application.
Deliverables
• Completed solution
• Documentation
• Deployment
