CN114153819A

CN114153819A - Database establishing and using method for SOA architecture development

Info

Publication number: CN114153819A
Application number: CN202111475544.XA
Authority: CN
Inventors: 陈敏; 刘聪; 程福明; 吴文杰; 董贵旭
Original assignee: Shanghai Hecheng Technology Co ltd
Current assignee: Shanghai Hecheng Technology Co ltd
Priority date: 2021-12-06
Filing date: 2021-12-06
Publication date: 2022-03-08

Abstract

The invention discloses a database establishment method for SOA architecture development, which relates to the field of database technology and includes a function definition stage and a function development stage. By redefining and analyzing functions, dismantling them into use cases to generate use cases for all functions After adding or modifying the corresponding functional requirements, you can quickly retrieve related use cases for modification or addition, and improve the efficiency of function definition. The invention also discloses a database using method for SOA architecture development, which includes four steps. By analyzing the implementation of existing functions and the capabilities of the current hardware, a service library is generated, and through the relationship between use cases and services, it can quickly locate the services required for the realization of new functions, thereby improving the reusability of the design. Provides methods for rapid functional development.

Description

Database establishing and using method for SOA architecture development

Technical Field

The invention relates to the technical field of databases, in particular to a database establishing and using method for SOA architecture development.

Background

The automobile industry is facing a new industrial revolution, and an intelligent, electric and digital era comes, so that a new challenge is provided for all aspects of product research, development, production, marketing and the like in the automobile industry. For the development of the electronic and electric appliance architecture (hereinafter referred to as architecture) of the whole vehicle, the definition of the development stage does not mean the end of the development task of the life cycle of the product, and also needs to consider the increasingly rapid function updating iteration in the later period, which requires the support or the provision of a new architecture or a development method:

1. the capability of the function definition to expand rapidly;

2. the ability to develop functions quickly;

3. OTA alternate capability.

Based on the above challenges, a new architecture concept has evolved from the traditional distributed to centralized, and function deployment is, in principle, switched from the original functional domain centralized to physical domain division; however, the traditional architecture development method still uses the function realization link as a core, uses the hardware ECU as an index, and embodies the realization dependency relationship of the functions through system documents of different levels. When a new function needs to be implemented, the conventional method may bring:

1. function definition inefficiency

The existing function definition method takes a fixed function list as input, defines entry/exit conditions such as function activation and exit, defines a state machine and switching conditions thereof, and further deduces signals required for realizing the function step by step; if the newly added functions comprise part of the defined existing functions, the newly added functions still need to be considered and designed again according to the traditional method, the reusability is poor, the efficiency is low, and the fast function expansion definition required by the SOA cannot be met.

2. Low efficiency of function development

The content of function development mainly comprises three aspects of function realization logic design, function distribution and function interaction design. In the traditional function development method, a document is used as a carrier, a function definition document is used as input, function development documents of different levels are defined, and a requirement document for each ECU hardware is output. This would result in:

A) the functional lines are longitudinally complete and difficult to transversely expand

If the function needs to be newly added in the later period, the function needs to be newly developed, and the existing design can not be reused. The form of the document is also a reason for hindering lateral connection and expansion.

B) Demand tracing and tracking are not efficient enough

Functional requirements and non-functional requirements are defined in a functional definition document, numbering is often performed through a certain standard, so that traceability of the requirements is realized, and the requirements need to be carried and realized in a functional development document. The interactive mode of the documents causes that if a certain requirement needs to be added or modified, a large number of documents need to be maintained, thereby causing low efficiency.

3. The OTA iteration period is long

When vehicle functions need to be added or modified in an OTA mode, the method is limited by function definition and function development methods adopted by the traditional architecture development method, and due to the limitation, the development period is long, so that the OTA iteration period is prolonged, and the vehicle using experience of a user is influenced.

Disclosure of Invention

The invention aims to provide a database establishing and using method for SOA architecture development, so as to solve the problems in the background technology.

In order to achieve the purpose, the invention provides the following technical scheme: a database establishing method for SOA architecture development comprises the following steps:

s1, function definition stage: inputting a function list provided by a product manager, and outputting a use case set for a specific function;

