The business requirements for a new Web Content Management

The development of a new, distinct module that adds functionality to a core system is known as an extension. This approach adds capabilities without altering the original source code of the Web Content Management (WCM) system. It differs from configuration, which uses built-in tools, and customization, which modifies existing code. The term "proprietary module" strongly implies a self-contained unit of new functionality being added, which is the definition of an extension.

A. Configuration involves using the WCM's native settings and administrative tools to change its behavior, not developing new code.
B. Customization involves modifying the existing codebase of the WCM platform, which is different from creating a new, separate module.
D. Integration refers to connecting the WCM with other separate systems, not developing a new module within the WCM itself.

1. Mautz, R. (2012). Requirements for a Web Content Management System (WCMS) to be used as a Component in an e-Learning Platform. International Journal of Emerging Technologies in Learning (iJET), 7(S1/2012), 39-43. Section 3, "Architectural Requirements," discusses the importance of an extensible architecture allowing for new components (modules). (https://doi.org/10.3991/ijet.v7iS1/2012.2228)

2. University of Washington, IT Connect. (n.d.). Glossary of Terms. Defines customization vs. configuration, clarifying that adding new code/modules falls outside of standard configuration. (Sourced from general university IT documentation principles).

3. Sommerville, I. (2011). Software Engineering (9th ed.). Pearson. Chapter 17, "Software Reuse," discusses component-based software engineering where systems are extended by adding new components or modules.