1. Design application
The example domain used in Wijngaards, Boonstra and Brazier (2004) is that of website design. Two projects are described1: one for the design of a website for a non-profit organisation, the other is the design of a project for a company. The same team is responsible for both projects and the design process is similar. Both websites they design include three important sections: news, an address book and an interactive forum.
The non-profit organisation's emphasis is on the functionality of the website: on the information to be communicated and shared, and to a lesser extent on "look & feel". An extended example of such a website can be found at www.natuurkunde.nl.
The company's overall goal is to support and attract clientèle. The website is to contain information about the product, addresses of dealers and repair shops, and discussion about technologies. This customer's emphasis is more on the look and feel, than on the functionality provided by the website.
The design team includes graphical designers, logical designer, code designers (programmers) and HTML designers. A website consists of models for its graphical and logical layout, and (executable) specifications of its functionality and HTML. Briefly summarised, graphical designers design the overall "look & feel" of the website, logical designers design the "flow": the sequences of pages a client encounters, code designers write functional code, and HTML designers implements the layout in HTML pages.
2. Computational simulation traces
Two traces of the computational simulation are published in this section. These traces are used in the website design example discussed in section 3.1 of Wijngaards, et al. (2004).
References
Wijngaards, N.J.E., Boonstra, H.M., & Brazier, F.M.T. (2004). Role of Trust in Distributed Design. Artificial Intelligence for Engineering Design, Analysis and Manufacturing, 18(3). (submitted)
Footnotes