You are on page 1of 8

General Issues on Web Information Systems Development

Professor Dumitru OPREA, PhD


"Alexandru Ioan Cuza" University of Iasi
Bd. Carol I, no. 22, 700505, Iasi, Romania
Phone: ++ 40-232-201415; Fax: ++40 232-217000
E-mail: doprea@uaic.ro

Associate Professor Gabriela MESNITA, PhD


"Alexandru Ioan Cuza" University of Iasi
Bd. Carol I, no. 22, 700505, Iasi, Romania
Phone: ++ 40-232-201585; Fax: ++40 232-217000
E-mail: gabim@uaic.ro

Abstract
In recent literature, many authors argue that “Web development” is new and different. The arguments are,
however, both debatable and debated, and often it is neither clear what is meant by Web development, nor what
it is supposed to be different from. Often-suggested special characteristics of Web development do not seem
special after all. The Web information space is rapidly growing in the size and the diversity of both its data and
its audience. A consequence is that Web Information Systems (WIS) in many applications replace existing
traditional (not Web based) information systems. Since the nature of WIS differs from the nature of traditional
information systems there is a strong demand for design methodologies specifically oriented towards WIS
design. The complexity of WIS implies the need for an effective design process and a rigorous and systematic
design approach.

Keywords: web information systems, development methodology, systems development

1. Introduction

In various application areas such as e-commerce, geographical information systems,


education etc., the Web is widely considered a reliable approach to support information
diffusion. As a result, important information systems efforts are geared increasingly toward
exploiting the benefits of this platform, leading to the development of information systems
based on Web technology, in other words “Web-based information systems” (WISs)1.

Most of Web sites propose visually attractive and elaborated graphical web pages, but
requirements of Web-based Information Systems (WISs) are beyond visual design. A WIS
can be seen as a set of technical means for collecting, structuring, storing, managing and
diffusing information as any traditional information system does. The difference is that these
actions are completed over a Web infrastructure. Consequently, WIS deals with a huge
quantity of information, coming from numerous sources, in different forms, and processed by
software environments which evolve rapidly. Moreover, services managed by WIS usually
have a high level of complexity as, for example, the management of the user’s shopping cart
in e-business sites. Then, the design of a WIS is a complex task which requires some methods
and tools in order to assist developers. However, most of the time, developments of WIS are
ad hoc and lead to more or less successful results can be acquired either by an explicit
technique (the user fulfils an informative form) or an implicit one (user’s actions are tracked
and analyzed).

2. Stages of WIS

For understanding the new developed theory, the idea of web information system (WIS) is
good to introduce. The simple definition says that it is a classical IS designed for running in
the world–wide web conditions.

There is a clear difference between a set of Web pages and a WIS. The latter supports work,
and is usually tightly integrated with other non-WISs such as transaction processing systems,
thus WISs are different from traditional information systems. WISs can integrate processes or
systems within a single interface, and allow access over a local intranet or global Internet
network. They require new approaches to design and development, have the potential of
reaching a much wider audience, and are usually a result of huge efforts. These differences
introduce managerial and technical challenges2.

1
Isakowitz, T., Bieber, M., Vitali, F. – „Web Information Systems”, Communications of the ACM,
July 1998/Vol. 41, p. 79
2
Villanova-Oliver, M., Gensel, J., Martin, H., Erb, C. – Design and Generation of Adaptable Web Information
Systems With KIWIS, www-lsr.imag.fr
The WIS is characterized by following features3:
• are inter-organizational and intra-organizational systems and involve many
different components within and out of an organization;
• users of a WIS have different backgrounds and computer experience. Also they are
geographically and culturally dispersed;
• reliance on the underlying Internet platform and hypermedia mechanisms, with
accompanying technologies, standards, and tools;
• have common interface(s) in the form of Web browsers.

An evolutionary classification of the development of WIS point out four stages4, presented in
table 1.
Table 1 – Characteristics of WIS stages
Stages of Scope of system Interactivity of Model of user Complexity of
WIS system feedback development
Static Limited, provide Data flow is in Unseen, disregarded Static hypermedia
information for one direction, The feedback and documents. Integrate a
existing and potential from server to queries could be sent conceptual data and
customers. client. only through e-mail, navigation model are
not by Web interface usually just as
applicable for
structured as well as
unstructured
information.
Dynamic The functionality of Interactivity, User feedback is A closer integration of
new WIS must presentation of introduced intro development is reached
include account product essential by extending the design
summaries and catalogues and communication and implementation
balances, money detailed product models. This requires phases with usage and
transfer, bill payment information, the analysis of analysis.
and a variety of online explicit and/or
support functions, as transactions. implicit user
is customer services, feedback.
search engine etc.
Adaptive Integrated solutions User profiles User feedback is Based on central user
become essential, and based on being processed model the WIS is
explicit and implicit preferences allow instantly within the automatically designing
user feedback is personally expected WIS and implementing. The
processed at the same addressing response time. WIS cannot be
time in order to customers with developed without a
update the main user dynamically clear understanding of
model. generated the appropriate
documents, and parameters which
improving requires a detailed
communication economic and
with dynamic marketing analysis, an
responses. assessment of technical
feasibility.

