Community of Interest [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Community of Interest ======

[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

A Community of Interest is a group of participants that share an interest, purpose, mission, problem, or information need within a defined subject area.

Participants can include:

  * [[public:99_annexes:annex-b-terms-and-definitions:o:organization|Organizations]]
  * Organizational units
  * [[public:99_annexes:annex-b-terms-and-definitions:u:user|Users]]
  * Subject-matter experts
  * System owners
  * System operators
  * Developers
  * Test authorities
  * Evaluators
  * Regulators
  * Standards bodies
  * Automated systems
  * Other interested parties

A Community of Interest can establish or maintain:

  * Shared objectives
  * Shared terminology
  * Shared information requirements
  * Shared data models
  * Shared [[public:99_annexes:annex-b-terms-and-definitions:t:test_definition|Test Definitions]]
  * Shared [[public:99_annexes:annex-b-terms-and-definitions:t:test_environment|Test Environments]]
  * Shared [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]]
  * Shared [[public:99_annexes:annex-b-terms-and-definitions:c:catalog|Catalogs]]
  * Shared [[public:99_annexes:annex-b-terms-and-definitions:p:policy|Policies]]
  * Shared [[public:99_annexes:annex-b-terms-and-definitions:g:governance_policy|Governance Policies]]
  * Shared evaluation criteria
  * Shared [[public:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] requirements
  * Shared interoperability expectations

A Community of Interest can identify:

  * Its identity
  * Its name
  * Its description
  * Its purpose
  * Its subject area
  * Its participating Organizations
  * Its participating Users
  * Its applicable [[public:99_annexes:annex-b-terms-and-definitions:r:role|Roles]]
  * Its governing authority
  * Its applicable [[public:99_annexes:annex-b-terms-and-definitions:g:governance_domain|Governance Domain]]
  * Its participation rules
  * Its decision process
  * Its applicable Policies
  * Its shared resources
  * Its [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * Its [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

===== Definition =====

//group of participants that share an interest, purpose, mission, problem, or information need within a defined subject area//

===== Source =====

Adapted from:

  * DIDO Reference Architecture
  * DIDO Reference Implementation Conceptual Model
  * DIDO-TE draft Requirements Register

===== Note =====

A Community of Interest differs from an [[public:99_annexes:annex-b-terms-and-definitions:o:organization|Organization]]:

  * An Organization has an identifiable organizational identity, purposes, structure, and responsibilities
  * A Community of Interest groups participants according to a shared interest, purpose, mission, problem, or information need

A Community of Interest can exist:

  * Within one Organization
  * Across multiple Organizations
  * Across organizational and jurisdictional boundaries
  * For a limited duration
  * As a continuing community

Membership in a Community of Interest does not by itself transfer ownership, authority, or responsibility among participating Organizations.

A Community of Interest does not necessarily have independent legal identity or governing authority. The applicable Governance Policy must identify any authority exercised by or on behalf of the Community of Interest.

Multiple Communities of Interest can use the same DIDO-TE deployment while applying different:

  * Test Definitions
  * Test Environments
  * Baselines
  * Governance Policies
  * Access controls
  * Evidence requirements
  * Validation criteria

===== Example =====

A distributed-systems testing Community of Interest includes:

  * Government acquisition Organizations
  * Test laboratories
  * System developers
  * Technology vendors
  * Security evaluators
  * Standards organizations

The participants share:

  * A DIDO-TE Test Environment
  * A Catalog of Test Definitions
  * Approved Baselines
  * Common Test Result formats
  * Evidence requirements
  * Rules for making Validation Decisions

Each participating Organization retains its own authority and responsibilities while using the shared resources established for the Community of Interest.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>