The object-oriented hypermedia design model
Communications of the ACM
A methodology for client/server and Web application development
A methodology for client/server and Web application development
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Building Web applications with UML
Building Web applications with UML
Collaborative Web development: strategies and best practices for Web teams
Collaborative Web development: strategies and best practices for Web teams
Web Modeling Language (WebML): a modeling language for designing Web sites
Proceedings of the 9th international World Wide Web conference on Computer networks : the international journal of computer and telecommunications netowrking
Configuration management: the missing link in Web engineering
Configuration management: the missing link in Web engineering
Requirements Engineering: Processes and Techniques
Requirements Engineering: Processes and Techniques
Managing Multimedia; Project Management for Interactive Media with CD-ROM
Managing Multimedia; Project Management for Interactive Media with CD-ROM
Web Development: Estimating Quick-to-Market Software
IEEE Software
A Framework for Defining Acceptance Criteria for Web Development Projects
Web Engineering, Software Engineering and Web Application Development
A diagrammatic tool for representing user interaction in UML
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
Towards a UML extension for hypermedia design
UML'99 Proceedings of the 2nd international conference on The unified modeling language: beyond the standard
Fine-grained, structured configuration management for web projects
Proceedings of the 13th international conference on World Wide Web
Hypermedia Systems Development Practices: A Survey
IEEE Software
Model transformations from requirements to web system design
ICWE '06 Proceedings of the 6th international conference on Web engineering
ICWE '06 Proceedings of the 6th international conference on Web engineering
The treatment of navigation in web engineering
Advances in Engineering Software
The 2QCV3Q quality model for the analysis of web site requirements
Journal of Web Engineering
The effect of specialized multimedia collections on web searching
Journal of Web Engineering
Agile web engineering (AWE) process: perceptions within a fortune 500 financial services company
Journal of Web Engineering
Impacts of web systems on their domain
Journal of Web Engineering
Software process improvement success factors for small and medium Web companies: A qualitative study
Information and Software Technology
Journal of Mobile Multimedia
Hi-index | 0.00 |
The nature of Web systems is substantially different from more conventional software systems. They are developed in shorter timeframes, often act as the direct interface between multiple stakeholders, meet a more generic set of requirements, and generally serve a less specific user group. They are often developed very quickly from templated solutions, using coarse-grained authoring tools, and by the efforts of a multidisciplinary team. There is often considerable uncertainty on the part of the client as to their own requirements. The importance of defining the objectives of the system during the early stages of a project are generally acknowledged to be important, but access to the tools and templates can encourage developers to build too early. Often requirements are inadequately documented, or only emerge during development, or change as development proceeds. The immaturity of the industry and the lack of standardised processes in web development have been demonstrated by web-based solutions that in many cases fail to meet fundamental requirements. Specifications for Web systems are consequently very different from those for more conventional software systems. Apart from an increased emphasis on user interactions and the underpinning content, they also reflect a blurring of the boundaries between requirements, specifications and designs in the development process. In this paper we offer an iterative model for Web systems development that incorporates the user of partial design prototypes as a crucial stage in resolving requirements. This is derived from an analysis of the results of a survey of commercial Web practice. In particular, we explore what this data tells us about the nature of Web specifications, particularly looking at what is typically specified and the stage at which certain characteristics emerge within the evolving specification. The results support the hypothesis that within commercial Web development, design artifacts become a crucial element in supporting client understanding and driving the formulation of requirements.