UML Weekend Crash Course™ - To Parent Directory

SESSION
28
Analysis and Architectural
Design of a Web Application
Session Checklist
✔ Explaining how requirements gathering and analysis are done
in a Web system
✔ Explaining the Model View Controller design principle
✔ Illustrating how the View and Controller can be separated
in a Java Web application
✔ Explaining and illustrating how UML can be used in the analysis and
architectural design of a Web system
Congratulations! You have almost completed your UML crash course. This weekend, you
have learned an incredible spectrum of techniques and strategies for using the UML to
model and develop applications. Sessions 28 and 29 will demonstrate how to model a
Web application from start to finish. You’ll see that the process of modeling a Web application
is primarily the same process used to model any application, but I will also point out
some special tricks and techniques that you can apply to Web modeling with the UML.
The Friendly Reminder Case Study
Sessions 28 and 29 will consider the development of a project that is a typical Web application.
In this project, your contracting firm is asked by a software company to develop a Web
component for its existing Visual Basic application, which is called Friendly Reminder. The
client’s initial project specification states that the current Friendly Reminder system allows
users to track their appointments and contacts by allowing them to