Figure 1 - uploaded by Arantza Irastorza
Content may be subject to copyright.
Contexts in source publication
Context 1
... used a car-retailer site as our running example. Figure 1 illustrates some of the interactions that can take place at this site. The system starts by prompting the user to provide the desired car model (see figure 1, first page); if more than one car matches the query criteria, the site returns a list with the matching cars (second page); once a car has been univocally identified, the site renders the corresponding car details (third page). ...
Context 2
... 1 illustrates some of the interactions that can take place at this site. The system starts by prompting the user to provide the desired car model (see figure 1, first page); if more than one car matches the query criteria, the site returns a list with the matching cars (second page); once a car has been univocally identified, the site renders the corresponding car details (third page). Figure 2 shows the design artifacts associated with the screen-shots of the previous figure. ...
Context 3
... shown in figure 2, the "carSearch" client page (the first page in figure 1) provides a link to the "CatalogueSearch" server page. This servlet accesses the "SecondHandCarCatalogue" domain object -the model-, and invokes the "BuildCarList" servlet which builds the presentation of the car list (the second page in figure 1). ...
Context 4
... shown in figure 2, the "carSearch" client page (the first page in figure 1) provides a link to the "CatalogueSearch" server page. This servlet accesses the "SecondHandCarCatalogue" domain object -the model-, and invokes the "BuildCarList" servlet which builds the presentation of the car list (the second page in figure 1). This interaction pattern is repeated for the remaining screen-shots. ...
Context 5
... can be regarded as an aggregation of the CLogo, CHeader and CForm components. It is a final component that maps to a page (e.g. a page similar to the 1st one in figure 1) while CLogo can be reused by components realising the 2nd and 3rd pages. ...
Context 6
... only difference beween this definition and the one shown in figure 6 is the isComponent property. It defines iSearch as a component which might represent the 1st page (in figure 1) of our Web application and it also sets the place from which the component may be obtained, namely www.carsellers.com/.../search.html. ...
Context 7
... terms of design, an IWS operation is a cohesive, purposeful unit of user interaction. The sequence of screen shots shown in figure 1 renders the presentation of the carSearch IWS operation. This set of pages supports a common goal: retrieving the available second hand cars of the desired car model. ...
