Highly interconnected, rapidly changing people, process, information, technology and needs requires a totally holistic and integrated view of an enterprise, well beyond the span and depth of traditional EA practices.
Next generation practices include systems engineering and technology-based program management practices to understand, produce, communicate and apply this view productively and in an efficient and effective manner.
Through the lens of a systems perspective of an enterprise in a start-up environment, the basic and fundamental needs, capabilities and elements of an enterprise are differentiated and defined, including the roles and responsibilities for architecting and managing each capability.
''Defining Enterprise' is not the typical enterprise architecture book helping a programmer find their way up the management ladder. Rather, 'Defining Enterprise' lays out practical strategies and tactics for architecting for management purposes -- that is, designing -- the business from the perspective of capabilities and intended outcomes. This book should be on the shelf of every executive, manager and architect.'- Richard Soley, Ph.D., Chairman & CEO Object Management Group (OMG)
'Marc has chosen a different approach to describing EA, describing management mechanisms and roles as a means to understand how the actions described in an architecture work to create success. Marc also provides a rationale for team contributions to this same overall success. Using his approach, it is much easier to see the various roles and how they contribute in an integrated, holistic way to creating and maintaining capabilities.' - John Tieso, CIO, CTO, Author, Lecturer
'A foundational piece of work that allows any organization to be described in a coherent and consistent manner. What's more, the relationships between these 'building blocks' of the enterprise are clearly defined, allowing these interactions and dependencies to be easily seen and understood. This is fundamentally important for architects and executives, to allow them to navigate this normally hidden complexity.' - Darryl Carr, Editor of the Enterprise Architecture Professional Journal
Highly interconnected, rapidly changing people, process, information, technology and needs requires a totally holistic and integrated view of an enterprise, well beyond the span and depth of traditional EA practices.
Next generation practices include systems engineering and technology-based program management practices to understand, produce, communicate and apply this view productively and in an efficient and effective manner.
Through the lens of a systems perspective of an enterprise in a start-up environment, the basic and fundamental needs, capabilities and elements of an enterprise are differentiated and defined, including the roles and responsibilities for architecting and managing each capability.
''Defining Enterprise' is not the typical enterprise architecture book helping a programmer find their way up the management ladder. Rather, 'Defining Enterprise' lays out practical strategies and tactics for architecting for management purposes -- that is, designing -- the business from the perspective of capabilities and intended outcomes. This book should be on the shelf of every executive, manager and architect.'- Richard Soley, Ph.D., Chairman & CEO Object Management Group (OMG)
'Marc has chosen a different approach to describing EA, describing management mechanisms and roles as a means to understand how the actions described in an architecture work to create success. Marc also provides a rationale for team contributions to this same overall success. Using his approach, it is much easier to see the various roles and how they contribute in an integrated, holistic way to creating and maintaining capabilities.' - John Tieso, CIO, CTO, Author, Lecturer
'A foundational piece of work that allows any organization to be described in a coherent and consistent manner. What's more, the relationships between these 'building blocks' of the enterprise are clearly defined, allowing these interactions and dependencies to be easily seen and understood. This is fundamentally important for architects and executives, to allow them to navigate this normally hidden complexity.' - Darryl Carr, Editor of the Enterprise Architecture Professional Journal