CN116521183A - Software development sharing management method and system - Google Patents
Software development sharing management method and system Download PDFInfo
- Publication number
- CN116521183A CN116521183A CN202310321137.6A CN202310321137A CN116521183A CN 116521183 A CN116521183 A CN 116521183A CN 202310321137 A CN202310321137 A CN 202310321137A CN 116521183 A CN116521183 A CN 116521183A
- Authority
- CN
- China
- Prior art keywords
- data
- application
- module
- layer
- development
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 41
- 238000011161 development Methods 0.000 claims abstract description 51
- 238000012545 processing Methods 0.000 claims abstract description 9
- 230000006870 function Effects 0.000 claims description 19
- 238000000034 method Methods 0.000 claims description 15
- 238000013500 data storage Methods 0.000 claims description 10
- 238000012217 deletion Methods 0.000 claims description 4
- 230000037430 deletion Effects 0.000 claims description 4
- 238000012986 modification Methods 0.000 claims description 4
- 230000004048 modification Effects 0.000 claims description 4
- 230000008520 organization Effects 0.000 claims description 4
- 230000008569 process Effects 0.000 description 8
- 230000003993 interaction Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000001545 Page's trend test Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
Abstract
The invention provides a software development sharing management method and a system, which are characterized in that after a development requirement input by a front end is received, a unified service layer is directly called to access a data layer of a rear end corresponding to the front end, and finally, an application module is used after processing data of an application module corresponding to the development requirement data in the data layer.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and a system for software development sharing management.
Background
At present, a code-free platform is generally used for realizing the sharing of the page level of the software code, the page level sharing can be realized according to the actual situation after the code-free platform is modularized, but the code-free platform has a plurality of defects, such as limited freedom of programmers, invisible source codes, limited use of professional programmers by components packaged by the code-free development platform, and can not meet the special software requirements of clients, in addition, the front-end programmers can not flexibly select the language and technology to be used, the business flow can only be changed along with the components, and the functions and types of the components limit the development of application programs.
Therefore, it is necessary to provide a software development sharing management method and system to solve the above technical problems.
Disclosure of Invention
In order to solve the technical problems, the invention provides a software development sharing management method and system.
The invention provides a software development sharing management method, which comprises the following steps:
receiving development requirements input by a front end;
based on the development requirement input by the front end, calling a unified service layer to access a data layer of the rear end corresponding to the front end;
and processing the data of the application module corresponding to the development requirement data in the data layer, and then using the processed application module.
Preferably, before the receiving the development requirement input by the front end, the method includes:
defining a corresponding relation model between an application module and a data layer;
generating an application page of an application module based on the general corresponding relation model;
and publishing the application pages to form a page sharing library.
Preferably, the defining a general correspondence model between the application object and the data storage according to the requirement includes:
defining data to form a data layer;
constructing a service layer matched with the data layer;
the service layer is invoked to operate the data layer to develop an application module.
Preferably, the data layer includes a toC table for storing information related to people and individuals, a toB table for storing information related to organizations, a toW table for storing physical or virtual article information, a toF table for storing relationship information of two or more than two, and a toD table for storing data generated by the above four storage objects.
Preferably, the service layer is an API interface, including a system service API interface and an application service API interface, where the system service API interface is configured to provide system services including unified login, organization architecture, rights, functions, system log, system alarm, and user management, and the application service API interface is configured to provide application services including data definition, data storage, data query, data modification, and data deletion.
Preferably, each application module comprises a number of application pages defining routing relationships.
The invention also provides a software development sharing management system, which comprises:
the receiving module is used for receiving development requirements input by the front end;
the calling module is used for calling the unified service layer to access the data layer of the rear end corresponding to the front end based on the development requirement input by the front end;
and the use module is used for using the processed application module after processing the data of the application module corresponding to the development requirement data in the data layer.
Preferably, the method further comprises:
the definition module is used for defining a corresponding relation model between the application module and the data layer;
the generation module is used for generating an application page of the application module based on the general corresponding relation model;
and the release module is used for releasing the application page to form a page sharing library.
Preferably, the method further comprises:
a data sub-module for defining data to form a data layer;
the service sub-module is used for constructing a service layer matched with the data layer;
and the development sub-module is used for calling the service layer to operate the data layer so as to develop the application module.
Compared with the related art, the software development sharing management method and system provided by the invention have the following beneficial effects:
according to the invention, after the development requirement input by the front end is received, the unified service layer is directly called to access the data layer of the rear end corresponding to the front end, and finally, the application module is used after the application module corresponding to the development requirement data processes the data in the data layer, so that the front end programmer can call the rear end by using the unified service layer when developing the front end page through the unified data layer and the service layer, the developed front end page has universality, other front end programmers can directly copy and use the front end page, the development efficiency is greatly improved, meanwhile, the shared front end page is ensured by the use of users, the reliability is ensured, the occurrence probability of bug is reduced, the corresponding relation model of the data layer and the application module is established, the relation between the front end business data and the rear end data storage is established by using the model, and thus, the uniformity and the universality of page interaction are ensured by using any page of the front end through the unified service layer.
Drawings
FIG. 1 is a schematic diagram of steps of a software development sharing management method according to the present invention;
FIG. 2 is a schematic diagram of a system architecture of a software development and sharing management system according to the present invention;
fig. 3 is an exemplary diagram of a software development sharing management method according to the present invention.
Detailed Description
The invention will be further described with reference to the drawings and embodiments.
Example 1
The embodiment discloses a software development sharing management method
In this embodiment, as shown in fig. 1, the management method includes:
step S100: receiving development requirements input by a front end; the input development requirement is a function which the front-end developer wants to realize, and keywords of the function development requirement can be typed into the management system provided by the invention when the front-end developer is in use.
Step S200: based on the development requirement input by the front end, calling a unified service layer to access a data layer of the rear end corresponding to the front end; after the front-end developer types in the function development requirement, the unified service layer is utilized to access the data layer of the back-end, and the bottom-layer back-end data of the existing application module is stored in the data layer, so that the front-end developer processes the back-end data corresponding to the application module, and the application module completely meeting the function requirement is obtained.
Step S300: using the processed application module after processing the data of the application module corresponding to the development requirement data in the data layer; the processing includes that the existing application module completely meets the requirements, the existing application module is directly used, or the application module modified on the basis of the existing application module is used under the condition that the existing application module does not completely meet the requirements.
Specifically, before the development requirement input by the front end is received, the method includes:
defining a corresponding relation model between an application module and a data layer; the step can establish the relation between the front-end service data and the back-end data storage by using the defined corresponding relation model, so that the back-end can provide a unified service layer (API service interface) for the front-end, any page of the front-end processes the back-end data corresponding to the front-end service data through the unified service layer (API service interface), and the uniformity and the universality of the front-end page interaction are ensured;
specifically, the method specifically comprises the following steps:
defining data to form a data layer; in this step, the data layer includes toC table for storing information related to people and individuals (such as objects related to all software application items of users, teachers, students, doctors and the like, people), toB table for storing information related to organizations (such as companies, associations, government institutions and the like), toW table for storing physical or virtual article information (such as equipment, assets, articles and the like), toF table for storing relationship information (such as orders, contracts, services and the like) of two or more, and toD table for storing data generated by the above four storage objects (such as people (company staff) generates attendance records, objects (equipment) generates running records and the like), and in use, the user directly defines data relationship according to requirements to form the data layer.
Constructing a service layer matched with the data layer; in the step, the service layer is an API interface, including a system service API interface and an application service API interface, where the system service API interface is used to provide system services including unified login, organization architecture, rights, functions, system logs, system alarms and user management, and the application service API interface is used to provide application services including data definition, data storage, data query, data modification and data deletion, where the user call API interface can implement all the functions.
Invoking the service layer to operate the data layer to develop an application module; in this step, the table storage of each data layer provides the front-end development programmer with a data operation service interface API, then the system service also provides the front-end development engineer with a unified service layer (API interface), the front-end development programmer can call the unified system service interface and the application service interface on the premise of adhering to the service interface call specification, then develop various application modules, each application module is composed of a plurality of application pages, and then the application pages have universality.
Generating an application page of an application module based on the general corresponding relation model; in this step, each application module is composed of a plurality of application pages, so that the application pages have universality, and when in use, routing relations among the application pages need to be defined.
Publishing the application pages to form a page sharing library; in the step, the developed application page can be used by a system developed by the user, after the application page test has no problem, the application page can be released into a page sharing library, other front-end programmers can find the application page related to the application page in the page sharing library and copy the application page to the user's own system for direct use if the application page has the same function requirement when the application page is used as other systems, and the page is not required to be re-developed.
As shown in the exemplary diagram provided in fig. 3, taking teacher management as an example, a teacher management function is to be developed:
firstly, a front-end programmer needs to define a corresponding relation model of an application object and a data layer by using the system provided by the invention;
secondly, after a model is defined, the system provided by the invention can automatically generate a front-end application page according to the model;
then, the front-end management page programmer can use a development tool to randomly adjust the style of the application page;
then, the routing relationship between the application pages needs to be defined, for example, a teacher management main interface is a teacher information list, buttons for inquiring a teacher, inputting the teacher, deleting the teacher information, modifying the teacher information and the like are arranged on the list, and after the relationship between the buttons and the paging surface is defined, the teacher management page can be completed.
Finally, registering relevant pages of the teacher management module to the system platform, and copying each page of teacher management by programmers of other projects to realize the teacher management function.
The working principle of the software development sharing management method provided by the invention is as follows: according to the invention, after the development requirement input by the front end is received, the unified service layer is directly called to access the data layer of the rear end corresponding to the front end, and finally, the application module is used after the application module corresponding to the development requirement data processes the data in the data layer, so that the front end programmer can call the rear end by using the unified service layer when developing the front end page through the unified data layer and the service layer, the developed front end page has universality, other front end programmers can directly copy and use the front end page, the development efficiency is greatly improved, meanwhile, the shared front end page is ensured by the use of users, the reliability is ensured, the occurrence probability of bug is reduced, the corresponding relation model of the data layer and the application module is established, the relation between the front end business data and the rear end data storage is established by using the model, and thus, the uniformity and the universality of page interaction are ensured by using any page of the front end through the unified service layer.
Example two
The embodiment discloses a software development sharing management system
In this embodiment, as shown in fig. 2, the management system includes:
the receiving module is used for receiving development requirements input by the front end; specifically, the input development requirement is a function which the front-end developer wants to realize, and when the front-end developer is in use, keywords of the function development requirement can be typed into the management system provided by the invention.
The calling module is used for calling the unified service layer to access the data layer of the rear end corresponding to the front end based on the development requirement input by the front end; specifically, after the front-end developer types in the function development requirement, the data layer of the back-end is accessed by using a unified service layer, and the bottom-layer back-end data of the existing application module is stored in the data layer, so that the front-end developer processes the back-end data corresponding to the application module to obtain the application module completely meeting the function requirement.
A use module for using the processed application module after processing the data of the application module in the data layer corresponding to the development requirement data; specifically, the processing includes that the existing application module completely meets the requirements, the existing application module is directly used, or the application module modified on the basis of the existing application module is used under the condition that the existing application module does not completely meet the requirements.
Further comprises:
the definition module is used for defining a corresponding relation model between the application module and the data layer; specifically, the relationship between the front-end service data and the back-end data storage can be established by using the defined corresponding relationship model, so that the back-end can provide a unified service layer (API service interface) for the front-end, any page of the front-end processes the back-end data corresponding to the front-end service data through the unified service layer (API service interface), and the uniformity and the universality of the front-end page interaction are ensured.
The generation module is used for generating an application page of the application module based on the general corresponding relation model; specifically, each application module is composed of a plurality of application pages, so that the application pages have universality, and when the application module is used, the routing relationship among the application pages needs to be defined.
The publishing module is used for publishing the application pages to form a page sharing library; specifically, the developed application page can be used by a system developed by the user, after the application page test has no problem, the application page can be released into the page sharing library, other front-end programmers can find the application page related to the application page in the page sharing library and copy the application page to the user's own system for direct use if the application page has the same function requirement when the application page is used as a different system, and the development efficiency is greatly improved by realizing page-level software development sharing in comparison with the traditional software development mode, and meanwhile, the reliability is verified because the shared application page is used for a long time by a user, so that the error rate is reduced.
The definition module further includes:
a data sub-module for defining data to form a data layer; specifically, the data layer includes toC table for storing information related to people and individuals (such as objects related to all software application items of users, teachers, students, doctors and the like) and to people, toB table for storing information related to organizations (such as companies, associations, government institutions and the like), toW table for storing physical or virtual article information (such as equipment, assets, articles and the like), toF table for storing relationship information (such as orders, contracts, services and the like) of two or more, and toD table for storing data generated by the above four storage objects (such as people (company staff) generates attendance records, objects (equipment) generates running records and the like), and when in use, the users directly define data relationship according to requirements to form the data layer.
The service sub-module is used for constructing a service layer matched with the data layer; specifically, the service layer is an API interface, including a system service API interface and an application service API interface, where the system service API interface is configured to provide system services including unified login, organization architecture, rights, functions, system logs, system alarms and user management, and the application service API interface is configured to provide application services including data definition, data storage, data query, data modification and data deletion, where the user call API interface is used to implement all the functions described above.
A development sub-module for invoking the service layer to operate the data layer to develop an application module; specifically, the table storage of each data layer provides a data operation service interface API for the front-end development programmer, and then the system service also provides a unified service layer (API interface) for the front-end development engineer, and the front-end development programmer can call the unified system service interface and the application service interface on the premise of adhering to the service interface call specification, and then develop various application modules, wherein each application module is composed of a plurality of application pages, and then the application pages have universality.
The working principle of the software development sharing management system provided by the invention is as follows: according to the invention, after the development requirement input by the front end is received, the unified service layer is directly called to access the data layer of the rear end corresponding to the front end, and finally, the application module is used after the application module corresponding to the development requirement data processes the data in the data layer, so that the front end programmer can call the rear end by using the unified service layer when developing the front end page through the unified data layer and the service layer, the developed front end page has universality, other front end programmers can directly copy and use the front end page, the development efficiency is greatly improved, meanwhile, the shared front end page is ensured by the use of users, the reliability is ensured, the occurrence probability of bug is reduced, the corresponding relation model of the data layer and the application module is established, the relation between the front end business data and the rear end data storage is established by using the model, and thus, the uniformity and the universality of page interaction are ensured by using any page of the front end through the unified service layer.
In the description of the present invention, it should be noted that the azimuth or positional relationship indicated by the terms "center", "up", "down", "left", "right", "vertical", "horizontal", "inside", "outside", etc. are based on the azimuth or positional relationship shown in the drawings, are merely for convenience of describing the present invention and simplifying the description, and do not indicate or imply that the apparatus or elements referred to must have a specific azimuth, be constructed and operated in a specific azimuth, and thus should not be construed as limiting the present invention.
The foregoing description is only illustrative of the present invention and is not intended to limit the scope of the invention, and all equivalent structures or equivalent processes or direct or indirect application in other related technical fields are included in the scope of the present invention.
Claims (9)
1. A software development sharing management method, characterized in that the management method comprises:
receiving development requirements input by a front end;
based on the development requirement input by the front end, calling a unified service layer to access a data layer of the rear end corresponding to the front end;
and processing the data of the application module corresponding to the development requirement data in the data layer, and then using the processed application module.
2. The software development sharing management method according to claim 1, comprising, before said receiving the development requirement input by the front end:
defining a corresponding relation model between an application module and a data layer;
generating an application page of an application module based on the general corresponding relation model;
and publishing the application pages to form a page sharing library.
3. The method for managing software development sharing according to claim 2, wherein the defining the general correspondence model between the application object and the data storage according to the requirement includes:
defining data to form a data layer;
constructing a service layer matched with the data layer;
the service layer is invoked to operate the data layer to develop an application module.
4. A software development sharing management method according to claim 3, wherein said data layer comprises toC table for storing information related to people, individuals, toB table for storing information related to organizations, toW table for storing physical or virtual article information, toF table for storing relationship information of two or more, and toD table for storing data generated by the above four storage objects.
5. A software development sharing management method according to claim 3, wherein said service layer is an API interface comprising a system service API interface for providing system services including unified login, organization architecture, rights, functions, system logs, system alarms, and user management and an application service API interface for providing application services including data definition, data saving, data query, data modification, and data deletion.
6. A software development sharing management method according to claim 2, wherein each application module comprises a number of application pages defining routing relationships.
7. A software development sharing management system, comprising:
the receiving module is used for receiving development requirements input by the front end;
the calling module is used for calling the unified service layer to access the data layer of the rear end corresponding to the front end based on the development requirement input by the front end;
and the use module is used for using the processed application module after processing the data of the application module corresponding to the development requirement data in the data layer.
8. The software development sharing management system of claim 7, further comprising:
the definition module is used for defining a corresponding relation model between the application module and the data layer;
the generation module is used for generating an application page of the application module based on the general corresponding relation model;
and the release module is used for releasing the application page to form a page sharing library.
9. The software development sharing management system of claim 8, further comprising:
a data sub-module for defining data to form a data layer;
the service sub-module is used for constructing a service layer matched with the data layer;
and the development sub-module is used for calling the service layer to operate the data layer so as to develop the application module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310321137.6A CN116521183A (en) | 2023-03-29 | 2023-03-29 | Software development sharing management method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310321137.6A CN116521183A (en) | 2023-03-29 | 2023-03-29 | Software development sharing management method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116521183A true CN116521183A (en) | 2023-08-01 |
Family
ID=87398448
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310321137.6A Pending CN116521183A (en) | 2023-03-29 | 2023-03-29 | Software development sharing management method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116521183A (en) |
-
2023
- 2023-03-29 CN CN202310321137.6A patent/CN116521183A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9390395B2 (en) | Methods and apparatus for defining a collaborative workspace | |
| US5799297A (en) | Task workflow management system and method including an external program execution feature | |
| KR101083488B1 (en) | Impact analysis in an object model | |
| US8412746B2 (en) | Method and system for federated querying of data sources | |
| US6338069B1 (en) | Method and apparatus for managing functions | |
| US20110119683A1 (en) | Object graph editing context and methods of use | |
| KR20060043629A (en) | Project time and expense | |
| WO2023231665A1 (en) | Distributed transaction processing method, system and device, and readable storage medium | |
| CN113971037A (en) | Application processing method and device, electronic equipment and storage medium | |
| CN111143391A (en) | Data sharing exchange method and system | |
| US20090254538A1 (en) | Methods, systems, and computer program products for social based assistance in a source code control system | |
| CN113760947A (en) | Data center, data processing method, device, equipment and storage medium | |
| CN110334545B (en) | SQL-based permission control method and device and electronic equipment | |
| CN115328569A (en) | Method, system, electronic device and computer readable storage medium for processing data conflict | |
| US20150127785A1 (en) | Gateway service manager for business object applications | |
| US6751509B2 (en) | Method for access control of aggregated data | |
| CN112365220A (en) | Informationized dynamic supervision platform | |
| CN116521183A (en) | Software development sharing management method and system | |
| CN116561146A (en) | Database log recording method, device, computer equipment and computer readable storage medium | |
| CN105518670B (en) | Data model indexing for model queries | |
| US8375353B2 (en) | Enabling the use of process flow applications within an information management system (IMS) | |
| Pick et al. | A framework for developing flexible virtual-reality-centered annotation systems | |
| Li et al. | Bank Management System Based on QT | |
| CN108509553A (en) | A kind of item file generation method and platform | |
| KR100653267B1 (en) | Method for database management and apparatus thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |