Difference between revisions of "Componentization"
(Componentization is the process of atomizing (breaking down) resources into separate reusable packages that can be easily recombined.) |
m (The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).) |
||
| Line 1: | Line 1: | ||
| − | Componentization is the process of atomizing (breaking down) resources into separate reusable packages that can be easily recombined. Simply put, software componentization is when you break your software system down into smaller easily identifiable pieces that have well-defined interfaces – and you do this in a specific way. | + | Componentization is the [[process]] of atomizing (breaking down) resources into separate reusable packages that can be easily recombined. Simply put, [[software]] componentization is when you break your software [[system]] down into smaller easily identifiable pieces that have well-defined interfaces – and you do this in a specific way. |
The promise of software componentization is five-fold:<br /> | The promise of software componentization is five-fold:<br /> | ||
| − | *Complexity Management: having a manageable unit of software functionality enables design time tools and run time tools to help developers divide and conquer their increasingly unwieldy device software. | + | *Complexity [[Management]]: having a manageable unit of software functionality enables [[design]] time tools and run time tools to help developers divide and conquer their increasingly unwieldy [[device]] software. |
| − | *Product Flexibility: the ability to easily replace a component when product requirements change provides product flexibility. | + | *[[Product]] Flexibility: the ability to easily replace a component when product requirements change provides product flexibility. |
*Product Reliability: matured components that meet well-defined specifications and get re-used increases product reliability. | *Product Reliability: matured components that meet well-defined specifications and get re-used increases product reliability. | ||
| − | *Time-to-Market: re-use of components in new products accelerates product development and lowers cost | + | *Time-to-[[Market]]: re-use of components in new products accelerates product development and lowers cost |
| − | *Collaboration: a common format for software implementations helps multiple companies collaborate more easily.<ref>What is Software Componentization? [http://blogs.windriver.com/koning/2006/09/components.html Windriver]</ref> | + | *[[Collaboration]]: a common format for software implementations helps multiple companies collaborate more easily.<ref>What is Software Componentization? [http://blogs.windriver.com/koning/2006/09/components.html Windriver]</ref> |
===Reference=== | ===Reference=== | ||
<references /> | <references /> | ||
Revision as of 14:44, 6 February 2021
Componentization is the process of atomizing (breaking down) resources into separate reusable packages that can be easily recombined. Simply put, software componentization is when you break your software system down into smaller easily identifiable pieces that have well-defined interfaces – and you do this in a specific way.
The promise of software componentization is five-fold:
- Complexity Management: having a manageable unit of software functionality enables design time tools and run time tools to help developers divide and conquer their increasingly unwieldy device software.
- Product Flexibility: the ability to easily replace a component when product requirements change provides product flexibility.
- Product Reliability: matured components that meet well-defined specifications and get re-used increases product reliability.
- Time-to-Market: re-use of components in new products accelerates product development and lowers cost
- Collaboration: a common format for software implementations helps multiple companies collaborate more easily.[1]