Home > Articles > Web Development

Web Specifications: Rhetoric vs. Reality

Although many Web-development companies assure clients that they have certain development processes in place, they sometimes don't back up their claims. David Lowe (pictured) and Vassiliki Veros Elliott report the findings of their study on the real vs. reported processes of Web-development organizations.
Like this article? We recommend

Web systems have a unique combination of characteristics that differentiate them from more conventional applications. In particular, they tend to have these characteristics:

  • Complex but open component-based architectures

  • Tighter linkage between the business needs and the underlying technology

  • Increased importance of usability and quality attributes (because applications are typically more visible externally)

  • Rapidly changing technologies,

A lack of detailed understanding of the client's own needs for the system and the potential impact within the organization

There is a growing awareness in both the research literature and commercial practice that these differences require changes in the development process that is adopted). One of the key areas impacted is the way the needs of clients are understood and system specifications are developed. Clients are often less aware of aspects such as the potential capabilities and limitations of the technology, as well as the ways in which possible solutions can change their business practices and models.

As a result, the initial stages of the development process often become highly exploratory, with the aim of using partial designs, prototypes, user focus groups, and similar tools to develop an understanding of client needs and how they relate to possible solution architectures. The latter stages of development then adopt an incremental evolutionary development of the system. This is illustrated in Figure 1.

Figure 1 Figure 1 Typical Web-development process.

In an earlier work (see the Journal of Web Engineering, "Client Needs and the Design Process in Web Projects," by D. Lowe and J. Eklund, vol. 1, p. 23–36), we investigated these specific issues in more detail. In particular, we utilized a comprehensive set of industry surveys and interviews, and analyzed existing commercial Web specifications. The result was an improved understanding of the issues impacting the specification activities in commercial Web-development projects. We also identified the elements that should typically be addressed within a Web specification.

One side issue that was hinted at in this earlier work was the perceived significance that many organizations (both Web developers and their clients) put on the existence of an appropriate development process. In particular, some anecdotal evidence showed that clients often saw the existence of a process as indicative of an improved development capability. Developers recognized this and subsequently realized the potential importance of ensuring that their clients (or prospective clients) were told of their claimed process—whether the Web-development company actually followed that process or not.

As a result, many Web-development organizations claim to utilize a process. However, there is a difference between claiming to use a process and actually adopting that process in a meaningful way. In this article, we analyze the available data from our earlier work to develop an understanding of industry practice for how descriptions of processes are used. In particular, we examine whether the publicly described processes reflect the true process as implemented or whether they predominantly serve as a marketing tool that is not reflected in actual practice.

We first consider the background, focusing on just why a modified development process might be appropriate. Then we look at the research approach that we adopted to gain insights into whether commercial practice reflects stated processes. We also analyze the collected data and describe the subsequent inferences. Finally, we explore future work and describe relevant conclusions.


A small but growing body of literature examines the differences between Web systems and conventional software systems. In general, this literature identifies unique characteristics of Internet-enabled systems that reflect technical, usability, and organizational requirements. These include aspects such as a tighter linkage between the business needs and the underlying technology (typically through a more visible system architecture), increased importance of usability and quality attributes (because applications are typically more visible externally), open modularized architectures, and rapidly changing technologies.

Many of the developmental characteristics, however, are more significant. In particular, initial client uncertainty, rapidly evolving client needs, short delivery time frames, and fine-grained evolution and maintenance all are likely to impact the approach to the development. The first of these typically leads to the need for an initial exploration of the problem before effective specification and scoping can occur. We often end up with a process that might be referred to as design-driven requirements, as developers use partial solutions to clarify potential systems with the client.

Once we have an initial specification, the need for rapid deployment and the likelihood of ongoing change make an incremental process involving tight interaction with the client appropriate—hence the claims by some authors that approaches such as eXtreme Programming (XP) are appropriate. The result is typically a process such as the one shown in Figure 1.

Although considerable work has been done on Web design methods and models, only minimal research has focused on the broader Web-development processes. The research that does exist tends to be relatively prescriptive and focuses on management of the technological infrastructure). One exception to this is our work on extensions to the OPEN (Object Process, Environment, and Notation) process framework to make it more suitable for supporting Web-development process (for details on this work, have a look at "OPEN Process Support for Web Development," by B. Henderson-Sellers, D. Lowe, and B. Haire, in the Annals of Software Engineering, vol. 13, p. 163–202). In particular, this work has identified additional tasks, techniques, and roles that are required to support Web development. Although this work provides a framework for describing Web-development processes, it does not provide insights into the actual structure of processes as they are (or should be) carried out.

Nevertheless, both commercial developers and clients recognize that adopting an appropriate development approach can have a major impact on the quality and cost of the systems being developed. As such, many Web-development organizations ensure that their development and adoption of a suitable process is highlighted in the information available to their clients. Although the form of these processes varies considerable, their existence is typically viewed as important.

In our earlier work, we investigated the issues that impact the specification activities in commercial Web-development projects and identified elements that should be addressed within a Web specification. In this article, we consider the related issue of the extent to which claimed processes appear to be adopted in carrying out actual projects. In other words, we consider the extent to which the described processes are simply useful marketing rhetoric, and to what extent clients can rely on the veracity of the claims.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020