Difference between revisions of "Component-Based Development (CBD)"
(Component-Based Development (CBD) is a branch of software engineering that emphasizes the separation of concerns in respect of the wide-ranging functionality available throughout a given software system.) |
m (The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).) |
||
Line 1: | Line 1: | ||
− | Component-Based Development (CBD) also known as Component-based software engineering (CBSE), is a branch of software engineering that emphasizes the separation of concerns in respect of the wide-ranging functionality available throughout a given software system. It is a reuse-based approach to defining, implementing and composing loosely coupled independent components into systems. This practice aims to bring about an equally wide-ranging degree of benefits in both the short-term and the long-term for the software itself and for organizations that sponsor such software.<ref>Definition of Component-Based Development (CBD) [https://en.wikipedia.org/wiki/Component-based_software_engineering Wikipedia]</ref> | + | Component-Based Development (CBD) also known as Component-based [[software]] engineering (CBSE), is a branch of software engineering that emphasizes the separation of concerns in respect of the wide-ranging functionality available throughout a given software [[system]]. It is a reuse-based approach to defining, implementing and composing loosely coupled independent components into systems. This practice aims to bring about an equally wide-ranging degree of benefits in both the short-term and the long-term for the software itself and for organizations that sponsor such software.<ref>Definition of Component-Based Development (CBD) [https://en.wikipedia.org/wiki/Component-based_software_engineering Wikipedia]</ref> |
===References=== | ===References=== | ||
<references/> | <references/> |
Latest revision as of 14:43, 6 February 2021
Component-Based Development (CBD) also known as Component-based software engineering (CBSE), is a branch of software engineering that emphasizes the separation of concerns in respect of the wide-ranging functionality available throughout a given software system. It is a reuse-based approach to defining, implementing and composing loosely coupled independent components into systems. This practice aims to bring about an equally wide-ranging degree of benefits in both the short-term and the long-term for the software itself and for organizations that sponsor such software.[1]