[Full modeling] relationship between business modeling, use case models, and Requirement Specification

BEIJING-firespider male 16:45:13

Ask qingrun: "Business modeling" is followed by "usecase model" and "usecase description" in the book, while "Business modeling" is used to output the "requirement specification". Is there no use case diagram in the requirement specification?

Qingrun 16:46:10

The business use case diagram is provided in this requirement specification.

In addition, the specification is not required.

The Requirement Specification is provided here only in concert with conventional documents.

In actual development, this manual is useless at all. It will inevitably be eliminated in the future.

Qingrun 16:47:27

Finally, we submit a model file to the user, which contains all the code documents and materials, including system deployment information.

BEIJING-firespider male 16:47:39

Well, I don't think it is useful either. Since the whole process of modeling is complete, this is just the form of text output of the model.

Clear water 16:48:14

Is there a Business Use Case in the requirement specification? Is it necessary to determine the business model with the user for business use cases?

Qingrun 16:48:19

In other words, this document must be generated here to help users who have not yet modeled the country or the world, or who have a sufficient understanding of the model.

The requirement specification does not need to be generated.

The business case model is required.

BEIJING-firespider male 16:48:45

If you do not consider the requirement specification, it seems that only the "Business Process" is generated in the business modeling phase, and the "usecase model" identifies the actor and usecase.

Qingrun 16:49:11

Business usecase is available in the business modeling stage.

Clear water 16:49:13

Oh, in full-process modeling, can the Requirement Specification be a snapshot of a certain stage of the model be understood in this way?

Qingrun 16:49:32

There is a ing between BUC and UC. The model provided in my book has a corresponding part. For more information, see.

This part was created by me and has not been mentioned in up or RUP.

The Requirement Specification is a snapshot of the business case model.

BEIJING-firespider male 16:50:01

Is business usecase described by "user" and "system?

Qingrun 16:50:27

It is basically correct.

For embedded systems, there may be some differences.

BEIJING-firespider male 16:50:59

Which of the following concepts is involved: "Business Case Model" and "Use Case Model?

Qingrun 16:51:09

There are also some special systems, such as time triggers or some type of streamer, which may also be somewhat different.

For the development of a large business system, you need to consider BUC and UC

BEIJING-firespider male 16:51:35

Is "user" and "system" described in business usecase?

Qingrun 16:51:42

For general systems, I do not recommend building a BUC because it is too complicated.

Qingrun 16:50:27

It is basically correct.

For embedded systems, there may be some differences.

Clear water 16:51:50

Hmm

Qingrun 16:52:07

Most systems can directly build ucmodel.

BEIJING-firespider male 16:53:53

However, I see that "Business modeling" draws a "Funding flowchart for a company's projects", which is described by "Lane activity diagram". Each Lane is a "participant ". There is no concept of "system.

Qingrun 16:54:35

No, it's the BUC process. I suggest you use the dashboard or status activity diagram to draw the detailed implementation of UC.