[Software Engineering] from the relationship between outline design and detailed design to the presentation of Business Use Cases and metadata use cases

The following is a discussion of dialogs from the "Theory and deduction" group.

 

2013-01-31

BEIJING-firespider male 13:28:45

Teacher qingrun asked a question: what is the relationship between software architecture design and software outline design?

Qingrun 14:20:25

The outline design extends from the demand. The architecture design focuses on the overall logical implementation of the system. Different perspectives.

BEIJING-firespider male 14:27:29

Oh, that is to say, does the summary design not involve system implementation?

Qingrun 14:27:54

The outline design is implemented by modules, and the architecture design needs to consider all modules.

Qingrun 14:28:24

The starting point is different, and the scope of consideration is also different. In addition, the outline design is generally further refined by requirements. In my book, it is called the semi-digital design.

Qingrun 14:28:32

Detailed design is a completely digital design.

Qingrun 14:28:54

That is to say, the architecture design starts to take effect in the outline design, but it takes effect only in the detailed design.

BEIJING-firespider male 14:29:16

Oh.

Qingrun 14:29:48

If you read the corresponding part of my book, you can see the difference between the outline and the detailed design, which is obvious and clear.

BEIJING-firespider male 14:30:29

Can this be said: The Outline Design corresponds to the case analysis phase, and has nothing to do with the system implementation, so it has nothing to do with the architecture design. The detailed design phase corresponds to the case design phase, because it is related to implementation, so it is related to the architecture.

Qingrun 14:31:02

This statement is incorrect.

Qingrun 14:31:13

There is no use case design phase.

Qingrun 14:31:26

The design for UC is promoted from the outline design to the detailed design.

Qingrun 14:32:03

Design overview. Generally, it is a simple MVC division. During detailed design, some detailed design patterns and application of specific design methods will be added.

BEIJING-firespider male 14:33:49

How can we change the case design to case implementation?

Qingrun 14:36:24

I have never heard of it.

Qingrun 14:36:44

Is the use case realization relation?

Qingrun 14:37:57

In this case, I think this is the implementation relationship between business use cases and system use cases.

That is to say, the business use cases that need to be implemented in this development will be converted to the corresponding system use cases and saved. Other UC instances will be planned for future development or not implemented.

BEIJING-firespider male 14:37:58

I am also confused. The System Analysis Design in many books is based on system use cases. The existing case analysis is then the design. Is it difficult to design the case?

Qingrun 14:38:39

The design must be for use cases, so many books have crossed this section, because they do not know.

Qingrun 14:39:00

I will give you a detailed description of this in the demand phase in my book.

BEIJING-firespider male 14:39:19

Okay.

BEIJING-firespider male 14:39:33

I forgot to bring your book today, so I cannot see it.

Qingrun 14:42:16

Qingrun 14:42:34

I noticed that the content in this section is not introduced in the book, but it is the content mentioned in the training.

BEIJING-firespider male 14:42:48

Hmm

Qingrun 14:43:02

There is a processing process between business use cases and system-implemented use cases. This process determines which users directly implement the requirements.

Qingrun 14:43:19

The relationship between BUC and UC is M: 1 or 1: M.

BEIJING-firespider male 14:43:29

Hmm

Qingrun 14:43:37

There is basically no M: n relationship, that is, it is not recommended that the BUC splitting problem exist.

Qingrun 14:44:39

Qingrun 14:44:48

This figure basically covers these situations.

Qingrun 14:45:08

The above error indicates that the relationship between BUC and UC is M: 1.

BEIJING-firespider male 14:46:51

Oh, yes.

Qingrun 14:47:28

This figure is a diagram of training for the general parameters in. It can be used because it does not involve confidential information.

BEIJING-firespider male 14:48:56

I think there are still misunderstandings in this aspect.

Qingrun 14:49:06

Well.

BEIJING-firespider male 14:56:13

This ing between BUC and UC should refer to the BUC that contains the sub-BUC, right. Because a BUC has a large granularity and contains many sub-BUC buckets, it may be displayed because the sub-BUC maps to multiple UC instances: One BUC corresponds to multiple UC instances.

Qingrun 14:57:00

In fact, BUC can be used as a metadata case.

BEIJING-firespider male 14:57:13

Hmm

Qingrun 14:57:17

It is very fine, so it cannot be further divided, and then combined to form the actual UC.

BEIJING-firespider male 15:05:52

This is the workflow of the leave business:

BEIJING-firespider male 15:07:18

If leave is expressed as a business use case, the following processing nodes are also counted as business use cases. This will appear: The Business Use Cases section contains four sub-Business Use Cases: "fill in the leave application form", "department manager approval", "General Manager approval", and "Administrative Archive.

BEIJING-firespider male 15:07:56

You can directly create system use cases from "fill in Leave Application Form", "department manager approval", "General Manager approval", and "Administrative Archive" to obtain system use cases: fill in the leave application form, department manager approval, General Manager approval, and administrative archive ".

BEIJING-firespider male 15:08:33

At the same time, you can directly create a system use case for leave. In this case, the system use cases include four sub-system use cases: "fill in the leave application form", "department manager approval", "General Manager approval", and "Administrative Archive.

BEIJING-firespider male 15:14:32