s2, after the function definition analysis of a plurality of functions is completed, a function use case base based on the whole function is formed;

s3, function development stage: inputting function use cases and current vehicle hardware configuration which are set as function definition stage output, and outputting services which are set as the function use cases;

and S4, after the function definition analysis of a plurality of functions and the configuration analysis based on hardware are completed, a service library based on specific hardware and virtual realization functions is formed.

Preferably, one function list in S1 corresponds to 1-n function use cases, where the function use cases are activities that are perceivable by a user, have value, and are independent of each other.

Preferably, the implementation of one function use case in S3 requires 1-n services.

Preferably, the hardware configuration comprises a sensor configuration and an actuator configuration of the vehicle.

Preferably, the service library in S4 is derived from two major aspects: one is based on current functional use case analysis and the other is based on hardware configuration analysis.

Preferably, the service library establishment based on the function implementation part in S4 is a continuously iterative and complete process.

A database usage method for SOA architecture development, comprising the steps of (based on an application case library):

the method comprises the following steps: firstly, performing function analysis, and disassembling a function case;

step two: after disassembly, the function can be analyzed according to the traditional flow, but the analysis is carried out in the case base, and the retrieval is carried out, and then the judgment is carried out according to the result;

step three: if the function case exists in the existing library, the function case defined in the library can be directly multiplexed, and then the service required by the case in the service library is directly multiplexed, so that the service depending on the realization function is obtained;

step four: if the case does not exist in the existing case library, the case needs to be designed, and the case library is updated and expanded after the design is completed, so that the multiplexing possibility is provided for the subsequent design.

Preferably, the service library is used in the same way as the function example library.

Preferably, the function cases in the function case library are all unique and independent, two identical function cases do not exist, and a case that one service has a relationship with a plurality of cases exists in the service library.

Compared with the prior art, the invention has the beneficial effects that:

(1) the invention redefines and analyzes the functions, disassembles the functions into cases, generates a case library aiming at all the functions, subsequently adds or modifies corresponding function requirements, can quickly search out the associated cases for modification or addition, and improves the efficiency of function definition;

(2) the invention generates the service library by analyzing the realization of the existing functions and the capability of the current hardware, rapidly positions and realizes the services required by the realization of the new functions by the incidence relation between the use case and the services, further improves the reusability of the design and provides a method for realizing the rapid function development;

(3) the invention can greatly shorten the time and period of the function OTA through the final function upgrading layer;

(4) the invention is beneficial to innovation of functions and scenes, and more conveniently supports designers to carry out innovative combination among different cases through the layout of a database form, thereby generating more new functions.

Drawings

FIG. 1 is a schematic diagram illustrating a process for establishing a functional example library according to the present invention;

FIG. 2 is a schematic diagram illustrating a process of establishing a service library according to the present invention;

FIG. 3 is a schematic diagram of the function definition and development process of two databases according to the present invention;

FIG. 4 is a diagram illustrating the relationship between a function case library and a service library according to the present invention;

fig. 5 is a schematic diagram showing a design result of the intelligent welcome function of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Example 1:

referring to fig. 1-2, the present invention provides a technical solution: a database establishing method for SOA architecture development comprises the following steps:

Wherein, one function list in S1 corresponds to 1-n function cases, the function cases are activities that are perceivable by a user, have value, and are independent of each other, the implementation of one function case in S3 requires 1-n services, the hardware configuration includes a sensor configuration and an actuator configuration of a vehicle, and the service library in S4 is derived from two major aspects: one is based on the current function use case analysis, the other is based on the hardware configuration analysis, and the service library establishment based on the function implementation part in the step S4 is a continuous iterative refinement process.

Example 2

Referring to fig. 3-4, the present invention further provides a technical solution: a database usage method for SOA architecture development, comprising the steps of (based on an application case library):

The service library is used in the same way as the function example library.

The function cases in the function case library are all unique and independent, two identical function cases do not exist, and the service library has the condition that one service has a correlation relation with a plurality of cases.

Example 3

The present invention will be further described below with reference to the two embodiments by using a specific example:

