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

2. Web Development 2 2 Learning Objectives v Outline a range of UML stereotypes available for the modelling of web applications v 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 v Demonstrate the use of UML extensions in web application models

3. Web Development 2 3 Stereotypes for Web Application Modelling «server page»Class «builds» Association «client page»Class «redirect» Association «form»Class «iiop» Association «frameset»Class «rmi»Association «target»Class«input element» Attribute «java script object»Class«select element»Attribute «client script object»Class«target area element» Attribute «link»Association«web page»Component «targeted link»Association «asp page»Component «frame content»Association«jsp page» Component «submit»Association«servlet»Component >Association«script library» Component

4. Web Development 2 4 Reminder - Web Application Architecture Patterns 1. Thin Web Client : Little control of client’s configuration Standard web browser All business logic executed on the server 2. Thick Web Client : Significant business logic executed on the client using dynamic HTML, Java applets etc. HTTP used for communication with server 3. 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. Web Development 2 5 Thin Web Client Design v 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. Web Development 2 6 Sequence Diagram for Thin Web Client Conallen, J. (2000)

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

8. Web Development 2 8 Separating Server Page Responsibilities

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

10. Web Development 2 10 Forms & Frames v > objects are aggregates of client pages –Standard input elements submitted for processing by server page –Stereotypes & tagged values can add information v Frames > 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. Web Development 2 11 Shipping address collection form Conallen, J. (2000)

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

13. Web Development 2 13 Alternative ways to express Scripts in a Client Page

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

15. Web Development 2 15 Sequence diagram involving client- side components

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

17. Web Development 2 17 Class diagram with Distributed Objects

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

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

20. Web Development 2 20 Summary v Outlined a range of UML stereotypes available for the modelling of web applications v 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 v Demonstrated the use of UML extensions in web application models

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