A business scenario is essentially a complete description of a business problem, both in business and in architectural
terms, which enables individual requirements to be viewed in relation to one another in the context of the overall
problem. Without such a complete description to serve as context:
There is a danger of the architecture being based on an incomplete set of requirements that do not add up to a
whole problem description, and that can therefore misguide architecture work.
The business value of solving the problem is unclear.
The relevance of potential solutions is unclear.
Also, because the technique requires the involvement of business line management and other stakeholders at an early
stage in the architecture project, it also plays an important role in gaining the buy-in of these key personnel to the
overall project and its end-product - the enterprise architecture.
An additional advantage of business scenarios is in communication with vendors. Most architecture nowadays is
implemented by making maximum use of Commercial Off-The-Shelf (COTS) software solutions, often from multiple vendors,
procured in the open market. The use of business scenarios by an IT customer can be an important aid to IT vendors in
delivering appropriate solutions. Vendors need to ensure that their solution components add value to an open solution
and are marketable. Business scenarios provide a language with which the vendor community can link customer problems
and technical solutions. Besides making obvious what is needed, and why, they allow vendors to solve problems
optimally, using open standards and leveraging each other's skills.