Hybrid case modeling [4]: System cases and Business Cases

What is the difference between the so-called "Business Case" and "system case?

First, the business and system use cases are relative.

Second, the business and system use cases are studied differently.

Take the classic bank as an example.

I open an account at a bank: I have a blank account opening application form in front of the counter and filled in my information, then, pass my ID card and the filled application form to the Clerk (this saves the trouble of waiting in queue for dozens of minutes and so on ...). The clerk took a list and entered my information into their system. After a long time, the password inner in front of me prompts me to set the account password twice. Then, he handed out the printed information list and asked me to sign for confirmation. I signed the paper and handed it to him. He gave me several stamps, handed me my passbook, ID card and ticket, and told me I had done it.

This is a very simple and common service for banks. It can also be called a function for banks. In fact, banks also have many other "functions", such as saving money, taking money, and report loss. At this time, we actually think of banks as a "system" that provides many "functions ".

At the same time, in this process, the clerk has been operating the bank's software system, the process may be like this:

The first choice is the account opening function. The software system requires the clerk to input my information and select the account opening type (I wrote the current account on the application form ); the software system may check whether my ID card number is legal; the software system generates a bank account for me; the software system will ask the clerk if I want a password (I indicated the need on the account opening application form ), so the software system prompts me to set the password; the software system prints out my passbook.

The Bank's software system provides many functions for clerks, including saving money, obtaining money, and report loss in addition to opening an account. However, these functions are provided by the Bank's software system to bank staff.

In this way, based on the above two processes, we are actually studying the "functions" at two levels ". The first level is the functions provided by the bank to the customers of the bank; the second level is the functions provided by the software system to the bank staff. As shown in:

When we model the banking business, we take the banking as a whole to study what services the bank will provide to customers. In this caseThe Study Targets banks..

 

 

When we model a bank's software system, we take the software system as a whole to study what functions it needs to provide to bank staff. In this caseThe research target is the banking software system..

In this way, the former is called the "Business Case model" for the sake of differentiation, and the latter is called the "system case model ".

There is no difference between business and system use cases in the use case technology, such as the relationship between use cases and the description of use cases.

There is also a concept in the business model, namely, "business worker )". Business work represents the role of the person, software, or hardware that implements the business. For example, in the "Account Opening" business case of a bank, the bank clerk, the software system, and the printer that prints the passbook can all be regarded as "business workers ".

Why business modeling? See "Use Case" and "Consequences" (to be released ).