REU.2 Management of Products for Reuse

• O1 Products for reuse are selected using defined criteria.
• O2 Products for reuse are analyzed for portability and interoperability.
• O3 Limitations for reuse are defined and communicated.
• O4 Products for reuse are verified.
• O5 Products for reuse are provided to affected parties.
• O6 Communication mechanism is established with the reuse product provider.

BP2 Analyze the reuse capability of the product. ( O2 )

Analyze the designated target architecture and the product to be reused to determine its applicability in the target architecture according to relevant criteria.
Note 2: Examples for criteria can be requirements compliance, verifiability of the product to be reused in the target architecture, or portability/interoperability.

Linked Knowledge Nuggets:
arrow_forward "What key aspects must be considered when reusing components in development projects?"

person Author: Process Fellows
Here comes an exemplary list of aspects to be considered when re-using an already existing component for a new system development:

1. Compatibility: The reused component must be technically and functionally compatible with the new system environment. This includes interfaces, data formats, protocols, and performance characteristics.
2. Requirements Alignment: The component must fulfill the current system’s requirements. Even if it worked in a previous context, it may not meet the specific needs or constraints of the new system. Example: Maybe there are now higher expectations regarding performance of some functions, while this was not so important in previous developments.
3. Traceability and Documentation: Clear documentation and traceability of the component’s design, behavior, and limitations are essential. This helps in understanding how it fits into the new system and supports verification and validation.
4. Licensing and Intellectual Property: Legal aspects such as licensing terms, usage rights, and intellectual property must be checked, especially when using third-party or open-source components.
5. Quality and Maturity: The component should have a proven quality level and maturity. Reusing a component with known issues or insufficient testing can introduce risks. Especially in automotive industry, consider safety aspects: Is it possible to re-use the component in the new environment, if it was development in the past on a "lower" safety integrity level?
6. Change Management: If the reused component is updated or modified, changes must be managed carefully to avoid unintended side effects in the new system.
7. Integration and Testing: Even if a component is reused, it must be integrated and tested within the new system context to ensure it behaves as expected.