BR-PROJ-001: Closed Project Update Restrictions

Mon, 01 Jan 0001 00:00:00 +0000

BR-PROJ-001: Closed Project Update Restrictions

Standard Classification: Behavioral Constraint / Access Control
Target Entity: Project
Status: Approved
Governing Configuration: projects.closed.update.strict (Default: false)

1. Executive Summary & Formal Statements

1.1 Formal Statement (RuleSpeak® / EARS)

While a Project has clearing state CLOSED (project.clearingState == ProjectClearingState.CLOSED):
- If projects.closed.update.strict is false, then the system shall allow users with role CLEARING_ADMIN (or above) as well as the project team (Creator, Project Responsible, Moderators, Contributors, and Lead Architects) to modify all fields of the project.
- If projects.closed.update.strict is true, then the system shall allow only CLEARING_ADMIN (or above) to modify all fields. The project team (Creator, Project Responsible, Moderators, Contributors, and Lead Architects) shall only be allowed to modify the allowlisted maintenance fields:
  1. Project State (state, project status, not clearing state)
  2. Project Responsibles (projectResponsible)
  3. Project Owner (projectOwner)
  4. Security Responsible (securityResponsible)
  5. Enable Security Vulnerability Monitoring (securityVulnerabilitiesMonitoring)
  6. Display Vulnerabilities (displayVulnerabilities)
  7. Phase-out date (phaseOutDate)
  8. External IDs (externalIds)
- If any other user attempts an update, or if a restricted user attempts to modify non-allowlisted fields in strict mode, the system shall reject the request with HTTP 403 Forbidden and shall not generate any moderation request.

1.2 Purpose & Risk Mitigated

This restriction is enforced strictly for audit and compliance purposes. A project is transitioned into the CLOSED clearing state only after its license clearing process is fully completed and approved. Once in the closed state, no changes that could result in a drift of license clearing (such as unauthorized modifications, additions, or removals of components, releases, attachments, or license obligations) shall be allowed. This guarantees that the cleared and certified baseline remains immutable and audit-compliant, while still permitting non-clearing operational lifecycle maintenance (e.g., updating security contacts, phase-out dates, or project ownership).

BR-PROJ-002: License Clearing Tab Status Badges & Color Representation

Mon, 01 Jan 0001 00:00:00 +0000

BR-PROJ-002: License Clearing Tab Status Badges & Color Representation

Standard Classification: Definitional Rule / UI Presentation Invariant
Target Entity: Project, Release, Project Details UI (License Clearing Tab)
Status: Approved
Enforcement Points: Frontend UI Views (ListView.tsx, TreeView.tsx)

1. Executive Summary & Formal Statements

1.1 Formal Statement (RuleSpeak® / EARS)

While an authenticated user is viewing an accessible Project in details mode under the License Clearing tab:
- The system shall render a hierarchical table displaying all linked releases (direct and transitive sub-project releases).
- The system shall display state indicator badges with abbreviations:
  - (PS) for Project Clearing State.
  - (CS) for Release Clearing State.
- When rendering the (PS) badge for a project row, the system shall apply the exact background color mapped to the project clearing state:
  - Closed $\rightarrow$ Green (#68C17C)
  - In-progress $\rightarrow$ Yellow (#FFD351)
  - Open $\rightarrow$ Red (#E6717C)
  - Not Applicable / Unknown $\rightarrow$ Grey (#DEE2E6)
- When rendering the (CS) badge for a release row, the system shall apply the exact background color mapped to the release clearing state:
  - NEW_CLEARING $\rightarrow$ Red (#E6717C)
  - UNDER_CLEARING $\rightarrow$ Yellow (#FFD350)
  - SENT_TO_CLEARING_TOOL or SCAN_AVAILABLE $\rightarrow$ Orange (#F7941E)
  - REPORT_AVAILABLE $\rightarrow$ Blue (#0D6EFD)
  - INTERNAL_USE_SCAN_AVAILABLE $\rightarrow$ Purple (#9370DB)
  - APPROVED $\rightarrow$ Green (#69C17D)
  - null, undefined, or unmapped $\rightarrow$ Grey (#DEE2E6)
- When a user hovers over any (PS) or (CS) badge, the system shall render a tooltip displaying the full, human-readable state name.

1.2 Purpose & Risk Mitigated

Compact color-coded badge representations allow project managers, architects, and clearing officers to assess compliance and clearing readiness across deeply nested dependency trees at a single glance. Standardizing the color mappings prevents misinterpretation of clearing risk across different pages and ensures accessibility via hover tooltips.

Project Business Rules on Eclipse SW360

BR-PROJ-001: Closed Project Update Restrictions

BR-PROJ-001: Closed Project Update Restrictions

1. Executive Summary & Formal Statements

1.1 Formal Statement (RuleSpeak® / EARS)

1.2 Purpose & Risk Mitigated

BR-PROJ-002: License Clearing Tab Status Badges & Color Representation

BR-PROJ-002: License Clearing Tab Status Badges & Color Representation

1. Executive Summary & Formal Statements

1.1 Formal Statement (RuleSpeak® / EARS)

1.2 Purpose & Risk Mitigated