Chapter 6. Realization Phase

By the end of Chapter 5, you should have a quantified scorecard that has been developed in full alignment with the company's investment strategy. Now is the time to drive the technology functionality to the architectural and implementation considerations.

Solution Architecting

Introduction

Some time ago, I read a good article and wrote some thoughts in reaction to it. These thoughts are about the characteristics of a good information (IT) architecture. They are, by the way, the notes I used to follow when architecting a solution:

  • Compatible

  • Migratable

  • Portable

  • Scalable

  • Longevity

  • Delivers good return on investment

  • Intra- and intercompany world wide integration

  • Functional support

  • Intuitive to users

  • Alerts, tracking, reports, workflow

  • Linking business processes to the business bottom line

Serious examination of these notes shows that they are the highlights of good architecture, even today.

Solution Mapping

However, the task on hand is to go from Business Process Re-Engineering/Business Blue Print (BPR/BBP) to solution architecture. From previous chapters, we have the value drivers (key performance indicators [KPIs] that drive the KPI variables measuring value). By mapping them on the solutions provided by prospective vendors, we are able to create a solution map. There will be no problem with higher-level functionality. Any problem will be in the details.

Column 1 of Table 6.1 shows the opportunities identified with the PC client with whom we had an engagement. Column 2 ...

Get Technology Scorecards: Aligning IT Investments with Business Performance now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.