CN112130824A - Rapid delivery software architecture design method and system - Google Patents
Rapid delivery software architecture design method and system Download PDFInfo
- Publication number
- CN112130824A CN112130824A CN202011078213.8A CN202011078213A CN112130824A CN 112130824 A CN112130824 A CN 112130824A CN 202011078213 A CN202011078213 A CN 202011078213A CN 112130824 A CN112130824 A CN 112130824A
- Authority
- CN
- China
- Prior art keywords
- task
- delivery
- information
- release
- workload
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000013461 design Methods 0.000 title claims abstract description 122
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000007726 management method Methods 0.000 claims description 20
- 238000012790 confirmation Methods 0.000 claims description 19
- 238000004891 communication Methods 0.000 claims description 18
- 230000004044 response Effects 0.000 claims description 5
- 238000012797 qualification Methods 0.000 claims description 4
- 230000007246 mechanism Effects 0.000 abstract description 7
- 230000006870 function Effects 0.000 description 50
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 7
- 230000006835 compression Effects 0.000 description 6
- 238000007906 compression Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012938 design process Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the application belongs to the technical field of computers, and relates to a software architecture design method and a software architecture design system for rapid delivery. The method adopts a plurality of associated common design task allocation strategies to carry out real-time adjustment of integral or split allocation, so that the associated tasks can be guaranteed to be processed by an engineer as much as possible, time is saved, meanwhile, the split strategies guarantee that the allocation of the tasks still meets the mechanism of priority consideration of the working efficiency, and the tasks are guaranteed to be completed as soon as possible. The whole task is designed according to the whole delivery result, and each specific function can be designed in place.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and a system for designing a fast delivery software architecture.
Background
The traditional delivery result design process is that firstly, a client issues a task, the client provides a requirement, a designer is recruited, and the client and the designer communicate to clarify the detail of the requirement and pay corresponding cost; then entering a design stage, designing by a designer according to the requirement document, submitting a design draft in the design process, and delivering the design draft to a client; after receiving the design draft, the client gives out a modification suggestion, the designer completes the modification in a matching way, and then the client checks and accepts to pay the residual design cost.
At present, the bottleneck affecting the working efficiency of platform design mainly lies in two links of demand communication and collaborative design, in which a large amount of communication work between designers and clients and between designers is involved. On one hand, the manual communication is easy to miss or misunderstand the required details, and on the other hand, the repeated communication confirmation takes longer time, thereby causing the delay of delivery time.
The design of delivered products usually includes multiple functions, there is usually a certain relation between the multiple functions, and the whole design task amount is large, and it is difficult to complete the design within the specified time limit assigned to one designer. The design of the delivered result is split and processed by a plurality of designers together, a proper allocation strategy is needed, the work efficiency of engineers, namely the relevance between functions, is considered, at present, a standardized development system designed based on the delivered result still does not exist, and a reasonable allocation strategy does not exist, so that the smooth proceeding of the development work is met.
Disclosure of Invention
The embodiment of the application aims to provide a method and a system for designing a software architecture for rapid delivery, so as to solve the problem that at present, a standardized development system designed based on delivery results still does not exist, and a reasonable distribution strategy does not exist so as to meet the requirement of smooth development work.
In order to solve the above technical problem, an embodiment of the present application provides a method for designing a fast-delivery software architecture, which adopts the following technical solutions:
receiving a design release request sent by a release terminal, wherein the design release request at least carries basic software requirement information, functional requirement information and software product design information;
responding the design release request, creating at least one release task in a design task follow-up table based on the function demand information, and broadcasting the release task to a network, wherein the release task at least carries a task target condition;
receiving a task order receiving signal which is sent by a delivery terminal and corresponds to the release task, wherein the task order receiving signal at least carries delivery identification information;
establishing an incidence relation between the delivery identification information and the release task in the design task follow-up information;
after the delivery terminal finishes the task target condition of the release task, receiving a delivery result sent by the delivery terminal;
judging whether the delivery result meets the task target condition or not;
if the delivery result does not meet the task target condition, sending a delivery unqualified signal to a delivery terminal corresponding to the delivery identification information;
and if the delivery result meets the task target condition, carrying out expense settlement operation on the user corresponding to the delivery identification information.
In order to solve the above technical problem, an embodiment of the present application further provides a system for designing a fast delivery software architecture, which adopts the following technical solutions:
a management server; and
at least one issuing terminal and at least one delivery terminal which are in communication connection with the management server; wherein
The management server includes:
the request receiving module is used for receiving a design release request sent by a release terminal, wherein the design release request at least carries basic software requirement information, functional requirement information and software product design information;
a request response module, configured to respond to the design issue request, create at least one issue task in a design task follow-up table based on the function requirement information, and broadcast the issue task to a network, where the issue task at least carries a task target condition;
the order receiving signal receiving module is used for receiving a task order receiving signal which is sent by a delivery terminal and corresponds to the release task, and the task order receiving signal at least carries delivery identification information;
the task follow-up module is used for establishing the incidence relation between the delivery identification information and the release task in the design task follow-up information;
the delivery result receiving module is used for receiving the delivery result sent by the delivery terminal after the delivery terminal finishes the task target condition of the release task;
the target condition judging module is used for judging whether the delivery result meets the task target condition;
the delivery unqualified module is used for sending a delivery unqualified signal to a delivery terminal corresponding to the delivery identification information if the delivery result does not meet the task target condition;
and the delivery qualification module is used for carrying out expense settlement operation on the user corresponding to the delivery identification information if the delivery result meets the task target condition.
Compared with the prior art, the design method and the system for the rapid delivery software architecture provided by the embodiment of the application have the following main beneficial effects:
the design of delivery results is realized by adopting a standardized flow, the process is standardized, the service flow is standardized, repeated confirmation of a large number of conventional requirements is avoided, and the communication workload between a client and a designer is reduced.
The design of the whole delivery result is divided into a main design task and a common design task, the total workload is calculated according to the function type and the number of function points, and the function is distributed according to the working efficiency of each engineer, so that each engineer can finish the task within the specified time. The method adopts a plurality of associated common design task allocation strategies to carry out real-time adjustment of integral or split allocation, so that the associated tasks can be guaranteed to be processed by an engineer as much as possible, time is saved, meanwhile, the split strategies guarantee that the allocation of the tasks still meets the mechanism of priority consideration of the working efficiency, and the tasks are guaranteed to be completed as soon as possible. The whole task is designed according to the whole delivery result, and each specific function can be designed in place.
Drawings
In order to more clearly illustrate the solution of the present application, the drawings needed for describing the embodiments of the present application will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
FIG. 1 is an exemplary system architecture diagram in which the present application may be applied;
FIG. 2 is a flowchart illustrating an implementation of a fast-delivering software architecture design method according to an embodiment of the present disclosure;
FIG. 3 is a flowchart of an implementation of a workload distribution method according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating an implementation of a task workload obtaining method according to an embodiment of the present application;
fig. 5 is a flowchart illustrating an implementation of a task issuance confirmation method according to an embodiment of the present application;
FIG. 6 is a flowchart of an implementation of a method for processing a relinquishing task according to an embodiment of the present application;
FIG. 7 is a block diagram of a fast delivery software architecture design system provided in the second embodiment of the present application;
fig. 8 is a schematic structural diagram of a workload distribution apparatus according to a second embodiment of the present application;
fig. 9 is a schematic structural diagram of a workload distribution apparatus according to a second embodiment of the present application;
fig. 10 is a schematic structural diagram of a task issuance confirmation apparatus according to a second embodiment of the present application;
fig. 11 is a schematic structural diagram of a task abandonment processing device according to a second embodiment of the present application.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of this application or in the above-described drawings are used for distinguishing between different objects and not for describing a particular order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.
Example one
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have various communication client applications installed thereon, such as a web browser application, a shopping application, a search application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture experts Group Audio Layer III, mpeg compression standard Audio Layer 3), MP4 players (Moving Picture experts Group Audio Layer IV, mpeg compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like.
The server 105 may be a server providing various services, such as a background server providing support for pages displayed on the terminal devices 101, 102, 103.
It should be noted that the fast-delivery software architecture design method provided by the embodiment of the present application is generally executed by a server/terminal device.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
With continuing reference to fig. 2, a flowchart of an implementation of a fast-delivery software architecture design method provided by an embodiment of the present application is shown, and for convenience of explanation, only the portions relevant to the present application are shown.
In step S101, a design release request sent by a release terminal is received, where the design release request at least carries basic software requirement information, functional requirement information, and software product design information.
In the embodiment of the present application, an electronic device (for example, the server/terminal device shown in fig. 1) on which the fast delivery software architecture design method operates may receive a design issue request sent by the terminal device through a wired connection manner or a wireless connection manner. It is noted that the wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a UWB (ultra wideband) connection, and other wireless connection means now known or developed in the future.
In the embodiment of the present application, the issuing terminal or the delivering terminal may be various electronic devices having a display screen and supporting web browsing, including but not limited to a smart phone, a tablet computer, an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III, motion Picture Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion Picture Experts compression standard Audio Layer 4), a laptop portable computer, a desktop computer, and the like.
In the embodiment of the application, a client inputs the delivery result design project requirements through a publishing terminal, wherein the delivery result design project requirements comprise basic software requirement information, a software function requirement document and a software product design document which are submitted by the client. The client uploads the required file through the publishing terminal, and the management server side returns the page name according to the file name after receiving the required file. The client only needs to provide the necessary information according to the prompt of the system, other detailed requirement information is contained in the design document, the client does not need to provide more requirement information, and the requirement communication workload is reduced as much as possible.
In step S102, in response to the design issue request, at least one issue task is created in the design task follow-up table based on the function requirement information, and the issue task is broadcast to the network, where the issue task at least carries a task target condition.
In step S103, a task order receiving signal corresponding to the release task and sent by the delivery terminal is received, where the task order receiving signal at least carries delivery identification information.
In step S104, the association relationship between the delivery identification information and the delivery task is established in the design task follow-up information.
In step S105, after the delivery terminal completes the task target condition for issuing the task, the delivery result sent by the delivery terminal is received.
In step S106, it is determined whether the delivery result satisfies the task target condition.
In step S107, if the delivery result does not satisfy the task target condition, a delivery failure signal is transmitted to the delivery terminal corresponding to the delivery identification information.
In step S108, if the delivery result satisfies the task object condition, the fee settlement operation is performed to the user corresponding to the delivery identification information.
In the embodiment of the application, the design of the delivery result is realized by adopting a standardized flow, the process is standardized, the service flow is standardized, the repeated confirmation of a large number of conventional requirements is avoided, and the communication workload between a client and a designer is reduced.
In the embodiment of the application, the design of the whole delivery result is divided into a main design task and a common design task, the total workload is calculated according to the function type and the number of function points, and the function is distributed according to the working efficiency of each engineer, so that each engineer can finish the task within the specified time. The method adopts a plurality of associated common design task allocation strategies to carry out real-time adjustment of integral or split allocation, so that the associated tasks can be guaranteed to be processed by an engineer as much as possible, time is saved, meanwhile, the split strategies guarantee that the allocation of the tasks still meets the mechanism of priority consideration of the working efficiency, and the tasks are guaranteed to be completed as soon as possible. The whole task is designed according to the whole delivery result, and each specific function can be designed in place.
Continuing to refer to fig. 3, a flowchart of an implementation of the workload distribution method according to an embodiment of the present application is shown, and for convenience of description, only the relevant portions of the present application are shown.
As some optional manners of the first embodiment of the present application, before the step S104, the method further includes: step S201, step S202, step S203, and step S204.
In step S201, the current workload information and the saturation amount information corresponding to the delivery identification information are acquired.
In step S202, it is determined whether the sum of the current workload information and the task workload of the issue task exceeds the saturation amount information.
In step S203, if the sum of the current workload information and the task workload exceeds the saturation amount information, a task amount excess signal is transmitted to the delivery terminal.
In step S204, if the sum of the current workload information and the task workload does not exceed the saturation amount information, an operation of establishing an association relationship between the delivery identification information and the release task in the design task follow-up information is performed.
Continuing to refer to fig. 4, a flowchart of an implementation of the task workload obtaining method according to an embodiment of the present application is shown, and for convenience of description, only the relevant portions of the present application are shown.
As some optional manners of the first embodiment of the present application, step S201 specifically includes: step S301 and step S302.
In step S301, the platform standard function information base is read, and a platform standard function list is obtained in the platform standard function information base, where the platform standard function list carries workload information corresponding to the function point.
In step S302, the function point list information and the platform standard function list are compared to obtain the task workload corresponding to the function point list information.
Continuing to refer to fig. 5, a flowchart of an implementation of the task issuance confirmation method provided in the first embodiment of the present application is shown, and for convenience of description, only the relevant portions of the present application are shown.
As some optional manners of the first embodiment of the present application, after step S104, the method further includes: step S401, step S402, step S403, and step S404.
In step S401, a confirmation order receiving signal is sent to the delivery terminal, and the current time is used as the start time of the release task.
In step S402, it is determined whether the function point list information establishes an association relationship in a preset distribution time period.
In step S403, if the function point list information establishes an association relationship in a preset distribution time period, a distribution completion signal is output to the distribution terminal.
In step S404, if no association relationship is established in the function point list information within the preset distribution time period, an issue failure signal is output to the issuing terminal.
With continuing reference to fig. 6, a flowchart of an implementation of the method for processing a disclaimer task according to an embodiment of the present application is shown, and for convenience of description, only the portion related to the present application is shown.
As some optional manners of the first embodiment of the present application, before the step S105, a step S501, a step S502, a step S503, and a step S504 are further included.
In step S501, when the task abandon signal transmitted from the delivery terminal is received.
In step S502, it is determined whether the remaining task time satisfies the standard working time.
In step S503, if the remaining task time satisfies the standard working time, the release task is rebroadcast to the network.
In step S504, if the remaining task time does not satisfy the standard operating time, a task delay signal is output to the distribution terminal.
In summary, an embodiment of the present application provides a design method for a fast delivery software architecture, which receives a design issue request sent by an issue terminal, where the design issue request at least carries basic software requirement information, functional requirement information, and software product design information; responding to a design release request, creating at least one release task in a design task follow-up table based on the functional requirement information, and broadcasting the release task to a network, wherein the release task at least carries a task target condition; receiving a task order receiving signal which is sent by a delivery terminal and corresponds to a release task, wherein the task order receiving signal at least carries delivery identification information; establishing an incidence relation between delivery identification information and a release task in design task follow-up information; after the delivery terminal finishes the task target condition of the release task, receiving a delivery result sent by the delivery terminal; judging whether the delivery result meets the task target condition or not; if the delivery result does not meet the task target condition, sending a delivery unqualified signal to a delivery terminal corresponding to the delivery identification information; and if the delivery result meets the task target condition, carrying out expense settlement operation on the user corresponding to the delivery identification information. The design of delivery results is realized by adopting a standardized flow, the process is standardized, the service flow is standardized, repeated confirmation of a large number of conventional requirements is avoided, and the communication workload between a client and a designer is reduced. The design of the whole delivery result is divided into a main design task and a common design task, the total workload is calculated according to the function type and the number of function points, and the function is distributed according to the working efficiency of each engineer, so that each engineer can finish the task within the specified time. The method adopts a plurality of associated common design task allocation strategies to carry out real-time adjustment of integral or split allocation, so that the associated tasks can be guaranteed to be processed by an engineer as much as possible, time is saved, meanwhile, the split strategies guarantee that the allocation of the tasks still meets the mechanism of priority consideration of the working efficiency, and the tasks are guaranteed to be completed as soon as possible. The whole task is designed according to the whole delivery result, and each specific function can be designed in place.
The block chain referred by the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
The application is operational with numerous general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, hand-held or portable devices, tablet-type devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware associated with computer readable instructions, which can be stored in a computer readable storage medium, and when executed, can include processes of the embodiments of the methods described above. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a Read-Only Memory (ROM), or a Random Access Memory (RAM).
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
Example two
With further reference to fig. 7, as an implementation of the method shown in fig. 2, the present application provides an embodiment of a fast delivery software architecture design system, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be applied to various electronic devices.
As shown in fig. 7, the fast-delivery software architecture design system of the present embodiment includes: a management server 200; and at least one distribution terminal 300 and at least one delivery terminal 400 communicatively connected with the management server 200. Wherein:
the management server 200 includes:
a request receiving module 201, configured to receive a design release request sent by a release terminal, where the design release request at least carries basic software requirement information, functional requirement information, and software product design information;
a request response module 202, configured to respond to a design issue request, create at least one issue task in a design task follow-up table based on the functional requirement information, and broadcast the issue task to a network, where the issue task at least carries a task target condition;
the order receiving signal receiving module 203 is configured to receive a task order receiving signal corresponding to the release task and sent by the delivery terminal, where the task order receiving signal at least carries delivery identification information;
the task follow-up module 204 is configured to establish an association relationship between the delivery identification information and the release task in the design task follow-up information;
a delivery result receiving module 205, configured to receive a delivery result sent by the delivery terminal after the delivery terminal completes a task target condition of the release task;
a target condition judgment module 206, configured to judge whether the delivery result meets the task target condition;
a delivery disqualification module 207, configured to send a delivery disqualification signal to the delivery terminal corresponding to the delivery identification information if the delivery result does not meet the task target condition;
and the delivery qualification module 208 is configured to perform a fee settlement operation to the user corresponding to the delivery identification information if the delivery result meets the task target condition.
In the embodiment of the present application, an electronic device (for example, the server/terminal device shown in fig. 1) on which the fast delivery software architecture design method operates may receive a design issue request sent by the terminal device through a wired connection manner or a wireless connection manner. It is noted that the wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a UWB (ultra wideband) connection, and other wireless connection means now known or developed in the future.
In the embodiment of the present application, the issuing terminal or the delivering terminal may be various electronic devices having a display screen and supporting web browsing, including but not limited to a smart phone, a tablet computer, an e-book reader, an MP3 player (Moving Picture Experts Group Audio Layer III, motion Picture Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion Picture Experts compression standard Audio Layer 4), a laptop portable computer, a desktop computer, and the like.
In the embodiment of the application, a client inputs the delivery result design project requirements through a publishing terminal, wherein the delivery result design project requirements comprise basic software requirement information, a software function requirement document and a software product design document which are submitted by the client. The client uploads the required file through the publishing terminal, and the management server side returns the page name according to the file name after receiving the required file. The client only needs to provide the necessary information according to the prompt of the system, other detailed requirement information is contained in the design document, the client does not need to provide more requirement information, and the requirement communication workload is reduced as much as possible.
In the embodiment of the application, the design of the delivery result is realized by adopting a standardized flow, the process is standardized, the service flow is standardized, the repeated confirmation of a large number of conventional requirements is avoided, and the communication workload between a client and a designer is reduced.
In the embodiment of the application, the design of the whole delivery result is divided into a main design task and a common design task, the total workload is calculated according to the function type and the number of function points, and the function is distributed according to the working efficiency of each engineer, so that each engineer can finish the task within the specified time. The method adopts a plurality of associated common design task allocation strategies to carry out real-time adjustment of integral or split allocation, so that the associated tasks can be guaranteed to be processed by an engineer as much as possible, time is saved, meanwhile, the split strategies guarantee that the allocation of the tasks still meets the mechanism of priority consideration of the working efficiency, and the tasks are guaranteed to be completed as soon as possible. The whole task is designed according to the whole delivery result, and each specific function can be designed in place.
Continuing to refer to fig. 8, a schematic structural diagram of the workload distribution apparatus according to the second embodiment of the present application is shown, and for convenience of description, only relevant portions of the present application are shown.
As some optional manners of the second embodiment of the present application, the management server 200 further includes: a workload obtaining module 209, a workload determination module 210, a workload overage module 211, and a workload appropriateness module 212. Wherein:
a workload obtaining module 209, configured to obtain current workload information and saturation amount information corresponding to the delivery identification information;
a workload judging module 210, configured to judge whether a sum of current workload information and task workload of a release task exceeds saturation information;
the workload excess module 211 is configured to send a task amount excess signal to the delivery terminal if the sum of the current workload information and the task workload exceeds the saturation amount information;
and a workload appropriateness module 212, configured to execute, if the sum of the current workload information and the task workload does not exceed the saturation amount information, an operation of establishing an association relationship between the delivery identification information and the release task in the design task follow-up information.
With continued reference to fig. 9, a schematic structural diagram of the workload distribution apparatus provided in the second embodiment of the present application is shown, and for convenience of description, only relevant portions of the present application are shown.
As some optional manners of the second embodiment of the present application, the workload obtaining module 209 specifically includes: a workload capture sub-module 2091 and a task workload capture sub-module 2092. Wherein:
the workload obtaining sub-module 2091 is configured to read the platform standard function information base, and obtain a platform standard function list from the platform standard function information base, where the platform standard function list carries workload information corresponding to the function point;
the task workload obtaining sub-module 2092 is configured to compare the function point list information with the platform standard function list to obtain a task workload corresponding to the function point list information.
With reference to fig. 10, a schematic structural diagram of a task issuance confirmation apparatus according to the second embodiment of the present application is shown, and for convenience of description, only relevant portions of the present application are shown.
As some optional manners of the second embodiment of the present application, the management server 200 further includes: a confirmation order taking module 213, an association confirmation module 214, a release completion module 215, and a release failure module 216. Wherein:
the order receiving confirmation module 213 is used for sending a order receiving confirmation signal to the delivery terminal and taking the current time as the starting time of the release task;
the association confirmation module 214 is configured to determine whether the function point list information establishes an association relationship in a preset distribution time period;
a release completion module 215, configured to output a release completion signal to the release terminal if the function point list information establishes an association relationship in a preset distribution time period;
the release failure module 216 is configured to output a release failure signal to the release terminal if no association relationship is established in the function point list information in the preset distribution time period.
With reference to fig. 11, a schematic structural diagram of a abandoned task processing device according to the second embodiment of the present application is shown, and for convenience of description, only relevant portions of the present application are shown.
As some optional manners of the second embodiment of the present application, the management server 200 further includes: an abort signal reception module 217, a remaining time determination module 218, a rebroadcast module 219, and a task postponement module 220. Wherein:
an abandon signal receiving module 217, configured to receive an abandon task signal sent by the delivery terminal;
a remaining time judging module 218, configured to judge whether the remaining task time meets the standard working time;
a rebroadcasting module 219, configured to rebroadcast the release task to the network if the remaining task time meets the standard working time;
and the task delay module 220 is configured to output a task delay signal to the issuing terminal if the remaining task time does not meet the standard working time.
To sum up, the second embodiment of the present application provides a fast delivery software architecture design system, which includes: a management server; at least one release terminal and at least one delivery terminal which are in communication connection with the management server; wherein the management server includes: the request receiving module is used for receiving a design release request sent by a release terminal, wherein the design release request at least carries basic software requirement information, functional requirement information and software product design information; the request response module is used for responding to the design release request, creating at least one release task in the design task follow-up table based on the functional requirement information, and broadcasting the release task to the network, wherein the release task at least carries a task target condition; the order receiving signal receiving module is used for receiving a task order receiving signal which is sent by the delivery terminal and corresponds to the release task, and the task order receiving signal at least carries delivery identification information; the task follow-up module is used for establishing an incidence relation between the delivery identification information and the release task in the design task follow-up information; the delivery result receiving module is used for receiving a delivery result sent by the delivery terminal after the delivery terminal finishes the task target condition of the release task; the target condition judging module is used for judging whether the delivery result meets the task target condition; the delivery disqualification module is used for sending a delivery disqualification signal to a delivery terminal corresponding to the delivery identification information if the delivery result does not meet the task target condition; and the delivery qualification module is used for carrying out expense settlement operation on the user corresponding to the delivery identification information if the delivery result meets the task target condition. The design of delivery results is realized by adopting a standardized flow, the process is standardized, the service flow is standardized, repeated confirmation of a large number of conventional requirements is avoided, and the communication workload between a client and a designer is reduced. The design of the whole delivery result is divided into a main design task and a common design task, the total workload is calculated according to the function type and the number of function points, and the function is distributed according to the working efficiency of each engineer, so that each engineer can finish the task within the specified time. The method adopts a plurality of associated common design task allocation strategies to carry out real-time adjustment of integral or split allocation, so that the associated tasks can be guaranteed to be processed by an engineer as much as possible, time is saved, meanwhile, the split strategies guarantee that the allocation of the tasks still meets the mechanism of priority consideration of the working efficiency, and the tasks are guaranteed to be completed as soon as possible. The whole task is designed according to the whole delivery result, and each specific function can be designed in place.
It is to be understood that the above-described embodiments are merely illustrative of some, but not restrictive, of the broad invention, and that the appended drawings illustrate preferred embodiments of the invention and do not limit the scope of the invention. This application is capable of embodiments in many different forms and is provided for the purpose of enabling a thorough understanding of the disclosure of the application. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to one skilled in the art that the present application may be practiced without modification or with equivalents of some of the features described in the foregoing embodiments. All equivalent structures made by using the contents of the specification and the drawings of the present application are directly or indirectly applied to other related technical fields and are within the protection scope of the present application.
Claims (10)
1. A fast-delivery software architecture design method is characterized by comprising the following steps:
receiving a design release request sent by a release terminal, wherein the design release request at least carries basic software requirement information, functional requirement information and software product design information;
responding the design release request, creating at least one release task in a design task follow-up table based on the function demand information, and broadcasting the release task to a network, wherein the release task at least carries a task target condition;
receiving a task order receiving signal which is sent by a delivery terminal and corresponds to the release task, wherein the task order receiving signal at least carries delivery identification information;
establishing an incidence relation between the delivery identification information and the release task in the design task follow-up information;
after the delivery terminal finishes the task target condition of the release task, receiving a delivery result sent by the delivery terminal;
judging whether the delivery result meets the task target condition or not;
if the delivery result does not meet the task target condition, sending a delivery unqualified signal to a delivery terminal corresponding to the delivery identification information;
and if the delivery result meets the task target condition, carrying out expense settlement operation on the user corresponding to the delivery identification information.
2. The method for designing software architecture for rapid delivery according to claim 1, wherein the step of associating the delivery identification information with the release task in the design task follow-up information further comprises the following steps:
acquiring current workload information and saturation information corresponding to the delivery identification information;
judging whether the sum of the current workload information and the task workload of the release task exceeds the saturation information;
if the sum of the current workload information and the task workload exceeds the saturation amount information, sending a task amount excess signal to the delivery terminal;
and if the sum of the current workload information and the task workload does not exceed the saturation amount information, executing the operation of establishing the association relationship between the delivery identification information and the release task in the design task follow-up information.
3. The method for designing a software architecture for rapid delivery according to claim 2, wherein the functional requirement information further includes functional point list information, and the step of acquiring the current workload information and the saturation amount information corresponding to the delivery identification information specifically includes the following steps:
reading a platform standard function information base, and acquiring a platform standard function list in the platform standard function information base, wherein the platform standard function list carries workload information corresponding to a function point;
and comparing the function point list information with the platform standard function list to obtain the task workload corresponding to the function point list information.
4. The method for designing a software architecture for rapid delivery according to claim 3, wherein the task target condition further includes a time condition, and after the step of establishing the association relationship between the delivery identification information and the release task in the design task follow-up information, the method specifically includes the following steps:
sending a signal for confirming order receiving to the delivery terminal, and taking the current time as the starting time of the release task;
judging whether the function point list information establishes an association relation in a preset distribution time period or not;
if the functional point list information establishes an association relation in a preset distribution time period, outputting a distribution completion signal to the distribution terminal;
and if the association relation is not established in the function point list information within a preset distribution time period, outputting a release failure signal to the release terminal.
5. The method for designing a software architecture for rapid delivery according to claim 3, wherein the platform standard function list further carries standard working time, and the method specifically comprises the following steps before the step of receiving the delivery result sent by the delivery terminal after the delivery terminal completes the task object:
if receiving a task abandoning signal sent by the delivery terminal;
judging whether the residual task time meets the standard working time or not;
if the residual task time meets the standard working time, the release task is broadcasted to the network again;
and if the residual task time does not meet the standard working time, outputting a task delay signal to the issuing terminal.
6. A rapid delivery software architecture design system, the system comprising:
a management server; and
at least one issuing terminal and at least one delivery terminal which are in communication connection with the management server; wherein
The management server includes:
the request receiving module is used for receiving a design release request sent by a release terminal, wherein the design release request at least carries basic software requirement information, functional requirement information and software product design information;
a request response module, configured to respond to the design issue request, create at least one issue task in a design task follow-up table based on the function requirement information, and broadcast the issue task to a network, where the issue task at least carries a task target condition;
the order receiving signal receiving module is used for receiving a task order receiving signal which is sent by a delivery terminal and corresponds to the release task, and the task order receiving signal at least carries delivery identification information;
the task follow-up module is used for establishing the incidence relation between the delivery identification information and the release task in the design task follow-up information;
the delivery result receiving module is used for receiving the delivery result sent by the delivery terminal after the delivery terminal finishes the task target condition of the release task;
the target condition judging module is used for judging whether the delivery result meets the task target condition;
the delivery unqualified module is used for sending a delivery unqualified signal to a delivery terminal corresponding to the delivery identification information if the delivery result does not meet the task target condition;
and the delivery qualification module is used for carrying out expense settlement operation on the user corresponding to the delivery identification information if the delivery result meets the task target condition.
7. The rapid delivery software architecture design system according to claim 6, wherein the management server further comprises:
the workload obtaining module is used for obtaining current workload information and saturation information corresponding to the delivery identification information;
the workload judging module is used for judging whether the sum of the current workload information and the task workload of the release task exceeds the saturation information;
the workload excess module is used for sending a task amount excess signal to the delivery terminal if the sum of the current workload information and the task workload exceeds the saturation amount information;
and the workload appropriateness module is used for executing the operation of establishing the association relationship between the delivery identification information and the release task in the design task follow-up information if the sum of the current workload information and the task workload does not exceed the saturation amount information.
8. The rapid delivery software architecture design system of claim 7, wherein the workload acquisition module comprises:
the workload acquisition submodule is used for reading a platform standard function information base and acquiring a platform standard function list in the platform standard function information base, and the platform standard function list carries workload information corresponding to the function point;
and the task workload obtaining submodule is used for comparing the function point list information with the platform standard function list to obtain the task workload corresponding to the function point list information.
9. The rapid delivery software architecture design system according to claim 8, wherein the management server further comprises:
the order receiving confirmation module is used for sending an order receiving confirmation signal to the delivery terminal and taking the current time as the starting time of the release task;
the association confirmation module is used for judging whether the function point list information establishes association relation in a preset distribution time period or not;
the release completion module is used for outputting a release completion signal to the release terminal if the function point list information establishes the association relation in a preset distribution time period;
and the release failure module is used for outputting a release failure signal to the release terminal if the function point list information does not establish the association relation in the preset distribution time period.
10. The rapid delivery software architecture design system according to claim 8, wherein the management server further comprises:
the abandon signal receiving module is used for receiving the abandon task signal sent by the delivery terminal;
the residual time judging module is used for judging whether the residual task time meets the standard working time or not;
a rebroadcasting module, configured to rebroadcast the release task to the network if the remaining task time meets the standard working time;
and the task delay module is used for outputting a task delay signal to the issuing terminal if the residual task time does not meet the standard working time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011078213.8A CN112130824A (en) | 2020-10-10 | 2020-10-10 | Rapid delivery software architecture design method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011078213.8A CN112130824A (en) | 2020-10-10 | 2020-10-10 | Rapid delivery software architecture design method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112130824A true CN112130824A (en) | 2020-12-25 |
Family
ID=73844087
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011078213.8A Pending CN112130824A (en) | 2020-10-10 | 2020-10-10 | Rapid delivery software architecture design method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112130824A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116739820A (en) * | 2023-08-16 | 2023-09-12 | 广东卓柏信息科技有限公司 | Block chain-based data processing method and data processing system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002037234A2 (en) * | 2000-10-20 | 2002-05-10 | Brown Kenneth B | System and method for collaborative order fulfillment |
| CN108876202A (en) * | 2018-07-24 | 2018-11-23 | 武汉空心科技有限公司 | Design work management method, platform and the system quickly delivered |
| CN108920143A (en) * | 2018-06-23 | 2018-11-30 | 上海泽阳智能科技有限公司 | A kind of quick development method for interactive software |
| CN109034609A (en) * | 2018-07-24 | 2018-12-18 | 武汉空心科技有限公司 | The software product design method and system quickly delivered |
| CN109214646A (en) * | 2018-07-24 | 2019-01-15 | 武汉空心科技有限公司 | The software system architecture design method and system quickly delivered |
| CN109597814A (en) * | 2018-12-06 | 2019-04-09 | 广州万惠信息技术咨询服务有限公司 | A kind of online quick delivery system of back-stage management information system |
| CN109740851A (en) * | 2018-12-03 | 2019-05-10 | 上海夫卡实业发展有限公司 | Design for Automatic Control Engineering work management method, platform and the system quickly delivered |
-
2020
- 2020-10-10 CN CN202011078213.8A patent/CN112130824A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2002037234A2 (en) * | 2000-10-20 | 2002-05-10 | Brown Kenneth B | System and method for collaborative order fulfillment |
| CN108920143A (en) * | 2018-06-23 | 2018-11-30 | 上海泽阳智能科技有限公司 | A kind of quick development method for interactive software |
| CN108876202A (en) * | 2018-07-24 | 2018-11-23 | 武汉空心科技有限公司 | Design work management method, platform and the system quickly delivered |
| CN109034609A (en) * | 2018-07-24 | 2018-12-18 | 武汉空心科技有限公司 | The software product design method and system quickly delivered |
| CN109214646A (en) * | 2018-07-24 | 2019-01-15 | 武汉空心科技有限公司 | The software system architecture design method and system quickly delivered |
| CN109740851A (en) * | 2018-12-03 | 2019-05-10 | 上海夫卡实业发展有限公司 | Design for Automatic Control Engineering work management method, platform and the system quickly delivered |
| CN109597814A (en) * | 2018-12-06 | 2019-04-09 | 广州万惠信息技术咨询服务有限公司 | A kind of online quick delivery system of back-stage management information system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116739820A (en) * | 2023-08-16 | 2023-09-12 | 广东卓柏信息科技有限公司 | Block chain-based data processing method and data processing system |
| CN116739820B (en) * | 2023-08-16 | 2024-01-19 | 广东卓柏信息科技有限公司 | Block chain-based data processing method and data processing system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20070079128A1 (en) | Electronic signature system and method | |
| CN103139299B (en) | Cloud service dispatching method between cloudy and system | |
| US20220391642A1 (en) | Method and apparatus for evaluating joint training model | |
| KR20130037051A (en) | Method and server for providing expert matching service | |
| CN106487655B (en) | Message interaction method and device and processing server | |
| US20070055634A1 (en) | Automated anonymous connection system (AACS) for facilitating business communication | |
| CN112130824A (en) | Rapid delivery software architecture design method and system | |
| CN112860662A (en) | Data blood relationship establishing method and device, computer equipment and storage medium | |
| CN108921522A (en) | A kind of method and apparatus that the cloud data sharing based on business subcontract automatically processes | |
| CN112988311A (en) | On-line experimental method based on WEB server | |
| CN102404302A (en) | Method for dispatching service and service dispatching server | |
| US20140032744A1 (en) | Method of comparing outputs in a plurality of information systems | |
| CN112035256A (en) | Resource allocation method, device, electronic equipment and medium | |
| CN111291045A (en) | Service isolation data transmission method and device, computer equipment and storage medium | |
| CN111552663A (en) | File consistency verification method and device, computer equipment and storage medium | |
| CN111026560A (en) | Method and device for processing product data, computer equipment and storage medium | |
| CN114374737A (en) | Message pushing method and device, computer equipment and storage medium | |
| JP2002183454A (en) | Method and system for request for quotation in electronic business | |
| CN114724561A (en) | Voice interruption method and device, computer equipment and storage medium | |
| CN114238585A (en) | Query method and device based on 5G message, computer equipment and storage medium | |
| CN113626438A (en) | Data table management method and device, computer equipment and storage medium | |
| CN114615325A (en) | Message pushing method and device, computer equipment and storage medium | |
| CN114221964A (en) | Access request processing method and device, computer equipment and storage medium | |
| CN113822704A (en) | Method and device for calculating discount cost, electronic equipment and readable storage medium | |
| CN111597441A (en) | Information processing method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |