Difference between revisions of "Application-Capability Reference Model (ARM)"

Revision as of 10:58, 17 January 2023

The Application-Capability Reference Model or Application Reference Model (ARM) is a business-driven, functional framework that supports Federal agencies. It classifies application capabilities with respect to how they support business and/or performance objectives. The ARM is envisioned being structured across horizontal service areas that, independent of the business functions, can provide a leveragable foundation for reuse of applications, application capabilities, components, and business service. The model aids in recommending applications to support the reuse of business components and services across the Federal Government. ^[1]

The Application Reference Model (ARM) supports architectural analysis and reporting in the applications sub-architecture view of the overall EA. The ARM is a component-driven taxonomy that categorizes the system and application related standards and technologies that support and enable the delivery of service components and capabilities. It also unifies existing agency application portfolios and guidance on standard desktop configurations by providing a foundation to advance the reuse and standardization of technology and service components from a Federal Government perspective. Aligning agency capital investments to the ARM leverages a common, standardized vocabulary, allowing inter-agency discovery, collaboration, and interoperability. Agencies and the Federal Government will benefit from economies of scale by identifying and reusing the best solutions and technologies for applications that are developed/provided or subscribed to support their business functions, mission, and target architecture.^[2]

source: The EA Pad

References

↑ Definition of Application-Capability Reference Model (ARM)FEAPMO
↑ What is Application-Capability Reference Model (ARM)? EA Pad

@@ Line 1: / Line 1: @@
-The [[Application]]-Capability Reference [[Model]] or Application Reference Model (ARM) is a [[business]]-driven, functional [[framework]]  that supports Federal agencies. It classifies application capabilities with respect to how they support business and/or performance objectives. The ARM is envisioned being structured across horizontal [[service]] areas that, independent of the business functions, can provide a leveragable foundation for reuse of applications, application capabilities, components, and business service. The model aids in recommending applications to support the reuse of business components and services across the Federal Government. <ref>Definition of Application-Capability Reference Model (ARM)[http://xml.coverpages.org/FEA-BusinessModelv10.pdf FEAPMO]</ref>
+The Application-Capability Reference Model or Application Reference Model (ARM) is a business-driven, functional framework  that supports Federal agencies. It classifies application capabilities with respect to how they support business and/or performance objectives. The ARM is envisioned being structured across horizontal service areas that, independent of the business functions, can provide a leveragable foundation for reuse of applications, application capabilities, components, and business service. The model aids in recommending applications to support the reuse of business components and services across the Federal Government. <ref>Definition of Application-Capability Reference Model (ARM)[http://xml.coverpages.org/FEA-BusinessModelv10.pdf FEAPMO]</ref>
-The Application Reference Model (ARM) supports architectural analysis and reporting in the applications sub-[[architecture]] view of the overall EA. The ARM is a component-driven [[taxonomy]] that categorizes the [[system]] and application related standards and technologies that support and enable the delivery of service components and capabilities. It also unifies existing agency application portfolios and guidance on [[standard]] [[desktop]] configurations by providing a foundation to advance the reuse and standardization of technology and service components from a Federal Government perspective. Aligning agency [[capital]] investments to the ARM leverages a common, standardized vocabulary, allowing inter-agency discovery, [[collaboration]], and [[interoperability]]. Agencies and the Federal Government will benefit from economies of scale by identifying and reusing the best solutions and technologies for applications that are developed/provided or subscribed to support their business functions, [[mission]], and [[target]] architecture.<ref>What is Application-Capability Reference Model (ARM)? [https://eapad.dk/gov/us/common-approach/reference-models/ EA Pad]</ref>
+The Application Reference Model (ARM) supports architectural analysis and reporting in the applications sub-architecture view of the overall EA. The ARM is a component-driven taxonomy that categorizes the system and application related standards and technologies that support and enable the delivery of service components and capabilities. It also unifies existing agency application portfolios and guidance on standard desktop configurations by providing a foundation to advance the reuse and standardization of technology and service components from a Federal Government perspective. Aligning agency capital investments to the ARM leverages a common, standardized vocabulary, allowing inter-agency discovery, collaboration, and interoperability. Agencies and the Federal Government will benefit from economies of scale by identifying and reusing the best solutions and technologies for applications that are developed/provided or subscribed to support their business functions, mission, and target architecture.<ref>What is Application-Capability Reference Model (ARM)? [https://eapad.dk/gov/us/common-approach/reference-models/ EA Pad]</ref>
@@ Line 9: / Line 9: @@
 ===See Also===
-[[Reference Model]]<br />
-[[Agent Systems Reference Model (ASRM)]]<br />
-[[Application-Capability Reference Model (ARM)]]<br />
-[[Technical Reference Model (TRM)]]<br />
-[[Performance Reference Model (PRM)]]<br />
-[[Data Reference Model (DRM)]]<br />
-[[Infrastructure Reference Model (IRM)]]<br />
-[[Security Reference Model (SRM)]]<br />
-[[Consolidated Reference Model (CRM)]]<br />
-[[Data and Information Reference Model (DRM)]]<br />
-[[SCOR (Supply Chain Operations Reference Model)]]<br />
-[[The HP IT Service Management Reference Model]]<br />
-[[Information Governance Reference Model (IGRM)]]<br />
-[[OASIS SOA Reference Model]]<br />
-[[Open-System Environment Reference Model (OSERM)]]<br />
-[[Reference Semantic Model (RSM)]]<br />
-[[Navy Process Reference Model]]<br />
-[[Enterprise Architecture]]<br />
-[[Enterprise Architecture Framework]]<br />
-[[Federal Enterprise Architecture Framework (FEA)]]<br />
-[[Enterprise Architecture Life Cycle (EALC)]]<br />
-[[Enterprise Architecture Management (EAM)]]<br />
-[[Enterprise Architecture Value Framework (EAVF)]]<br />
-[[Enterprise Architecture Governance]]<br />
-[[Business Strategy]]<br />
-[[IT Strategy (Information Technology Strategy)]]<br />
-[[IT Governance]]<br />
-[[IT Operations (Information Technology Operations)]]<br />
-[[IT Sourcing (Information Technology Sourcing)]]< br />
-[[Chief Information Officer (CIO)]]
@@ Line 46: / Line 17: @@
 ===Further Reading===
-*Introduction to the Architectural Reference Model for the [[Internet]] of Things [http://iotforum.org/wp-content/uploads/2014/09/120613-IoT-A-ARM-Book-Introduction-v7.pdf iotforum.org]
+*Introduction to the Architectural Reference Model for the Internet of Things [http://iotforum.org/wp-content/uploads/2014/09/120613-IoT-A-ARM-Book-Introduction-v7.pdf iotforum.org]
 *Application Reference Model - UK Government [[Reference Architecture]] [https://lenand.files.wordpress.com/2012/01/ukra1-0-lpa.doc Steve Walters, Paul Turton]
 *Australian Government Architecture Reference Models [https://ofti.org/wp-content/uploads/2012/07/aga_rm_v3_0.pdf ofti.org]