Difference between revisions of "Component-based software engineering"
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) |
||
| Line 1: | Line 1: | ||
'''Component-based software engineering''' ('''CBSE'''), also known as '''component-based development''' ('''CBD'''), is a branch of [[software engineering]] that emphasizes the [[separation of concerns]]. | '''Component-based software engineering''' ('''CBSE'''), also known as '''component-based development''' ('''CBD'''), is a branch of [[software engineering]] that emphasizes the [[separation of concerns]]. | ||
| − | |||
| − | |||
== Description == | == Description == | ||
Revision as of 10:05, 4 February 2016
Component-based software engineering (CBSE), also known as component-based development (CBD), is a branch of software engineering that emphasizes the separation of concerns.
Contents
Description
It is a reuse-based approach to defining, implementing and composing loosely coupled independent components into systems.
Benefits
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.
Software engineering practitioners regard components as part of the starting platform for service-orientation.
Web services
Components play this role, for example, in web services
More recently, components have played a role in service-oriented architectures (SOA), whereby a component is converted by the web service into a service and subsequently inherits further characteristics beyond that of an ordinary component.
Event-driven architecture
Components can produce or consume events and can be used for event-driven architectures.
See also
- Design by contract
- Event-driven architecture
- Separation of concerns
- Service-oriented architecture
- Software engineering
- Structured programming
- Web service
External links
- Component-based software engineering @ Wikipedia