firstly, in a car body domain and an entertainment domain, selecting a plurality of existing function use cases and corresponding services, wherein the designed function use cases and services (parts) are shown in the following table:

table 1 existing function use case and service (part)

Note: the use case column and the service column are used as examples, and the content is not complete.

In table 1 above, the function list is an input described on a certain function list, and includes four functions of a guest greeting function, a lighting function, an intelligent air conditioner, and an account management; the case list is a case contained in each function defined according to the principle of function analysis; the service column is the service required to implement the particular use case.

Secondly, due to the personalized requirements of users, a new function scene is added after the mass production of products, the name of the function scene is called intelligent welcome, and the target realization scene is as follows: after a user carries the intelligent key to be close to the vehicle, the vehicle is automatically unlocked, the outer lamp can automatically switch on and off the high beam once (welcome effect), the door is opened to enter the vehicle, and the air conditioner can be automatically opened and adjusted to the temperature, the wind speed and the wind direction customized by the user.

The original welcome function does not have the function, and the traditional methodology is used for analysis, so that the function use case and the service requirement behind the function use case need to be redefined, and the efficiency is influenced.

However, based on the existing use case library, the function of rapidly disassembling the intelligent welcome is composed of UC-001, UC-003, UC-004, UC-005, UC-006 and UC-008 in the use case library. And obtaining services necessary for realizing the functional scene according to the association relationship between each use case and the service in the use case library, wherein the services include S0001, S0002, S0003, S0006, S0007, S0008, S0009, S0010, S0011, S0012, S0013, S0016 and S0017. Therefore, the original design can be reused, and the purposes of quickly finishing function definition and function development are achieved. The final result appears as shown in fig. 5.

Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.

Claims

1. a database establishment method for SOA architecture development, is characterized in that, comprises the following steps:

S1. Function definition stage: the input is set as the function list provided by the product manager, and the output is set as the use case for a specific function;

S2. After completing the function definition analysis of multiple functions, a functional use case library based on the overall function is formed;

S3. Function development stage: the input is set as the functional use case and the current vehicle hardware configuration output in the function definition stage, and the output is set as the service used to realize these functional use cases;

S4. After completing the function definition analysis of multiple functions and the hardware-based configuration analysis, a service library based on specific hardware and virtual implementation functions is formed.

2. The method for establishing a database for SOA architecture development according to claim 1, wherein a function list in the S1 corresponds to 1-n functional use cases, and the functional use cases are user-perceivable , valuable, independent activities.

3 . The method for establishing a database for SOA architecture development according to claim 2 , wherein the implementation of a functional use case in the S3 requires 1-n services. 4 .

4 . The method for establishing a database for SOA architecture development according to claim 1 , wherein the hardware configuration includes the sensor configuration and the actuator configuration of the vehicle. 5 .

5. a kind of database establishment method for SOA architecture development according to claim 1, is characterized in that: the service library in described S4 is derived from two big aspects: one is based on current functional use case analysis, the other is a hardware-based configuration analysis.

6 . The method for establishing a database for SOA architecture development according to claim 1 , wherein the establishment of the service library based on the function implementation part in the S4 is a process of continuous iterative improvement. 7 .

7. a kind of database using method for SOA architecture development as described in any one of claim 1-6, is characterized in that, comprises the following steps (based on use case library):

Step 1: First perform functional analysis and disassemble functional use cases;

Step 2: After dismantling, the function implementation analysis can no longer be carried out according to the traditional process, but firstly go to the use case library for retrieval, and then judge according to the results;

Step 3: If it exists in an existing library, the function use case defined in the library can be directly reused, and then the service required for the use case in the service library can be directly reused to obtain the services that the function depends on;

Step 4: If it does not exist in the existing use case library, it is necessary to design the use case. After the design is completed, update and expand it into the use case library to provide the possibility of reuse for subsequent designs.

8. The method for using a database for SOA architecture development according to claim 7, wherein the method for using the service library is the same as the method for using the functional use case library.

9. The method for using a database for SOA architecture development according to claim 7, wherein the functional use cases in the functional use case library are all unique and independent, and there are no two identical functional use cases, In the service library, there is a situation where a service is associated with multiple use cases.