In BluePrint # 4 (access
Http://www.sybase.com/blueprint For the electronic version of the previous problem, we explore five UML charts: use case diagrams, sequence diagrams, event diagrams, class diagrams, and component maps, they can help you master your system Demand, design its physical structure and expected function, and convert to code. We can also use another 4 UML diagrams to further streamline the definitions contained in the top 5 drawings, or define the system from a completely different angle.
These charts (object diagrams, collaboration diagrams, state diagrams, deployment charts) form all charts in PowerDesigner together and can be used in PowerDesigner9.5.
Object Diagram:
Like class diagrams, the object map is also a UML static structural diagram; it defines the physical elements having the system at a given time without specific consideration of the dynamic activity of the system. It corresponds to the code, but unlike class diagrams, we discuss the specific classifier now, not the classifier definition. Describe the object diagram as class instant diagram may be the most appropriate.
The main purpose of the object map is to analyze. There is an uncertain constraint between classes that cannot be represented in class diagrams. We will use the object map to record these constraints. Moreover, when we view the specific class instance examples managed to clarify the interaction relationship between these elements, the object map also allows us to define specific "What if" scenes.
The following is an initiator for OO modeling: The classifier is an abstract object structure definition. The classifier can tell us what type of data (attribute / member representing data elements) and the classifier have the ability (operation / method representing the behavior of the object). An example is a specific classifier example. Assume that a class named Customer is defined, which has a Name property. An instance of class Customer "Jane Doe" is a customer named "Jane Doe". Examples typically have a richer meaning than classifiers, because the classifier represents an overview of a certain level. Several instances or examples of collected a classifier may help you understand their use and use it better.
Therefore, the object map is the specific form of the class diagram, indicating a class instance sample, and the key value and relationship are displayed. For example, the CustomerBean class has the following customer instance: the customer's ID is 52271, named "John Doe". The customer instance is related to three order instances (three orders), and the order numbers are 122047, 122103, and 122399, respectively.
Collaboration Diagram:
Collaborative drawings and sequence diagrams are very similar. In fact, the sequence diagrams and collaboration graphs can be used effectively, and can be easily converted. It is different from the way users who are reading and understanding. The sequence diagram has a good hierarchy and is constructed around the time. Collaborative drawings are mainly constructed around the object structure. By numbered the message in the figure, the order of the message can be represented. When using this method, even if the structure of the figure is not based on time, the timing relationship will also be held.
Collaboration maps use the interaction between elements or objects in the system, indicating the dynamics of the system, that is, the manifestation in a period of time. It adds to the class diagram and object maps by means of a static structure of the system, but is not based on the structure-based relationship, but is transmitted between the interaction between system objects.
The static model can also be tested in the conceptual level when constructing a collaboration map. A class instance is defined in the class diagram, and the interaction between these class instances defines a specific usage scheme and internal communication that will occur between these elements. We can also use other roles to represent the external rolers and internal users of the system, such as examples.
For example, we can build an order input system for use by customers and sales representatives. Customers interact with the system by creating new orders. The order object is dialogue between the sales object, which is represented by the link message, in which case only two messages: one is a order request from the Orders class, one is an order confirmation from the Sales class. There is no limit to the number of messages on a link. The dialogue we discussed here starts with a order request, and then confirming the order. applicability
Collaboration map is especially important for designers because it clarifies the role of the object. You can construct a collaboration map before the sequence diagram (if you plan to construct these two charts), but is usually the structure of the collaboration method after completing the class diagram to illustrate the interaction between the objects exported from the class. One or more collaboration maps can be used to implement one case, or the complex behavior can be divided into multiple logistic sub-behaviors.
Statechart Diagram:
The state diagram (also known as a state machine) describes the behavior when a particular class or component is constantly changing throughout its lifecycle. The figure shows what triggers the conversion from one state to another, and which operations are called on this class to provide behavior or triggering this conversion. For example, an order is in an initial state when it is created. After the customer confirms the order correctly, the order will enter the confirmation status. After delivery, the order needs to enter the delivery status from the confirmation status.
Therefore, whenever a class has different available options (different valid behavior) at different stages of its lifecycle (different valid behavior), you can use the status map to model these rules and conditions. Each stage in the lifecycle is a state of the object, and each changed state is a conversion from one state to another. You can switch from a certain state to any plurality of other states as needed, or you can enter a state from a plurality of states.
Substitudinal map
To keep the status diagram simple and easy to read, you may find that one or more states defined can actually involve more complex behavior, so that it can be defined as a state diagram. At this point, better practice is to decompose this separate state into multiple sub-states, thereby form a more complex internal behavior of the parent status to define a more complex internal behavior of the parent state. .
Deployment Diagram:
Deployment diagrams can help us determine all code elements in the storage location in the server, workstation, and database. Some nodes need to rely on hardware or software boxes to run some business logic. These nodes interact with how we developed multiple computers and systems interact and integrate. The node contains an instance that will be deployed to a database, an application, or a web server.
The deployment drawing is used to actually deploy components into the server. By defining locations where you want to run, we can quickly map, deploy, and manage business logic or database-side server logic between client applications and application server-side components. The following is a 1: 1 model of the physical architecture to be managed.
For example, suppose we have decided to implement two Enterprise Java Beans and run them on the application server. The figure below shows a single node and two components within the node (one component each EJB). We can see that Employeebean depends on CustomerBean in the same application server.
in conclusion
When we use an example example, a sequence diagram, an active diagram, a class diagram, a basic UML modeling, we will need some other tools to define more information about certain elements in the system. We may want to use an exact example to represent the structure of the object in the object map, or more understanding of the class of a class having a plurality of complex states inside therein by means of a state diagram. We need to use a collaborative map from structural angles rather than from a time angle to visit the interaction between system components. Finally, you also need to use deployment diagrams to display the location of all system components in the physical hardware or server in the run environment, so that the usage method of the distributed architecture is more detailed.
