This document defines system engineering and management requirements for the life cycle of websites, including strategy, design, engineering, testing and validation, and management and sustainment for intranet and extranet environments. This document applies to those using web technology to present information and communications technology (ICT) information, such as information for users of systems and services, plans and reports for systems and software engineering projects, and documentation of policies, plans, and procedures for IT service management. This document provides requirements for website owners and website providers, managers responsible for establishing guidelines for website development and operations, website engineers, designers, developers, and operations and maintenance staff, who can be external or internal to the website owner's organization. It applies to websites for public access and for limited access, such as for users, customers, and subscribers seeking information on IT systems, products and services. The requirements and recommendations in this document address the following aspects of usability of informational websites and ease of maintenance of managed website operations: a) locating relevant and timely information; b) applying information security management; c) facilitating accessibility and ease of use; d) providing for consistent and efficient development and maintenance practices. This document is not particularly applicable to websites used primarily for marketing or sales, to deliver instructional material (tutorials), or to provide graphical user interfaces (GUI) for business or consumer transactional application processing. However, this document can provide useful insights for managing such sites. This document does not address vendor and product considerations for website engineering and management. This document does not include specifications for application development tools, programming and scripting languages used for websites, metadata tags, or protocols for network communications. It does not address tools or systems used for management or storage of information content (data, documents) that can be presented on websites. This document does not address the design and architecture of software and systems supporting the Internet.
- Standard Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
- Status
- Active Standard
- PAR Approval
- 2020-09-24
- Superseding
- 23026-2015
- Board Approval
- 2023-06-05
- History
-
- Published:
- 2023-07-18
Working Group Details
- Society
- IEEE Computer Society
- Standard Committee
- C/S2ESC - Software & Systems Engineering Standards Committee
- Working Group
-
23026 - WG23026 Engineering and management of web sites
- IEEE Program Manager
- Patricia Roder
Contact Patricia Roder - Working Group Chair
- Annette Reilly
Other Activities From This Working Group
Current projects that have been authorized by the IEEE SA Standards Board to develop a standard.
No Active Projects
Standards approved by the IEEE SA Standards Board that are within the 10-year lifecycle.
No Active Standards
These standards have been replaced with a revised version of the standard, or by a compilation of the original active standard and all its existing amendments, corrigenda, and errata.
2001-2002
IEEE Recommended Practice for the Internet - Web Site Engineering, Web Site Management and Web Site Life Cycle
Replaced by ISO/IEC 23026: 2006. Recommended practices for World Wide Web page engineering for Intranet and Extranet environments, based on World Wide Web Consortium (W3C(R) ) and related industry guidelines,are defined in this recommended practice. This recommended practice does not address stylistic considerations or human-factors considerations in web page design beyond limitations that reflect good engineering practice.
23026-2006
ISO/IEC 23026:2006, Software Engineering---Recommended Practice for the Internet---Web Site Engineering, Web Site Management, and Web Site Life Cycle
This document defines recommended practices for World Wide Web page engineering for Intranet and Extranet environments, based on World Wide Web Consortium (W3C) and related industry guidelines. This recommended practice does not address stylistic considerations or human-factors considerations in Web page design beyond limitations that reflect good engineering practice. Annex B contains topics which are not sufficiently mature or where there are not specific recommendations for inclusion in the current issue of this recommended practice.
23026-2015
ISO/IEC/IEEE International Standard - Systems and software engineering - Engineering and management of websites for systems, software, and services information
This standard defines system engineering and management requirements for the life cycle of websites, including strategy, design, engineering, testing and validation, and management and sustainment for Intranet and Extranet environments. The goal of this standard is to improve the usability of informational websites and ease of maintenance of managed Web operations in terms of locating relevant and timely information, applying information security management, facilitating ease of use, and providing for consistent and efficient development and maintenance practices. .It applies to those using web technology to present information and communications technology (ICT) information, such as user documentation for systems and software, life-cycle documentation for systems and software engineering projects, and documentation of policies, plans, and procedures for IT service management. This standard provides requirements for website owners and website providers, managers responsible for establishing guidelines for website development and operations, for software developers and operations and maintenance staff who may be external or internal to the website owner's organization. It applies to websites for public access and for limited access, such as for users, customers, and subscribers seeking information on IT products and services. It includes increased emphasis on the human factors concerns for making information easily retrievable and usable for the intended audience. It focuses on vendor- and product-independent considerations.
These standards have been removed from active status through a ballot where the standard is made inactive as a consensus decision of a balloting group.
No Inactive-Withdrawn Standards
These standards are removed from active status through an administrative process for standards that have not undergone a revision process within 10 years.
No Inactive-Reserved Standards