One: The core view of UML---> If UML is a language, the participants in the previous chapter are the basic words of UML, then the view is the grammar. UML organizes the base elements together in a view to form meaningful sentences. The features of the--->uml visualization are represented by various views, each showing the same software product from different angles. Explain exactly what the software is going to look like. ---> Static view: On the one hand we need to describe the structural characteristics of the system, and the structure determines what the system can do. Structural properties are expressed in a static view. ---> Dynamic view: On the other hand, we need to describe the runtime behavior of the system, which determines what the system does. Behavioral features are expressed in a dynamic view.Two: Static view of UML---> Static view describes only the static structure of a thing, not its dynamic behavior. ---> Static views: Use case diagrams, Class diagrams, Package diagramsThree: Use case diagram---> Use case diagrams: Use actors and use cases as basic elements. The functional requirements of the system are presented in different perspectives. ---> Use case diagrams: Use actors and use cases as basic elements. The functional requirements of the system are presented in different perspectives. ---> Business use Case view.---> Business use case implementation View---> Conceptual use Case View---> System use Case View---> System use case implementation view
Four: Business use case view---> Business use case view uses business leads and business use cases to demonstrate the results of business modeling. In most cases, the business use case view needs to be presented from the business lead and business module two perspectives. --->[business lead perspective]: To show what business use cases are being used by business actors to achieve business goals. This perspective helps to verify that the business goals are complete and that there are no missing business use cases found. --->[business module Perspective]: to showcase business objectives in the business area, the protagonists and business use cases that are involved in achieving this business goal are presented in this view. V: Business use case implementation View---> Business use case implementation view shows what the business use cases are implemented. ---> Generally there is only one way to implement a business use case, so it is not necessary to draw a view of the business use case implementation, a bit superfluous, it is recommended to draw---> in special cases a business use case may have multiple implementations, which can clearly express the business use case. For example, borrow books in the library, can borrow through the counter, also can borrow through the network. VI: Conceptual use case View---> Conceptual use Case view is used to present key conceptual use cases that have been analyzed and decomposed in business use cases,---> concept use cases to mark the relationship between it and business use cases. In general, these relationships are extended, inclusive, and refined. ---> For conceptual use case views, it is generally presented as a unit of business use cases. Closely related business use cases, or they can be put together to show the conceptual use case view. ---> Conceptual use Case view is not required, and if a business use case is a complex business, drawing a conceptual use case view can help refine and more accurately understand business use cases. Seven: System use case view---> System use Case view shows the system scope, showing the system use cases that are obtained after the analysis of the business use cases---> Frankly, is the whole system of participants and participants of the use case, drawn in a diagram eight: System use case implementation View---> by use case as a unit, the implementation of the way to show it. ---> Draw out the implementation of all the use cases of the whole system.
< 13 business use case diagram of >UML core view static view
