Software Product Line Engineering Method-architecture of BAPO)

ArticleDirectory

• Three aspects

Family Evaluation Framework (FEF) is an evaluation framework developed by the European industry and academia over six years from numerous projects. For example, this evaluation framework has five levels, Covering four evaluation dimensions of Software Engineering (business, architecture, process and organization)Each dimension has three to four aspects. This article will introduce the architecture dimension, which is the most important dimension for our business and developers.

Three aspects

The architecture of BAPO focuses on the following three aspects:

•Asset reuse level: Reuse assets
•Reference Architecture: Reference architecture, used as the infrastructure of the application architecture
•Variability management: Variability management

Level 1: Independent Development)

General description: only the architecture for a single system is supported.
•Asset reuse level: No or systematic reuse
•Reference Architecture: No software product line Architecture
•Variability management: Do not manage Variability

Level 2: standard infrastructure (standardised infrastructure)

General description: reuse is concentrated on third-party infrastructure. There is no formal reusable domain assets.
•Asset reuse level: Use common third-party infrastructure.
•Reference Architecture: The product line architecture is based on third-party infrastructure and is mainly used for these infrastructures.
•Variability management: Sometimes limited by the variability provided by third-party Basic settings. Most of the variability is provided by the application architecture.

Level 3: Software Platform)

General description: it captures the versatility of the field and is implemented on the platform. All applications can share a reference architecture. The configuration platform can be used for different products, however, there is still no good support for variable management.
•Asset reuse level: Defines multiple general assets and carries out planned reuse under the platform and architecture.
•Reference Architecture: Reference architecture as the starting point of application architecture
•Variability management: The reference architecture determines the configurations required for core assets to support application development and has a clear application production plan.

Level 4: variant Products)

General description: The product line clearly defines the variability management, and can well carry out the common and variability management in the field.

•Asset reuse level: Application development allows explicit variability management
•Reference Architecture: The reference architecture supports variable management and clearly shows how the reference architecture supports changes in the application architecture.
•Variability management: Unified management of Application Engineering Variability

Level 5: configurable)

General description: The reference architecture is dominant, with only a small number of application architectures, and more uses modeling, scripts, tools, and configurations to automatically generate products from the reference architecture.
•Asset reuse level: System planning and reuse Asset Library
•Reference Architecture: The reference architecture completely determines the application architecture. The application can be generated after automatic configuration.
•Variability management: Variables are fully integrated into the architecture. variables are described as models and managed in semantic languages.

 

More information:  Large-scale product development method-product line engineering 100222.pdf

 

Welcome to reprint, reprint Please note: Reprinted from Zhou jingen [http://zhoujg.cnblogs.com/]