Tuesday, March 31, 2020

Chapter-4 Business Use Cases

Chapter-4
(Business Use Cases)

Created by:- Ramandeep Kaur

1. What are the business events and their responses?

Answer: A business event happens at the moment the adjacent system decides to do something, or as part of its work some processing condition occurs. The adjacent system tells the work that the event has happened by sending a triggering data flow. When this stream of data arrives, the work responds by processing the incoming data, and by retrieving and recording stored data.

2. Explain formality guide in business use case?

Answer: Rabbit—small, fast, and short-lived. Rabbit projects are typically smaller projects with shorter lifetimes, where close stakeholder participation is possible. Rabbit projects usually include a lesser number of stakeholders.

Horse—fast, strong, and dependable. Horse projects are probably the most common corporate projects—they are the “halfway house” of formality. Horse projects need some formality—there is likely a need for written requirements so that they can be handed from one department to another. Horse projects have medium longevity and involve more than a dozen stakeholders, often in several locations, factors that necessitate consistently written documentation.

Elephant—solid, strong, long life, and a long memory. An elephant project needs a complete requirements specification. If you are outsourcing the work, or if your organizational structure requires complete, written specifications, you’re an elephant. In certain industries, such as pharmaceuticals, aircraft manufacture, or the military, regulators demand not only that full specifications be produced, but also that the process used to produce them be documented and auditable. Elephant projects typically have a long duration, and they involve many stakeholders in distributed locations.

3. What is Time-Triggered Business Events with example?

Answer: A time-triggered business event happens when a prearranged time is reached. This is based on either a periodic occurrence (for example, the end of the month, or a certain time each day), a fixed time interval (for example, three hours since the last occurrence), or a certain amount of time elapsing since another business event (for example, 30 days after sending out an invoice). The normal response is to retrieve stored data, process it, and send some information to an adjacent system.

4. List of Business Events and Their Associated Input and Output Flows for the Road De-icing Work.

Answer: Event Name(Input and Output)
1. Weather Station transmits a reading Weather Station Readings (in) 
2. Weather Bureau forecasts weather District Weather Forecasts (in) 
3.  Road engineers advise there are changed roads Changed Road (in)
4.  Road Engineering installs a new weather station (in) 
5.  Road Engineering changes the weather station Changed Weather Station (in) 
6. Time to test Weather Stations Failed Weather Station Alert (out) 
7. Truck Depot changes a truck Truck Change (in) 
8. Time to detect icy roads Road De-icing Schedule (out) 
9. Truck treats a road Treated Road (in) 
10. Truck Depot reports a problem with a truck Truck Breakdown (in) Amended De-icing Schedule (out) 
11. Time to monitor road de-icing Untreated Road Reminder (out)

5. How Business Case Use is different from System Use Case?

Answer: Business Case Use: -A Business Use-Case is to do with “using a business”: this recognizes that businesses1 are created and organized to do things for people – mainly customers, but also other “actors”. So a Business Use-Case is a way in which a customer or some other interested party can make use of the business to get the result they want – whether it’s to buy an item, to get a new driving license, to pay an invoice, or whatever.


System Use Case:- In contrast, a System Use-Case is a way in which a user of a computer system can make use of the system to get the result they want. This will typically be something we can readily imagine as being done in a single sitting on a single PC or other devices such as an ATM or a mobile/cell phone, usually with a single UI, or a small number of closely-related screens such as a wizard, and taking maybe between a couple of minutes and a half-hour at most.




3 comments:

  1. Business events provide a mechanism that lets external systems receive notifications from Finance and Operations applications. In this way, the systems can perform business actions in response to the business events.Business events can be consumed in Microsoft Power Automate via the application connector. The connector has a trigger that is named when a business event occurs. This trigger can be used to subscribe to any of the business events that are available in the target instance of the application. A business action that a user performs can be either a workflow action or a non-workflow action.

    ReplyDelete
  2. A time triggered business event is quite common for Microsoft. Many of the projects that Microsoft works on are related to updates for previous work. These updates are usually systematic and come at regular intervals. For example, their operating systems get regular updates every six months. This would mean that the update (which is the event) has been triggered to be made because the time limit that Microsoft made requires it to be so.

    ReplyDelete
  3. Business events and business use cases allow you to carve out a cohesive piece of the work for further modeling and study. By understanding the work being done by each of the BUCs, you come to understand the optimal product you can build to support that work. If you are outsourcing, you might not determine the product use cases, but work instead on the business use cases. These business use cases can then serve as your negotiating document when you ask your outsourcer which parts of them he can deliver as product use cases.

    ReplyDelete

Chapter - 12 - Fit, Criteria and Rationale

Fit, Criteria and Rationale Formality Guide A pleasing aspect (amongst many) of Kent Beck’s extreme Programming technique is its i...