Web Development Methodology

1. Introduction:

Web Development Methodology is a relatively new area where there has not been a solid method emerged. Usually most companies develop their own methodologies and these methodologies differ mainly because of the size of the web project.

The major concern is the negotiation between technological, organizational, and human aspects of development. WISDM (Web Information System Development Methodology)(1,2) offers methodology for socio-technical view where a web development methodology has to deal with user satisfaction in addition to technical limitations.


2. WISDM:

From the Multiview Approach of WISDM, technical development tools, organizations and individuals need to be considered all together.

The following chart demonstrates the relationship between the different aspects of development (i.e technology, developers, situation, organisation and humans).

Graph 1 – WISDM Framework


Graph 2 – WISDM Matrix


2.1. Organisational Analysis:
The concern is to determine the business strategy alignment with the web development. Depending on the degree of the web presence (i.e. e-marketing, e-commerce or e-operations), we should be looking for the answers to the following concerns on this analysis:

  • · What is the business of the organisation?
  • · What are the products and / or services?
  • · Who are the customers?
  • · Who are the competitors?
  • · Current marketing strategies?
  • · What are the ways to access new markets across the globe? (1)
  • · How to target the market segments effectively?
  • · How to increase the speed on getting into the market and reach customers?
  • · How to create relationships with the customers remotely from the web?
  • · How to make at least info on products or services continuously?
  • · How to reduce several costs?
  • · How to improve the efficiency of the supply chain
  • · How to create cost effective and motivative working methods?
  • · How to improve the image of the company with the help of internet?

2.2 Work Design:

is to measure the user satisfaction and quality where it is the most important part of the methodology since human preferences differ in many ways and it is difficult to standardize.

The measurement systems involve all the users who have a relationship with the organization differing with their importance. These include the endusers, managers, employees, developers etc.

The WebQual (1) has developed a questionnaire set in order to measure website quality in terms of user satisfaction.

The following topics are being given points in order to determine an overall average score.

  • · I find the site easy to learn to operate
  • · My interaction with the site is clear and understandable
  • · I find the site easy to navigate
  • · I find the site easy to use
  • · The site has an attractive appearance
  • · The design is appropriate to the type of the site
  • · The site conveys a sense of competency
  • · The site creates a positive experience for me
  • · Provides accurate information
  • · Provides believable information
  • · Provides timely information
  • · Provides relevant information
  • · Provides easy to understand information
  • · Provides information at the right level of detail
  • · Presents the information in an appropriate format
  • · Has a good reputation
  • · It feels safe to complete transactions
  • · My personal information feels secure
  • · Creates a sense of personalization
  • · Conveys a sense of community
  • · Makes it easy to communicate with the organization
  • · I feel confident that goods/services will be delivered as promised
  • · My overall view of this website


2.3 Information Analysis:

deals with the modeling of the information systems. WISDM uses Unified Modeling Language (UML) where the elements of this analysis include the following:

  • · Functional requirements view: use-case diagrams
  • · Static structural view: class diagrams, composite structure diagrams
  • · Dynamic behavior view: sequence diagrams, activity diagrams, state machine diagrams.

The diagrams are:

  • · Structure diagrams: class diagrams, component diagrams, composite structure diagrams, deployment diagrams, object diagrams, package diagrams
  • · Behavior diagrams: activity diagrams, state diagrams, use-case diagrams,
  • · Interaction diagrams: communication diagrams, interaction overview diagrams, sequence diagrams, timing diagrams

Graph 3 – Umbrello UML Modeler(1)

2.4 Technical Design:

is UML plus physical design as dicated by the target implementation environment which includes:

  • · Data design
  • · Architectural design
  • · Component design
  • · Interface design
  • · Aesthetic design
  • · Navigation design

4. Alignment with ISO 9000-3

Aligning the Web Development Methodology with the ISO 9000-3 Quality System Life Cycle Standards give the following details:

ISO 9000-3 Quality System Life Cycle Activities

Web Development Methodology

1. Contract Review

Request for Proposal

Interviews and view-point analysis

Analyzing the scope of the Project

Business and Organisational Requirements

Technical, Organisational and Economical Feasibility Studies

E-business Plan

Evaluating the project Time Frame

Detailed planning of dates and allocation of resources

Legal Issues and Arrangement

2. Requirements Specification

Activity and State Diagrams, DFD’s

Use-case Diagrams

3. Development Planning

Risk Analysis

Communications Plan

Testing Strategy Analysis

Detailed Hardware / Software Procurement Planning

Change Management Analysis

4. Quality Planning

Quality Analysis

5. Design and Implementation

Interface Design

Database design with ER Diagrams

6. Testing, Validation and Acceptance

Mockups Approval

Internal Testing

Full Feature Presentation and Incrementing

Acceptance

7. Replication, Delivery and Installation

Installation to the Web Server

8. Maintenance

Bug Reporting System

Support System

Knowledge Base

5. References:

Filed under: Articles

No Comments

(Required)
(Required, will not be published)
« ISO/IEC 90003 International Standard Summary