.: Implementation
Although implementation strategy can vary considerably depending on whether the project is large or small, is an in-house system or a commercial product, and so on, here are a few key points that apply to all projects.
- Plan implementation strategy. There’s no formula for the “best” implementation strategy, but here are some factors to consider. It’s usually a good idea to attack difficult tasks and risks first so any impact on cost, duration or architecture can be known as soon as possible. The approach of creating a small, operational version of the application and then building on that will affect the order in which components are implemented. Other obvious factors are the need to assign tasks based on the skills of team members and the need to level resources in order to minimize elapsed implementation time.
- Create small core application; build on it. Whenever possible, we create a small, operational “core” version of the application, to which additional components can be added as they are completed. By choosing the components for the core application appropriately, we can insure that underlying technologies, architecture, third-party components, development platform and frameworks, middleware, hardware infrastructure, and so on, operate correctly and with expected performance and reliability—and if problems are encountered, we can address them early, minimizing the amount of implemented code that might have to be changed.
- Unit testing. Each developer is responsible for effective unit-testing of his/her components and for initial integrated testing of the component when it is added to the running core application.
Discovery / Requirements
Problem Domain
Risks
Architecture
External Design
Functional Design
Implementation
Quality Assurance
|
