[masc2023]

Improvement

Description

Aligns SCORE's Change Management Plan with the ISO 26262-8:2018 clarifications tracked by
process_description audit issue eclipse-score/process_description#567 and drafted in
eclipse-score/process_description#834 (8.4.1.2, 8.4.1.3, 8.4.2.2, 8.4.3.1, 8.4.4.2).

Adds four small, non-behavioral clarifications to
docs/platform_management_plan/change_management.rst:

• Change Management Scope subsection: identifies which work products/items are subject to
  change management by reusing the existing identification in the Configuration Management
  Plan, and states that it applies for their complete lifecycle,
  distinct from an individual Change Request's Milestone/Expected Implementation Version.
• One sentence summarizing what the existing Impact Analysis Template covers (interfaces,
  connected elements, affected-vs-modified work products, distributed-development
  responsibilities, safety impact, implementation/verification timing)
• One sentence clarifying that a Change Request's date is the ISSUE creation date (GitHub
  metadata) and that its starting release version is the main baseline state at creation
  time (identifiable via the linked PR's base commit), distinct from the target Expected
  Implementation Version.
• One sentence clarifying that the implementer of an accepted Change Request is recorded via
  the ISSUE's Assignees field and/or linked implementation PRs/Issues, reusing the same
  convention already used in problem_resolution.rst.

No changes to workflows, FEP routing, responsibilities, approval gates, states, or compliance
tags. docs/platform_management_plan/config_management.rst and the shared .github issue
forms were inspected but not modified (out of scope / not owned by this repo).

Follow-up (outside this repo): once process_description#834 merges and SCORE's
score_process_description pin is bumped past v2.1.2, revisit whether the upstream
guideline/template updates make any of this wording redundant.

Validation

• bazel run //:docs — build succeeded, no new warnings/errors.
• git diff --check — passed, no whitespace issues.

Related ticket

closes N/A — no SCORE-side issue exists; tracked upstream by
eclipse-score/process_description#567 and eclipse-score/process_description#834.

[github-actions]

Documentation preview for this pull request is available at:
pr-3347: https://eclipse-score.github.io/score/pr-3347/