Shulou(Shulou.com)06/03 Report--

Abstract

1. Introduce the background of application software in the industry, and compare the automobile industry with the software industry.

2. concept introduction, from software project to software product, software product line, software platform, software production line and so on.

3. Manage and operate the software product line

4. Organize and build a software production line

5. Improve productivity (Merge platform)

Reference:

1. The design idea of software product line.

two。 Design reference for the platform:

Get to know Volkswagen platform https://wenku.baidu.com/view/52118fe171fe910ef12df8d8.html

Http://www.pcauto.com.cn/client/782/7826488.html, the platform of MQB, MLB and MEB.

3. PLM solution for Automobile Industry

Https://wenku.baidu.com/view/34d86dec4afe04a1b071de90.html

Background

Compared with the traditional industries such as vehicle manufacturing, the software industry belongs to the emerging industry, the development time is relatively late, and the history of development is relatively short, but its development speed is really rapid. In the software industry, the development of software (operating system, tool software, programming language, etc.) and hardware is changing with each passing day, which poses a new challenge to the traditional industry. On the one hand, the traditional industry recognizes its future development and realizes that it must be integrated with the software industry (that is, Internet + 's idea) in order to break through the bottleneck and achieve further development in the future. enterprises and companies in various industries are making continuous efforts to implement business system software. On the other hand, the development of the software industry does not start from the perspective of serving the traditional industry, at the same time, due to the short development time, there is a lack of a group of mature cross-border talents in the industry. they are experts in the software industry and have an in-depth understanding of the development characteristics of the traditional industry, which can better achieve the goal of integrating the traditional industry and software.

The result of this situation is that the enterprises that implement the system software are very painful and often purchase and implement 10 business modules. with the inconsistency between enterprise operation and management and system functions becoming increasingly prominent, the result is that enterprises often give in to the goal of adapting and limited use of system functions, making full use of the functions of 2-3 business modules, resulting in a lot of waste. This kind of waste is not very sensitive to the software team (company) of the system provider, and this process can also be said to be that the customer is paying for the growth of the team.

However, this process is the only way for software team to mature and software product forming. The goal of software product line architecture design introduced in this paper is to standardize and shorten this process, and to provide an idea for the transformation of software R & D team from project research and development to product development.

Concept import

Step 1: from vehicle product line to software product line

The development of the application of the software industry is mainly to learn from and learn from the industry experience involved, for example, the design of software engineering is established with reference to the process of construction engineering. The software product line mentioned in this paper takes the establishment of the whole vehicle product line as a reference.

Use the table below to quickly establish a conceptual reference from the automotive product line to the software product line.

Serial number

The concept of vehicle domain

Software domain concept

one

Complete vehicle finished product

Sales order (car model + optional parts)

Project deliverables

Customer requirements (application platform + custom components)

two

Optional fittings

The buyer chooses the changeable configuration, such as leather seat, skylight, body color, interior color and so on.

Custom component

Special components tailored to the needs of target customers.

three

Vehicle model design

Platform + variants

Software products

Application platform + standard components

four

Changeable parts

Different types of assemblies, modules and parts, such as body housings, are added based on the platform.

Standard component

Standard business components designed for industry characteristics, including preset business processes.

five

Product line of vehicle type

Divided by platform

Software product line

Divided by application platform

six

Platform

The immutable assemblies, modules and parts in the whole vehicle are integrated into one platform.

Application platform

The immutable part of the system: system framework, rights management, component calling mode, running environment and so on.

After sorting out the above table, we do find that the corresponding mapping can be established between the software product line and the whole vehicle product line in terms of logical concepts. from this, it can be proved that it is feasible to apply the product line management mode of the whole vehicle industry to manage the software product line, as long as a suitable mapping model is established.

Step 2: from vehicle production line to software production line

The establishment of the whole vehicle production line is based on the completion of the production objectives of each process stage of the whole vehicle production. it is generally divided into stamping process (raw material blank to car body blank), welding process (car body forming), painting process (car body painting) and final assembly process (assembly assembly). The whole vehicle production line is expensive and complex in design. It can adapt to the multi-variety and small batch production mode driven by the production order for the preset product line, which is characterized in that the design of the production line is generally established for the product lines of a few models on the same platform, and the change is relatively controllable. end users can only choose among several designed changes.

In contrast, the design process of software products is often based on projects. Due to the lack of formed standards in the application industry, it is impossible to provide customers with optional projects and standards efficiently or accurately. At the same time, the business tasks of customer enterprises are unable to provide accurate requirements targets due to lack of computing thinking. (customer business personnel often propose a large number of demand changes during the trial run of the system and the early stage of project acceptance.) In addition, the information attenuation caused by the R & D team in the process of software engineering responsibility transformation leads to the continuous occurrence of requirements deviation, design deviation, requirement refinement and requirement change in the process of project implementation. as a result, the R & D team paid more than 30% of the cost than expected and delivered highly customized business components.

Compared with the vehicle production line model with mature design, complete technology and flow operation, the research and development process of software products is more like the era of pure manual operation, and this is the driving force of the concept of software production line.

Through the table below, the goal of establishing a software production line with reference to the characteristics of the whole vehicle production line is put forward.

Serial number

Vehicle production line (taking final assembly process as an example)

Software production line

one

Complete vehicle finished product

Production order (car model + optional parts)

Project deliverables

Customer requirements (application platform + custom components)

two

Pick-up list

Get the assembly parts needed for the production order products from the inventory.

Business component requirements list

List of components required for the product after decomposing customer requirements.

three

Out of warehouse bill

The parts are out of the warehouse to the side of the production line.

Component library

Select the preset standard business components (universal), develop and deliver according to individual needs.

four

Parts assembly and information collection

According to the assembly process design, the workers complete the assembly of the parts at the target station and record the information in the MES system as follow-up traceability information.

Component installation and configuration

Install the business components to the system running platform, which can be completed manually or handed over to the product line architecture system. At the same time, configuration management tools are applied to manage traceability information based on the idea of MES traceability.

five

Vehicle quality inspection

The process is completed by a special inspection line, which submits the vehicle quality inspection form and prints the vehicle qualification certificate by the MES system.

Integration testing

Generally use testing tools to complete regression testing, stress testing, supplemented by manual completion of complex business process testing. Submit system test report.

six

Vehicle delivery and delivery

The driver of the manufacturer will transport the vehicle to the warehouse of the sales company (or finished product shipping warehouse).

Installation and deployment

The system implementation staff will complete the installation, debugging and training of the system for the customer.

Manage and operate the software product line

With the development of the R & D team, the software product line operated by the R & D team will continue to expand and can be divided into multiple product families according to the industry to which the product belongs and the application platform. the products in each family use a unified operating platform (there may be version differences) and are in the same or similar business areas.

Each product release is accompanied by a series of organizational activities and deliverables. The overall operating architecture is shown in the following figure:

Product line architecture design is based on the understanding of software products (product = platform + components), combined with the final assembly process in the vehicle production process, drawing lessons from some ideas of PLM. The production flow in the figure involves the design process of the running platform / components, the assembly process of the platform and components, the final inspection process and the rerepair process from left to right, respectively. The work-in-process deliverables during the period include the running platform, standard components, customized components, and software products. The entire production process uses traceability and configuration management in the MES system to implement version management of the running platform, components and released products.

Organize and build a software production line

The software production line is at the core of the software product line architecture, and its goal is to provide a detailed description of each process step, and put forward solutions to the key problems in the production process.

The design goal of the running platform starts with the underlying functions that support business processing, including the processing of components, the support of component-dependent development tools, the functions of running log and monitoring, and the functional design of system operation authorization.

The design goal of the component starts from the point of view of the management of the component, each component information not only develops the relevant engineering code and deployment files, but also contains version information, along with relevant requirements documents, design documents, user manuals and other resource class files, and also provides installation instructions, configuration instructions and other materials for the target operating platform.

The realization process of assembly process

Instantiate the running platform (that is, the project environment), including the code deployed by the platform, middleware, database, etc.

Instantiate the component:

A) Standard components: select the appropriate components from the component library and deploy the components to the running platform according to the installation and configuration instructions.

B) customized components: follow the specification of the running platform for component development, make customized development combined with specific customer needs, and place it in the custom component library for management, and then deploy on the running platform.

The final inspection process part uses regression testing, stress testing and other tools for systematic testing, supplemented by manual completion of complex business process testing to form a test report.

The repair process part applies the software defect management method to repair the defects of the platform or components, and integrates into the version management in the form of small version.

The process of production

After applying the management method of software product line, the work of customized delivery to product R & D will be carried out from two aspects: running platform and component library:

Customized components will gradually accumulate and can be systematically transformed into standard components.

The running platform will be gradually improved in the process of continuous implementation.

Further improve the previous positioning of the product:

Better products = better platforms + more applicable components

Increase productivity

In the process of applying the idea of software product line architecture to research and development, the running platform is relatively stable, and in general, a version can be updated every 3-6 months. how to quickly develop standard components and custom components has become the key issue of whether the product line can be rapidly prototyped.

For this part, I will write a blog post dedicated to a work I developed, the rapid development platform Merge.

Summary

With reference to the working mode of the whole vehicle production line, this paper puts forward the architecture design of software product line, and puts forward the idea of changing from project delivery to product R & D for the software team in the research and development field.

The application of software product line architecture to the operation of software products, there is no insurmountable gap in pure technology, the difficulty is to integrate the architecture idea into the team organization and management process, and continue to adhere to it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.