You and Tom are writing the solution scope for a new project in your organization. You need to create a method to define what solution will and will not provide for the organization. What technique…

Stakeholder interviews are an elicitation technique for gathering information and requirements, not a method for formally defining or documenting solution boundaries.

User stories capture functional requirements from the perspective of a user role but do not serve as a technique for formally bounding what a solution will or will not deliver at the project level.

Functional decomposition breaks a system into its component parts and sub-functions for analysis purposes, but it does not define the outer boundary of what is in or out of scope for the solution.

Scope modeling is a structured technique that explicitly defines the boundaries of a solution by depicting what is in scope and what is excluded, often through context diagrams or scope matrices. It is the purpose-built method for answering the question of what the solution will and will not provide, making it the most appropriate choice when establishing solution limits during planning.