Book Pick: EA Modernization

Open-ended workflow weaving together refactoring, overhauls, and breakthroughs
Excerpt from Enterprise Architecture Fundamentals:

***

Modernization projects could then be organized as workflows that are managed dynamically, depending on the status of model-driven engineering processes, which are themselves built on work units; for example (figure 14-16):

  • Collect and organize legacy code (a)
  • Translate into system cases (SC) (b)
  • Refactor technical (or Platform specific) models according to architecture tech- nical patterns (c)
  • Redesign Use cases (UC) (d)
  • Refactor prescriptive (or Platform independent) models according to changes in Use cases and architecture functional patterns (e)
  • Edit or create descriptive (or Computation independent) models in line with business cases (BC) (f )

Figure 14-16. Modernization Workflow

Augmented backlog mechanisms (as described above) could then be used to control the execution of all work units, whether set with Agile or phased development processes; the former would be focused on Use and system cases, and the latter, backed by descriptive and prescriptive models.

For enterprise architects, the integration of engineering backlogs with ontologies means that profiles and Knowledge graphs could be used to support the whole scope of the decision-making process (cf. chapter 10).

The next chapter will consider the benefits of upgrading MBSE to EA for enterprises’ capacity and maturity.

***

(From Chapter 14)