Chapter 4 - BUSINESS USE CASES

Business use cases -Business events are useful to partition the work, but it is the work’s response to the event that now captures the interest of the requirements analyst. For every business event, there is a preplanned response to it, known as a business use case (BUC).

 Rabbit Projects - it is important to have a rock-solid grasp of the business problem to be solved. Rabbits make use of business use cases to explore their problem domain before starting to formulate a solution. This approach does not add to the documentation load, and it lessens the time spent delivering inappropriate solutions.

 Horse Projects - Horse projects are more strategic than rabbits. they need more time to complete. There is also the possibility of using Business use case scenarios as the documentation to pass along to the developers.

 Elephant Projects - elephant projects have a large number of stakeholders, clear communication is both important and difficult. Business use case scenario is also useful for discussing high-level issues with outsourcers.

 The Scope of the work - The work is the business activity of the owner of the eventual product; alternatively, it as the part of the business that the customer or client wants to improve.



Comments

  1. Kirandeep Kaur2 April 2020 at 18:03

    This chapter provides an information about finding the most appropriate business use case. Also, this chapter discussed about dividing the work into smaller parts on the basis of user's views of the system. "Work" means system for doing business and work may be commercial, scientific, manual and so on. Work provide services to the outside world by receiving information and signals from them. When the adjacent system wants to do something, then business events occur. In the business events, there should always be one data flow to show it on the context diagram. Product use cases are derived from the business use case to group the requirements according to the work that responds to the business event.

    ReplyDelete
  2. Kerone Barnett2 April 2020 at 19:58

    Chapter 4 emphasizes how important it is for the Business Analyst to go above and beyond the expectations of the end-user/ client/ project sponsor. The Business Analyst (BA) focuses on the business activity or business event from end to end - what triggered the event and what adjacent systems are at work at the time of the triggered business event. The BA must examine all the activities of the work itself and understand the nature of the work. This understanding will help to determine business use cases and ultimately contribute to the design of the product as per user requirements.

    ReplyDelete
  3. Sukhpreet Singh3 April 2020 at 21:25

    Business use case – It describes the way to discuss partitioning the work in smooth and fail – safe way as per requirements of investigation.
    1. Understanding the work – In this there is no matter what kind of work you do that could be commercial, scientific or any other kind, it must improve owner’s work then it will be installed in business area of owner.
    2. Formality guide – Guides are very important for Rabbit Project; they must use this to explore their problems and know more about them. Elephant project have large number of stakeholders; therefore, they must also use business events.
    3. Business events – Things that happen outside the scope of business or happen because it is time for work to do something and result in some response in any way are called business events.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 7 – Business Requirements Gathering

Chapter 7 –  Understanding the Real Problem This chapter focuses on the Business Analyst “thinking above the line” and focusing on the true essence of the business. This requires reviewing the Brown Cow Model – that is looking at the area above the line – the “ What Now ”. This section examines the undiluted and core reason for the business’ existence. The next step would be to look at the future of the business, called the “Future What”. Examining these two areas helps the Business Analyst get to the heart of the business problem, rather than focus on possible solutions. With the right focus the Business Analyst is not distracted by what others may think the solution could be, but the BA delves and trawls through as much information as possible to accurately understand the business and how it functions, minus technology or automation. This determination to channel all efforts towards the core purpose of the business allows the BA to be more open to all possible solutions...
Read more

Chapter 3 - Business Requirements Gathering

Chapter 3 - Scoping the Business Problem This chapter focuses on Project Blastoff Deliverables such as Project Purpose, Scope of work, Stakeholders, Constraints, Names, Estimated Cost and Risks. The chapter refers to Scope, Stakeholders and Purpose as the Trinity confirming that these are core elements of any successful project blastoff. ·          For Project Scope, we must understand the extent of the work to be done and how this task (business improvement) will impact the current operational environment and its existing products and services. We must ensure that we accurately document the depth and breadth of the project. ·          For Project Purpose, we must accurately capture the quantifiable/ measurable business benefit to be gained from the completion of the project. ·          For Stakeholders, we must document all possible persons with a vest...
Read more