Book Pick: Development Models

Projects Have to Liaise

Excerpt from Enterprise Architecture Fundamentals, available on:


Beyond the perennial nature of change and the need to maintain business efficiency, changes at the enterprise level encompass a whole range of structural, organizational and cultural dimensions, set across different time frames, and involving a plurality of stakeholders. The challenge for EA engineering can only be met through workflows that combine phased and iterative schemes; the former dealing with architecture- based functions, and the latter, with business-specific applications. The refactoring of requirements should thus support clear and easy decision-making guidelines regarding (figure 12-10):

  1. Agile development, for stand-alone developments free of cross dependencies
  2. Model-based developments, possibly in conjunction with Agile ones, for requirements with system-level dependencies
  3. Workflows combining Agile and Model-based developments, for requirements with enterprise-level dependencies

Figure 12-10. How to Pick a Development Model

The choice between Agile and phased development models is often presented as a binary one, overlooking the diversity and specificity of engineering issues in large and complex organizations. The next chapter will focus on the benefits of Use cases for dealing with EA separation of concerns, and chapter 14 will concentrate on Model-based engineering processes.


(From Chapter 12)