Is that true?

BEIJING-firespider male 15:14:28

BEIJING-firespider male 15:15:46

BEIJING-firespider male 15:15:55

Wrong picture.

BEIJING-firespider male 15:16:10

BEIJING-firespider male 15:16:38

Can the relationship between leave system use cases and these business use cases be considered as: Does multiple business use cases correspond to one system use case?

BEIJING-firespider male 15:16:55

BEIJING-firespider male 15:17:07

Can a system use case correspond to a business use case?

Qingrun 15:57:34

For this question, you should take a look at the definition and analysis of the concept of the metacase.

Qingrun 15:58:01

Can all use cases under the business case of leave of absence be split? If yes, you can continue the split until it becomes a metabusiness use case.

Qingrun 15:58:36

Use cases must be reasonable, that is, they must be a combination of multiple use cases.

Meta-Business Use Cases and meta-use cases may have a relationship. At present, we need to perform a thorough logical analysis to determine whether the relationship is always.

BEIJING-firespider male 16:01:49

I think it is difficult for me to use the metadatabase in combination with the interface prototype to know how to use the brain to deduce it. Sometimes, just a representation can be determined at once.

Qingrun 16:02:14

This is completely unnecessary.

Qingrun 16:02:27

The meta-use case was created to measure the use case size.

Qingrun 16:03:01

That is, it is used to calculate the complexity of Use Cases and evaluate the development workload. Later, I extended it to the complete implementation details of the requirements.

BEIJING-firespider male 16:07:54

"Meta-Business Use Cases and meta-use cases may have a relationship ", if multiple "meta-Business Use Cases" correspond to a "meta-Business Use Case", do you think that "meta-Business Use Cases" need to be further split?

Qingrun 16:08:18

Is it reversed? Haha

Qingrun 16:08:26

It should be a metadata case that needs further splitting.

BEIJING-firespider male 16:08:35

Oh, yes, huh, huh.

Qingrun 16:08:38

In general, the meta-Business Use Case is.

Qingrun 16:08:55

In addition, the metadatabase is pushed to the metadatabase. This process does not need to be merged.

BEIJING-firespider male 16:08:56

Hmm

Qingrun 16:09:17

However, when the system is not so complex, it does not need to be too many use cases. You can use the meta-Business Use Cases to map them into use cases.

Qingrun 16:09:25

There is no need to take several steps to perform simple operations.

Qingrun 16:09:36

Otherwise, you will complicate yourself.

Qingrun 16:10:00

Therefore, in general, this assumption does not exist. It is only possible that the meta-business use cases are too complex and not minimized. Therefore, splitting should be considered.

Qingrun 16:10:30

That is to say, if there is a subitem activity in the flowchart, you need to consider the splitting of the activity to form more meta-Business Use Cases. Otherwise, you do not need to consider it.

BEIJING-firespider male 16:12:44

As shown in the preceding figure, the Business Use Cases "document writing" and "sending email" may be built-in in system implementation, that is, after "document writing" is completed and submitted, an email is automatically sent. In this case, multiple business use cases correspond to one system use case.

Qingrun 16:13:15

Yes. Multiple business use cases correspond to one system use case, which is very common.

Qingrun 16:13:35

Business Use Cases can be discussed very carefully, or even directly at the level of the use case.

BEIJING-firespider male 16:13:43

Hmm

BEIJING-firespider male 16:14:27

It seems that you need to think about business informatization.

Qingrun 16:14:46

Haha.

BEIJING-firespider male 16:14:46

Different people may make different analyses.

Qingrun 16:15:01

Which can be separated, and which do not need to be implemented by the system.

BEIJING-firespider male 16:29:56

I think this involves business restructuring.

Qingrun 16:30:15

It may also be business restructuring or unclear business research.

BEIJING-firespider male 16:30:32

To map a business case to multiple system cases, it should involve business restructuring.

BEIJING-firespider male 16:30:39

Hmm

Qingrun 16:30:56

In fact, about 1/3 of the responsibility for changing user requirements lies with programmers because they do not understand user services or do not have clear research results.

BEIJING-firespider male 16:32:42

Well, it is very likely.

Qingrun 16:33:13

Not very likely. It's a fact. Programmers are not willing to admit that they are involved.

Qingrun 16:33:21

We are not God, and not all needs can be understood.

Qingrun 16:33:29

Process is required and time is required.

Qingrun 16:33:38

Understanding errors is inevitable.

BEIJING-firespider male 16:33:42

However, for example, in our current oil pipeline inspection, the original business is that the pipeline administrator buried a paper note for the inspection staff and asked the inspection staff to find it as an assessment indicator. However, after the GPS patrol, the business method has completely changed.

Qingrun 16:33:52

However, we are in the industry and will inevitably want to mask ourselves.

BEIJING-firespider male 16:33:55

Although the business objectives are consistent, the business implementation methods are completely different.

BEIJING-firespider male 16:34:06

At this time, the business node actually needs to be reconstructed.

Qingrun 16:34:17

This is a business reform, that is another thing.

BEIJING-firespider male 16:34:22

Hmm

BEIJING-firespider male 16:54:23

Thank you for your patience. Qingrun 16:54:35

You're welcome.