System architects and analysts use unified modeling language (UML) deployment diagrams to model the configuration of the hardware and software

System architects and analysts use unified modeling language (UML) deployment diagrams to model the configuration of the hardware and software components of a system and how they will be deployed in a production environment. In other words, deployment diagrams show the system's hardware, the software that is installed on the hardware, and the middleware that is used to integrate the components. These diagrams are very beneficial when modeling multi-tiered applications.

Consider, for example, the architecture of a textbook ordering system that uses a web client for the presentation, a web server for presentation logic, an application server for the application logic, and a database server which stores the data. A single diagram can depict each piece of hardware (represented as a node) and labeled with the software that is executed on that node. In addition, the diagram can indicate the technology that connects the nodes (hardware), such as an http connection. Deployment diagrams are valuable artifacts to communicate to system designers how system components are to be integrated.

Using diagramming software with which you are already familiar (such as a UML modeler, Visio, Powerpoint, etc.), create a deployment diagram that illustrates the connectivity between the system components as explained in the ordering system described above.

At a minimum, your diagram should include nodes for a client, web server, application server, and a data server. In addition, include software components (a COTS package, a DBMS, and a web browser) and place them on the appropriate node. Depict and specify the middleware technologies that integrate the various nodes.

Then, in a 2-3 page paper, explain your diagram and justify your integration choices.