UML Weekend Crash Course™ - To Parent Directory

300
Sunday Afternoon
Traditional Wired Device
Visual
Basic Client
Web Server
Web
Browser
Upload
Appointments
Servlet
JavaBeans
Database
Server
Wireless Device
like Cell Phone
Micro Web
Browser
WAP Gateway
Wired Web
Controller
Servlet
Wireless
Interface
Controller Servlet
JSP pages
with HTML
content
JSP pages
with WML
content
Figure 29-4
UML Deployment diagram, Visual Basic client
Detailed Design
The design team has now completed the high-level architectural design of the system. They
have chosen the technologies that they will be using and the organization of those technologies
required to solve the business problem. In the detailed design, they will specify how
each individual part of the system will be implemented. The Component and Deployment diagrams
illustrate how the different Web technologies will be organized. In the detailed design,
the component and deployment diagrams will be used less and the Class, Object, Sequence,
and Collaboration diagrams will tend to be used more.
Querying appointments and contacts
In the detailed design phase, the designers want to create a roadmap for the programmers,
specifying how the browsers, servlets, JSP pages, JavaBeans, and databases will work
together to allow customers to query for appointments and contacts. Because there isn’t
space or time to explore the entire detailed design, we will focus on the design of appointment
querying by customers using traditional wired Web clients.
The development team first makes the Collaboration diagram in Figure 29-5 to show
how the user will move from one Web page to another. This particular diagram is not
meant to show the inner workings of the system. Because it only shows what the user will
see, this diagram will only contain JSP pages. The diagram shows that the user must use
the Login JSP page to log in prior to accessing the AppointmentQueryForm JSP page. This
form will allow the user to enter criteria for the appointments he wants to search for.
When he submits the query form, if there are matching results, he will be sent to the
AppointmentQueryResults JSP page, which will display those results. If there are no
matching results, he will be sent to the No Appointments JSP page, which will inform
him that there were no matches to his query.