Miracle adopts a two part strategy when it comes to defining a technology roadmap for customers.
Part One : is the identification of a technology stack that addresses the current and future needs of a customer's business. This is essentially a top-down exercise, the starting point being the enterprise-wide architecture that is assumed to be mainly invariant as far as there is no fundamental change in business processes. Currently we support three tier, multi-tier, client-server, SOA, grid and SEDA style architectural flavors and combinations.
For an identified combination of architectural styles, the next level of details includes identification of technology domains and enablers within each domain. Technology domains usually align along the lines of logical layers and tiers while enablers include adopted technical standards, protocols, technologies and tools.
Enablers are revised periodically to address the lifecycle of a given technology within the stack. As part of the roadmap definition we classify these enablers into the following six categories:
- Baseline - Includes standards, protocols, technologies and tools in use today by the customer.
- Tactical - Recommended for use in near or tactical time frames (6 months - 1 year).
- Strategic - Enablers that are expected to provide strategic advantage and might be of use in the future. (1 - 3 years)
- Retirement - Enablers targeted for dis-investment during the planned horizon (3 years)
- Containment - Enablers targeted for limited investment mainly because of maturity and standardization of the corresponding business processes.
- Emerging technologies - Enablers that should be evaluated for the future based on technology availability and business need. These solutions may be available today, but the customer is not aware of the same.
The timelines mentioned above are indicative and may vary depending on the volume and complexity of the customer's business processes.
Part Two : is the usage of these enablers and identification of patterns in combining these enablers to meet current and future business needs. This is driven by the following:
- Definition of the context and evaluation criteria to choose the 'right' enabler for a specific requirement - critical for enablers that are identified as strategic and are also extremely relevant for enablers that are marked as emergent.
- Guidelines for migration across enablers as well as upgrades to the same enabler - critical for enablers that are earmarked as baseline or tactical.
- Analysis of business services, processes, rules, events
- Architecture review and evaluation
- Strategy and roadmap definition, architectural project planning
- Evaluation of implementation technologies and platforms.
- Enterprise architecture
- Conceptualization and design architecture that aligns with client's business goals
- Design the process, applications, data and technology architecture
- Products and solution architecture
- Architecture for modernization.
Prototype Development, Implementation and Testing
- Develop prototypes for early architecture validation
- Service oriented implementation
- Testing of services.