Abstract
The terms and primary concepts of reuse have been introduced, discussed, and exemplified at the end of the last chapter. The present chapter will review aspects of application, architecture and organization, and assurance and legal issues of reuse, based on IEC/PAS 62814 [16].
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Recommended Further Reading
Ezran, M., Morisio, M., Tully, C.: Practical Software Reuse. Springer Practitioner Series (2002)
IEC 62628:2012 guidance on software aspects of dependability
Petersen, K., Badampudi, D., Syed, M.A.S., Wnuk, K., Gorschek, T., Papatheocharous, E., Axelsson, J., Sentilles, S., Crnkovic, I., Cicchetti, A.: Choosing component origins for software intensive systems: in-house, COTS, OSS or outsourcing?—a case survey. IEEE Trans. Softw. Eng. 44 (2018). https://doi.org/10.1109/TSE.2017.2677909
References
Acar, H., Benfenatki, H., Gelas, J.-P., da Silva, C.F., Alptekin, G., Benharkat, A.-N., Parisa Ghodous, P.: Software greenability: a case study of cloud-based business applications provisioning. In: Proceedings of IEEE 11th International Conference on Cloud Computing (CLOUD), pp. 875–878 (2018). https://doi.org/10.1109/CLOUD.2018.00125.hal-01887065
AIAA R-013-1992: Recommended practice: software. Reliability (1992)
Badareen, A.B., Selamat, M.H., Jabar, M.A., Din, J., Turaev, S.: Reusable software component life cycle. Int. J. Comput. 5(2), 191–199 (2011). Available at http://www.naun.org/journals/computers/19-863.pdf
Dimov, A., Punnekkat, A.: On the estimation of software reliability of component-based dependable distributed systems. In: Proceedings QoSA-SOQUA 2005, LNCS 3712, pp. 171–187. Springer, Berlin
Frakes, W.B., Isoda, S., Success factors of systematic reuse. IEEE Softw. 11(5), 14–19 (1994). Available at http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=311045
Hossain, S.: Rework and reuse effects in software economy. Glob. J. Comput. Sci. Technol. C Softw. Data Eng. 1(4) (2018)
IEC 62309: Dependability of products containing reused parts—requirements for functionality and test (2004)
IEC 62628:2012 Guidance on software aspects of dependability
ISO/IEC 12207: 2017 systems and software engineering—software life cycle processes
IEEE 1633: 2016, Recommended practice for software reliability
IEEE 1517-2010: IEEE standard for information technology, system and software life cycle processes, reuse processes (2010)
ISO/IEC/IEEE 42010:2011: Systems and software engineering—architecture description
IEC/PAS 62814-2012: Dependability of Software Products Containing Reusable Components—Guidance for Functionality and Tests (withdrawn, however available)
IEC 61508:2010: Functional safety of electrical/electronic/programmable electronic safety-related systems: Part 1: General requirements, Part 2: Requirements for electrical/electronic/programmable electronic safety-related systems, Part 3: Software requirements, Part 3-1: Software requirements—reuse of pre-existing software elements to implement all or part of a safety function (2016), Part 4: Definitions and abbreviations
Mili, A., Chmiel, S.F., Gottumukkala, R., Zhang, L.: Managing software reuse economics: an integrated ROI-based model. Ann. Softw. Eng. 11, 175–218 (2001)
Microsoft, Accenture and WSP environment & energy study. https://news.microsoft.com/2010/11/04/microsoft-accenture-and-wsp-environment-energy-study-shows-significant-energy-and-carbon-emissions-reduction-potential-from-cloud-computing/
Oracle practitioner guide, determining ROI of SOA through reuse (2012)
Poulin, J.S., Caruso, J.M., Hancock, D.R.: Business case for software reuse. IBM Syst. J. 32(4), 567–594 (1993)
Author information
Authors and Affiliations
Corresponding author
Key Points, Exercises, Recommended Further Reading, References
Key Points, Exercises, Recommended Further Reading, References
1.1 Key Points
-
Architecture of a system to be built by reuse is crucial; it necessitates components to be built in.
-
Characteristics of a component to be reused is crucial.
-
Reusable components need to be tested before storage and retested before usage.
-
The development process of components to be reused differs from the development of one-way components.
-
The development process of systems to be built by reusable components differs from the development of conventional systems.
-
Validation , re-validation , and reliability of software reuse each have their own rules, technically and legally.
1.2 Exercises
-
1.
Which architectural form is appropriate for reusability?
-
2.
What are the differences between the pre-store and pre-use characteristics of reusable components?
-
3.
Are there any specific features of systems built by reuse?
-
4.
What are the differences between the development of reusable components and one-way components?
-
5.
What are the differences between the development of systems built by reuse and conventional systems?
-
6.
Name the differences between the validation assurance of reusable components and those of conventional systems.
-
7.
List the differences in the legal aspects of reusable components and conventional systems.
Rights and permissions
Copyright information
© 2021 The Author(s), under exclusive license to Springer Nature Switzerland AG
About this chapter
Cite this chapter
Belli, F., Quella, F. (2021). Application Aspects and Organization of Dependable Software Reuse. In: A Holistic View of Software and Hardware Reuse. Studies in Systems, Decision and Control, vol 315. Springer, Cham. https://doi.org/10.1007/978-3-030-72261-6_2
Download citation
DOI: https://doi.org/10.1007/978-3-030-72261-6_2
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-030-72260-9
Online ISBN: 978-3-030-72261-6
eBook Packages: Earth and Environmental ScienceEarth and Environmental Science (R0)