Architecture domain

<h2 id="overview">Overview</h2>

<p>Since Stephen Spewak's book called <a href="/facts/Enterprise_architecture_planning/JSWwt7bM">enterprise architecture planning</a> (EAP) in 1993,<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> and perhaps before then, it has been normal to recognise four types of architecture domain. The <a href="/facts/British_Computer_Society/2Fy6gNq9">British Computer Society</a>'s "Reference Model for Enterprise and Solution Architecture" also follows this subdivision but additionally mentions the (single) application architecture level just below the application<i>s</i> architecture as well as the domains of information architecture, information systems architecture, or <a href="/facts/Security_architecture/7E5dIy7G">security architecture</a> (a cross-cutting concern):<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a>
</p>
<ul><li><a href="/facts/Business_architecture/j8oFVaaR">Business architecture</a>: The structure and behaviour of a business system (not necessarily related to computers). Covers business goals, business functions or capabilities, business processes and roles etc. Business functions and business processes are often mapped to the applications and data they need.</li>
<li><a href="/facts/Data_architecture/Hj8zHXGX">Data architecture</a>: The data structures used by a business and/or its applications. Descriptions of data in storage and data in motion. Descriptions of data stores, data groups and data items. Mappings of those data artifacts to data qualities, applications, locations etc.</li>
<li><a href="/facts/Applications_architecture/49t5XMlb">Applications architecture</a>: The structure and behaviour of applications used in a business, focused on how they interact with each other and with users. Focused on the data consumed and produced by applications rather than their internal structure. In application portfolio management, the applications are usually mapped to business functions and to application platform technologies.
Application (or Component) architecture: The internal structure, the modularisation of software, within an application. This is <a href="/facts/Software_architecture/1Hokp0Ed">software architecture</a> at the lowest level of granularity. It is usually below the level of modularisation that solution architects define. However, <i>there is no rigid dividing line</i>.</li>
<li><a href="/facts/Information_technology_architecture/A6k3coAm">Technology architecture</a> or infrastructure architecture: The structure and behaviour of the <a href="/facts/IT_infrastructure/U83mT1UW">IT infrastructure</a>. Covers the client and server nodes of the hardware configuration, the infrastructure applications that run on them, the infrastructure services they offer to applications, the protocols and networks that connect applications and nodes.</li></ul>
<p>Note that the applications architecture is about the application portfolio, not the internal architecture of a single application - which is often called the application architecture.
</p><p>Many EA frameworks combine data and application domains into a single layer, sitting below the business (usually a human activity system; that is a notational system expressing a purposeful human activity in a theoretical way using intellectual constructs and not descriptions of actual real-world activity<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a>) and above the technology (the platform IT infrastructure). There are many variations on this theme.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Enterprise_Architecture_framework/kq1FCjjT">Enterprise Architecture framework</a></li>
<li><a href="/facts/Federal_Enterprise_Architecture/tc8880VW">Federal Enterprise Architecture</a></li>
<li><a href="/facts/Solution_architecture/B5l1EzLq">Solution architecture</a></li>
<li><a href="/facts/TOGAF/G8qggAIa">TOGAF</a></li>
<li><a href="/facts/Architectural_pattern_(computer_science)/GnN0z06K">Architecture Patterns (EA Reference Architecture)</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>N. Dedic, "FEAMI: A Methodology to include and to integrate Enterprise Architecture Processes into Existing Organizational Processes," in IEEE Engineering Management Review, doi: 10.1109/EMR.2020.3031968. <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Steven Spewak; S. C. Hill (1992). Enterprise Architecture Planning: Developing a Blueprint for Data, Applications, and Technology. Boston, QED Pub. Group. ISBN 978-0-471-59985-2. <a href="978-0-471-59985-2" target="_blank">978-0-471-59985-2</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>"Reference Model for ISEB Certificates in Enterprise and Solution Architecture Version 3.0" (PDF). bcs. 2010. <a href="http://www.bcs.org/upload/pdf/reference-model-enterprise-solution-architecture.pdf" target="_blank">http://www.bcs.org/upload/pdf/reference-model-enterprise-solution-architecture.pdf</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>Human activity systems - Systems Thinking, Systems Practice, Peter Checkland, 1981, page 115, 314 <a href="http://www.perflensburg.se/Privatsida/cp-web/capchasy.htm" target="_blank">http://www.perflensburg.se/Privatsida/cp-web/capchasy.htm</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
</ol>

Architecture domain open-in-new

Architecture domain