Architecting and designing > UML 2.0 Lite > UML profiles and extensions > Web Application Extensions (WAE)
  
Web Application Extensions (WAE)
The Web Application Extensions to UML have become a popular extension to the UML for modeling web applications. They are put forth by Jim Conallen in his book Building Web Applications with UML (Addison-Wesley, 1999). The extension defines a set of stereotypes, tagged values, and constraints that enable modeling of web applications. The following stereotypes can be applied to classes (on Class, Component, and Use Case diagrams), components (on Component diagrams), and object lifelines (on Sequence diagrams):
Server page
A server page is represented by a class of stereotype Server Page. It represents a web page that has scripts executed by the server. The scripts interact with resources such as databases, and so on.
This graphic is described in the surrounding text.
Client page
A client page is represented by a class of stereotype Client Page. An instance of a client page is an HTML-formatted web page. It is a mix of data, presentation, and logic.
This graphic is described in the surrounding text.
Form
A form is represented by a class of stereotype Form. It is a collection of input fields that are part of the client page.
This graphic is described in the surrounding text.
Frameset
A frameset is represented by a class of stereotype Frameset. A frameset is a container of multiple web pages.
This graphic is described in the surrounding text.
Target
A target is represented by a class of stereotype Target. A target is a named compartment in a browser window in which web pages can be rendered.
This graphic is described in the surrounding text.
JavaScript object
A JavaScript Object is represented by a class of stereotype JavaScript. JavaScript object instances exist only in the context of client pages.
A JavaScript object does not have an icon.
ClientScript object
A ClientScript Object is represented by a class of stereotype ClientScript. A ClientScript object is a separate collection of client-side scripts that exist in a separate file and are included by a separate request on the part of the client browser.
This graphic is described in the surrounding text.
Web page
A web page is represented by a component of stereotype Web Page.
This graphic is described in the surrounding text.
ASP page
An ASP page is represented by a component of stereotype ASP Page. An ASP page is one that implements ASP server-side code.
This graphic is described in the surrounding text.
JSP page
An ASP Page is represented by a component of stereotype JSP Page. A JSP Page is a web page that implements JSP server-side code.
This graphic is described in the surrounding text.
Servlet
A servlet is represented by a component of stereotype Servlet. A servlet is considered a Java Servlet component, and is only applicable in development environments that support Oracle servlets.
This graphic is described in the surrounding text.
Script Library
A Script Library is represented by a component of stereotype Script Library. A Script Library is a component that provides a library of subroutines or functions that can be included by other web page components.
This graphic is described in the surrounding text.
See also
UML profiles and extensions