Scope Creep and Context Models

A context model explicitly defines what is inside the system boundary and what is outside, making it clear when proposed additions fall outside the agreed scope and should be treated as change requests rather than included by default

Explanation

A proper context model defines the system boundary — what is and is not part of the system. By establishing this boundary early, the team and stakeholders have a shared understanding of scope. When new features or functions are proposed, it is immediately visible whether they fall inside or outside the boundary. Additions that cross the boundary can be formally treated as scope changes requiring cost and effort reassessment, rather than quietly absorbed into the project.