1 / 21

And Franchise Colleges

And Franchise Colleges. Modelling for Web Development - 2. Name : MANSHA NAWAZ room : G 0/32 email : m.nawaz@tees.ac.uk. Learning Objectives. Outline a range of UML stereotypes available for the modelling of web applications

jonah
Download Presentation

And Franchise Colleges

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. And Franchise Colleges Modelling for Web Development - 2 • Name : MANSHA NAWAZ • room : G 0/32 • email : m.nawaz@tees.ac.uk

  2. Learning Objectives • Outline a range of UML stereotypes available for the modelling of web applications • Using a set of UML models illustrate the modelling of web applications based on the architecture patterns: • Thin Web Client • Thick Web Client • Web Delivery • Demonstrate the use of UML extensions in web application models

  3. Stereotypes for Web Application Modelling

  4. Reminder - Web Application Architecture Patterns • Thin Web Client: • Little control of client’s configuration • Standard web browser • All business logic executed on the server • Thick Web Client: • Significant business logic executed on the client using dynamic HTML, Java applets etc. • HTTP used for communication with server • Web Delivery: • May support distributed objects where web browser acts as a delivery and container device for the objects • Uses additional protocols such as RMI, IIOP and DCOM

  5. Thin Web Client Design • Thin web client actors only interact with client pages & server pages only interact with server resources • Need to incorporate client & server pages in sequence diagrams • Boundary objects from analysis model become client pages • Transform controller objects become server pages

  6. Sequence Diagram for Thin Web Client Conallen, J. (2000)

  7. Thin Web Client Design • Server-side objects can be overloaded • Executing business logic • Building user interface to send to client • Can alleviate this by separating business logic processing from interface building • Conceptual web pages and business objects

  8. Separating Server Page Responsibilities

  9. Logical-view classes related to checking-out a shopping cart

  10. Forms & Frames • <<Form>> objects are aggregates of client pages • Standard input elements submitted for processing by server page • Stereotypes & tagged values can add information • Frames <<framesets>> allow browser windows to be subdivided into panes each containing its own webpage • Each pane is a target that other client pages can request web pages for

  11. Shipping address collection form Conallen, J. (2000)

  12. Thick Web Client Design • Client-side scripting allows processing on client • e.g. recalculation of shopping cart after quantity changes • Functionality can also be provided by ActiveX controls, Java applets & JavaBeans components – client pages can invoke operations on them • Server objects interact with server-side resources to provide functionality

  13. Alternative ways to express Scripts in a Client Page

  14. Class Diagram with Client Page that uses ActiveX components Conallen, J. (2000)

  15. Sequence diagram involving client-side components

  16. Web Delivery Design • Distributed objects can provide real flexibility • RMI/IIOP or DCOM provides additional communication protocols • Direct communication between client & server objects improves efficiency • Frequently business logic is initially modelled without deployment to simplify developer understanding • Deployment view of architecture covers these issues

  17. Class diagram with Distributed Objects

  18. Web Delivery Deign – Sequence Diagram (without deployment shown) Online Sporting Event System – Conallen (2000)

  19. Web Delivery Deign – Class Diagram (deployment shown)

  20. Summary • Outlined a range of UML stereotypes available for the modelling of web applications • Using a set of UML models illustrated the modelling of web applications based on the architecture patterns: • Thin Web Client • Thick Web Client • Web Delivery • Demonstrated the use of UML extensions in web application models

  21. References • Conallen, J. (2000) Building Web Applications with UML Addison Wesley • Conallen, J. (1999) Modelling Web Application Architectures with UML Communications of the ACM volume 42, number 10 • Ceri, S., Fraternali, P. & Matera, M. (2002) Conceptual modelling of data-intensive Web applications IEEE Internet Computing volume 6, number 4

More Related