Individual Paper Presentation on the topic of Business Use Case

1. 1
MIS 620
Business Use Case
Individual Paper
Utkarsh Agrawal
11/30/2017

2. CONTENTS
Sr. No. Topic Page No.
1 Introduction 1
2 Explanation: Point 1 4
3 Explanation: Point 2 7
4 Explanation: Point 3 9
5 The Dangers of Misusing Use Case 11
6 Conclusion 13
7 Bibliography 14

3. 1
INTRODUCTION
The term use case was coined by Ivar Jacobson back in 1987 as a way to describe an
interaction between a system and a user of that system. Jacobson needed to break the
system into smaller units, as he felt that object models were not scalable. Thus, to conquer
the complexity and largeness of modern systems, he said it was first necessary to partition
them into convenient chunks, and that these chunks should be based on the user’s view of
the system.
However, Jacobson left us with some loose ends. For example, his definition of
a use case does not indicate precisely where or how a use case starts and ends. Truth be
told, Jacobson’s meaning of a use case more likely than not left some equivocalness;
different writers have expounded on utilize cases and not very many of them have a similar
thought of what it is. There are around 40 distributed meanings of “use case” with none of
them concurring. This tumult is tragic.
A primary purpose of the model of business use cases and actors is to describe how
the business is used by its customers and partners. Activities that directly concern the
customer, or partner, as well as supporting or managerial tasks that indirectly concern the
external party can be presented.
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 licence, to pay an invoice, or whatever. An important point is that a single
execution of a Business Use-Case should encompass all the activities necessary to do what

4. 2
the customer (or other actor) wants, and also any activities that the business needs to do
before the process is complete from its point of view.
Use cases focus on the users of the system, not the system itself, thus the real system
needs are brought to light early on. Since a use case consists mainly of narrative text, it is
easily understandable by all stakeholders, including customers, users and executives, not
just developers and testers. By including all the stakeholders during the early planning
stages of a project, you bring in people who best understand the problems at hand,
promote a sense of buy-in from end users, and eliminate surprises when the system is
deployed.
Use cases concentrate on the users of the framework, not simply the framework, in this
way the genuine framework needs are uncovered at an early stage. Since a use case
comprises for the most part of account content, it is effortlessly justifiable by all partners,
including clients, users and administrators, not simply designers and analyzers. By including
every one of the partners amid the early arranging phases of a task, you get individuals who
best comprehend the current issues, advance a feeling of purchase in from end users, and
dispose of amazements when the framework is conveyed.
Each use case depicts one way the framework is used, yet one of the enormous
advantages of use case demonstrating is that it likewise portrays everything that may turn
out badly. Distinguishing special cases to an effective situation right on time in the venture
spares a ton of time by finding inconspicuous necessities.

5. 3
At long last, once a use case show has been produced, it can be used to drive numerous
different parts of programming improvement, including venture arranging (cost, intricacy
and timing gauges), protest models, experiment definitions, and user documentation.
The three reasons why business use cases are important for System Analysts and
Developers are as follows:
1. Use Case helps in refining/narrowing down and requirement tracking of a user to
introduce a better elastic search algorithm.
2. They help understand the process in simplified manner.
3. A business use case makes it possible to constantly improve the model and avoid
any misuse of the already in-use business model.
Further, there is an explanation as to how the above stated points are important to
System Developers and Analysts. Explanation comes along with the examples and use case
diagrams for better understandings.

6. 4
Point 1
Use Case helps in refining/narrowing down and requirement tracking of
a user to introduce a better elastic search algorithm.
Here we consider an example of e-commerce websites. While e-commerce (EC) is
growing huge, many transactional deals are now being performed through the
Internet. the picture of the marketplace has changed from the traditional one to the
one in which the business model is a complicated, rapidly changing business
strategies, evolving products and smoother services, marketing methods, etc. The
complications have rendered the older approach to defining application requirements
obsolete.
E-commerce websites are required to be multi-functional, having a strong link
to business strategy and incorporate marketing skills. This implies that a business to
customer application shall create value, making aligning application development
projects with critical business strategies.
Even when, several EC application development methods, such as the Web IS
Development Methodology, e-Commerce Development Method, and Internet
Commerce Development Methodology, have been recommended after some time, a not
very many really bolster every one of the attributes of EC applications. These usually
incorporate a conceptual framework that starts with the fabrication of the business
strategy and terminates at the production of a set of graphic tools for modelling
and specifying the requirements of an application.

