IEF-RA 2.0b2 FTF Avatar
  1. OMG Issue

IEFRA2 — 6.3 Weaknesses & Gaps - Sec 1.6

  • Key: IEFRA2-64
  • Status: open  
  • Source: Advanced Systems Management Group Ltd. ( Mr. Michael Abramson)
  • Summary:

    "6.3 Weaknesses & Gaps
    6.3.1 Objectives versus Non-Functional Requirements
    The IEF Objectives outlined in Section 1.6 play a critical role in shaping the non-functional qualities of the Information Exchange Framework Reference Architecture (IEF-RA). However, the current document does not explicitly clarify that these objectives function as non-functional requirements (NFRs)—essential constraints that govern the system’s security, scalability, interoperability, and adaptability.
    While the document correctly refers to them as objectives, some readers—especially those from a software engineering, security, or enterprise architecture background—may assume that the absence of the term ""non-functional requirements"" means they are merely guiding principles rather than mandatory constraints for compliance. This could lead to inconsistent implementation or misinterpretation of IEF-RA’s critical design expectations.
    By adding a brief clarification and linking to the OMG DIDO Reference Architecture’s Non-Functional
    Requirements section, we achieve three key benefits:
    ● Clarifies the Mandatory Nature of These Objectives
    ● Provides an Industry-Recognized Framework for Understanding NFRs
    ● Bridges the Gap Between High-Level Objectives and Technical Requirements

    Suggest: The objectives outlined in this section represent the foundational principles that guide the IEF-RA. While they are not labeled as 'non-functional requirements' in a formal sense, they serve a similar role by defining essential system qualities such as security, scalability, interoperability, and manageability. These objectives are not optional—they are key constraints that must be met for any implementation of IEF-RA to be considered compliant. In later sections, these objectives will be further refined into specific technical and operational requirements.
    For a more detailed discussion of non-functional requirements and their role in a reference architecture, refer to the OMG DIDO Reference Architecture Non-Functional Requirements section: OMG DIDO Wiki - Non-Functional Requirements."""

  • Reported: IEF-RA 2.0a1 — Mon, 4 Aug 2025 12:40 GMT
  • Updated: Mon, 4 Aug 2025 12:40 GMT