- 2068 Chaitra · 2.5 marks
- Year not given · 4 marks
Short note: component-based software engineering
Short answer
Component-based software engineering builds systems by composing independent executable components specified by provides and requires interfaces. It relies on component standards and middleware, with a development process that adapts requirements to available components. Benefits are faster development, lower cost, and reliable parts; problems include trusting components, certification, and emergent properties.
Write a short note on component based software engineering.
Component-based software engineering (CBSE) is an approach to software development that relies on reuse of independent, executable software components. Systems are built by composing components that are defined by their interfaces, rather than writing all code from scratch. It grew from the failure of object-oriented development to give large-scale reuse, since single classes are too detailed and specific.
Component characteristics: standardised (conform to a component model), independent, composable (all interaction through interfaces), deployable (run without being compiled in) and documented.
Each component has two interfaces:
- Provides interface – services the component offers to others.
- Requires interface – services it needs from other components.
+-----------------+
provides | | requires
O--------| Component |--------C
| |
+-----------------+
Essentials of CBSE
- Independent components fully specified by their interfaces.
- Component standards / models (e.g. EJB, .NET, CORBA Component Model) that define interfaces, packaging and deployment.
- Middleware that handles component communication and services like transactions and security.
- A development process geared to reuse: outline requirements → identify candidate components → modify requirements to suit available components → architectural design → identify more components → compose components.
Benefits: faster development, lower cost, reliable tested parts, easier maintenance. Problems: trusting components without source code, certifying quality, predicting emergent properties of the composed system, and trade-offs between requirements and available components.
✓ Answer checked by Claude Sonnet 5.5
Related questions
- Objectives of FTR; cleanroom software engineering · Software Engineering, chapter 9
- Application framework versus component reuse · Software Engineering, chapter 5
- Component, integration and release testing · Software Engineering, chapter 8
- Short note: generator-based reuse · Software Engineering, chapter 5
- Software errors and their impact on cost · Software Engineering, chapter 7 · asked 2×
- Software reliability and reliability models · Software Engineering, chapter 9 · asked 2×
- Microwave radiation hazards based on radiation fields · RF and Microwave Engineering, chapter 7 · asked 2×
- Water-based diseases · Water Supply Engineering, chapter 4 · asked 2×
- Short note: Sulphur based polymers · Engineering Chemistry, chapter 4
- Short note: Planning software, MS Project · Project Engineering, chapter 3 · asked 2×