Chapter 6 – Scenarios


A scenario is “an outline of a plot, or a postulated sequence of steps.”

When discussing requirements work, this term is to uses to symbolize the plot of a section of the work being studied. The idea to use “plot” is to imply that the work is broken down into a series of steps, and by explaining these steps, the work is explained.

The scenario should be neutral, and both simple and understandable to all stakeholders. A modeled scenario to be used to read an agreement on what the work must do.

The authors suggest that a scenario is written by breaking the functionality of the business use case down into a series of steps; each step being an activity that form part of the BUC.
The parts involved in formalizing a scenario are:
  1.  Identify the scenario and give it a meaningful name.
  2. Add the trigger for the business case.
  3. Add any preconditions that must exist when the business use case is triggered.
  4. Add the interested stakeholders.
  5. Identify the active stakeholders.

Always make sure the scenario represents the essence of the business: “What does the business really need to do?” This might involve eliminating technological bias and rewording the parts in the scenario.

Finally, according to each situation and group of stakeholders, it’s possible to diagram the scenario to explain the functionality of a business case.



Source: Mastering the Requirements Process - Getting Requirements Right; pages: 128-145

Comments

  1. Kent Dela Cruz14 November 2019 at 12:56

    Benefits of Business Scenarios
    A business scenario is essentially a complete description of a business problem in business terms, which enables individual requirements to be viewed in relation to one another in the context of the overall problem. An additional advantage of business scenarios is in communication with vendors.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.

    ReplyDelete
  2. Parminder Singh16 November 2019 at 19:04

    A scenario is a natural language tool for telling a story. We have discussed how to write this
    story; its intention is to help you and your stakeholders come to a coherent understanding of
    the functionality of a business use case. Writing the BUC scenario tests whether sufficient
    study has been done or the business analyst needs to ask more questions and investigate
    further.Once the BUC scenario is agreed—that is, you and your stakeholders have come to a
    consensus that it accurately represents the desired state of the work—it forms the basis for
    writing the requirements.
    Some requirements analysts—and some stakeholders—prefer to use a diagram to explain the
    functionality of a business use case. This preference is a matter of personal choice, and it
    depends largely on whether your audience responds more favorably to text or to
    diagrammatic scenarios. We leave it to you to experiment and decide which form of
    representation is right for you.Several diagrams can be used for scenarios.

    ReplyDelete
  3. Harleen Virk16 November 2019 at 21:30

    Misuse cases (you may get a kick out of the chance to consider them "miserable cases") show negative or destructive potential outcomes, for example, somebody mishandling the work or endeavoring to swindle it. Models incorporate clients intentionally entering mistaken information, clients utilizing taken charge cards, and pranksters making imaginary calls or exchanges, planting an infection or other malware, or taking part in any of the bunch different things that should be possible to hurt the work. It might be useful here to think in wording drawn from fiction composing and utilize the possibility of the hero and the foe. The hero is the legend or principle character of the story: the hero, the client, the on-screen character utilizing the item following your ordinary use case situation. Winnie the Pooh is the perfect hero—he is good natured and you need him to win out at last. In any case, as Pooh, your hero may be of next to no mind and commit errors: overlook his secret phrase, pick an inappropriate choice, get nectar on the keys, or any of the numerous shocking things a Pooh can do. Give your hero a role as somebody who is careless, slow, occupied, and not focusing. (You will undoubtedly realize somebody like that.) Go through the typical case situation, and for each progression, ask what should be possible wrongly. It might be less difficult to compose another situation for each abuse, as the repercussions of a stumble might be intricate enough to warrant their very own different story. So much for the hero. The rival is the individual who restricts the work, tries to hurt it, or needs to dupe it. Programmers are the most ordinarily considered case of opponents. Look at all of the means for the typical case and inquire as to whether there is a plausibility of somebody contradicting or abusing that activity. For this situation, the repercussions after finding an adversary's abuse might be to just stop the business use case.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 1 - What is Business Analysis?

Hello! Welcome to our Business Analysis blog.  We are Mariane, Harleen, Kent and Parminder, and we are Business Technology Management students at Red River College.  Throughout our Fall term we will be using this blog to share some important concepts regarding Business Analysis.  For our first post, we will start with the basics, and define exactly what is Business Analysis, and other important concepts related to it. According to BABOK, " Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders. Business analysis enables an enterprise to articulate needs and the rationale for change, and to design and describe solutions that can deliver value. "  Business analysis cannot work without having a representative to intermediate these practices within an enterprise. This professional is called a Business Analyst who is responsible for putting in practice the tasks desc...
Read more

Chapter-12 Fit Criteria and Rationale

Image
FORMALITY GUIDE Horse ventures need to have an exact and effectively shareable comprehension of the significance of necessities. It has been our experience that when the task has numerous partners—which is the standard for horse ventures—various partners relegate various implications to prerequisites. Including a reason and a fit basis to every necessity implies it is for all intents and purposes inconceivable for errors to happen. We prescribe that pony ventures incorporate both of these in their necessities. Elephant ventures must utilize methods of reasoning and fit criteria. These tasks are compelled to deliver a composed determination to be given on to some other gathering, either another piece of the association or an outsourcer. Having a detail containing just unambiguous, testable necessities is pivotal to elephant ventures on the off chance that the other party is to comprehend and, at that point convey the right item Scale of Measurement Any prerequisite can be ...
Read more

Chapter 5 - Investigating the Work

The starting point for any product that will be built is the owner's work.  The book mentions that business analysts go "trawling" after business requirements.  The first task in the business requirements gathering process is to understand and investigate the work that is being done. Once that's understood, then the "essence needs to be understood, that is the clean picture of the business, without technology.  In this chapter the "Brown Cow Model" is also introduced. Which is divided into 4 parts:  How-Now: shows the implementation of the work as it currently exists, including physical artifacts, people and processors to do the work.   What-Now: shows the real business policy (essence). No machines, people, or organizational departments. Future-What: shows the business as your owner wants to have it, but still with no technology applies to it. Future-How: shows the idealized future business policy, augmented with the technology and people ...
Read more