How do we get there?
Implementation takes place once processes have been defined, requirements have been written, technologies and vendors have been selected, and a future architecture has been defined. These are the artifacts that are critical to a successful implementation. In the context of implementation, several core tasks are included. They are:
In the end to-end solution, one or more technologies may be simply procured, deployed, and configured without custom development. Some of these technologies may be deployed on premise, and others may be implemented in the cloud (Software as a Service). Regardless of where it is deployed, these solutions must be configured and tweaked to meet the requirements, processes, and data model associated with the future state. System configuration and customization is generally preferred over custom development because of the lower implementation and operational costs.
Custom development may be required if no suitable solutions could be purchased and configured. In some cases, platforms (such as Salesforce.com) can be purchased and configured, but also provide a platform for custom development. Such a platform can be the best of both worlds, where much of the functionality is available out of the box, and only a small amount of custom development is required to meet all of the business and technical requirements.
Certain solutions may require the integration of multiple systems. Some of these may be newly implemented systems, and others may be legacy systems that must be connected to the new techoligies to meet the business and technical requirements. Such integration may take place on premise or in the cloud, or both. The design of this integration is critical to ensure performance, availability, and security, and should scrutinized carefully for vulnerabilities and limitations. Industry standards for integration should be adopted if at all possible.