7. 5
The use-case model aids the developers with a guiding framework for planning
and formulating EC strategies effectively. The approach also addresses multi-
requirement conflict issues and provides a systematic trade-off solution and
requirement analysis for application development. It provides a systemic approach
that makes the eliciting and modelling of EC system requirements easier. It
amalgamates several concepts and methodologies (like Virtual Value Chain, Customer
Decision Process, ECVM, and a goal-acquiring use case model) into a requirement
elicitating process and allows the seamless definition of customized requirements
from EC strategies. Second, it takes both strategic and technical aspects into account,
and not only provides e-business managers with a framework to help them develop
differentiated EC strategies and gain a competitive advantage, but also helps system
designers to translate the core e-services into critical system requirements.
A use case can be viewed as a process that is associated with a maintained, goal
achieved, optimized, or impaired by the use case. The relationships between goals
and use cases can be analyzed by investigating the effects of the use cases on the
goals. According to Lee et al., five predicates can be defined to characterize the
relationships between use cases and goals: satisfied, satisfiable, denied, deniable, and
independent. A goal will be satisfied or denied, depending on whether it can be
achieved or have to be abandoned. The predicates satisfiable and deniable will be
used to describe a goal that can be satisfied or denied to some degree. The
predicate independent is used to describe a goal that will not be affected by any
designated use case.

8. 6
Let’s consider an e-commerce website. Every e-commerce website has a search bar
which allows user to search their product with the website across different categories. Now
after making a search user might want to refine the search to get better results. This kind of
search is called ‘Advanced search’. The user might want to see results that are relevant to
him considering his previous searches or see the results that do not contain adult rated
content/product.
Use Case Model
Customers
<<extend>>
Legend: àActor àuse case àgoal
Easy to find
Products
Strict to filter adult rated
results
Effective to find products
relevant to previous
searches or similar to
fuzzy criteria
Efficient to find products
for auction on line
Advanced to find
products based on
criteria
Keyword based
Search
Safe SearchFuzzy Search
Online Auction
Search
Advanced
Search

9. 7
Point 2
Use cases help understand the process in simplified manner.
Recruiters are usually worried with the notion that they lack adequate tools to
place all the candidates in the right jobs as quickly as possible. Since the results of
matching the resume keywords with the job descriptions are no longer satisfactory,
recruiters are employing new approaches to using big data for recruitments, allowing
them to simplify and fasten the placement process while automating it, like never
before.
Recruitments from big data platforms can dig from internal databases and
provide an all round details of the candidate, such as educational background,
experience, skill set, job titles, certifications, geographic details, and anything else
that the recruiters might need then compare them to company's past hiring
experiences, successful candidates, salaries, etc. to pick the "best match".
The management of human talent and achievements, effectively, is the key to
the market value. Human Resources (HR) departments that respect this philosophy
and are undergoing a transformation from being the record rooms of the personnel-
related matters to the roles of business strategies and human capital managers.
Hence, the employee recruitment and selection is a critical matter, so as to
ease the transformation of the resource and development sector. Research shows
that when high performance HR practices, including recruiting and selection systems,
are designed to be aligned with corporate goals, and employees who can help

10. 8
achieve these goals are hired, the company’s financial performance can be positively
influenced.
The most important dimensions of employee selection systems is efficiency.
Efficiency can be magnified with automation. Compared to traditional hiring models
(paper-based, multistaged, costly) automation should bring immediate value to the
organization. Automation frees human resource professional’s time so they can
provide more strategic direction to the company. It reduces the time they spend on
routine administrative tasks. Automation also reduces operating costs. For
example, Web-based hiring processes allow launching a job requisition with a single
mouse click. Once hired, employee data can be electronically integrated into a
company’s human resource information system (HRIS), further reducing time,
paperwork, data input errors, and operating expenses. Thus, automation can offer
considerable advantages over traditional recruiting, screening, and hiring processes.

11. 9
Point 3
A business use case makes it possible to constantly improve the model
and avoid any misuse of the already in-use business model.
Use case models are often employed for better technical support management. This
has become easier via the registration and direction of the support requirement and
assessment of the issue over online system rather than engaging valuable manpower behind
it. The systems very smartly, incorporate a filtration for the embezzlement of the service
requests too.
For example, a customer registering a complaint regarding malfunction of a laptop.
The complaint, in the form of an assistance request is submitted to the database of the
technical support department of the company and a ticket is generated. This request is
attended by the system analytics log and is attempted to be resolved via artificial assistance.
If the service provided is not adequate or satisfactory in order to resolve the issue,
allocation of an expert is carried out. The IT sector of the company communicates with the
customer on the basis of the generated service request listed under the assigned ticket
number, and the issue is attended to. If the assigned agent towards the ticket is unable to
resolve the problem then, the problem is escalated to his senior.
Here the misuse or the negative use of authority can be made like for example, if the
agent deletes the ticket or he edits the ticket without solving the problem. The use case
model can be made here for to revoke the access to the agent to edit or delete the ticket or
mark it resolved unless the problem is actually resolved.

12. 10