3
Gregor, S., Jones, D., Lynch, T., Plummer, A.A. – Web Information Systems Development: Some neglected
aspects, http://cq-pan.cqu.edu.au
4
Bauer, C., Scharl, A. – Development of Web Information Systems: Conceptual Models and Examples from
Retail Financial Services Industry, www.mngt.waikato.ac.nz/school/knowledge
Stages of Scope of system Interactivity of Model of user Complexity of
WIS system feedback development

Agent The transformation of Principal-agent The „request- No widespread design


negotiations the client/server relations replace response” specific to and/or analysis
infrastructure into the traditional previous stages will approaches for agent
agent environment client/server be replaced by the negotiation can be
with multi-lateral approach with direct interaction of identified, mainly
interaction requires agent software equal partners in an because of the
the extension of the acting as clients agent-driven complexity of such a
development strategy and servers at the communication task and the insecurity
to include the WIS same time. network environment. in the nature of this
development at both upcoming information
ends of interaction. infrastructure.

The successful development of Web Information Systems becomes critical for organizations
competing for business and consumers on the Internet. Competitive Web Information
Systems development is only feasible with a clear understanding of the essential technical
infrastructure and the associated features.

3. Methodologies of WIS development

In the IS field, the use of an information systems development methodology has long been
postulated as a means of improving this process. Postulated benefits include reduced cost and
time in system development, improved quality of the resulting information systems, and
improved benefit realization by the organization that uses the resulting information systems.

A WIS development methodology is an information system development methodology that is


specifically aimed at development of a WIS. A number of methodologies have been
proposed, classified into three different categories5:
1. using modified models based on traditional information systems or software
development methodologies,
2. based on hypertext modelling;
3. built into web site development tools.

The main characteristics of four of most important of WIS development methodologies


(RMM – Relationship Management Methodology6, OOHDM – Object/Oriented Hypermedia

5
Venable, J.R., Lim., F.C.B – Development Activities and Methodology Usage by Australian Web Site
Consultants, Proceedings of 4th Western Australian Workshop on Information Systems Research, 2001
6
Isakowitz, T. – What is RMM?, www.stern.nyu.edu
German, D.M. – The Relationship Management Methodology, http://ag.cs.uvic.ca.
Design Model7, NLG – Natural Language Generation8, W3DT – World Wide Web Design
Technique9) are presented in table 2.
Table 2 – The characteristics of RMM, OOHD and NLG as methodologies to WIS development
Characteristics Methodologies
RMM OOHD NLG W3DT
Category of Based on Based on Based on Both based on
methodology traditional hypertext hypertext traditional and
development modelling modelling hypertext
methodologies.
Focus Define a data Use abstraction The information Provide a
model in order to and composition storage and conceptual, user-
abstract and mechanisms in an retrieval aspect centric framework
structure the object oriented of WIS and the and graphical
application framework to notation for the
need to move
allow: construction of
domain quickly from
- concise both reference and
description of one document to customized
complex another. models.
information items,
- specification of
complex
navigation
patterns and
interface
transformations
Phases 310 511 312 413
Criticism Applicable to a Data relationship Not dealing with There still is a
limited domain of may not reflect the way users of lack of non-
web sites the users’ needs the WWW read redundant meta
and give a poor documents, models for WIS
support for reducing the which does not
linking to back- benefit of ignore the
end database carefully hierarchical,
organizing pages recipient oriented
to eliminate structure.
redundancies.

7
Schwabe, D., Ross, G. – The Object-Oriented Hypermedia Design Model, Communications of the ACM, Vol.
38, No. 8, 1995, pp. 45-48
Lang, M. – Hypermedia Systems Development: Do We Really Need New Methods?, 2002,
www.ecommerce.lebow.drexel.edu
8
Wilcock, G. – Integrating Natural Language Generation with XML Web Technology, www.ling.helsinki.fi
Stenzorhn, H. – XtraGen - A Natural Language Generation System Using XML and Java technologies, 2002,
www.mietta.info.
9
Scharl, A. – A Conceptual, User-Centric Approach of Modeling Web Information Systems, 1999,
http://ausweb.scu.edu.au
Bichler, M., Nusser, S. – Modular Design of Complex Web-Applications with SHDT, http://wicky-wu-
wien.ac.at
10
Entity relationship design, entity design, navigation design
11
Requirements gathering, conceptual design (classes, relationships, attributes, perspectives), navigational
design (nodes and links), abstract interface design (interface classes), implementation (mapping interface objects
to implementation objects)
12
Context selection (deciding what should be communicated), text structuring (organizing the information for
presentation), text planning (composition of plan based on facts in a knowledge base)
13
Analysis, design, implementation and maintenance the WIS
Though Web Information Systems involves programming and software development, and
adopts some of the principles of the software engineering, is different from information
systems and software development due to the following reasons14:
• WIS are document-oriented containing static or dynamic Web pages;
• they will continue to be focused on look and feel, favoring visual creativity and
incorporation of multimedia in presentation and interface;
• multiplicity of user profiles;
• the Web exemplifies a greater connection between art and science than generally
encountered in software development;
• most Web-based systems need to be developed within a short time, making it difficult
to apply the same level of formal planning and testing as used in software
development;
• the type of individuals who build/develop Web-based systems are vastly varied in
their background, skills, knowledge and system understanding, and as well as their
perception of Web and quality Web-based system.

