The Community for Technology Leaders
RSS Icon
Issue No.06 - November/December (2008 vol.25)
pp: 42-49
Slinger Jansen , Utrecht University
Sjaak Brinkkemper , Utrecht University
Ivo Hunink , Utrecht University
Cetin Demir , Utrecht University
Reusing software components and services lets software vendors quickly develop innovative applications and products. According to current literature and experience reports, software development can't integrate functionality successfully without formal component and service selection and integration procedures. Here, the authors discuss two start-up companies that have each developed a product using a pragmatic approach to third-party functionality reuse and integration. Developing products and services pragmatically places requirements on the relationship between the software developer and the third-party functionality provider. The authors discuss the architectural impacts of decisions made during integration. These experiences show other software developers how to speed up product development with minimal risk.
opportunistic reuse, software extension mechanisms, pragmatic reuse, COTS, services, product software
Slinger Jansen, Sjaak Brinkkemper, Ivo Hunink, Cetin Demir, "Pragmatic and Opportunistic Reuse in Innovative Start-up Companies", IEEE Software, vol.25, no. 6, pp. 42-49, November/December 2008, doi:10.1109/MS.2008.155
1. R. van Ommering, "Software Reuse in Product Populations," IEEE Trans. Software Eng., vol. 31, no. 7, 2005, pp. 537–550.
2. M.F. Dunn and J.C. Knight, "Software Reuse in an Industrial Setting: A Case Study," Proc. 13th Int'l Conf. Software Eng., IEEE CS Press, 1991, pp. 329–338.
3. E. Henry and B. Faller, "Large-Scale Industrial Reuse to Reduce Cost and Cycle Time," IEEE Software, vol. 12, no. 5, 1995, pp. 47–53.
4. S. Morad and T. Kuflik, "Conventional and Open Source Software Reuse at Orbotech—an Industrial Experience," Proc. Int'l Conf. Software—Science, Technology, and Eng. (SwSTE 05), IEEE CS Press, 2005, pp. 110–117.
5. S. McConnell, Rapid Development: Taming Wild Software Schedules, Microsoft Press, 1996.
6. A. Tomer et al., "Evaluation Software Reuse Alternatives: A Model and Its Application to an Industrial Case Study," IEEE Trans. Software Eng., vol. 30, no. 9, 2004, pp. 601–612.
7. S. Ajmani, B. Liskov, and L. Shrira, "Modular Software Upgrades for Distributed Systems," Proc. European Conf. Object-Oriented Programming (ECOOP 06), IEEE Press, 2006, pp. 452–476.
8. C.W. Krueger, "Software Reuse," ACM Computing Surveys, vol. 24, no. 2, 1992, pp. 131–181.
9. C. Szyperski, Component Software: Beyond Object-Oriented Programming, Addison-Wesley Professional, 1997.
10. M. Shaw, R. DeLine, and G. Zelesnik, "Abstractions and Implementations for Architectural Connections," Proc 3rd Int'l Conf. Configurable Distributed Systems, IEEE Press, 1996, pp. 2–10.
11. W. Tracz, "Software Reuse Myths Revisited," Proc. 16th Int'l Conf. Software Eng. (ICSE 94), IEEE CS Press, 1994, pp. 271–272.
12. S. Jansen et al., "Integrated Development and Maintenance for the Release, Delivery, Deployment, and Customization of Product Software: A Case Study in Mass-Market ERP Software," J. Software Maintenance, vol. 18, no. 2, 2006, pp. 133–151.
4 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool