Imagine...unleashing your organization's potential, people knowing what must be done and empowered to do it, executing the right decisions the first time with predictable and desirable outcomes. Imagine...this is you! Opportunities through Discovery. Innovation by Design. What opportunities can you imagine?
The purpose of the Architecture Body of Knowledge™ (ABoK™) is to establish a common understanding of the terminology, principles, and best practices for automation solution design, development and delivery. Key elements to the ABoK™ include Governance, Principles, Technology Catalog, and Solutions. Simply said, ABoK™ is common sense put to words and diagrams, organized in a way that is pragmatic, useful, and intuitive. The most experienced architects appreciate models that crystalize the concepts they must convey, align teams toward achieving mission goals, and engender productive developers of rich solutions to complex business needs. Painful lessons learned in the software development industry are incorporated into our understanding of best practices. The ABoK™ accounts for the influences of individuals, paradigms, and movements important to the evolution of automation while unveiling the concepts and principles that are timeless. This body of knowledge integrates patterns (e.g., GoF), models (e.g., SEI CMMI, FEA, ITIL®), practices (e.g., PMI® PMBoK®, TOGAF™, ITSM), and technologies (e.g., Java, .NET™, EAI, Web Services), along with their applications to solving business and technical issues in automation development. Through broad inclusion of these aspects, ABoK™ puts forth a perspective that wouldn’t otherwise be evident to those practicing the architecture discipline. The scope of the ABoK™ encompasses multiple software development movements and levels of abstraction, including enterprise architectures, model-driven approaches, new developments in user experience design, pattern catalogs, and software frameworks available commercially and as open source. Design dimensions of software, information (motion and rest), interfaces, security, and performance are woven into the content.