13. 11
THE DANGERS OF MISUSING USE CASES
Because of their many important advantages and extreme popularity, use cases have
become a fundamental part of object technology and have been incorporated in one form or
another into most major object-oriented development methods. In the rush to jump onto the
use case bandwagon, use cases have been perceived by some as either a panacea or as an end
in-and-of themselves. Unfortunately, this has often led to the uncritical acceptance of use
cases without any examination of their numerous limitations and ample opportunities they
offer for misuse. The following provides an overview of the major risks associated with use
cases:
· Use cases are defined in terms of interactions between one or more actors and the
system to be developed. However, all systems do not have actors and systems may
include signification functionality that is not a reaction to an actor's input. Embedded
systems may perform major control functions without significant user input.
Concurrent objects and classes need not passively wait for incoming messages to
react. They may instead proactively make decisions based on results derived from
polling terminators. Traditional use case modeling seems less appropriate for such
applications.
· Another major problem with use case modeling is the lack of formality in the
definitions of the terms use case, actor, extends, and uses. Similarly, the specification
of individual use cases in natural languages such as English provides ample room for
miscommunication and misunderstandings. Use cases provide a much less formal
specification of their instances (i.e., individual usage scenarios) than do classes of
objects. Whereas the inheritance relationship between classes of objects is well-
defined and has been automated by compilers, the 'inheritance' and 'delegation'

14. 12
relationships provided by extends and uses associations are much less well defined.
While everything may seem clear that the highest level of abstraction, the translation
of use cases into design and code at lower levels of abstraction is based on informal
human understanding of what must be done. This also causes problems when it comes
to using use cases for the specification of acceptance tests, because the criteria for
passing those tests may not be adequately defined.
· Another major problem corresponds to the archetypical subsystem architecture that
can result from blindly using use cases. Several examples in books and papers have
consisted of a single functional control object representing the logic of an individual
use case and several dumb entity objects controlled by the controller object. They also
may include an interface object for each actor involved with the use case. Such
architecture typically exhibits poor encapsulation, excessive coupling, and an
inadequate distribution of the intelligence of the application among the classes. Such
architectures are less maintainable than more object-oriented architectures.
· Finally, the use of use cases as the foundation of incremental development and project
tracking has its limitations. Basing increments on functional use cases threatens to
cause the same problems with basing builds on major system functions. Instead of
building complete classes, developers will tend to create partial variants that require
more iteration from build to build than is necessary. In turn, this will unnecessarily
increase the maintenance costs of inheritance hierarchies. Basing earned value on the
number of use cases implemented may be misleading because all use cases may not
be of equal value to the user and because of the previously mentioned problems due to
functional decomposition and the scattering of partial variant objects and classes
among use cases.

15. 13
CONCLUSION
What at that point should developers do? Use cases unmistakably offer numerous
critical advantages and are capable weapons that most likely ought to be in the arms
stockpile of all product examiners, creators, and analyzers. Shockingly anyway, they are
practical as opposed to questioning situated and can essentially trade off the advantages of
protest innovation if aimlessly added at to the question arranged advancement process.
Luckily, the dangers related to use case displaying can be relieved through information,
preparing, and maintaining a strategic distance from an overeager acknowledgment.
Use cases ought to be just a single of a few methods for catching user necessities.
The model of items, classes, and their semantic connections ought to be reliable with,
however not completely determined by, the use cases. Creators should be careful with and
limit dissipating the highlights of a use case's items and classes, and they should practice
incredible care to evade the production of incomplete, excess variations of classes,
particularly on huge ventures including different forms and discharges.

16. 14
BIBLIOGRAPHY
1. [1] Ivar Jacobson, Object-Oriented Development in an Industrial
Environment, Proceedings of OOPSLA´87, SIGPLAN Notices, Vol. 22, No. 12, pages
183-191, 1987.
2. [2] Ivar Jacobson, Magnus Christerson, Patrik Jonsson, and Gunnar
Övergaard, Object-Oriented Software Engineering: A Use Case Driven Approach,
Addison-Wesley, Wokingham, England, 1992.
3. [3] Ivar Jacobson, Maria Ericsson, and Agneta Jacobson, The Object Advantage:
Business Process Re-engineering with Object Technology, Addison-Wesley,
Wokingham, England, 1995.
4. [4] James Rumbaugh, "Getting Started: Using Use Cases to Capture
Requirements," Journal of Object-Oriented Programming (JOOP), SIGS Publications,
Vol. 7, No. 5, New York, New York, September 1994, pages 8-12.
5. Mastering the requirements process: getting requirements right by Suzanne.
Robertson, James Robertson
6. The e-commerce value matrix and use case model: A goal-driven methodology for
eliciting B2C application requirements by Tzyh-Lih Hsia,, Jen-Her Wub and Eldon Y. Li
7. The use of an automated employment recruiting and screening system for
temporary professional employees by Patrick Buckley, Kathleen Minette, Dennis Joy,
and Jeff Michaels
8. Websites: Science Direct, IEEE Explore and Stevens library