REQ-NFR-067

Critical-path computation completes within 500 ms for up to 500 activities

ID: REQ-NFR-067
Category: Non-Functional Requirements
Status: approved
Priority: P0
Created: 2026-05-11T18:34:00.000Z
Approved: 2026-05-11T18:37:00.000Z
Updated: 2026-05-11T18:37:00.000Z

What

For a project of up to 500 activities and up to 1000 dependency edges, the critical-path computation (REQ-FUN-103) SHALL complete within 500 ms p95 on the reference machine.

Why

Interactive UI workflows (drag a date, see the new critical path) require sub-second feedback. 500 ms is the documented established_guidelines_tool norm.

How

CPM is O(V+E); benchmark harness in test suite exercises a synthetic 500-activity / 1000-edge network and asserts the bound. Server caches the computed path per schedule_version to avoid recomputation on re-read.

Done when

Benchmark in CI passes the 500 ms p95 bound on the reference machine.

Out of scope

Sub-millisecond critical path for huge schedules (> 5000 activities).

established project management guidelines Mapping

Primary Knowledge Area: Schedule Management
Secondary KAs: Quality Management
Primary Process Group: Planning
established project management guidelines Deliverable: Schedule Management Plan

Performance NFR tied to established project management guidelines Develop Schedule responsiveness.