The AGILE SOFTWARE PRODUCT LINE AUTOMOTIVE - ASSESSMENT MODEL


The Overview

The ASLPA model aims at integrating agile software development into the development of automotive software product lines. Characteristics for automotive software development are high cost pressure, test and validation under real-time conditions and a high amount of software variants. Safety-critical applications on the one hand and cost pressure on the used hardware on the other hand are encountered in the automotive domain. Furthermore, strict processes for car development have to be considered. Automotive functions must be verified by long term field tests and endurance tests that are enforced by law. The ASPLA model consists of seven topic areas which are named as honeycombs (HC). The honeycombs may be used by the development departments of automotiveembedded software, when responding and delivering software, including the engineering processes needed for specification, design, development, integration and testing. The primary seven topic areas consists of the following honeycombs:


The internal structure of the Honeycombs

Purpose: The purpose statement contains the unique functional objectives of the Honeycomb when performed in a particular environment.
Outcomes: For each purpose statement a list of specific outcomes is associated.
Product related Outcomes: Outcomes are expected positive results of the development performance which are induced by properties of the product.
Process related Outcomes: Outcomes are expected positive results of the process performance which are related to the proper implementation of the development process.




Honeycomb Performance Indicators:

The performance indicators (Product Attribute, Work Products, Base Practices) relate to one or more Honeycomb-outcomes. The indicators are used for judging the performance of a honeycomb within an assessment. During an assessment, the performance indicators are supposed to be a quickly accessible information source. However, the indicators are not a "strict must" nor are they normative for organizations. They represent an example structure only, the assessor can use.
Product Attributes: The Product Attributes define the characteristics of the product to be developed and represent product oriented indicators.
Work Products: Work Products represent result oriented indicators. They indicate a successful achievement of Product related Outcomes and Process Related Outcomes.
Base Practices: Base Practices represent activity-oriented indicators. They indicate a successful achievement of the Process related Outcomes.

Relations:

1. The Honeycomb – Outcomes are the results of a successful implementation to fulfill the Honeycomb – Purpose.
2. The Honeycomb – Purpose is characterized by the Honeycomb – Outcomes.
3. Product Attributes indicate a successful achievement of Product related Outcomes.
4. Product related Outcomes are supported by the Product Attributes.
5. Work Products indicate a successful achievement of Product related Outcomes.
6. Product related Outcomes affect the Work Products.
7. Work Products indicate a successful achievement of Process related Outcomes.
8. Process related Outcomes lead to Work Products.
9. Base Practices indicate a successful achievement of Process related Outcomes.
10. Process related Outcomes are supported by Base Practices.