Blog
4 (Pawandeep Kaur)
CHAPTER
4: Business Use Cases
Business Event: Business event also called business transactions. Any piece
of work responds to things that happen outside it—it’s that simple. These
happening called business event. Here I am giving an example of business event.
: 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.
Time-Triggered Business Events: These events are initiated by the arrival of a predetermined
time (or date). There can be good
example for understanding better like, your insurance company sends you a
renewal notice a month before the anniversary of your policy.A business event
takes place outside the scope of the work, and the work learns that it has
happened through the arrival of an incoming flow of information. The work
contains a business use case that responds to this business event.
Why Business Events and Business Use
Cases Are a Good Idea: The help desk person initiates the use case by asking the
caller for details of the problem and logging the call." The use case is the
logging, and the actor is the help desk person. Again, this product-centric
view misses the real business event the happening that started it all. In this case it is the
initiation of the call to the help desk. The work’s response to a
business event brings together all the things that belong together. As a
result, you get cohesive partitions with minimal interfaces between the pieces.
the fewer dependencies that exist between the pieces, the
more the analysts can investigate the details about one piece without needing
to know everything about all the other pieces. There is one more reason for
using business use cases, and that is to prompt an investigation of what is happening at the time of the business
event.
Finding the Business Events: Business
events are things that happen and, in turn, make the work respond in some way.
An event may happen outside the scope of the work (an external event), or it
may happen because it is time for the work to do something (a time-triggered
event). For find a business event we can
say that whenever a business event occurs, there must be at least one data flow
to show it on the context diagram. Here I am attaching a List of Business
Events and Their Associated Input and Output Flows for the Road De-icing Work
which we can suppose a best example to describe to find the business events.
Business Use Cases: For
every business event, there is a preplanned response to it, known as a business
use case (BUC). The business use case is always a collection of identifiable
processes, data that is retrieved and/or stored, output generated, messages
sent, or some combination of these. The business use case is the most
convenient unit of work to study. You can identify one or more stakeholders who
are expert in each event. You can
readily isolate the work of a business use case, because it has no processing
connections to other BUCs; the only overlap between BUCs is their stored data.
As a consequence, different analysts can investigate different parts of the
work without the need for constant communication between them. This relative
isolation of each business use case makes it easier to identify the
stakeholders who are expert in that part of the work, and they can (with your
help) describe it precisely and in detail.
I want to talk more about business use case. It describes a series of events and interactions between user and a system, in order to produce a result of value means goal. A business use case describes the more general interaction between a business system and the users of that system to produce business goals. A use-case provides the benefits such as it is an easy means of capturing the functional requirements with a focus on value added to the user and use-cases are relatively easy to write and read compared to the traditional requirement methods. Moreover, use-case engage the user in the requirement process.
ReplyDeleteI would like to talk about the sizes of the project which are: rabbit, horse and elephant. This chapter is mainly based upon the formally guide to the size of the project. First is the rabbit project, it used when the project have the good catch on the problems before starting to the solution of it. This is because it will lower the load of the documentation and deliverable approaches.
ReplyDeleteSecond is Horse project, in this BUC is the good tool to use because it will discuss about both present and future business with the stakeholders and this scenarios will help the user to writing to many documentations.
Third is Elephant project, using BUC is helpful because elephant projects are the larger and they have larger number of stakeholders and BUC will help the user to discussing their work in geographically distributed teams. It also helps to discuss about the high-level issues with suitable outsources.
I would to like to talk about business use case, it means the list of steps in a process that help to achieve a business goal and use case is very beneficial to solve problem and helps you understand where errors could occur in the process and design features to resolve those errors.For example, imagine you're a cook who has a goal of preparing a grilled cheese sandwich. The use case would describe through a series of written steps how the cook would go about preparing that sandwich.
ReplyDelete