CN105354037B - Modular software development methodology and software development apparatus - Google Patents
Modular software development methodology and software development apparatus Download PDFInfo
- Publication number
- CN105354037B CN105354037B CN201510857488.4A CN201510857488A CN105354037B CN 105354037 B CN105354037 B CN 105354037B CN 201510857488 A CN201510857488 A CN 201510857488A CN 105354037 B CN105354037 B CN 105354037B
- Authority
- CN
- China
- Prior art keywords
- development
- version
- leaved
- functional module
- needed
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 26
- 230000008878 coupling Effects 0.000 claims description 12
- 238000010168 coupling process Methods 0.000 claims description 12
- 238000005859 coupling reaction Methods 0.000 claims description 12
- 230000006870 function Effects 0.000 description 12
- 230000008569 process Effects 0.000 description 9
- 230000003252 repetitive effect Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Landscapes
- Stored Programmes (AREA)
Abstract
The present invention provides a kind of modular software development methodology and software development apparatus, wherein modular software development methodology, comprising: stores the source code of at least one version of developed functional module；Software project leaved for development is divided into multiple functional modules leaved for development, and version information needed for determining each functional module leaved for development；According to the source code of version information needed for each functional module leaved for development and at least one version of the developed functional module, it is determined whether the source code of version needed for being stored with any functional module leaved for development；When the source code of version needed for being stored with any functional module leaved for development in determination, the source code of version needed for any functional module leaved for development is mounted in the software project and is debugged.Technical solution of the present invention can reduce the development amount of software project, and then shorten the development cycle of software project, improve the development efficiency of software project.
Description
Technical field
The present invention relates to technical field of software development, in particular to a kind of modular software development methodology and one
The modular software development apparatus of kind.
Background technique
In e-commerce system and other information management systems, rights management, user management, logistics management, Hui Yuanguan
The functions such as reason, merchandise control are the functions all having in most of management systems.But present information management system is being developed
When for backstage exploitation mainly have following several schemes:
1, using Web Service (be independent platform, lower coupling, it is self-contained, based on programmable Web
Application program) mode, module is directly broken into Jar file, processing is realized by the way of static loading Jar, by file
It is put into below Classpath and is called for the external world, an API (Application Programming is externally provided
Interface, application programming interface).When the function of a Jar file can not meet current demand, it can weigh
It is newly developed, it repacks, operates and be inconvenient.
2, using the configuration mode of XML (Extensible Markup Language, extensible markup language), first
It is that the component that will be needed is made into Jar file, when project initiation, by reading the configuration file finished writing in advance, dynamic adds
Carry Jar file.The module of needs can dynamically be added by only needing to modify configuration file, but the not control of version information
System, if current Jar file is problematic, needs to return to a version information and a complicated process.
3, by the way of relying on management, it (is based on item objects mould that most of project, which is all using Maven, now
Type, can be by a bit of description information come the software project management tool of the building of management project, report and document) either
Ant goes to establish dependence, the version of cited Jar is controlled, if a file modification, it is necessary to repack, again
The dependence for carrying out Jar packet, will increase very big workload in this way.
Therefore, the workload of software project in the process of development how is reduced, the development efficiency of software project is improved
As technical problem urgently to be resolved.
Summary of the invention
The present invention is based at least one above-mentioned technical problem, proposes a kind of new modular software development side
Case can realize the management to functional module version, and then can subtract while reducing to functional module progress repetitive operation
The development amount of few software project, shortens the development cycle of software project, improves the development efficiency of software project.
In view of this, the invention proposes a kind of modular software development methodologies, comprising: store developed function mould
The source code of at least one version of block；Software project leaved for development is divided into multiple functional modules leaved for development, and is determined
Version information needed for each functional module leaved for development；According to version needed for each functional module leaved for development
The source code of at least one version of information and the developed functional module, it is determined whether be stored with any function leaved for development
The source code of version needed for energy module；The source generation of version needed for being stored with any functional module leaved for development in determination
When code, the source code of version needed for any functional module leaved for development is mounted in the software project and is adjusted
Examination.
In the technical scheme, by the way that software project leaved for development is divided into multiple functional modules leaved for development, and really
Version information needed for fixed each functional module leaved for development, with the version needed for being stored with any functional module leaved for development
Source code when, the source code of version needed for any functional module leaved for development is mounted in software project and is debugged,
So that developed functional module can be reused when developing software project, and it can select to reuse as needed and develop
Functional module version, reduce to functional module carry out repetitive operation while, realize to functional module version
Management, and then the development amount of software project can be reduced, the development cycle of software project is shortened, software project is improved
Development efficiency.
In the above-mentioned technical solutions, it is preferable that determine whether to be stored with needed for any functional module leaved for development
It the step of source code of version, specifically includes: detecting whether to be stored in local store path described any leaved for development
The source code of version needed for functional module；If any function leaved for development is not detected in the local store path
The source code of version needed for energy module, then being detected in long-range store path according to the remote document access path of configuration is
It is no be stored with any functional module leaved for development needed for version source code.
In the technical scheme, for compared to the information obtained in long-range store path, path is locally stored in acquisition
In information can be more convenient, directly, therefore needed for determining whether to be stored with any functional module leaved for development version
When source code, can first it be detected in local store path, when being not detected in local store path, then
It is detected in long-range store path.
In any of the above-described technical solution, it is preferable that store the source generation of at least one version of developed functional module
It the step of code, specifically includes: described in being stored in the local store path and/or in the long-range store path
The source code of at least one version of the functional module of exploitation；
Wherein, the long-range store path includes the library GIT and/or the library Maven of creation.
In any of the above-described technical solution, it is preferable that by the source of version needed for any functional module leaved for development
Code is mounted to the step of being debugged in the software project and specifically includes: configuring text by configuration order row or loose coupling
The source code of version needed for any functional module leaved for development is mounted in the software project and debugs by part.
In the technical scheme, by way of configuration order row, can be convenient by any functional module leaved for development
The source code of required version, which is mounted in software project, to be debugged；By configuring loose coupling configuration file, it can be convenient ground
Upgrade components version, and a set of code can be made anywhere to establish association directly debugging, save the development time.
In any of the above-described technical solution, it is preferable that further include: determining not stored there is any function leaved for development
When the source code of version needed for module, create standard module file, for developer according to the standard module file to institute
Version needed for stating any functional module leaved for development is developed；The version needed for any functional module leaved for development
After this exploitation is completed, the source code of version needed for storing any functional module leaved for development.
In the technical scheme, it after being completed by the exploitation of the version needed for any functional module leaved for development, deposits
The source code of version needed for storing up any functional module leaved for development, so that being able to carry out in subsequent software development process
It reuses.
According to another aspect of the present invention, it is also proposed that a kind of modular software development apparatus, comprising: storage unit,
For storing the source code of at least one version of developed functional module；Division unit is used for software item leaved for development
Mesh is divided into multiple functional modules leaved for development, and version information needed for determining each functional module leaved for development；Really
Order member, for the version information according to needed for each functional module leaved for development and the developed functional module
The source code of at least one version, it is determined whether the source code of version needed for being stored with any functional module leaved for development；Place
Unit is managed, the source code for version needed for determining in the determination unit and be stored with any functional module leaved for development
When, the source code of version needed for any functional module leaved for development is mounted in the software project and is debugged.
In the technical scheme, by the way that software project leaved for development is divided into multiple functional modules leaved for development, and really
Version information needed for fixed each functional module leaved for development, with the version needed for being stored with any functional module leaved for development
Source code when, the source code of version needed for any functional module leaved for development is mounted in software project and is debugged,
So that developed functional module can be reused when developing software project, and it can select to reuse as needed and develop
Functional module version, reduce to functional module carry out repetitive operation while, realize to functional module version
Management, and then the development amount of software project can be reduced, the development cycle of software project is shortened, software project is improved
Development efficiency.
In the above-mentioned technical solutions, it is preferable that the determination unit is specifically used for: detecting in local store path is
It is no be stored with any functional module leaved for development needed for version source code, if in the local store path not
The source code of version needed for detecting any functional module leaved for development, then according to the remote document access path of configuration
The source code of version needed for being stored with any functional module leaved for development is detected whether in long-range store path.
In the technical scheme, for compared to the information obtained in long-range store path, path is locally stored in acquisition
In information can be more convenient, directly, therefore needed for determining whether to be stored with any functional module leaved for development version
When source code, can first it be detected in local store path, when being not detected in local store path, then
It is detected in long-range store path.
In any of the above-described technical solution, it is preferable that the storage unit is specifically used for: in the local store path
In and/or store in the long-range store path the developed functional module at least one version source code；
Wherein, the long-range store path includes the library GIT and/or the library Maven of creation.
In any of the above-described technical solution, it is preferable that the processing unit is specifically used for: passing through configuration order row or loose coupling
Close configuration file, by the source code of version needed for any functional module leaved for development be mounted in the software project into
Row debugging.
In the technical scheme, by way of configuration order row, can be convenient by any functional module leaved for development
The source code of required version, which is mounted in software project, to be debugged；By configuring loose coupling configuration file, it can be convenient ground
Upgrade components version, and a set of code can be made anywhere to establish association directly debugging, save the development time.
In any of the above-described technical solution, it is preferable that further include: creating unit, for being determined not in the determination unit
When the source code of version needed for being stored with any functional module leaved for development, standard module file is created, for exploitation
Person develops version needed for any functional module leaved for development according to the standard module file；The storage is single
Member is also used to, and after the exploitation of the version needed for any functional module leaved for development is completed, is stored described any wait open
The source code of version needed for the functional module of hair.
In the technical scheme, it after being completed by the exploitation of the version needed for any functional module leaved for development, deposits
The source code of version needed for storing up any functional module leaved for development, so that being able to carry out in subsequent software development process
It reuses.
By above technical scheme, can realize while reducing to functional module progress repetitive operation to function mould
The management of block version, and then the development amount of software project can be reduced, the development cycle of software project is shortened, is improved
The development efficiency of software project.
Detailed description of the invention
Fig. 1 shows the schematic flow diagram of the modular software development methodology of embodiment according to the present invention；
Fig. 2 shows the schematic block diagrams of the modular software development apparatus of embodiment according to the present invention；
Fig. 3 shows the schematic block diagram of the modular software development system of embodiment according to the present invention；
Fig. 4 shows the storage mode schematic diagram of the functional module of embodiment according to the present invention；
Fig. 5 shows the modular software development process schematic diagram of embodiment according to the present invention.
Specific embodiment
To better understand the objects, features and advantages of the present invention, with reference to the accompanying drawing and specific real
Applying mode, the present invention is further described in detail.It should be noted that in the absence of conflict, the implementation of the application
Feature in example and embodiment can be combined with each other.
In the following description, numerous specific details are set forth in order to facilitate a full understanding of the present invention, still, the present invention may be used also
To be implemented using other than the one described here other modes, therefore, protection scope of the present invention is not by described below
Specific embodiment limitation.
Fig. 1 shows the schematic flow diagram of the modular software development methodology of embodiment according to the present invention.
As shown in Figure 1, the modular software development methodology of embodiment according to the present invention, comprising:
Step 102, the source code of at least one version of developed functional module is stored；
Step 104, software project leaved for development is divided into multiple functional modules leaved for development, and determine it is each it is described to
Version information needed for the functional module of exploitation；
Step 106, the version information according to needed for each functional module leaved for development and the developed function
The source code of at least one version of module, it is determined whether the source generation of version needed for being stored with any functional module leaved for development
Code；
Step 108, when the source code of version needed for being stored with any functional module leaved for development in determination, by institute
The source code of version needed for stating any functional module leaved for development, which is mounted in the software project, to be debugged.
In the technical scheme, by the way that software project leaved for development is divided into multiple functional modules leaved for development, and really
Version information needed for fixed each functional module leaved for development, with the version needed for being stored with any functional module leaved for development
Source code when, the source code of version needed for any functional module leaved for development is mounted in software project and is debugged,
So that developed functional module can be reused when developing software project, and it can select to reuse as needed and develop
Functional module version, reduce to functional module carry out repetitive operation while, realize to functional module version
Management, and then the development amount of software project can be reduced, the development cycle of software project is shortened, software project is improved
Development efficiency.
In the above-mentioned technical solutions, it is preferable that determine whether to be stored with needed for any functional module leaved for development
It the step of source code of version, specifically includes: detecting whether to be stored in local store path described any leaved for development
The source code of version needed for functional module；If any function leaved for development is not detected in the local store path
The source code of version needed for energy module, then being detected in long-range store path according to the remote document access path of configuration is
It is no be stored with any functional module leaved for development needed for version source code.
In the technical scheme, for compared to the information obtained in long-range store path, path is locally stored in acquisition
In information can be more convenient, directly, therefore needed for determining whether to be stored with any functional module leaved for development version
When source code, can first it be detected in local store path, when being not detected in local store path, then
It is detected in long-range store path.
In any of the above-described technical solution, it is preferable that store the source generation of at least one version of developed functional module
It the step of code, specifically includes: described in being stored in the local store path and/or in the long-range store path
The source code of at least one version of the functional module of exploitation；
Wherein, the long-range store path includes the library GIT and/or the library Maven of creation.
In any of the above-described technical solution, it is preferable that by the source of version needed for any functional module leaved for development
Code is mounted to the step of being debugged in the software project and specifically includes: configuring text by configuration order row or loose coupling
The source code of version needed for any functional module leaved for development is mounted in the software project and debugs by part.
In the technical scheme, by way of configuration order row, can be convenient by any functional module leaved for development
The source code of required version, which is mounted in software project, to be debugged；By configuring loose coupling configuration file, it can be convenient ground
Upgrade components version, and a set of code can be made anywhere to establish association directly debugging, save the development time.
In any of the above-described technical solution, it is preferable that further include: determining not stored there is any function leaved for development
When the source code of version needed for module, create standard module file, for developer according to the standard module file to institute
Version needed for stating any functional module leaved for development is developed；The version needed for any functional module leaved for development
After this exploitation is completed, the source code of version needed for storing any functional module leaved for development.
In the technical scheme, it after being completed by the exploitation of the version needed for any functional module leaved for development, deposits
The source code of version needed for storing up any functional module leaved for development, so that being able to carry out in subsequent software development process
It reuses.
Fig. 2 shows the schematic block diagrams of the modular software development apparatus of embodiment according to the present invention.
As shown in Fig. 2, the modular software development apparatus 200 of embodiment according to the present invention, comprising: storage unit
202, division unit 204, determination unit 206 and processing unit 208.
Wherein, storage unit 202, the source code of at least one version for storing developed functional module；It divides
Unit 204, for software project leaved for development to be divided into multiple functional modules leaved for development, and determination is each described to be developed
Functional module needed for version information；Determination unit 206, for the version according to needed for each functional module leaved for development
The source code of at least one version of this information and the developed functional module, it is determined whether be stored with any leaved for development
The source code of version needed for functional module；Processing unit 208 is stored with described appoint for determining in the determination unit 206
When the source code of version needed for one functional module leaved for development, by version needed for any functional module leaved for development
Source code is mounted in the software project and is debugged.
In the technical scheme, by the way that software project leaved for development is divided into multiple functional modules leaved for development, and really
Version information needed for fixed each functional module leaved for development, with the version needed for being stored with any functional module leaved for development
Source code when, the source code of version needed for any functional module leaved for development is mounted in software project and is debugged,
So that developed functional module can be reused when developing software project, and it can select to reuse as needed and develop
Functional module version, reduce to functional module carry out repetitive operation while, realize to functional module version
Management, and then the development amount of software project can be reduced, the development cycle of software project is shortened, software project is improved
Development efficiency.
In the above-mentioned technical solutions, it is preferable that the determination unit 206 is specifically used for: being examined in local store path
The source code for surveying version needed for whether being stored with any functional module leaved for development, if in the local store path
In any functional module leaved for development is not detected needed for version source code, then according to the remote document access of configuration
Path detects whether the source generation of version needed for being stored with any functional module leaved for development in long-range store path
Code.
In the technical scheme, for compared to the information obtained in long-range store path, path is locally stored in acquisition
In information can be more convenient, directly, therefore needed for determining whether to be stored with any functional module leaved for development version
When source code, can first it be detected in local store path, when being not detected in local store path, then
It is detected in long-range store path.
In any of the above-described technical solution, it is preferable that the storage unit 202 is specifically used for: in the local storage
The source generation of at least one version of the developed functional module is stored in path and/or in the long-range store path
Code；Wherein, the long-range store path includes the library GIT and/or the library Maven of creation.
In any of the above-described technical solution, it is preferable that the processing unit 208 is specifically used for: by configuration order row or
The source code of version needed for any functional module leaved for development is mounted to the software project by loose coupling configuration file
In debugged.
In the technical scheme, by way of configuration order row, can be convenient by any functional module leaved for development
The source code of required version, which is mounted in software project, to be debugged；By configuring loose coupling configuration file, it can be convenient ground
Upgrade components version, and a set of code can be made anywhere to establish association directly debugging, save the development time.
In any of the above-described technical solution, it is preferable that further include: creating unit 210, in the determination unit 206
Determine it is not stored have any functional module leaved for development needed for version source code when, create standard module file, with
Version needed for any functional module leaved for development is developed according to the standard module file for developer；It is described
Storage unit 202 is also used to, after the exploitation of the version needed for any functional module leaved for development is completed, described in storage
The source code of version needed for any functional module leaved for development.
In the technical scheme, it after being completed by the exploitation of the version needed for any functional module leaved for development, deposits
The source code of version needed for storing up any functional module leaved for development, so that being able to carry out in subsequent software development process
It reuses.
Fig. 3 shows the schematic block diagram of the modular software development system of embodiment according to the present invention.
As shown in figure 3, the modular software development system 300 of embodiment according to the present invention, comprising: order line load
Module 302, functional module storage unit 304 and management module 306, introduce the function of modules individually below:
Order line loading module 302: initially entering and need to create software item destination path, executes the order line of creation project
(such as happy new app v1.0) will create a series of file, the file including following path:
Src modules promotion app controllers, wherein be to put inside file controllers
The association requests of page invocation；
Src modules promotion app models, wherein put database manipulation inside file models
File；
Src modules promotion app views, wherein put page presentation file inside file views；
Src modules promotion conf Depend.xml, wherein, can by configuring depend.xml file
Directly functional module to be added in current project, when project initiation, can be added by reading the configuration file
The functional module of version required for carrying；
Src modules promotion conf Routes.xml, wherein routes.xml file is mainly configured with
The request path of module in the project.
Functional module storage unit 304: as shown in figure 4, there are two types of forms for the storage of functional module: one is local mould
Formula, the second is remote mode.Local mode is mainly stored in above locally specified server, the mode of definitive document carry
Realize the public of code；Remote mode is mainly realized by the creation library GIT and the library Maven.With version pipe general at present
Managing maximum is not both to carry out Version Control by way of managing original.It will be required by Http, Https, Udp agreement
The module wanted is got on local server, is imported among project finally by the mode of file mount, is compiled and portion
Administration.
Management module 306: using the configuration mode of file, configuration item mainly includes the path, remote of local file server
The path of the type (Maven, GIT) of journey server, remote file server, is directly embedded into original item in a manner of file
In mesh.Loose coupling configuration file can be easy to unified upgrade components version, so that a set of code is anywhere
It establishes association directly to debug, directly develops, save the plenty of time.
The realization process of modular software development system 300 is as described below:
1, it when functional module does not create, can be created by order line (such as happy new promotion v1.0)
The module of one standard, that is, a series of file and file are generated, such as above-mentioned file controllers, file
Press from both sides models, file views, depend.xml file and routes.xml file etc..
2, when functional module is original already existing, but is not referred in software project, need to pass through life
Row (such as happy get promotion v1.0) is enabled to carry out the acquisition of source code to module.It is used using a set of code many places, it is more
Place's compiling, solves the problems, such as block code repetitive operation.Wherein, the process of acquisition mainly includes following several steps:
2.1, the functional module whether local path has corresponding version can be detected first, assisted if there is with regard to passing through http
View gets the functional module in current project from local file server；
2.2, when local server does not correspond to the module of version, a telefile warehouse is had, is passed through
The access path of depend.xml file configuration remote file server and the type of remote warehouse.When executing order line
It waits, the automatic start command of meeting stores module in remote server among local server and current project.
3, the functional module can be mounted to by software item by order line (such as happy set promotion v1.0)
Code is debugged and modified among mesh, realizes the dynamic debugging of module.
4, it when not needing the functional module in project, needs through order line (such as happy setup promotion
V1.0) functional module can be unloaded from current software project, using the method in external member library, is managed collectively, solves
The problem of company's project management.
5, when deployment, it is only necessary to check that the storage path of configuration file and corresponding file can directly make
With original is directly disposed.It can be added using order line form dynamic when needing some module, not have to modification
Original；The source that module is obtained by configuration file, obtains the version information of module, has accomplished the back-up processing of resource；It is logical
The mechanism for crossing threaded file folder accomplishes to carry out real time modifying debugging to original；By the method in external member library, it is managed collectively, it will
Online bring point danger is preferably minimized, while reducing deployment on-line time difference problem.
It is illustrated by taking the product line of certain company as an example below with reference to Fig. 5: if stored functional module and its version
Include:
The following version of authority module: Q1.0, Q1.1, Q2.0, Q2.1；The following version of line module: U1.0, U1.1,
U2.0；The following version of merchandise module: P1.0, P1.1, P2.0, P2.1, P3.1；The following version of order module: O1.0,
O1.1、O2.0、O2.1。
Wherein, project 1 uses Q1.0 version, the U1.1 version of line module, the P1.0 version of merchandise module of authority module
Originally, the O1.1 version of order module；Project 2 uses Q1.0 version, U1.2 version, the merchandise module of line module of authority module
P1.0 version, the O2.1 version of order module；Project 3 using the Q1.1 version of authority module, the U2.1 version of line module,
P4.0 version, the O2.1 version of order module of merchandise module；Project 4 is using the Q2.0 version of authority module, line module
U1.1 version, the P4.0 version of merchandise module, the O1.1 version of order module.Later by all modules according to the need of each project
It asks and combines deployment by configuring, online publication, to reach the demand online according to functional configuration module.
The technical solution of the above embodiment of the present invention realizes following technical effect: 1, reducing block code repetitive operation
Problem accomplishes that a set of code repeatedly compiles；2, accomplish that project is managed collectively, solve the problems, such as company's project management；3, using life
Enable line mode dynamic addition removing module.
The technical scheme of the present invention has been explained in detail above with reference to the attached drawings, and the invention proposes a kind of new modular soft
Part development plan can realize the management to functional module version while reducing to functional module progress repetitive operation, into
And the development amount of software project can be reduced, the development cycle of software project is shortened, the exploitation of software project is improved
Efficiency.
The foregoing is only a preferred embodiment of the present invention, is not intended to restrict the invention, for the skill of this field
For art personnel, the invention may be variously modified and varied.All within the spirits and principles of the present invention, made any to repair
Change, equivalent replacement, improvement etc., should all be included in the protection scope of the present invention.
Claims (10)
1. a kind of modular software development methodology characterized by comprising
Store the source code of at least one version of developed functional module；
Software project leaved for development is divided into multiple functional modules leaved for development, and determines each function mould leaved for development
Version information needed for block；
According at least the one of version information needed for each functional module leaved for development and the developed functional module
The source code of a version, it is determined whether the source code of version needed for being stored with any functional module leaved for development；
It, will be described any to be developed when the source code of version needed for being stored with any functional module leaved for development in determination
Functional module needed for the source code of version be mounted in the software project leaved for development and debugged.
2. modular software development methodology according to claim 1, which is characterized in that determine whether to be stored with described appoint
It the step of source code of version needed for one functional module leaved for development, specifically includes:
The source generation of version needed for detecting whether to be stored with any functional module leaved for development in local store path
Code；
If the source generation of version needed for any functional module leaved for development is not detected in the local store path
Code, then detect whether to be stored in long-range store path described any to be developed according to the remote document access path of configuration
Functional module needed for version source code.
3. modular software development methodology according to claim 2, which is characterized in that store developed functional module
At least one version source code the step of, specifically include:
The developed functional module is stored in the local store path and/or in the long-range store path
At least one version source code；
Wherein, the long-range store path includes the library GIT and/or the library Maven of creation.
4. modular software development methodology according to claim 1, which is characterized in that by any function leaved for development
The source code of version needed for energy module is mounted to the step of being debugged in the software project leaved for development and specifically includes:
By configuration order row or loose coupling configuration file, by the source generation of version needed for any functional module leaved for development
Code, which is mounted in the software project leaved for development, to be debugged.
5. modular software development methodology according to any one of claim 1 to 4, which is characterized in that further include:
Determine it is not stored have any functional module leaved for development needed for version source code when, creation standard module text
Part, so that developer opens version needed for any functional module leaved for development according to the standard module file
Hair；
After the exploitation of the version needed for any functional module leaved for development is completed, any function leaved for development is stored
The source code of version needed for energy module.
6. a kind of modular software development apparatus characterized by comprising
Storage unit, the source code of at least one version for storing developed functional module；
Division unit for software project leaved for development to be divided into multiple functional modules leaved for development, and determines each described
Version information needed for functional module leaved for development；
Determination unit, for the version information according to needed for each functional module leaved for development and the developed function
The source code of at least one version of module, it is determined whether the source generation of version needed for being stored with any functional module leaved for development
Code；
Processing unit, for version needed for determining in the determination unit and be stored with any functional module leaved for development
When source code, the source code of version needed for any functional module leaved for development is mounted to the software item leaved for development
It is debugged in mesh.
7. modular software development apparatus according to claim 6, which is characterized in that the determination unit is specifically used
In:
The source generation of version needed for detecting whether to be stored with any functional module leaved for development in local store path
Code, if the source generation of version needed for any functional module leaved for development is not detected in the local store path
Code, then detect whether to be stored in long-range store path described any to be developed according to the remote document access path of configuration
Functional module needed for version source code.
8. modular software development apparatus according to claim 7, which is characterized in that the storage unit is specifically used
In:
The developed functional module is stored in the local store path and/or in the long-range store path
At least one version source code；
Wherein, the long-range store path includes the library GIT and/or the library Maven of creation.
9. modular software development apparatus according to claim 6, which is characterized in that the processing unit is specifically used
In:
By configuration order row or loose coupling configuration file, by the source generation of version needed for any functional module leaved for development
Code, which is mounted in the software project leaved for development, to be debugged.
10. modular software development apparatus according to any one of claims 6 to 9, which is characterized in that further include:
Creating unit, for the determination unit determine it is not stored have any functional module leaved for development needed for version
Source code when, create standard module file, for developer according to the standard module file to described any leaved for development
Version needed for functional module is developed；
The storage unit is also used to, and after the exploitation of the version needed for any functional module leaved for development is completed, is deposited
The source code of version needed for storing up any functional module leaved for development.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510857488.4A CN105354037B (en) | 2015-11-30 | 2015-11-30 | Modular software development methodology and software development apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510857488.4A CN105354037B (en) | 2015-11-30 | 2015-11-30 | Modular software development methodology and software development apparatus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105354037A CN105354037A (en) | 2016-02-24 |
| CN105354037B true CN105354037B (en) | 2019-04-16 |
Family
ID=55330013
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510857488.4A Active CN105354037B (en) | 2015-11-30 | 2015-11-30 | Modular software development methodology and software development apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105354037B (en) |
Families Citing this family (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106126204B (en) * | 2016-06-15 | 2019-03-19 | 中邮建技术有限公司 | A kind of information system based on modularized design is iterative to expand and develop method |
| CN106372857A (en) * | 2016-08-31 | 2017-02-01 | 上海锐鸿通信技术有限公司 | Method and system for automatically establishing project |
| CN106547545A (en) * | 2016-10-17 | 2017-03-29 | 桐城市闲产网络服务有限公司 | A kind of computer software development approach |
| CN107066246B (en) * | 2016-12-27 | 2021-03-05 | 深圳虚觅者科技有限公司 | Software development method and device |
| CN107193622B (en) * | 2017-05-16 | 2020-03-17 | 北京小米移动软件有限公司 | Code compiling processing method and device and terminal |
| CN107783787A (en) * | 2017-10-19 | 2018-03-09 | 平安科技（深圳）有限公司 | A kind of software systems method for splitting and terminal device |
| CN107861719A (en) * | 2017-12-18 | 2018-03-30 | 广东阿拉丁网络科技服务有限公司 | A kind of modular software development methodology |
| CN108256352B (en) * | 2018-01-15 | 2021-10-22 | 北京安博通科技股份有限公司 | Method, device and terminal for automatically packaging web protection feature library |
| CN108733366A (en) * | 2018-05-22 | 2018-11-02 | 深圳Tcl新技术有限公司 | The method, apparatus and computer readable storage medium of software product release code |
| CN108829378B (en) * | 2018-05-24 | 2022-06-21 | 北京顺丰同城科技有限公司 | Application software development method and device and electronic equipment |
| CN109146251A (en) * | 2018-07-24 | 2019-01-04 | 武汉空心科技有限公司 | Component- based development method and system |
| CN109408104B (en) * | 2018-09-18 | 2021-11-30 | 天津龙拳风暴科技有限公司 | Method and device for acquiring game integration information |
| CN110989985B (en) * | 2019-11-29 | 2024-01-23 | 深圳前海环融联易信息科技服务有限公司 | Maven-based dependency package management method, device, computer equipment and storage medium |
| CN111221512B (en) * | 2020-01-03 | 2023-12-05 | 杭州涂鸦信息技术有限公司 | Function module mixed use method, electronic device and storage medium |
| CN111831323A (en) * | 2020-05-29 | 2020-10-27 | 大数金科网络技术有限公司 | A containerized approach to incremental continuous delivery |
| CN111984369B (en) * | 2020-07-29 | 2022-11-22 | 苏州浪潮智能科技有限公司 | Container calling method and device |
| CN112068806B (en) * | 2020-09-09 | 2021-12-24 | 上海万向区块链股份公司 | Method and system for optimizing project management in software development |
| CN112732248A (en) * | 2020-12-30 | 2021-04-30 | 武汉木仓信息技术有限公司 | Modularized software development method and device, electronic equipment and storage medium |
| CN113094711B (en) * | 2021-04-30 | 2023-05-16 | 云南电网有限责任公司 | Open source code detection method and system based on staged project development |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1627255A (en) * | 2003-12-10 | 2005-06-15 | 英业达股份有限公司 | Method and system for automatically generating modular customer-tailored software |
| CN103092624A (en) * | 2013-01-25 | 2013-05-08 | 互动在线（北京）科技有限公司 | Content module development method and application (App) generation method based on cloud services |
| CN105049486A (en) * | 2015-06-16 | 2015-11-11 | 腾讯科技（北京）有限公司 | Version management and file pulling control methods for static files, version management and file pulling control devices, and version control system |
-
2015
- 2015-11-30 CN CN201510857488.4A patent/CN105354037B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1627255A (en) * | 2003-12-10 | 2005-06-15 | 英业达股份有限公司 | Method and system for automatically generating modular customer-tailored software |
| CN103092624A (en) * | 2013-01-25 | 2013-05-08 | 互动在线（北京）科技有限公司 | Content module development method and application (App) generation method based on cloud services |
| CN105049486A (en) * | 2015-06-16 | 2015-11-11 | 腾讯科技（北京）有限公司 | Version management and file pulling control methods for static files, version management and file pulling control devices, and version control system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105354037A (en) | 2016-02-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105354037B (en) | Modular software development methodology and software development apparatus | |
| US9760365B2 (en) | Systems, methods, and computer program products for a software build and load process using a compilation and deployment service | |
| KR101314949B1 (en) | Integration environment generator | |
| EP3798756A1 (en) | Industrial automation domain-specific language programming paradigm | |
| Almonaies et al. | Legacy system evolution towards service-oriented architecture | |
| CN101937336B (en) | Software asset bundling and consumption method and system | |
| Vogel et al. | A language for feedback loops in self-adaptive systems: Executable runtime megamodels | |
| CN102449598A (en) | Package design and generation | |
| CN104077140A (en) | Automatic compiling method and compiling device for continuous integration | |
| US20080276221A1 (en) | Method and apparatus for relations planning and validation | |
| US20180121852A1 (en) | Executing a business process by a standard business process engine | |
| Rademacher et al. | Microservice architecture and model-driven development: Yet singles, soon married (?) | |
| De Gouw et al. | Declarative elasticity in ABS | |
| De Gouw et al. | On the integration of automatic deployment into the ABS modeling language | |
| KR102242622B1 (en) | Method and system of providing solution for smart factory | |
| Dorodko et al. | Selective Java code transformation into AWS Lambda functions | |
| CN105493033A (en) | Declarative configuration elements | |
| Biehl et al. | Model-based service discovery and orchestration for OSLC services in tool chains | |
| Weigert et al. | Experiences in deploying model-driven engineering | |
| Jelschen | Service-oriented toolchains for software evolution | |
| US10958514B2 (en) | Generating application-server provisioning configurations | |
| CN107861719A (en) | A kind of modular software development methodology | |
| Oertel et al. | Interoperable requirements engineering: tool independent specification, validation and impact analysis | |
| Yang et al. | An introduction to the xSDK a community of diverse numerical HPC software packages. | |
| Cansado et al. | Unifying architectural and behavioural specifications of distributed components |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |