Posted by Mike Rollings
Simply put, TOGAF provides methodology to discover the inputs to an architecture, and methodology to describe an architecture. It does not provide proven architectural approaches that are related to a set of typical client requirements. Client requirements may be localized to a particular technical architecture domain (the classification of technologies imposed by TOGAF methodology) or may cross domains. TOGAF provides an approach to consider the requirements, but non-Burton Group clients are responsible for having the knowledge to thoroughly conduct the analysis, interpret the analysis, identify the implications upon requirement’s, and determine the appropriate architectural solution.
Since requirements must be identified by the client – the obvious questions become:
• How do you know core requirements are complete?
• What architectural approach will satisfy the requirements?
• How can I accelerate this process?
Burton Group’s Reference Architecture (RA) answers these questions and an architecture methodology like TOGAF does not.
Burton Group's RA helps technologists examine technical architecture requirements that are imposed by business strategies upon the technology domains. Our Technical Positions identify the set of typical requirements encountered for an architecture (e.g. Network Intrusion Detection and Response), alternatives, future developments, and evaluation criteria. It then provides decision-making logic used to identify a tuned architectural approach to satisfy the set of requirements.
Therefore, organizations can accelerate their technical architecture creation by starting with the Burton Group RA based on an understanding of their strategy in a given area, identifying pertinent requirements from our collection, and then using our decision logic to create an architectural recommendation. This saves time and money!