What is the primary purpose of the practice known as Assess reuse risks and costs?

What is the primary purpose of the practice known as Assess reuse risks and costs?

• A. A software best practice that evaluates the feasibility of reusing existing components.
• B. A procurement policy for deploying hardware in the field.
• C. A financial model for evaluating new software licenses.
• D. A project risk register focusing on schedule delays.

Answer: (A)

The core idea is to systematically evaluate whether existing software components can be reused in a project and whether doing so is feasible and cost-effective. This practice looks beyond just finding something that works; it weighs the technical and financial implications of reuse. Consider whether a component fits the target architecture, interfaces, and dependencies; whether it will require significant modification, integration effort, or reengineering; and how it affects performance, security, and maintainability. It also weighs licensing terms, support availability, and the risk of obsolescence. The aim is to determine if reusing assets saves time and money without introducing unacceptable risks, or if building anew or adapting components would be a better choice. This is distinct from policies about hardware procurement, a general financial model for licenses, or a broad project risk register focused on schedule delays, which do not specifically address the feasibility and cost implications of reusing existing software components.

The core idea is to systematically evaluate whether existing software components can be reused in a project and whether doing so is feasible and cost-effective. This practice looks beyond just finding something that works; it weighs the technical and financial implications of reuse. Consider whether a component fits the target architecture, interfaces, and dependencies; whether it will require significant modification, integration effort, or reengineering; and how it affects performance, security, and maintainability. It also weighs licensing terms, support availability, and the risk of obsolescence. The aim is to determine if reusing assets saves time and money without introducing unacceptable risks, or if building anew or adapting components would be a better choice.

This is distinct from policies about hardware procurement, a general financial model for licenses, or a broad project risk register focused on schedule delays, which do not specifically address the feasibility and cost implications of reusing existing software components.