Success of our process is based on well-defined milestones that signal transition from research to production phases of a project. Earlier phases focus on functionality, while later concentrate on achieving product qualities (robustness, performance, commercial presentation) Inception PhaseInception phase defines product ideas and requirements (Requirement specifications). The goals are: Determine the scope of the software, what is and what is not intended to be in the products. Define primary usage scenarios. Project team composition Design and Elaboration PhaseDesign and elaboration phase produces design, architecture and functional prototype. Design and implementation plans are set down with:
Project team composition Construction and ImplementationThe team rapidly constructs initial version of the system early in the development process. This early integration allows:
Iterative development process. Each design element, and along with its documentation is 'elaborated' through analysis, design, and implementation. It allows more details to be added in successive iterations, along with enhancements, and refinements. Object-Orientation and Component lead to:
Project team composition Beta Testing and Completion PhaseBeta-testing usually includes several iterations of pilot-releases. It provides important feedback from end-users, and assures that acceptance criteria are met. We help supporting users in the initial product use and react to user feedback. We develop or assist in development of user documentation and training materials. Technology transfer is an important part of completion phase, and includes archiving of the project, both for our on-site storage and our offsite, secure storage, as well as for the client. Archiving is done on CD, and includes:
After making the first copy of the archive, we test the code again to make sure the product can actually build on a clean development platform from just the source that is on the CD, based on the instructions provided. Project team composition |