Developing

3.0 DEVELOPING is divided into 3 phases (DESIGN, IMPLEMENTATION and INTEGRATION)
3.a. DEVELOPING (DESIGN): After project requirements are identified and project requirement document is fixed, there is a necessity to transform business concepts and project requirements to technical vision of the product. At the design phase project team makes project design consisting of: project architecture, division by modules, project behavioral description, deployment schemes, static class and domain model, test cases, database and user interface design. If it is necessary to prove concepts and proposed technologies, some product prototypes can be developed. The result of this stage is a Technical Design Document (TDD) which contains technical project description and representation, Test Cases Document, Database Design document and User Interface Design Document. UML diagrams are used to determine behavioral and static project representation. The design process gives the team a systematic way to work from abstract concepts down to specific technical detail. The Technical design document is a starting point of product development and can be kept internal to the team and changed without burdening the customer with technical issues.
Activity: Provide technical representation of the product, create Technical Documentation, update project plan, create product prototype for proof of concept, risk assessment.
Input: Product Specification document, Project Plan Document, Development Plan, Test Plan, Risks Assessment Document.
Output: Technical Design Documentation, Final version of Project Plan (Project Plan Document, Development Plan, Test Plan, Risks Assessment Document), Product Prototype, Test specifications and test cases.
3.b. DEVELOPING (IMPLEMENTATION): Project development is performed at this phase. Not only source code is developed but also overall project documentation is updated during this phase. It includes: configure development environment, features implementation according to the technical design documentation and project plan, updating project documentation to have it in valid state, updating test cases. Modules integration is also performed here. To increase code quality different techniques and technologies are used. The most significant is Test Driven Development technique which supposes that all features should be tested and as a result unit tests are developed simultaneously with source code. The Integration Server is used to continuously perform project build, run unit tests, count code coverage and so on. This allows project team to eliminate a lot of bugs early at the development stage and really increase code quality. At the end of this stage all project features are completed and solution is ready for testing.
Activity: Implement features according to the plan and technical documentation, updating test cases, project documentation.
Input: Product Specification Document, Technical Design Document, Project Plan.
Output: Source codes and binary executables, list of implemented features. Updated project documentation.
3.c DEVELOPING (INTEGRATION): At this stage team performs overall project integration, making together all project parts and modules; performs development testing of the whole project, final code review and update. When the integration is completed the project is ready to be released for stabilization phase. All supportive documentation is being developed here: user manuals, installation guides, release notes, etc. This phase usually does not take a lot of efforts but is very important for product realization and should be passed to have certainty about the fact that all features are implemented, all project parts and modules are integrated successfully and there are no blocking bugs.
Activity: Integrate implemented features, perform development test, create user guide.
Input: Source codes and binary executables, list of implemented features. Project Specification Document, Technical Design Document, Project Plan.
Output: Confirmed implemented features list, tested software build, updated project documentation and user guides.