Environment Behavior Drives End‐State Architecture Decomposition
Michael Mayerfeld Bell · 2016
An end-state architecture environment behavioral decomposition could divulge imperative details about the architecture's justification to exist. Each segment of the grand architecture can tell a story about the driving business requirements. Each part of the design could shed light on the composition of systems and applications. A collaboration between the architecture segments could divulge the overall enterprise integration scheme. This chapter focuses on three behavioral layers in an overall system environment: system-level crosscutting assets behavior, application-level behavior, and component-level behavior. The work of environment behavior decomposition should start with the lowest one in the hierarchy, the component level, next moving up to the application level, and finally concluding with the system-level crosscutting asset. It is important to note that each layer in the environment structure directly or indirectly depends on each other. The chapter also focuses on building a diagram that exemplifies the concept of end-state architecture environment behavior.