[ WWW2005 logo - takes you to the trip report main page ]

Trip Report WWW2005

tutorial: web engineering


presenters:

audience:

there were 9 attendees in the beginning, of which at least 6 were from europe (including me). later 2 more persons showed up.

[ tutorial TFR03 at hotel new otani ]
(click on the image for an enlargement)

definition:

web engineering is the application of systematic, disciplined and quantifiable approaches to design, production, deployment, operation, maintenance and evolution of web based software products.

introduction:

current practices / problems:

WebIS development is carried out in an ad hoc manner:

[ idea / requirement -> publish -> fix problems (infinitive loop) ]

web application development is a process, not an event.

project success factors:

according to CHAOS report by the standish group, the two top success factors for projects are:

  1. support from executive management
  2. user involvement

problems with large web-based projects:

of all large projects, only the following percentage fullfil the goals:

  1. satisfy business needs: 16%
  2. have the required functionality: 47%
  3. delivered in time: 21%
  4. within budget: 37%

project management problems:

project management means manage expectations.


goals of web engineering:

  1. develop high quality web applications
  2. maintain and evolve ("plan for change")

process models:

prevent permanent changes:

introduce change control, e.g. through a change request procedure.

design phases:

  1. assessing requirements: understand and organize the requirements; prototyping (proof of concept); risk reduction; business rules; prioritises requirements
  2. conceptual design: achieve a maintainable description of requirements
  3. logical design: shape the product; achieve a design model; separate logical units
  4. data design: design the information space
  5. presentation design: design the final audio and visual presentation
  6. navigation design: improve ease of use and access to information and processes; consider familiar navigation patterns such as “site map”, “bred crumb”, “landmark” etc.
  7. interaction design: logical design of how a user or system may interact with the information space of a web application
  8. process design: design the overall business logic of the web application
  9. distributed system architecture (DSA) design: define global wiring of the overall business logic of the application; define communication, constraints and external relationships between all application units

development:

build and test

evolution:

  1. test and monitor
  2. operation and maintenance

additional information:


open question:

could the COnstructiv COst MOdel (COCOMO) developped by berry boehm in 1984 in order to estimate the overall cost and duration of software projects be used or adapted for web based projects ?

see COCOMO II (presented by Center for Software Engineering)


[ to the trip report main page ] to the trip report main page


tutorial.html / 12-may-2005 (ra) / reto ambühler