CHAPTER 6: SCENARIOS
CHAPTER 6: SCENARIOS
What is the scenario? Why to have scenarios in a project?
Scenarios are the future events which are foreseen by
considering various feasible results or outcomes. One exact picture of the
future is not clearly shown in the scenario. Instead, the scenario presents several
alternative future developments. As a result, a scope of possible future
outcomes is observable. The outcomes and the development paths leading to the
outcomes are both observable.
Scenario helps business analysts facilitate business
decisions by taking into account a number of potential developments and
possible future events in business environments. Business analysts can use scenarios
in the business use case workshops and even in risk management of a project.
Why should business analysts concern about the essence of business?
The essence of business is in the above quadrants of the Brown
Cow Model, the What-Now and Future-What views which is the reason why focusing
on the essence of business are important. When looking at the essence of
business, a business is facing the real problems of the company, not better solutions
for the problems. After finding the real business problem, a business analyst
can eliminate all the technological disguise that normally makes up a
description of some work.
Why and How to create diagram of the scenario?
The scenario diagram is not mandatory, but business analysts
are recommended to use it because the audience responds more favorably to
diagrammatic scenarios. Various kinds of diagrams can be used to present the scenario.
There are two most commonly used diagrams: The UML (Unified Modeling Language)
activity diagram and the BPMN (Business Process Modeling Notation). The UML is
a more popular choice. Generally, business analysts can choose any diagrams that
suit the company’s needs or requirements. Below is the example of a UML
diagram:
In Figure 6.2, the dotted lines are called “swim lanes” that
divide the work between the participants. Swim lanes are intentional, but because
they are both good and bad, a business analyst should be careful when using it.
The activity diagram shows a certain amount of parallel
processing. For example, there is no reason why the Attach frequent-flyer
number and Allocate seat activities cannot be performed at the same time. The
text scenario does not show this possibility.
The activity diagram also shows other control aspects. For
example, the diamond at the bottom of the model in Figure 6.2 is called a
merge. This symbol means that all processing must reach this point before
proceeding. In the case of the airline check-in, the entire process cannot end
until both the bag tags and the boarding pass have been printed. Diamonds are
also used to denote decisions, just as they are in traditional flowcharts.
What are the differences between Alternatives and Exceptions?
An exception path contains steps that execute if something
goes wrong, such as an input from the actor that the system cannot handle or a
condition or series of conditions that occurs that are not part of the
functionality. An example of an exception path is an actor keying in a record
for a search and the record not being found.
An alternative path is actually much closer to the basic
course of events because everything happens correctly (in other words, there
are no errors); an alternative path simply is less likely to happen than the
basic course of events. An example of an alternative path is the use of an
unusual form of payment, such as the use of a credit card when a PO is more
common.
Posted by Kim Le
I am going to describe alternatives and exceptions in my words. According to me Alternatives are the wanted and acceptable deviations from the normal case. These deviations are the mainly choices that we want, these choices are intentional as they are wanted and defined by the business. Moreover it is very important for BA to consider alternatives , as the two BAs may have different ideas and thoughts.
ReplyDeleteExceptions:- Exceptions are the unwanted and inevitable deviations from the normal case. These are unacceptable because the owner of the work do not want that exceptions will happen.
A scenario is an outline of a plot, or a postulated sequence of steps. The use of “plot” is intended to imply that you break the work into a series of steps or scenes, and by explaining these steps, you explain the work. The scenario is a neutral medium, and one that is both simple and understandable to all stakeholders. Stakeholders are invited to participate and revise the scenario until it represents a consensus view of what the work should be.
ReplyDeleteScenario is a framework of any activity. Business scenario helps BAs to take the right business decisions as it shows several future events. Business Analysts also lay stress on the essence of business as it helps to identify real business problems. Apart from this, alternatives and exceptions play important role in the business requirements process. Alternatives are acceptable variations while exceptions are totally unwanted and inevitable deviations. BAs have to deal with both alternatives and exceptions to be a successful business person.
ReplyDelete