Web Site Development Methodologies - High Level Models and Methodologies for Information Systems - page 64

is implementation design. At this point, the of the Web site is developed.

The purpose is to produce a reliable, enjoyable, and ef

“ look ”

for the con-
ceptual design made in prior stages. The fourth stage is implementation, the actual
completion of the Web site, and its placement online.
When developing an application with this methodology, the developer must
follow a well-de

cient “ look ”

ned design philosophy that will aid him/her with the necessary
support to organize the Web site. With the WSDM, development comprises a chain
of successive stages. Each stage has a well-de

ned output. Therefore, for each
stage, a (sub) method that illustrates how to obtain the output from its input is
offered. The output of one phase is the input of a following phase (Troyer et al.
2008 ).
The implementation of WSDM guarantees that autonomic computing elements
can be accessed in a regular way and have well-de ned life cycles. Furthermore,

each of the elements is regarded as a resource that is addressable through the Web
Services Addressing Standard (Litoiu et al. 2008 ).
Burner ( 2002 ) argues that “ WSDM is good to design front-ends and design the

' but it does not either explicitly design, or manage dynamic data. It

is advisable to combine it with a second methodology to design the structure of the
data and dynamics.

look and feel, '

”

4.4 Relationship Management Methodology (RMM)

The Relationship Management Methodology (RMM) was originally developed in
the 1990s, as a framework for the design and construction of hypermedia appli-
cations. It is thus called because it focuses on hypermedia applications as a vehicle
for the relationships between information objects (Isakowitz et al. 1995 ).
RRM is a structured methodology. The design stages of the process are preceded
by a number of studies focusing on such things as the objectives of the Web site,
market and user analysis, information sources and permissions, distribution chan-
nels, and cost

t analysis. This results in feasibility studies, as well as a
thorough knowledge of both information and navigational requirements (Isakowitz
et al. 1995 ).
After needs, goals, and requirements of the project are well de

bene

-

ned, there fol-

lows a process of seven stages, as illustrated in Fig. 4.2 .

E-R Design The information domain of the application is represented via an
Entity

rst
step of the design process represents a study of the relevant entities and relation-
ships of the application domain.
Entity Design This step establishes how the information in the selected entities will
be presented to users and how they may access it. The resulting concept is described
as an E-R+diagram. It involves dividing an entity into meaningful pieces and
organizing these into a hypertext network.

- Relationship (E-R) diagram. According to Isakowitz et al. ( 1995 ), this