CN103777965A - Interlayer model for collaborative software development - Google Patents

Abstract

The invention discloses an interlayer model for software cooperative development, including a first circuit for developing domain prototypes and a second circuit for developing domains; the domain prototypes correspond to domain concepts, A domain refers to a range oriented to a certain requirement, and its size and specificity are not fixed; a domain prototype is a kit provided for design and development under a domain, and the kit includes all the content in the defined domain; The first line and the second line are developed in parallel. The advantages of the present invention are: the parallel development of two lines makes the development process truly separated, which is beneficial to the globalized socialized production; at the same time, the emergence of the domain model reduces the duplication of software work, and is also a solution to the previous software components. The supplement of reuse thought increases the type of reuse and improves the efficiency of reuse.

Description

A Mesolayer Model for Software Collaborative Development

technical field

The invention belongs to the field of software engineering, relates to an interlayer model for software cooperative development, and is a software development model different from the traditional one.

the

Background technique

At present, software development is mainly based on some traditional development models. There is only one development line in traditional development. From requirements analysis to the realization of the final product, it is completely a single-line operation. However, this development method inevitably involves repetitive labor and development efficiency. low.

the

Contents of the invention

In order to solve the above-mentioned technical problems, the present invention proposes a two-line interlayer model for software development.

The technical solution adopted by the present invention is: a kind of interlayer model for software cooperative development, characterized in that: it includes a first circuit for developing a domain prototype and a second circuit for developing a domain; the domain prototype Corresponding to the concept of a domain, a domain refers to a range oriented to a certain requirement, its size is not fixed, and its specificity is not fixed; a domain prototype is a suite that provides design and development under the domain, and the said suite includes the defined All content in the field; said first line and second line are developed in parallel.

As a preference, the specific development process of the first line for developing domain prototypes includes the following sub-steps:

Step 1.1: Demand analysis, determine the object, method and goal of demand analysis;

Step 1.2: Domain definition is to determine the domain scope and expression form of development after the requirements collection is completed;

Step 1.3: domain development, which is to design, develop and implement according to the results of domain definition;

Step 1.4: Testing, testing the usability, practicability and security of the results after domain design;

Step 1.5: Offer to buy, sell domain prototypes.

As a preference, the specific development process of the second line for the development field includes the following sub-steps:

Step 2.1: Requirements analysis, analyze the requirements, and determine the requirements of the target software development;

Step 2.2: Find and purchase domain prototypes;

Step 2.3: Development, after completing the domain prototype search and purchase, develop and implement according to the rules of the domain prototype;

Step 2.4: Test.

Compared with the prior art, the present invention has the following advantages:

1. The parallel development of the two lines makes the development process truly separated, which is conducive to the globalization and socialization of production;

2. The emergence of the domain model reduces the repetitive labor of software, and is also a supplement to the previous reuse ideas such as software components, increasing the types of reuse and improving the efficiency of reuse.

the

Description of drawings

Accompanying drawing 1: is the schematic flow chart of the method of the embodiment of the present invention.

the

Detailed ways

In order to facilitate those skilled in the art to understand and implement the present invention, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments.

See also Fig. 1, the technical scheme that the present invention adopts is: a kind of interlayer model that is used for software cooperative development, comprises the first circuit that is used to develop domain prototype and the second circuit that is used to develop domain; Domain prototype and domain The concept is corresponding, the domain refers to the scope of a certain demand, its size is not fixed, and the degree of specificity is not fixed; the domain prototype is a kit that provides design and development under the domain, and the kit includes all the defined domains. Content; The first line and the second line are developed in parallel.

The invention is a development interlayer model that provides market incentives and software reuse based on group wisdom. The interlayer model first divides the development into two lines: the first line and the second line. The first line is mainly used to develop reusable materials, and the second line is mainly used to develop the final software product. The difference between this and traditional development is that traditional development generally has only one line, from the acquisition of requirements to the realization of the final product. However, the two lines in the present invention can be used for division of labor, effectively improving the efficiency of development and reducing duplication of labor.

The concepts of domain and domain prototype in the present invention are corresponding, and domain refers to a range oriented to a certain demand, and its size is not fixed, and its specific degree is not fixed. For example, medicine, chemistry, electronics, etc. are a relatively broad field, and electronic oscilloscope waveform noise analysis and extraction are a relatively specific field; field prototypes provide design and development kits under the field, and this kit should include All the content in the defined domain, because the domain can be large or small, can be specific or abstract, so the domain prototype will also appear in this situation, for example, a medical domain prototype may contain the knowledge base required by medicine and all operation, and for the input of biological samples and the statistical domain model may only need to provide biological input interfaces and statistical functions. Domains and domain prototypes are a manifestation of commonality. Under a domain prototype, many kinds of software can be developed, but there are commonality among them, and this commonality is the embodiment of domain. The purpose of domain and domain prototype is to provide a set of highly reusable development constructs for specific software types.

