Acceptance of fee-based system cooperation edition for data centers (I) -- Differences Between include and extend

Today, our partner edition project has been accepted. Because we have already worked on a Personal Edition project, it is relatively easy for the partner edition project. There are basically no functional problems, and the code is OK! During the acceptance process, the students primarily asked us questions and answered questions through the acceptance documents and UML diagrams!

The first thing we mentioned is the relationship in the UML diagram. The typical difference is the include and extend:

I personally think there are two types of include relationships: one is to segment several small cases under a rough case, and the other is to include the relationship between these small cases and the rough case, another scenario is to abstract several use cases into one (in fact, they do not exist and are generally used to divide use cases from functions ), the relationships between these use cases and abstract use cases are also inclusive.

The extended relationship is relatively simple. To determine whether two use cases are extended, you only need to determine whether the basic use cases are implemented before implementing the extended use cases. If the answer is yes, the two use cases are extended. Otherwise, the two use cases are not extended. Note that the extended use cases and basic use cases are relatively independent. The extended use cases only provide new functions for the basic use cases. For example, the system allows you to export and print the query results. For a query, whether to export or print the results is the same, and whether to export or print the results is invisible. Export, print, and query are relatively independent, and new behaviors are added to the query;

In addition to the above relationships, there are also associations and inheritance relationships between use cases, which are easy to understand and will not be described here!