The AGILE SOFTWARE PRODUCT LINE AUTOMOTIVE - ASSESSMENT MODEL




Purpose

The purpose of Product Line Architecture HC is to provide a suitable software architecture to enable the implementation of several software variants for different products with a high degree of software reuse.


Outcomes

Process related Outcome - Base Practices - Work Products

ProcO_01.01 A software product line architecture is defined that enables the development of various software variants for different products.
BP_ProcO_01.01 Define a software product line architecture. Ensure that a software product line is used for development and that the software product line architecture is able to generate various software variants for different products and different markets.
A_04-02 Domain architecture
A_04-04 Software architectural design
A_08-17 Reuse plan
A_08-17 Reuse proposal
A_19-05 Reuse Strategy
A_19-05 System requirements specification
ProcO_01.02 The software product line architecture supports a distributed development.
BP_ProcO_01.02 Use only one software product line. Ensure that only one software product line is used for the worldwide development of a product.
A_08-17 Reuse plan
A_08-17 Reuse proposal
A_19-05 Reuse Strategy
A_19-05 System requirements specification
ProcO_01.03 The consistency and bidirectional traceability between software requirements, software units and software architecture is supported by a toolchain.
BP_ProcO_01.03 Manage the SPL by means of suitable tools. Ensure traceability and consistency between software requirements, software units and the software architecture by means of suitable tools.
A_13-22 Traceability record
A_14-01 Change History
A_14-01 Tracking system
A_14-01 Work product list
ProcO_01.04 The software architecture is agreed and communicated to all affected parties.
BP_ProcO_01.04 Distribute software product line architecture. Ensure that the worldwide software product line is efficient. Decisions on the software product line architecture are reviewed before they are distributed. Ensure that all involved parties receive the information.
A_08-17 Reuse plan
A_08-17 Reuse proposal
A_11-05 Software unit
A_13-04 Documentation Plan
A_13-04 Configuration management record
A_13-04 Progress status record
A_13-04 Proposal review record
ProcO_01.05 Timeframes to refactor the software architecture are granted on demand within the development process.
BP_ProcO_01.05 Grant refactoring time. Ensure that additional timeframes are provided to conduct the refactoring of the architecture.
A_19-05 Reuse Strategy
A_19-05 System requirements specification
ProcO_01.06 Standardized interfaces for software units are defined.
BP_ProcO_01.06 Define a standardized interface between software units. Ensure that interfaces are standardized to enable the development to replace software parts easily.
A_04-04 Software architectural design
A_04-06 System architectural design
A_11-05 Software unit
A_17-08 Interface requirements specification
A_17-08 Software requirements specification
ProcO_01.07 The software architecture is compliant with safety regulations.
BP_ProcO_01.07 Analyze and consider safety regulations. Ensure that safety regulations are addressed in the software architecture. Ensure that development decisions, addressing the safety regulations are documented to retain the traceability and consistency between software requirements, software units and the software architecture.
A_07-05 Project measure
A_07-05 Quality measure
A_07-05 Risk measure
A_15-01 Analysis Report
A_15-01 Risk analysis report
ProcO_01.08 The software architecture is compliant with security regulations.
BP_ProcO_01.08 Analyze and consider security regulations . Ensure that security regulations are addressed in the software architecture. Ensure that development decisions, addressing the security regulations are documented to retain the traceability and consistency between software requirements, software units and the software architecture.
A_07-05 Project measure
A_07-05 Quality measure
A_07-05 Risk measure
A_15-01 Analysis Report
A_15-01 Risk analysis report


Product related Outcome - Process Attributes - Work Products

ProdO_01.01 A high modularity of software components is achieved.
PA_ProdO_01.01 The software architecture shall be modular. Ensure that parts of the software can be replaced or reused without affecting other parts of the software, by means of loosely coupling between software units.
A_08-17 Reuse plan
A_08-17 Reuse proposal
A_17-08 Interface requirements specification
A_17-08 Software requirements specification
ProdO_01.02 The software architecture is open to changes, refactoring is possible.
PA_ProdO_01.02 The software architecture shall be open to change. Ensure that the software architecture is not a monolithic architecture, by means of a modular architecture structure that is capable to manage loosely coupled software units.
A_04-04 Software architectural design
A_04-06 System architectural design
ProdO_01.03 Fast changes in requirements are supported by the software architecture.
PA_ProdO_01.03 The software architecture shall provide the possibility to include fast changing requirements. Ensure that the architecture of the software can deal with fast changing requirements, by means of standardized interfaces between software units and a modular architecture.
A_04-04 Software architectural design
ProdO_01.04 Hardware restrictions and limited hardware resources are addressed by the software architecture.
PA_ProdO_01.04 The software architecture shall be hardware independent. Ensure that the software managed by SPL is working on various hardware versions and that the selected architecture is independent from the selected hardware, by means of a scalable architecture according to the hardware.
A_04-04 Software architectural design
A_04-06 System architectural design