CN105354037A - Modularized software developing method and software developing device - Google Patents
Modularized software developing method and software developing device Download PDFInfo
- Publication number
- CN105354037A CN105354037A CN201510857488.4A CN201510857488A CN105354037A CN 105354037 A CN105354037 A CN 105354037A CN 201510857488 A CN201510857488 A CN 201510857488A CN 105354037 A CN105354037 A CN 105354037A
- Authority
- CN
- China
- Prior art keywords
- development
- version
- functional module
- leaved
- source code
- 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.)
- Granted
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a modularized software developing method and software developing device. The modularized software developing method comprises the following steps: storing a source code of at least one version of a developed function module; dividing a to-be-developed software project into a plurality of to-be-developed function modules, and determining required version information for each to be-developed function module; determining whether the source code of the required version for any to-be-developed function module is stored according to the required version information for each to-be-developed function module and the source code of at least one version of the developed function module; mounting the source code of the required version for any to-be-developed function module to the software project to debug while determining that the source code of the required version for any to-be-developed function module is stored. Through the adoption of the technical scheme provided by the invention, the development workload of the software project can be reduced, and then the development period of the software project is shortened, and the development efficiency of the software project is improved.
Description
Technical field
The present invention relates to technical field of software development, in particular to the modular software development methodology of one and the modular software development apparatus of one.
Background technology
In e-commerce system and other information management systems, the functions such as rights management, user management, logistics management, member management, merchandise control are the functions all had in most of management system.But, several scheme below present information management system mainly contains for backstage exploitation when developing:
1, adopt WebService (be a platform independently, low coupling, self-contained, based on programmable web application) mode, module is directly broken into Jar file, the mode of static loading Jar is adopted to realize process, file is put into below Classpath and calls for the external world, an API (ApplicationProgrammingInterface, application programming interface) is externally provided.When the function of a Jar file can not meet current demand time, again can develop, repack, operate very inconvenient.
2, XML (ExtensibleMarkupLanguage is adopted, extend markup language) configuration mode, be first also that the assembly of needs is made Jar file, when project initiation, by reading the configuration file finished writing in advance, dynamic load Jar file.Only needing to revise configuration file and just can add the module of needs dynamically, but do not have the control of version information, if current Jar file has problem, need to get back to a version information, is also a complicated process.
3, the mode relying on management is adopted, present most project is all adopt Maven (to be based on item objects model, carry out the software project management instrument of the structure of management project, report and document by a bit of descriptor) or ant go to set up dependence, control quote the version of Jar, if a file modification, must repack, re-start the dependence of Jar bag, very large workload can be increased like this.
Therefore, how can reduce software project workload on stream, the development efficiency improving software project becomes technical matters urgently to be resolved hurrily.
Summary of the invention
The present invention just based on above-mentioned technical matters one of at least, propose a kind of modular software development scheme newly, can while minimizing carries out repetitive operation to functional module, realize the management to functional module version, and then the development amount of software project can be reduced, shorten the construction cycle of software project, improve the development efficiency of software project.
In view of this, the present invention proposes a kind of modular software development methodology, comprising: the source code storing at least one version of the functional module developed; Software project leaved for development is divided into multiple functional module leaved for development, and determines the version information needed for each described functional module leaved for development; The source code of the version information needed for each described functional module leaved for development and at least one version of the described functional module developed, determines whether the source code of the version stored needed for arbitrary functional module leaved for development; When determining the source code of the version stored needed for described arbitrary functional module leaved for development, the source code of the version needed for described arbitrary functional module leaved for development being mounted in described software project and debugging.
In this technical scheme, by software project leaved for development is divided into multiple functional module leaved for development, and determine the version information needed for each functional module leaved for development, with when storing the source code of the version needed for arbitrary functional module leaved for development, the source code of the version needed for arbitrary functional module leaved for development is mounted in software project and debugs, make when developing software project, the functional module developed can be reused, and the version of reusing the functional module developed can be selected as required, while decreasing repetitive operation carried out to functional module, achieve the management to functional module version, and then the development amount of software project can be reduced, shorten the construction cycle of software project, improve the development efficiency of software project.
In technique scheme, preferably, determine whether the step of the source code of the version stored needed for described arbitrary functional module leaved for development, specifically comprise: the source code detecting the version whether stored needed for described arbitrary functional module leaved for development in the store path of this locality; If the source code of the version needed for described arbitrary functional module leaved for development do not detected in the store path of described this locality, then in long-range store path, detect the source code of the version whether stored needed for described arbitrary functional module leaved for development according to the remote document access path of configuration.
In this technical scheme, compared to the information obtained in long-range store path, the information obtained in local store path can be more convenient, direct, therefore when determining whether the source code of the version stored needed for arbitrary functional module leaved for development, can first detect in the store path of this locality, when not detecting in the store path in this locality, then detect in long-range store path.
In above-mentioned arbitrary technical scheme, preferably, store the step of the source code of at least one version of the functional module developed, specifically comprise: the source code of at least one version of the functional module developed described in storing in the store path of described this locality and/or in described long-range store path;
Wherein, described long-range store path comprises GIT storehouse and/or the Maven storehouse of establishment.
In above-mentioned arbitrary technical scheme, preferably, the source code of the version needed for described arbitrary functional module leaved for development is mounted in described software project the step of carrying out debugging specifically comprise: by configuration order row or loose coupling configuration file, the source code of the version needed for described arbitrary functional module leaved for development is mounted in described software project and debugs.
In this technical scheme, by the mode of configuration order row, easily the source code of the version needed for arbitrary functional module leaved for development can be mounted in software project and debug; By configuration loose coupling configuration file, can upgrade components version easily, and a set of code can be made anywhere to be associated directly debugging, save the development time.
In above-mentioned arbitrary technical scheme, preferably, also comprise: when determining the source code of the version do not stored needed for described arbitrary functional module leaved for development, create standard module file, according to described standard module file, the version needed for described arbitrary functional module leaved for development is developed for developer; After the version needed for described arbitrary functional module leaved for development has been developed, store the source code of the version needed for described arbitrary functional module leaved for development.
In this technical scheme, by after having developed the version needed for arbitrary functional module leaved for development, store the source code of the version needed for arbitrary functional module leaved for development, made, in follow-up software development process, can be reused.
According to a further aspect in the invention, also proposed a kind of modular software development apparatus, comprising: storage unit, for storing the source code of at least one version of the functional module developed; Division unit, for software project leaved for development is divided into multiple functional module leaved for development, and determines the version information needed for each described functional module leaved for development; Determining unit, for the source code of at least one version of the version information needed for each described functional module leaved for development and the described functional module developed, determines whether the source code of the version stored needed for arbitrary functional module leaved for development; Processing unit, during for determining the source code of the version stored needed for described arbitrary functional module leaved for development in described determining unit, is mounted to the source code of the version needed for described arbitrary functional module leaved for development in described software project and debugs.
In this technical scheme, by software project leaved for development is divided into multiple functional module leaved for development, and determine the version information needed for each functional module leaved for development, with when storing the source code of the version needed for arbitrary functional module leaved for development, the source code of the version needed for arbitrary functional module leaved for development is mounted in software project and debugs, make when developing software project, the functional module developed can be reused, and the version of reusing the functional module developed can be selected as required, while decreasing repetitive operation carried out to functional module, achieve the management to functional module version, and then the development amount of software project can be reduced, shorten the construction cycle of software project, improve the development efficiency of software project.
In technique scheme, preferably, described determining unit is specifically for the source code that detects the version whether stored needed for described arbitrary functional module leaved for development in the store path of this locality, if the source code of the version needed for described arbitrary functional module leaved for development do not detected in the store path of described this locality, then in long-range store path, detect the source code of the version whether stored needed for described arbitrary functional module leaved for development according to the remote document access path of configuration.
In this technical scheme, compared to the information obtained in long-range store path, the information obtained in local store path can be more convenient, direct, therefore when determining whether the source code of the version stored needed for arbitrary functional module leaved for development, can first detect in the store path of this locality, when not detecting in the store path in this locality, then detect in long-range store path.
In above-mentioned arbitrary technical scheme, preferably, described storage unit is specifically for the source code of at least one version of functional module developed described in storing in the store path of described this locality and/or in described long-range store path; Wherein, described long-range store path comprises GIT storehouse and/or the Maven storehouse of establishment.
In above-mentioned arbitrary technical scheme, preferably, described processing unit specifically for: by configuration order row or loose coupling configuration file, the source code of the version needed for described arbitrary functional module leaved for development is mounted in described software project and debugs.
In this technical scheme, by the mode of configuration order row, easily the source code of the version needed for arbitrary functional module leaved for development can be mounted in software project and debug; By configuration loose coupling configuration file, can upgrade components version easily, and a set of code can be made anywhere to be associated directly debugging, save the development time.
In above-mentioned arbitrary technical scheme, preferably, also comprise: creating unit, during for determining the source code of the version do not stored needed for described arbitrary functional module leaved for development in described determining unit, create standard module file, according to described standard module file, the version needed for described arbitrary functional module leaved for development is developed for developer; Described storage unit also for, after the version needed for described arbitrary functional module leaved for development has been developed, stored the source code of the version needed for described arbitrary functional module leaved for development.
In this technical scheme, by after having developed the version needed for arbitrary functional module leaved for development, store the source code of the version needed for arbitrary functional module leaved for development, made, in follow-up software development process, can be reused.
By above technical scheme, while minimizing carries out repetitive operation to functional module, the management to functional module version can be realized, and then the development amount of software project can be reduced, shorten the construction cycle of software project, improve the development efficiency of software project.
Accompanying drawing explanation
Fig. 1 shows the schematic flow diagram of modular according to an embodiment of the invention software development methodology;
Fig. 2 shows the schematic block diagram of modular according to an embodiment of the invention software development apparatus;
Fig. 3 shows the schematic block diagram of modular according to an embodiment of the invention software development system;
Fig. 4 shows the storage mode schematic diagram of functional module according to an embodiment of the invention;
Fig. 5 shows modular according to an embodiment of the invention software development process schematic diagram.
Embodiment
In order to more clearly understand above-mentioned purpose of the present invention, feature and advantage, below in conjunction with the drawings and specific embodiments, the present invention is further described in detail.It should be noted that, when not conflicting, the feature in the embodiment of the application and embodiment can combine mutually.
Set forth a lot of detail in the following description so that fully understand the present invention; but; the present invention can also adopt other to be different from other modes described here and implement, and therefore, protection scope of the present invention is not by the restriction of following public specific embodiment.
Fig. 1 shows the schematic flow diagram of modular according to an embodiment of the invention software development methodology.
As shown in Figure 1, modular according to an embodiment of the invention software development methodology, comprising:
Step 102, stores the source code of at least one version of the functional module developed;
Step 104, is divided into multiple functional module leaved for development by software project leaved for development, and determines the version information needed for each described functional module leaved for development;
Step 106, the source code of the version information needed for each described functional module leaved for development and at least one version of the described functional module developed, determines whether the source code of the version stored needed for arbitrary functional module leaved for development;
Step 108, when determining the source code of the version stored needed for described arbitrary functional module leaved for development, being mounted to the source code of the version needed for described arbitrary functional module leaved for development in described software project and debugging.
In this technical scheme, by software project leaved for development is divided into multiple functional module leaved for development, and determine the version information needed for each functional module leaved for development, with when storing the source code of the version needed for arbitrary functional module leaved for development, the source code of the version needed for arbitrary functional module leaved for development is mounted in software project and debugs, make when developing software project, the functional module developed can be reused, and the version of reusing the functional module developed can be selected as required, while decreasing repetitive operation carried out to functional module, achieve the management to functional module version, and then the development amount of software project can be reduced, shorten the construction cycle of software project, improve the development efficiency of software project.
In technique scheme, preferably, determine whether the step of the source code of the version stored needed for described arbitrary functional module leaved for development, specifically comprise: the source code detecting the version whether stored needed for described arbitrary functional module leaved for development in the store path of this locality; If the source code of the version needed for described arbitrary functional module leaved for development do not detected in the store path of described this locality, then in long-range store path, detect the source code of the version whether stored needed for described arbitrary functional module leaved for development according to the remote document access path of configuration.
In this technical scheme, compared to the information obtained in long-range store path, the information obtained in local store path can be more convenient, direct, therefore when determining whether the source code of the version stored needed for arbitrary functional module leaved for development, can first detect in the store path of this locality, when not detecting in the store path in this locality, then detect in long-range store path.
In above-mentioned arbitrary technical scheme, preferably, store the step of the source code of at least one version of the functional module developed, specifically comprise: the source code of at least one version of the functional module developed described in storing in the store path of described this locality and/or in described long-range store path;
Wherein, described long-range store path comprises GIT storehouse and/or the Maven storehouse of establishment.
In above-mentioned arbitrary technical scheme, preferably, the source code of the version needed for described arbitrary functional module leaved for development is mounted in described software project the step of carrying out debugging specifically comprise: by configuration order row or loose coupling configuration file, the source code of the version needed for described arbitrary functional module leaved for development is mounted in described software project and debugs.
In this technical scheme, by the mode of configuration order row, easily the source code of the version needed for arbitrary functional module leaved for development can be mounted in software project and debug; By configuration loose coupling configuration file, can upgrade components version easily, and a set of code can be made anywhere to be associated directly debugging, save the development time.
In above-mentioned arbitrary technical scheme, preferably, also comprise: when determining the source code of the version do not stored needed for described arbitrary functional module leaved for development, create standard module file, according to described standard module file, the version needed for described arbitrary functional module leaved for development is developed for developer; After the version needed for described arbitrary functional module leaved for development has been developed, store the source code of the version needed for described arbitrary functional module leaved for development.
In this technical scheme, by after having developed the version needed for arbitrary functional module leaved for development, store the source code of the version needed for arbitrary functional module leaved for development, made, in follow-up software development process, can be reused.
Fig. 2 shows the schematic block diagram of modular according to an embodiment of the invention software development apparatus.
As shown in Figure 2, modular according to an embodiment of the invention software development apparatus 200, comprising: storage unit 202, division unit 204, determining unit 206 and processing unit 208.
Wherein, storage unit 202, for storing the source code of at least one version of the functional module developed; Division unit 204, for software project leaved for development is divided into multiple functional module leaved for development, and determines the version information needed for each described functional module leaved for development; Determining unit 206, for the source code of at least one version of the version information needed for each described functional module leaved for development and the described functional module developed, determines whether the source code of the version stored needed for arbitrary functional module leaved for development; Processing unit 208, during for determining the source code of the version stored needed for described arbitrary functional module leaved for development in described determining unit 206, the source code of the version needed for described arbitrary functional module leaved for development is mounted in described software project and debugs.
In this technical scheme, by software project leaved for development is divided into multiple functional module leaved for development, and determine the version information needed for each functional module leaved for development, with when storing the source code of the version needed for arbitrary functional module leaved for development, the source code of the version needed for arbitrary functional module leaved for development is mounted in software project and debugs, make when developing software project, the functional module developed can be reused, and the version of reusing the functional module developed can be selected as required, while decreasing repetitive operation carried out to functional module, achieve the management to functional module version, and then the development amount of software project can be reduced, shorten the construction cycle of software project, improve the development efficiency of software project.
In technique scheme, preferably, described determining unit 206 is specifically for the source code that detects the version whether stored needed for described arbitrary functional module leaved for development in the store path of this locality, if the source code of the version needed for described arbitrary functional module leaved for development do not detected in the store path of described this locality, then in long-range store path, detect the source code of the version whether stored needed for described arbitrary functional module leaved for development according to the remote document access path of configuration.
In this technical scheme, compared to the information obtained in long-range store path, the information obtained in local store path can be more convenient, direct, therefore when determining whether the source code of the version stored needed for arbitrary functional module leaved for development, can first detect in the store path of this locality, when not detecting in the store path in this locality, then detect in long-range store path.
In above-mentioned arbitrary technical scheme, preferably, described storage unit 202 is specifically for the source code of at least one version of functional module developed described in storing in the store path of described this locality and/or in described long-range store path; Wherein, described long-range store path comprises GIT storehouse and/or the Maven storehouse of establishment.
In above-mentioned arbitrary technical scheme, preferably, described processing unit 208 specifically for: by configuration order row or loose coupling configuration file, the source code of the version needed for described arbitrary functional module leaved for development is mounted in described software project and debugs.
In this technical scheme, by the mode of configuration order row, easily the source code of the version needed for arbitrary functional module leaved for development can be mounted in software project and debug; By configuration loose coupling configuration file, can upgrade components version easily, and a set of code can be made anywhere to be associated directly debugging, save the development time.
In above-mentioned arbitrary technical scheme, preferably, also comprise: creating unit 210, during for determining the source code of the version do not stored needed for described arbitrary functional module leaved for development in described determining unit 206, create standard module file, according to described standard module file, the version needed for described arbitrary functional module leaved for development is developed for developer; Described storage unit 202 also for, after the version needed for described arbitrary functional module leaved for development has been developed, stored the source code of the version needed for described arbitrary functional module leaved for development.
In this technical scheme, by after having developed the version needed for arbitrary functional module leaved for development, store the source code of the version needed for arbitrary functional module leaved for development, made, in follow-up software development process, can be reused.
Fig. 3 shows the schematic block diagram of modular according to an embodiment of the invention software development system.
As shown in Figure 3, modular according to an embodiment of the invention software development system 300, comprising: order line load-on module 302, functional module storage unit 304 and administration module 306, introduces the function of modules below respectively:
Order line load-on module 302: first enter and need to create software item destination path, the order line (as happynewappv1.0) performing establishment project can create a series of file, comprises the file in following path:
Src modules promotion app controllers, wherein, be put the association requests of page invocation inside file controllers;
Src modules promotion app models, wherein, inside file models, put database manipulation file;
Src modules promotion app views, wherein, inside file views, put page presentation file;
Src modules promotion conf Depend.xml, wherein, by configuration depend.xml file, can directly functional module be added in current project, when project initiation time, just can load the functional module of required version by reading this configuration file;
Src modules promotion conf Routes.xml, wherein, routes.xml file is mainly configured with module request path in the project.
Functional module storage unit 304: as shown in Figure 4, functional module deposited two kinds of forms: first local mode, it two is remote modes.Local mode mainly leaves in above the server of specifying this locality, the mode code of definitive document carry public; Remote mode is mainly realized by establishment GIT storehouse and Maven storehouse.With maximum not being both of version management general at present, carry out Version Control by the mode managing original.Get on home server by Http, Https, Udp agreement by required module, the mode finally by file mount imports among project, carries out compiling and disposing.
Administration module 306: the configuration mode adopting file, configuration item mainly comprises the path of local file server, the type (Maven, GIT) of remote server, the path of remote file server, is directly embedded in original project in the mode of file.Loose coupling configuration file can be easy to unified upgrade components version, thus a set of code can be made anywhere to be associated directly debugging, directly develops, saves the plenty of time.
The implementation procedure of modular software development system 300 is as described below:
1, when functional module does not create, the module of a standard can be created by order line (as happynewpromotionv1.0), namely generate a series of file and file, file controllers described above, file models, file views, depend.xml file and routes.xml file etc.
2, when functional module originally existed, but when not being referred in software project, the acquisition by order line (as happygetpromotionv1.0), module being carried out to source code is needed.Adopt a set of code many places to use, many places compile, and solve block code repetitive operation problem.Wherein, the process of acquisition mainly comprises several step below:
2.1, first can detect this functional module whether local path has corresponding version, just by http agreement, this functional module be got in the middle of current project from local file server if existed;
2.2, when home server does not have the module of corresponding version, a telefile warehouse is had, by the access path of depend.xml file configuration remote file server and the type of remote warehouse.When fill order row time, the automatic startup command of meeting, among module stores in remote server to home server and current project.
3, this functional module can be mounted among software project by order line (as happysetpromotionv1.0) and carry out debugging and revising code, achieve the dynamic debugging of module.
4, when not needing this functional module in project, need this functional module to be unloaded from current software project by order line (as happysetuppromotionv1.0), have employed the method in external member storehouse, unified management, solve the problem of company's project management.
When 5, disposing, only need to check depositing path and just can directly using of configuration file and corresponding file, original is directly disposed.Order line form can be adopted dynamically to add when needs some modules time, need not original be revised; By the source of configuration file acquisition module, the version information of acquisition module, has accomplished the back-up processing of resource; By the mechanism that chained file presss from both sides, accomplish to carry out real time modifying debugging to original; By the method in external member storehouse, unified management, a point danger of bringing reaching the standard grade drops to minimum, reduces simultaneously and disposes on-line time difference problem.
Be described for the product line of certain company below in conjunction with Fig. 5: if the functional module stored and version thereof comprise:
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 adopts Q1.0 version, the U1.1 version of line module, the P1.0 version of merchandise module, the O1.1 version of order module of authority module; Project 2 adopts Q1.0 version, the U1.2 version of line module, the P1.0 version of merchandise module, the O2.1 version of order module of authority module; Project 3 adopts Q1.1 version, the U2.1 version of line module, the P4.0 version of merchandise module, the O2.1 version of order module of authority module; Project 4 adopts Q2.0 version, the U1.1 version of line module, the P4.0 version of merchandise module, the O1.1 version of order module of authority module.Afterwards all modules are combined deployment according to the demand of each project by configuration, issue of reaching the standard grade, thus reach the demand of reaching the standard grade according to functional configuration module.
The technical scheme of the above embodiment of the present invention achieves following technique effect: 1, decrease block code repetitive operation problem, accomplishes that a set of code repeatedly compiles; 2, accomplish project unified management, solve the problem of company's project management; 3, command line mode is adopted dynamically to add removing module.
More than be described with reference to the accompanying drawings technical scheme of the present invention, the present invention proposes a kind of modular software development scheme newly, can while minimizing carries out repetitive operation to functional module, realize the management to functional module version, and then the development amount of software project can be reduced, shorten the construction cycle of software project, improve the development efficiency of software project.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. a modular software development methodology, is characterized in that, comprising:
Store the source code of at least one version of the functional module developed;
Software project leaved for development is divided into multiple functional module leaved for development, and determines the version information needed for each described functional module leaved for development;
The source code of the version information needed for each described functional module leaved for development and at least one version of the described functional module developed, determines whether the source code of the version stored needed for arbitrary functional module leaved for development;
When determining the source code of the version stored needed for described arbitrary functional module leaved for development, the source code of the version needed for described arbitrary functional module leaved for development being mounted in described software project and debugging.
2. modular software development methodology according to claim 1, is characterized in that, determines whether the step of the source code of the version stored needed for described arbitrary functional module leaved for development, specifically comprises:
The source code of the version whether stored needed for described arbitrary functional module leaved for development is detected in the store path of this locality;
If the source code of the version needed for described arbitrary functional module leaved for development do not detected in the store path of described this locality, then in long-range store path, detect the source code of the version whether stored needed for described arbitrary functional module leaved for development according to the remote document access path of configuration.
3. modular software development methodology according to claim 2, is characterized in that, stores the step of the source code of at least one version of the functional module developed, specifically comprises:
The source code of at least one version of the functional module developed described in storing in the store path of described this locality and/or in described long-range store path;
Wherein, described long-range store path comprises GIT storehouse and/or the Maven storehouse of establishment.
4. modular software development methodology according to claim 1, is characterized in that, the source code of the version needed for described arbitrary functional module leaved for development is mounted in described software project the step of carrying out debugging and specifically comprises:
By configuration order row or loose coupling configuration file, the source code of the version needed for described arbitrary functional module leaved for development is mounted in described software project and debugs.
5. modular software development methodology according to any one of claim 1 to 4, is characterized in that, also comprise:
When determining the source code of the version do not stored needed for described arbitrary functional module leaved for development, creating standard module file, according to described standard module file, the version needed for described arbitrary functional module leaved for development being developed for developer;
After the version needed for described arbitrary functional module leaved for development has been developed, store the source code of the version needed for described arbitrary functional module leaved for development.
6. a modular software development apparatus, is characterized in that, comprising:
Storage unit, for storing the source code of at least one version of the functional module developed;
Division unit, for software project leaved for development is divided into multiple functional module leaved for development, and determines the version information needed for each described functional module leaved for development;
Determining unit, for the source code of at least one version of the version information needed for each described functional module leaved for development and the described functional module developed, determines whether the source code of the version stored needed for arbitrary functional module leaved for development;
Processing unit, during for determining the source code of the version stored needed for described arbitrary functional module leaved for development in described determining unit, is mounted to the source code of the version needed for described arbitrary functional module leaved for development in described software project and debugs.
7. modular software development apparatus according to claim 6, is characterized in that, described determining unit specifically for:
The source code of the version whether stored needed for described arbitrary functional module leaved for development is detected in the store path of this locality, if the source code of the version needed for described arbitrary functional module leaved for development do not detected in the store path of described this locality, then in long-range store path, detect the source code of the version whether stored needed for described arbitrary functional module leaved for development according to the remote document access path of configuration.
8. modular software development apparatus according to claim 7, is characterized in that, described storage unit specifically for:
The source code of at least one version of the functional module developed described in storing in the store path of described this locality and/or in described long-range store path;
Wherein, described long-range store path comprises GIT storehouse and/or the Maven storehouse of establishment.
9. modular software development apparatus according to claim 6, is characterized in that, described processing unit specifically for:
By configuration order row or loose coupling configuration file, the source code of the version needed for described arbitrary functional module leaved for development is mounted in described software project and debugs.
10. the modular software development apparatus according to any one of claim 6 to 9, is characterized in that, also comprise:
Creating unit, during for determining the source code of the version do not stored needed for described arbitrary functional module leaved for development in described determining unit, create standard module file, according to described standard module file, the version needed for described arbitrary functional module leaved for development is developed for developer;
Described storage unit also for, after the version needed for described arbitrary functional module leaved for development has been developed, stored the source code of the version needed for described arbitrary 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 true CN105354037A (en) | 2016-02-24 |
| CN105354037B 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) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106126204A (en) * | 2016-06-15 | 2016-11-16 | 中邮建技术有限公司 | A kind of iterative regarded as output controlling method of information system based on modularized design |
| 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 |
| CN107066246A (en) * | 2016-12-27 | 2017-08-18 | 深圳虚觅者科技有限公司 | A kind of software development methodology and device |
| CN107193622A (en) * | 2017-05-16 | 2017-09-22 | 北京小米移动软件有限公司 | Processing method, device and the terminal of code compilation |
| 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 |
| CN108256352A (en) * | 2018-01-15 | 2018-07-06 | 北京安博通科技股份有限公司 | A kind of method, apparatus and terminal of web protection feature database automatic packaging |
| CN108733366A (en) * | 2018-05-22 | 2018-11-02 | 深圳Tcl新技术有限公司 | The method, apparatus and computer readable storage medium of software product release code |
| CN108829378A (en) * | 2018-05-24 | 2018-11-16 | 北京顺丰同城科技有限公司 | A kind of development approach of application software, device and electronic equipment |
| CN109146251A (en) * | 2018-07-24 | 2019-01-04 | 武汉空心科技有限公司 | Component- based development method and system |
| CN109408104A (en) * | 2018-09-18 | 2019-03-01 | 天津龙拳风暴科技有限公司 | A kind of method and device for obtaining game and integrating information |
| CN110989985A (en) * | 2019-11-29 | 2020-04-10 | 深圳前海环融联易信息科技服务有限公司 | Maven-based dependency package management method and device, computer equipment and storage medium |
| CN111221512A (en) * | 2020-01-03 | 2020-06-02 | 杭州涂鸦信息技术有限公司 | Function module mixing method, electronic device, and storage medium |
| CN111831323A (en) * | 2020-05-29 | 2020-10-27 | 大数金科网络技术有限公司 | Containerized incremental continuous delivery method |
| CN111984369A (en) * | 2020-07-29 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Container calling method and device |
| CN112068806A (en) * | 2020-09-09 | 2020-12-11 | 上海万向区块链股份公司 | 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 |
| CN113094711A (en) * | 2021-04-30 | 2021-07-09 | 云南电网有限责任公司 | 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 | 英业达股份有限公司 | Automatic method for generating modular software of user customized and system |
| 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 | 英业达股份有限公司 | Automatic method for generating modular software of user customized and system |
| 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 |
Cited By (29)
| 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 |
| CN106126204A (en) * | 2016-06-15 | 2016-11-16 | 中邮建技术有限公司 | A kind of iterative regarded as output controlling method of information system based on modularized design |
| 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 |
| CN107066246A (en) * | 2016-12-27 | 2017-08-18 | 深圳虚觅者科技有限公司 | A kind of software development methodology and device |
| CN107066246B (en) * | 2016-12-27 | 2021-03-05 | 深圳虚觅者科技有限公司 | Software development method and device |
| CN107193622A (en) * | 2017-05-16 | 2017-09-22 | 北京小米移动软件有限公司 | Processing method, device and the terminal of code compilation |
| 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 |
| CN108256352A (en) * | 2018-01-15 | 2018-07-06 | 北京安博通科技股份有限公司 | A kind of method, apparatus and terminal of web protection feature database automatic packaging |
| 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 |
| CN108829378A (en) * | 2018-05-24 | 2018-11-16 | 北京顺丰同城科技有限公司 | A kind of development approach of application software, device and electronic equipment |
| 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 |
| CN109408104A (en) * | 2018-09-18 | 2019-03-01 | 天津龙拳风暴科技有限公司 | A kind of method and device for obtaining game and integrating information |
| CN109408104B (en) * | 2018-09-18 | 2021-11-30 | 天津龙拳风暴科技有限公司 | Method and device for acquiring game integration information |
| CN110989985A (en) * | 2019-11-29 | 2020-04-10 | 深圳前海环融联易信息科技服务有限公司 | Maven-based dependency package management method and device, computer equipment and storage medium |
| CN110989985B (en) * | 2019-11-29 | 2024-01-23 | 深圳前海环融联易信息科技服务有限公司 | Maven-based dependency package management method, device, computer equipment and storage medium |
| CN111221512A (en) * | 2020-01-03 | 2020-06-02 | 杭州涂鸦信息技术有限公司 | Function module mixing method, electronic device, 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 | 大数金科网络技术有限公司 | Containerized incremental continuous delivery method |
| CN111984369A (en) * | 2020-07-29 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Container calling method and device |
| CN111984369B (en) * | 2020-07-29 | 2022-11-22 | 苏州浪潮智能科技有限公司 | Container calling method and device |
| CN112068806A (en) * | 2020-09-09 | 2020-12-11 | 上海万向区块链股份公司 | 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 |
| CN113094711A (en) * | 2021-04-30 | 2021-07-09 | 云南电网有限责任公司 | Open source code detection method and system based on staged project development |
| CN113094711B (en) * | 2021-04-30 | 2023-05-16 | 云南电网有限责任公司 | Open source code detection method and system based on staged project development |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105354037B (en) | 2019-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105354037A (en) | Modularized software developing method and software developing device | |
| CN106559438B (en) | Program uploading method and device based on target network platform | |
| CN104793946B (en) | Dispositions method and system are applied based on cloud computing platform | |
| EP3188009B1 (en) | Development, delivery, deployment and operation of an application | |
| CN109491695A (en) | A kind of increment updating method of integrated Android application | |
| CN103473108A (en) | Java code generating method | |
| KR20180038539A (en) | A method and system for implementing data tracking with a software development kit | |
| CN104077140A (en) | Automatic compiling method and compiling device for continuous integration | |
| CN104517181B (en) | Enterprise content management system and method for nuclear power station | |
| CN102141919A (en) | Modularized java application software online updating system and method | |
| CN104142825A (en) | Method and system for modularization development of products | |
| CN106293701A (en) | The application engine method for designing of many tenants version management based on cloud server | |
| CN106293704A (en) | Dynamic micro services edit methods, device and the server of multilingual cloud compiling | |
| CN104050261A (en) | Stormed-based variable logic general data processing system and method | |
| CN111736954B (en) | Multi-intelligent contract virtual machine implementation method, multi-intelligent contract virtual machine and system | |
| CN109284106A (en) | Method for release management, electronic device and the readable storage medium storing program for executing of business rule | |
| CN101162428A (en) | Method for acquiring and converting the state of component in the time of operation during software dynamic evolvement | |
| CN102023885A (en) | Method and system for storing bytecode of JCRE (Java card run time environment) | |
| CN111797157B (en) | Data processing method, system, electronic equipment and storage medium | |
| CN103678135A (en) | System and method for achieving cross-process and cross-thread debugging in large-data environment | |
| CN109032631A (en) | Application program service packs acquisition methods, device, computer equipment and storage medium | |
| CN104657142A (en) | CCFD (China Computational Fluid Dynamics) system based on OSGi (Open Service Gateway Initiative) technology | |
| CN110321131A (en) | Service Component packaging method, system and server | |
| CN113364515B (en) | Satellite remote control method, device, equipment and storage medium based on Xstate | |
| CN111158743B (en) | Big data operation and maintenance management platform |
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 |