The specific development process of the first line for developing domain prototypes in this embodiment includes the following sub-steps:

Step 1.1: Requirements analysis, determine the object, method and goal of requirements analysis; this is consistent with the concept of requirements analysis in software engineering, but the goal is not to realize software, but to realize how to provide a better domain prototype.

Step 1.2: Domain definition is to determine the domain scope and expression form of development after the requirements collection is completed; this is completely determined by the developers according to the requirements and their own conditions.

Step 1.3: Domain development is to design, develop and implement according to the results of the domain definition; in this process, other development models can be used for specific development. Of course, the difference from other development models is still the purpose of development. , other models are to realize a specific software product, but here is only to realize a domain prototype. At this stage, you can purchase and use other field prototypes for development, and there is a phenomenon of continuous superposition.

Step 1.4: Testing, testing the usability, practicability and security of the results after domain design;

Step 1.5: Offer to buy, sell domain prototypes. Because the domain prototype is not a complete software product, but it provides a basic development resource for software development in the domain, so it is like selling a set of painting tools, which can be oil painting tools or watercolor painting tools. It can be sold to developers who develop domain models, and it can also be provided to developers who develop software. The advantage of this is to reduce the duplication of software development as much as possible and achieve efficient software production.

For the second circuit in the development field of this embodiment, its specific development process includes the following sub-steps:

Step 2.1: Requirements analysis, first of all, the same as the traditional development model, it is still to analyze the requirements to determine the requirements of the target software development;

Step 2.2: Find and purchase domain prototypes; on the basis of demand analysis, it is difficult to find the exact domain prototypes. Often the domain prototypes found may be broader than the required software, and some functions still need to be freely developed. However, if it is based on the requirements analysis of the domain prototype, it may be possible to obtain a better domain prototype.

Step 2.3: Development, after completing the search and purchase of domain prototypes, develop and implement according to the rules of domain prototypes; in addition, it is also possible to follow the traditional development model.

Step 2.4: Test. In the end, the testing link is indispensable. In this process, it is different from the traditional development mode, because the domain prototype is used for development, and the domain prototype in it has been tested in line 1, so its usability, use, and safety are guaranteed, so what needs to be tested is only additional Added modules and overall testing. In theory, the cost of testing is reduced.

On the whole, there is a value chain in the interlayer model: sell-buy. This value chain is an incentive that exists in social culture and can well promote the human factor in software development. At the same time, in this value chain Separated from the development line, it can promote the socialization and globalization of development, and use the wisdom of the group to produce incredible results. At the same time, the emergence of the domain model reduces the repetitive labor of software, and is also a supplement to the previous reuse ideas such as software components, increasing the types of reuse and improving the efficiency of reuse. The two development lines also make the development process truly separated, which is conducive to globalized and socialized production. All in all, no matter from the point of view of things or people, the interlayer model provides a new perspective of development or a change of development.

The specific embodiments described herein are merely illustrative of the spirit of the invention. Those skilled in the art to which the present invention belongs can make various modifications or supplements to the described specific embodiments or adopt similar methods to replace them, but they will not deviate from the spirit of the present invention or go beyond the definition of the appended claims range.

Claims (3)

1. A kind of interlayer model that is used for software cooperative development, it is characterized in that: comprise the first circuit that is used for developing domain prototype and the second circuit that is used for developing domain; The concept of described domain prototype and domain is corresponding Yes, a domain refers to a range that is oriented to a certain requirement, and its size is not fixed, and its specificity is not fixed; a domain prototype is a kit that provides design and development under the domain, and the kit includes all the content in the defined domain; The first line and the second line are developed in parallel. 2. The interlayer model for software cooperative development according to claim 1, characterized in that: the first line for the development domain prototype, its specific development process comprises the following sub-steps: Step 1.1: Demand analysis, determine the object, method and goal of demand analysis; Step 1.2: Domain definition is to determine the domain scope and expression form of development after the requirements collection is completed; Step 1.3: domain development, which is to design, develop and implement according to the results of domain definition; Step 1.4: Testing, testing the usability, practicability and security of the results after domain design; Step 1.5: Offer to buy, sell domain prototypes. 3. The interlayer model for software cooperative development according to claim 1, characterized in that: for the second line in the development field, its specific development process includes the following sub-steps: Step 2.1: Requirements analysis, analyze the requirements, and determine the requirements of the target software development; Step 2.2: Find and purchase domain prototypes; Step 2.3: Development, after completing the domain prototype search and purchase, develop and implement according to the rules of the domain prototype; Step 2.4: Test.