====== Maintenance Activity ======

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

===== Discussion =====

A Maintenance Activity is a coordinated set of actions performed to analyze, control, implement, verify, or record a [[public:99_annexes:annex-b-terms-and-definitions:c:change|Change]] to a [[public:99_annexes:annex-b-terms-and-definitions:m:maintained_item|Maintained Item]]. It provides the organizing context that relates the Maintained Item, Change, governance decisions, implementation information, verification information, and resulting [[public:99_annexes:annex-b-terms-and-definitions:m:maintenance_outcome|Maintenance Outcome]].

A Maintenance Activity may include actions that:

  * Identify the Maintained Item
  * Identify applicable Maintainability Criteria
  * Identify dependencies
  * Identify expected Change effects
  * Associate the Change with governing Baselines
  * Obtain and enforce a [[public:99_annexes:annex-b-terms-and-definitions:c:change_authorization|Change Authorization]]
  * Implement permitted alterations
  * Record alterations actually made
  * Verify the implemented Change
  * Perform [[public:99_annexes:annex-b-terms-and-definitions:r:regression_test|Regression Tests]]
  * Record the Maintenance Outcome

A Maintenance Activity does not require every listed action. The applicable Change, Requirements, Policies, Constraints, Maintainability Criteria, and Change Authorization determine which actions apply.

===== Definition =====

//coordinated set of actions performed to analyze, control, implement, verify, or record a change to a maintained item//

===== Source =====

Dido Solutions, Inc. and Jackrabbit Consulting, Inc., derived from the software-maintenance activity and process concepts in ISO/IEC/IEEE 14764:2022

===== Note =====

A Maintenance Activity may complete successfully, fail, stop before completion, be suspended, be canceled, or be rolled back. Each completion or termination produces a Maintenance Outcome.

The applicable [[public:99_annexes:annex-b-terms-and-definitions:a:authority|Authority]] issues the Change Authorization. The Maintenance Activity may request, receive, record, validate, and enforce that authorization but does not invent it.

A Maintenance Activity may contain subordinate activities or actions and may involve multiple actors, [[public:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], [[public:99_annexes:annex-b-terms-and-definitions:t:test_asset|Test Assets]], operational resources, or execution environments.

The Maintenance Activity should retain sufficient [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] and [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to relate its Maintenance Outcome to the governed and realized maintenance history.

===== Example =====

A Maintenance Activity identifies a [[public:99_annexes:annex-b-terms-and-definitions:t:test_executable|Test Executable]] as the Maintained Item, analyzes a proposed dependency Change, associates the Change with its governing Baseline, enforces the Change Authorization, records the implemented alteration, performs verification and Regression Tests, and records the resulting Maintenance Outcome.

----

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