In project network analysis (PERT/CPM), the ‘‘slack’’ of an event is defined as the calculated time span within which the event must occur. Is this statement correct?

Introduction / Context:
Project scheduling relies on understanding floats or slack—the allowable delay without affecting subsequent events or the overall deadline. Clarity on this definition is essential for prioritizing activities and managing buffers.

Given Data / Assumptions:

• Events (nodes) and activities (arcs) are defined in a PERT/CPM network.
• Early and late times for events are computed via forward and backward passes.
• Slack refers to timing flexibility for events or activities.

Concept / Approach:
Event slack equals Late Event Time minus Early Event Time. It is the permissible window for the event’s occurrence without delaying dependent events or the project completion.

Step-by-Step Solution:

Verification / Alternative check:
Where slack is zero, events lie on the critical path and must occur exactly at their early/late times to avoid project delay.

Why Other Options Are Wrong:
‘‘false’’ and ‘‘cannot be said’’ contradict the standard CPM definition; ‘‘All of the above’’ is logically inconsistent.

Common Pitfalls:
Confusing activity float with event slack; while related, the formulas and interpretations differ.

Final Answer:
true