[[00 - Outcome 2 - Analysis and Design#7. characteristics of solution scope, including|U3-AOS2-KK7]] ## What is a scope? A description of software in terms of; major inputs, processing functionality and outputs. The scope defines where a solution's responsibilities end (e.g. A toaster should NOT be expected to make a cup of tea) The scope essentially answers the question: **"What is included in this project, and where does our responsibility end?"** For example: If you were designing a calculator you would need to define what math functions it could do and which it cannot. Most calculators cannot do statistically analysis but some can. ## System Boundaries These are the clear lines of demarcation for the software. They identify: - **Included Features:** The specific functionalities, user roles, and data that the system will handle. - **Excluded Features:** Functionalities or integrations that might seem related but are deliberately left out of the current development effort (e.g., "The system will manage employee records but will **not** handle payroll calculations"). This is crucial for managing expectations. - **Interfaces:** How the system interacts with external users, hardware, and other existing software systems. ## Scope Creep **Scope creep** is the term for uncontrolled, continuous growth or expansion of a project's requirements after the initial scope has been formally agreed upon and signed off. ### Key Characteristics of Scope Creep: - **Unapproved Changes:** It involves adding new features, requirements, or functionalities without corresponding adjustments to the **schedule, budget, or resources**. - **The "Gold Plating" Effect:** Often happens when developers or clients keep adding small, extra functionalities that seem minor individually but, cumulatively, significantly derail the project. - **Consequences:** Scope creep is the primary reason projects **fail to deliver on time and within budget**. It leads to: - **Delayed Delivery** - **Increased Costs** - **Reduced Quality** (due to rushing to finish the new, unplanned work) - **Team Burnout** ### Mitigating Scope Creep A well-defined scope and system boundary in the SRS is the first and most powerful defense against scope creep. Any request for a feature not explicitly in the scope must be handled through a formal **change control process** (e.g., a new scope document, updated budget/timeline, and management approval).