tailieunhanh - business modeling with uml business patterns at work phần 9

Ví dụ, hậu cần trong một công ty bao gồm cả việc vận chuyển thực tế hàng hoá và thông tin về những hàng hóa và vận chuyển của họ. Hàng hoá có các thuộc tính như màu sắc, kích thước, và hình thức trong khi các thông tin về hàng hóa có thuộc tính như địa chỉ giao hàng, | Figure Top-level diagram of the logical view showing the packages and their dependencies in the system. This is a class diagram which shows only packages UML does not have a specific diagram for packages . Figure A deployment diagram showing the physical structure of the hardware nodes and their connections. The top uses standard UML symbols the others have special icons for the different node stereotypes. A tool should be able to switch between both of these representations. Figure shows the top-level diagram for the logical view with a number of packages and their dependencies to each other. In contrast Figure shows the deployment view of the system with the nodes computers and devices in the system and their connections to each other. It is also possible to show the executable components allocated to each of the nodes by drawing components inside the nodes but that hasn t been done in this example. The figure shows the same diagram twice in the top figure the diagram uses standard UML symbols in the bottom figure the diagram uses special icons attached to the different stereotypes such as PC Printer and Server. None of these stereotypes is standard in UML but all can be used to get special icons for the different node types thus making the deployment diagram more like a normal system diagram that has been hand-drawn with a drawing tool. The second picture uses the correct set of stereotypes and thus adheres to the UML specification. Using the Business Architecture to Define the Software Architecture Transferring the information in the business model to the software model is not a simple or automatic process. Unfortunately there isn t a one-to-one mapping for this process and there is no simple algorithm to translate the business model into a software model. They are two different models with different purposes. The business model describes a business or a specific part of a business and not all parts of the business transfer into the software