4. Conclusions

The literature on design and development of web-based information systems seems to agree
that development of web-based systems is different from development of traditional IT-based
systems. The technology mainly is an interaction medium and that in www-environment new
applications will be developed and assembled by cloning existing components. The keywords
of the information systems discipline will be prototyping, object orientation, reuse,
networking, redundancy, plug-ins, innovations, customer focus and time to market.”15.

But with these differences, could be observed there are many activities in WIS development
which are similar with those from traditional information systems development, starting from
conception and development to implementation, performance evaluation, and continual
maintenance, as is presented in the following image (fig. 1):

14
Murugesan, S., Deshpande, Y., Hansen, S., Ginige, A. – Web Engineering: A New Discipline for Development
of Web-based Systems, www-itec.uni-klu.ac.at
15
Carstensen, P.H., Vogelsang, L. – Design of Web-Based Information Systems – New Challenges for Systems
Development?, www.diwa.dk
Indentify and selection of web project development
Micronalysis Planning of project
Configuration and project management

Requirements specification
Outline overall structure
Analysis Filter information and refine requirements
Data and processe modeling

Develop prototype
Integration with legacy systems
Design Migration of legacy system to Web environments
Web-based real-time applications development

Testing, verification and validation


Quality assessment, control and assurance
Implementation Performance specification and evaluation
Education and training

Manage system modifications


Operation and Improve existing functions
maintenance Ensure the system performs
at acceptable level

Fig. 1 Main activities of WIS development

Web information systems are, however, different from traditional information systems in the
sense that they require new approaches and often are results of vast efforts. Some authors also
stress the differences in terms of the speed of change in the technological basis. The pace at
which the continuous evolvement of tools and features are running at the web-technology is
extreme even compared to the rest of the IT area, and that these tools have attract people
away from recognizing the need for a systematic design approach.

References

1. Bauer, C., Scharl, A., Development of Web Information Systems: Conceptual Models and Examples from
Retail Financial Services Industry, www.mngt.waikato.ac.nz/school/knowledge
2. Bichler, M., Nusser, S., Modular Design of Complex Web-Applications with SHDT, http://wicky-wu-
wien.ac.at
3. Carstensen, P.H., Vogelsang, L., Design of Web-Based Information Systems – New Challenges for Systems
Development?, www.diwa.dk
4. German, D.M., The Relationship Management Methodology, http://ag.cs.uvic.ca
5. Gregor, S., Jones, D., Lynch, T., Plummer, A.A., Web Information Systems Development: Some neglected
aspects, http://cq-pan.cqu.edu.au
6. Isakowitz, T., Bieber, M., Vitali, F. (1998), Web Information Systems, Communications of the ACM, Vol.
41, p. 79
7. Isakowitz, T., What is RMM?, www.stern.nyu.edu
8. Lang, M. (2002), Hypermedia Systems Development: Do We Really Need New Methods?,
www.ecommerce.lebow.drexel.edu
9. Murugesan, S., Deshpande, Y., Hansen, S., Ginige, A., Web Engineering: A New Discipline for
Development of Web-based Systems, www-itec.uni-klu.ac.at
10. Scharl, A. (1999), A Conceptual, User-Centric Approach of Modeling Web Information Systems,
http://ausweb.scu.edu.au
11. Schwabe, D., Ross, G. (1995), The Object-Oriented Hypermedia Design Model, Communications of the
ACM, Vol. 38, pp. 45-48
12. Stenzorhn, H. (2002), XtraGen - A Natural Language Generation System Using XML and Java
technologies, www.mietta.info
13. Venable, J.R., Lim., F.C.B (2001), Development Activities and Methodology Usage by Australian Web Site
Consultants, Proceedings of 4th Western Australian Workshop on Information Systems Research
14. Villanova-Oliver, M., Gensel, J., Martin, H., Erb, C., Design and Generation of Adaptable Web Information
Systems With KIWIS, www-lsr.imag.fr
15. Wilcock, G., Integrating Natural Language Generation with XML Web Technology, www.ling.helsinki.fi

You might also like