A scope model is most often used to define the boundaries of control or change, a solution, or a business need. In most cases, a scope model will show items that are either in scope or out of scope. It can also show both in-scope and out-of-scope items. 

A business analyst is mostly concerned with the elements that are part of in-scope items; however, they also need to be clear on which items are out of scope and what the broader context of this is.

The level of detail when defining scope boundaries is important as the scope model should contain enough detail to be meaningful but not be too detailed and cause a situation where "analysis paralysis" slows down the initiative's progress. Any assumptions made at the time of defining the scope model must be expressed and maintained. The scope model can be described using text or diagrams, or a combination of both.