UML Weekend Crash Course⢠- To Parent Directory
UML Weekend Crash Course⢠- To Parent Directory UML Weekend Crash Course⢠- To Parent Directory
Session 28—Analysis and Architectural Design of a Web Application 295 Gateways that translate between WAP and HTTP. All you have to do is write JSP pages containing WML, specify the MIME content type for WML, and place them on your normal Web server. The WAP Gateway, which is usually provided by the wireless network provider, not by you, automatically takes care of the rest. Figure 28-6 shows a Deployment diagram with the hardware (traditional wired device, wireless device, WAP Gateway, and the Web Server). The components from Figure 28-5 are placed onto the nodes of the Deployment diagram to show where they will reside. Traditional Wired Device Web Browser Web Server JavaBeans Wireless Device like Cell Phone WAP Gateway JSP pages with WML content JSP pages with HTML content Micro Web Browser Figure 28-6 UML Deployment diagram, WAP Gateway REVIEW Because requirements gathering and analysis are more about the business problem than the technical solution to it, the process for these phases should not be any different for a Web system than for a non-Web system. One exception to this general rule is that the customer should consider additional technological factors such as scalability, reliability, availability, performance, and security — considerations that may not be as important when designing a standalone system. The Model View Controller (MVC) design pattern simplifies development and enhances maintainability by separating the data model, user interface views, and controller logic aspects of your system. MVC can be adapted to Java Web applications by separating the model into JavaBeans and the view into JSP pages. Session 29 will show you how to separate out the controller. MVC also makes it easier to have two views, such as a WML view and an HTML view. QUIZ YOURSELF 1. What additional kinds of technological factors should a customer consider with a Web system (See “Requirements Gathering.”) 2. Which UML diagram would you use to model a resource like a JavaBean (See “JavaBeans.”)
296 Sunday Afternoon 3. How would you use the Component diagram in the development of a Web system (See “MVC pattern in the case study.”) 4. What is the purpose of the Model View Controller (MVC) pattern (See “Model View Controller.”)
- Page 268 and 269: SESSION 24 Modeling the Development
- Page 270 and 271: Session 24—Modeling the Developme
- Page 272 and 273: Session 24—Modeling the Developme
- Page 274 and 275: Session 24—Modeling the Developme
- Page 276 and 277: Session 24—Modeling the Developme
- Page 278 and 279: SESSION 25 Modeling the Static View
- Page 280 and 281: Session 25—Modeling the Static Vi
- Page 282 and 283: Session 25—Modeling the Static Vi
- Page 284 and 285: Session 25—Modeling the Static Vi
- Page 286 and 287: SESSION 26 Modeling the Static View
- Page 288 and 289: Session 26—Modeling the Static Vi
- Page 290 and 291: Session 26—Modeling the Static Vi
- Page 292 and 293: Session 26—Modeling the Static Vi
- Page 294 and 295: Session 26—Modeling the Static Vi
- Page 296 and 297: PART # V Sunday Morning Part Review
- Page 299 and 300: PART VI Sunday Afternoon Session 27
- Page 301 and 302: 278 Sunday Afternoon design, and mo
- Page 303 and 304: 280 Sunday Afternoon :User :Web Br
- Page 305 and 306: 282 Sunday Afternoon studied Java p
- Page 307 and 308: 284 Sunday Afternoon and time. A JS
- Page 310 and 311: SESSION 28 Analysis and Architectur
- Page 312 and 313: Session 28—Analysis and Architect
- Page 314 and 315: Session 28—Analysis and Architect
- Page 316 and 317: Session 28—Analysis and Architect
- Page 320 and 321: SESSION 29 Design of a Web Applicat
- Page 322 and 323: Session 29—Design of a Web Applic
- Page 324 and 325: Session 29—Design of a Web Applic
- Page 326 and 327: Session 29—Design of a Web Applic
- Page 328 and 329: Session 29—Design of a Web Applic
- Page 330 and 331: SESSION 30 UML Modeling Tools Sessi
- Page 332 and 333: Session 30—UML Modeling Tools 309
- Page 334 and 335: Session 30—UML Modeling Tools 311
- Page 336 and 337: Session 30—UML Modeling Tools 313
- Page 338 and 339: PART VI # Sunday Afternoon Part Rev
- Page 340 and 341: APPENDIX A Answers to Part Reviews
- Page 342 and 343: Answers to Part Reviews 319 20. I a
- Page 344 and 345: Answers to Part Reviews 321 26. It
- Page 346 and 347: Answers to Part Reviews 323 22. Dra
- Page 348 and 349: Answers to Part Reviews 325 Sunday
- Page 350 and 351: Answers to Part Reviews 327 It maps
- Page 352 and 353: APPENDIX B What’s on the CD-ROM T
- Page 354 and 355: What’s on the CD-ROM 331 Trial So
- Page 356 and 357: Glossary abstract class A class th
- Page 358 and 359: Glossary 335 automatic transition A
- Page 360 and 361: Glossary 337 decomposition Separati
- Page 362 and 363: Glossary 339 link A relationship b
- Page 364 and 365: Glossary 341 overloading Used to de
- Page 366 and 367: Glossary 343 specialization The ide
Session 28—Analysis and Architectural Design of a Web Application 295<br />
Gateways that translate between WAP and HTTP. All you have to do is write JSP pages containing<br />
WML, specify the MIME content type for WML, and place them on your normal Web<br />
server. The WAP Gateway, which is usually provided by the wireless network provider, not by<br />
you, automatically takes care of the rest. Figure 28-6 shows a Deployment diagram with the<br />
hardware (traditional wired device, wireless device, WAP Gateway, and the Web Server). The<br />
components from Figure 28-5 are placed onto the nodes of the Deployment diagram to show<br />
where they will reside.<br />
Traditional Wired<br />
Device<br />
Web<br />
Browser<br />
<br />
Web Server<br />
JavaBeans<br />
Wireless Device<br />
like Cell Phone<br />
<br />
WAP Gateway<br />
<br />
JSP pages<br />
with WML<br />
content<br />
JSP pages<br />
with HTML<br />
content<br />
Micro Web<br />
Browser<br />
Figure 28-6<br />
<strong>UML</strong> Deployment diagram, WAP Gateway<br />
REVIEW<br />
Because requirements gathering and analysis are more about the business problem<br />
than the technical solution to it, the process for these phases should not be any<br />
different for a Web system than for a non-Web system. One exception to this general<br />
rule is that the customer should consider additional technological factors such as<br />
scalability, reliability, availability, performance, and security — considerations that<br />
may not be as important when designing a standalone system.<br />
The Model View Controller (MVC) design pattern simplifies development and enhances<br />
maintainability by separating the data model, user interface views, and controller<br />
logic aspects of your system. MVC can be adapted to Java Web applications by separating<br />
the model into JavaBeans and the view into JSP pages. Session 29 will show<br />
you how to separate out the controller. MVC also makes it easier to have two views,<br />
such as a WML view and an HTML view.<br />
QUIZ YOURSELF<br />
1. What additional kinds of technological factors should a customer consider with a<br />
Web system (See “Requirements Gathering.”)<br />
2. Which <strong>UML</strong> diagram would you use to model a resource like a JavaBean (See<br />
“JavaBeans.”)
Change language