The 4x6 Tiered Architecture Method: An Approach to the Design of Enterprise Solutions

  • Ethan Hadar
  • Irit Hadar
  • Gabriel M. Silberman
  • John J. HarrisonJr.
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 112)


Enterprise architecture software design is all about composing applications to assemble value-added solutions rather than standalone products. Yet, each product and technology may have been designed and developed separately because of software engineering practices, management control over the deliverables, or technology acquisitions. To promote efficient assembly, solutions must be architected in a similar style, adhering to fundamental design principles while leveraging capabilities available in modern environments and relevant platforms. Furthermore, business agility and cost requirements dictate the identification of common capabilities and their development as reusable components across products and solutions. The 4x6 Tiered Architecture Method presented in this paper imposes a structured design, in terms of steps to follow, structure and documentation, for the logical view of an enterprise solution. Application of the 4x6 method to the analysis of an enterprise solution yields a six-tiered architecture structure and an abstract architecture specification. This specification expresses the various components, dependencies and design patterns using a graph-based data model (or “architecture catalog”) and blueprint, the latter expressed as both a diagram and XML document. The 4x6 Method has been applied in practice; this experience indicates that this method results in higher quality architecture and requires lower effort for both constructing and reviewing the architecture and its documentation.


Design Tools and Techniques Software Architectures Domainspecific architectures Patterns 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Kruchten, P.: The rational unified process: An introduction, 3rd edn. Addison-Wesley Professional, Boston (2003)Google Scholar
  2. 2.
    Rising, L.: The benefit of patterns. IEEE Software 27(5), 15–17 (2010)CrossRefGoogle Scholar
  3. 3.
    Maiden, N.: Service design: It’s all in the brand. IEEE Software 27(5), 18–19 (2010)CrossRefGoogle Scholar
  4. 4.
    Hadar, E., Silberman, G.M.: Agile architecture methodology: Long term strategy interleaved with short term tactics. In: Companion to the 23rd ACM SIGPLAN Conference on Object-Oriented Programming Systems Languages and Applications, pp. 641–652. ACM, Nashville (2008)CrossRefGoogle Scholar
  5. 5.
    Silverstein, D., Samuel, P., DeCarlo, N.: The innovator’s toolkit: 50+ techniques for predictable and sustainable organic growth. Wiley, Hoboken (2008)CrossRefGoogle Scholar
  6. 6.
    Buschmann, F., Henney, K.: Five considerations for software architecture, Part 1. IEEE Software 27(3), 63–65 (2010a)CrossRefGoogle Scholar
  7. 7.
    Buschmann, F., Henney, K.: Five considerations for software architecture, Part 2. IEEE Software 27(4), 12–14 (2010b)CrossRefGoogle Scholar
  8. 8.
    Burbeck, S.: Application programming in Smalltalk-80: How to use model-view-controller (MVC) (1992), (retrieved)
  9. 9.
    Bosch, J.: Toward compositional software product lines. IEEE Software 27(3), 29–34 (2010)CrossRefGoogle Scholar
  10. 10.
    Ferguson, D.F., Hadar, E.: Constructing and evaluating supply-chain systems in cloud-connected enterprise. In: Moinhos Cordeiro, J., Virvou, M., Shishkov, B. (eds.) Proceedings of the International Conference on Software and Data Technologies, ICSOFT 2010, pp. 69–76. SciTePress, Athens (2010)Google Scholar
  11. 11.
    Sherman, S., Hadar, I., Hadar, E., Harrison, J.: Architecture documentation for agile development. Paper Presented at SATURN 2011, San Francisco, California (May 2011)Google Scholar
  12. 12.
    Booch, G.: An architectural oxymoron. IEEE Software 27(5), 96 (2010)CrossRefGoogle Scholar
  13. 13.
    Buschmann, F.: On architecture styles and paradigms. IEEE Software 27(5), 92–94 (2010)CrossRefGoogle Scholar
  14. 14.
    Hadar, E., Perreira, M.: Web services variation façade – Domain specific reference architecture for increasing integration usability. In: IEEE International Conference on Web Services, pp. 1207–1211. IEEE Computer Society, Salt Lake City (2007)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Ethan Hadar
    • 1
  • Irit Hadar
    • 2
  • Gabriel M. Silberman
    • 1
  • John J. HarrisonJr.
    • 1
  1. 1.CTO Office, CA TechnologiesUSA
  2. 2.Department of Information SystemsUniversity of HaifaIsrael

Personalised recommendations