UML Basic Architecture Modeling-general class modeling technology (III)

Zookeeper

Modeling nonsoftware things

Build a non-software thing Model

 

Sometimes, the things you model may never have an analog in software. for example, the people who send invoices and the robots that automatically package orders for shipping from a warehouse might be a part of the workflow you model in a retail system. your application might not have any software that represents them (unlike MERs in the example above, since your system will probably want to maintain information about them ).

Sometimes, the thing model you build may never be simulated by software. for example, the invoice sender and machines that automatically package and ship the purchased goods from the warehouse may be part of the workflow in the retail system model. your applications may not need any software to express them (unlike the customers in the above example, your system may want to maintain their information ).

 

To model nonsoftware things,

Modeling non-software things,

 

1. model the thing you are using acting as a class.

Modeling abstract things in the form of Classes

 

2. If you want to distinguish these things from the UML's defined building blocks, create a new building block by using stereotypes to specify these new semantics and to give a distinctive visual cue.

If you want to distinguish these things from the build modules defined in UML, you can create a new build module by using the model, it is used to describe these new semantics and provide a unique visualized mark.

 

3. If the thing you are modeling is some kind of hardware that itself contains software, consider modeling it as a kind of node as well, so that you can further expand on its structure.

If the model you are building is a kind of hardware with software, you may consider modeling as a node so that you can further expand on the basis of its existing structure.

 

Note: The UML is mainly intended for modeling software-intensive systems, although, in conjunction with textual hardware modeling languages, such as VHDL, the UML can be quite expressive for modeling hardware systems. the OMG has also produced a UML extension called sysml intended for systems modeling.

Note: The main purpose of UML is to build an integrated software system. Although, when combined with a text-based hardware modeling language, such as VHDL, UML can provide a very expressive hardware system for modeling. OMG also generates an extended UML called sysml for system modeling.

 

As figure 4-11 shows, it's perfectly normal to abstract humans (like accountsreceivableagent) and hardware (like robot) as classes, because each represents a set of objects with a common structure and a common behavior.

4-11 shows that it is very standard to abstract people (such as accounting agents) and hardware (such as robots) in the form of classes ), because each of them represents a group of objects with a common structure and behavior.

 

 

UML Basic Architecture Modeling-general class modeling technology (III)