CN115840560A - Management system for software development process - Google Patents

Management system for software development process Download PDF

Info

Publication number
CN115840560A
CN115840560A CN202310147040.8A CN202310147040A CN115840560A CN 115840560 A CN115840560 A CN 115840560A CN 202310147040 A CN202310147040 A CN 202310147040A CN 115840560 A CN115840560 A CN 115840560A
Authority
CN
China
Prior art keywords
software
unit
module
change
demand
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.)
Withdrawn
Application number
CN202310147040.8A
Other languages
Chinese (zh)
Inventor
李晓
李志云
田洁
周宁宁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shandong College Of Information Technology
Original Assignee
Shandong College Of Information Technology
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shandong College Of Information Technology filed Critical Shandong College Of Information Technology
Priority to CN202310147040.8A priority Critical patent/CN115840560A/en
Publication of CN115840560A publication Critical patent/CN115840560A/en
Withdrawn legal-status Critical Current

Links

Images

Abstract

The invention relates to the technical field of software development, and discloses a management system for a software development process, which comprises a demand unit, a development unit, a test unit, a defect unit and a change unit, wherein the demand unit collects the demands of customers so as to plan the functional targets of the developed software; and the evaluation formula of the evaluation standard is used for evaluating reasonability, consistency and traceability, and a weighting formula is used for carrying out comprehensive calculation, so that the calculation result is more accurate, the situation that the calculation cannot be carried out due to the fact that a larger defect exists in the evaluation formula when the evaluation formula is carried out in the development stage is avoided, and the development rigidness is ensured.

Description

Management system for software development process
Technical Field
The invention relates to the technical field of software development, in particular to a management system for a software development process.
Background
Software development is the process of building a software system or software parts in the system according to the requirements of users, the software development is a system engineering including requirement capture, requirement analysis, design, implementation and test, the software is generally realized by using a certain programming language, the software is divided into system software and application software, and not only includes programs which can run on a computer, but also files related to the programs are generally considered as a part of the software.
The software development process comprises the steps of designing the functions of software, realizing algorithms and methods, designing the overall structure and modules of the software, programming and debugging, jointly debugging and testing the program, then writing and submitting the program, and because the whole software development process has more steps, a management system is arranged to manage the whole process of software development so as to ensure the development process to be carried out sequentially, but the traditional software development process management system has the following problems:
during development of software, the most important aspect is the aspect of demand collection, and when the demand collection is performed in the prior art, the requirements cannot be considered in all aspects, so that after the demands are collected finally and software development is performed according to the demands, more customers do not meet the developed software, and the required period is longer when the software is developed;
at present, after software is developed, maintenance and updating are required to be carried out continuously in the follow-up process, when a customer puts forward a new requirement, the software needs to be upgraded according to the requirement of the customer, the requirement content of the customer is more, each requirement content is different, and part of requirements cannot be identified, so that a great amount of time is wasted when the requirement investigation is carried out.
Disclosure of Invention
In order to overcome the above-mentioned drawbacks of the prior art, embodiments of the present invention provide a management system for software development processes to solve the technical problems set forth in the background art.
In order to achieve the purpose, the invention provides the following technical scheme: a management system for a software development process, comprising: the system comprises a demand unit, a development unit, a test unit, a defect unit and a change unit, wherein the demand unit collects the demands of customers so as to plan the functional targets of developed software, the development unit develops target software according to the demands collected by the demand unit, the test unit tests the developed target software, the defect unit modifies the defects tested by the test unit, and the change unit collects the change demands of the customers and changes the target software;
the demand unit comprises an acquisition module, a review module and a prediction module, wherein the acquisition module acquires the demand information of a client and sends the demand information to the review module, the review module reviews the demand information of the client, the reviewed demand information is sent to the estimation module for prediction processing, and the demand information qualified in the prediction processing generates a demand specification and enters the development unit for formal software development;
the evaluation criteria in the evaluation module are feasibility Q, rationality p1, consistency p2 and traceability p3, and the calculation formula is
Figure SMS_1
Where M is the final review score, k1, k2, k3 are weights, and k1+ k2+ k3>0, the score criteria of the rationality p1, the consistency p2 and the traceability p3 are between 1 and 100, the score criteria of Q is 1 or 0, and when the score of K is 80 or more, the evaluation is passed.
In a preferred embodiment, the collection module comprises an individual demand system, a collective demand system and a functional information system, the individual demand system targets the individual demand information of the client to the software, the collective demand system collects the collective demand information, the functional information system collects the functional information which can be realized by the existing stage data, and matches the demands collected by the individual demand system, the collective demand system and the functional information system, and when the two can be matched, the demand collection is completed.
In a preferred embodiment, the system for collective demand comprises a blood margin population direction, a geomargin population direction, a business margin population direction and an interest margin population direction, and the demand information of the blood margin population direction, the geomargin population direction, the business margin population direction and the interest margin population direction is collected in a simultaneous and mutually-covered mode.
In a preferred embodiment, the development unit includes a code reuse module, a component reuse module, and a system reuse module, the code reuse module is implemented by using homomorphic mapping and can be modified when the code reuse module is mapped, the component reuse module uses a platform of homomorphic development components, and the components are all described by using XML language, the system reuse module generalizes, simplifies and analyzes the requirements proposed by the user to form a formalized specification, and searches a system analysis diagram with the highest matching degree from a component library, so that the analysis diagram is stored in the component library and used as a component for subsequent use.
In a preferred embodiment, the test unit includes an integrated test module, a functional test module and a system test module, the integrated test module tests the page, detects whether the style of each element in the page is consistent with the style in the demand information, detects the information provided in the page, determines whether the page information is accurate, stores the qualified data, and sends the unqualified data to the defect unit.
In a preferred embodiment, when the functional test module performs the test, the developed software is in a full operation state, the operation limit of the software system and the problem occurring when the software system is in full operation are tested, and the detected problem data is sent to the defect unit.
In a preferred embodiment, when the system test module runs, the software is combined with computer hardware, data supporting the software and workers in a formal environment, the software is run and tested in an actual running environment, the software is tested in an equivalent class division manner in a black box test, and the test standard is the definition of the software requirement specification on each required function.
The test unit comprises the following operation steps:
s1, a defect unit receives problem data of a test unit and hands over the problem data to a programmer;
s2, receiving problem data by a programmer, repairing software defects, and sending repaired software to a test unit after repairing the defects;
s3, the testing unit receives the software after the defect repair and carries out software testing again;
and S4, when the testing unit tests that the software has defects again, executing the step S1 and the step S2, and when the testing unit tests that the software has no defects, completing software development.
In a preferred embodiment, the requirement unit collects software use suggestion information of a client and sends the software use suggestion information to the change unit, the change unit receives the software use suggestion information sent by the requirement unit and generates change information, and the change unit changes object attributes and object behaviors of the software during running according to the change information.
In a preferred embodiment, the change unit includes an unconditional change module, a conditional change module and a non-changeable module, when the change information conforms to the unconditional change module, the unconditional execution change requirement is performed, when the change information conforms to the conditional change module, the conditional change module judges whether the change information satisfies the condition for executing the change, the change requirement is performed when the change information satisfies the condition, otherwise, the execution is rejected, the changed condition is the condition set by the auditor, and when the change information is the non-changeable module, the execution is rejected.
The invention has the technical effects and advantages that:
the demand unit comprises an acquisition module, a review module and a prediction module, review is carried out through a review formula of a review standard, reasonableness, consistency and traceability are scored, a weighting formula is adopted for carrying out comprehensive calculation, the calculation result is more accurate, the situation that when the demand unit is developed, the situation that the demand unit is unable to be developed due to the fact that a large defect exists in the demand unit is avoided, the situation that the demand unit is unable to be developed due to the fact that a large cost is invested is avoided, and the development rigidness is guaranteed;
the acquisition module comprises an individual demand system, a collective demand system and a functional information system, and is provided with a blood margin group direction, a geography margin group direction, a business margin group direction and an interest margin group direction, so that acquisition can be performed in different directions, data acquired by demand is more accurate, and each individual belongs to the geography margin group direction, the business margin group direction and the interest margin group direction while belonging to the blood margin group direction, so that an acquisition mode of mutual coverage is performed, and the acquired information is more accurate;
the development unit comprises a code reuse module, a component reuse module and a system reuse module, wherein the code reuse module can finish the quick realization of software and can modify during homomorphic mapping so as to correct the existing problems;
the change unit comprises an unconditional change module, a conditional change module and a non-alterable module, different information is processed by different change modules, software can be changed when the change is carried out, the problem that the whole operation of the software is wrong due to the change of data in the software is avoided, and when the change information is unreasonable information, the change information is directly rejected, so that the time is saved.
Drawings
Fig. 1 is a schematic view of the overall structure of the present invention.
FIG. 2 is a schematic diagram of the operation steps of the test unit of the present invention.
Detailed description of the preferred embodiments
The technical solution of the present invention will be clearly and completely described below with reference to the accompanying drawings of the present invention, and the forms of the respective structures described in the following embodiments are merely examples, and the management system for software development process according to the present invention is not limited to the respective structures described in the following embodiments, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts belong to the scope of protection of the present invention.
Referring to fig. 1, the present invention provides a management system for a software development process, including: the system comprises a demand unit, a development unit, a test unit, a defect unit and a change unit, wherein the demand unit collects the demands of customers so as to plan the functional targets of developed software, the development unit develops target software according to the demands collected by the demand unit, the test unit tests the developed target software, the defect unit modifies the defects tested by the test unit, and the change unit collects the change demands of the customers and changes the target software;
the demand unit comprises an acquisition module, a review module and a prediction module, wherein the acquisition module acquires the demand information of a client and sends the demand information to the review module, the review module reviews the demand information of the client, the reviewed demand information is sent to the estimation module for prediction processing, and the demand information qualified in the prediction processing generates a demand specification and enters the development unit for formal software development;
the evaluation criteria in the evaluation module are feasibility Q, rationality p1, consistency p2 and traceability p3, and the calculation formula is
Figure SMS_2
Where M is the final review score, k1, k2, k3 are weights, and k1+ k2+ k3>0, the scoring standards of the rationality p1, the consistency p2 and the traceability p3 are between 1 and 100, the scoring standard of Q is 1 or 0, when the score of K is more than 80, the evaluation is passed, the scoring standard of the feasibility Q is that a nameless administrator is adopted for voting, when five administrators consider that the planning is feasible, the scoring standard is 1, when two or more of the five administrators consider that the planning is feasibleAnd when the plan is not feasible, the scoring standard is 0, when one person considers that the plan is not feasible, two rounds of voting are carried out, the scoring standard is 1 when five persons agree, otherwise, the scoring standard is 0, ten rounds of scoring are carried out by adopting ten managers according to the reasonability p1, the consistency p2 and the traceability p3, the scoring standard of each round is 0-10, and the average value of all the results is the scoring standard of the reasonability p1, the consistency p2 and the traceability p 3.
In the embodiment of the application, when the software development can be carried out according to the evaluation formula of the evaluation standard, firstly, the feasibility can be judged whether the software development can be carried out according to the requirement of the client, so that the evaluation standard only has 1 and 0, which respectively represent that the software development can be carried out normally and cannot be carried out, when the software development cannot be carried out and cannot be carried out, the evaluation standard of the evaluation is directly 0, and when the software development can be carried out, the evaluation does not influence other evaluation standards, the evaluation is carried out through rational, consistency and traceability, and the weighting formula is adopted for comprehensive calculation, so that the calculation result is more accurate, the condition that the development cannot be carried out due to the fact that a large defect exists in the development stage is found, the evaluation cannot be carried out due to the fact that a large cost is invested, the development cannot be carried out is ensured, the development rigidness is ensured, wherein k is the weight, the specific numerical value can be automatically selected according to the type of the software to be developed, and the final denominator is k1+ k2+ k3 in the calculation formula, so that the average calculation is ensured to be larger than zero, and the whole k + 1 is not meaningful value.
Referring to fig. 1, the collection module includes a personal demand system, a collective demand system and a functional information system, the personal demand system collects demand information of a target customer for software, the collective demand system collects collective demand information, the functional information system collects functional information that can be realized by existing stage data, and matches the demands collected by the personal demand system, the collective demand system and the functional information system, and when the two can be matched, the demand collection is completed.
In the embodiment of the application, individual demand system, collective demand system gathers individual and collective demand information, human life style, only can there be individual life alone, and with the relatives, the colleague, the classmate, friend or couple life style together, consequently, carry out the demand collection to different groups, function information system can match the function that present stage data can be accomplished with the demand function this moment, when can matching, then can develop, when needing quick shopping, can provide sufficient shopping relevant data information and carry out data development this moment, can normally carry out software development this moment, thereby can accomplish the demand collection, if the demand is when traveling in space again, lack sufficient data this moment and support, then can't match, then can't accomplish the demand collection, need to continue to carry out the demand collection.
Furthermore, the collective demand system comprises a blood margin population direction, a geography margin population direction, a business margin population direction and an interest margin population direction, and the demand information of the blood margin population direction, the geography margin population direction, the business margin population direction and the interest margin population direction is collected in a mode of simultaneous and mutual coverage.
In the embodiment of the application, including blood margin group direction in the collective demand system, the direction of geographical group, the direction of business margin group and the direction of interest margin group, consequently, can cover present whole group as a collective, individual demand system carries out the demand collection from the angle that customer was alone, the customer need not to carry out the consideration of other factors this moment, and when collective demand system carried out the demand collection, customer identity changed this moment, just business margin group direction if the work is, need carry out the demand collection according to the type of its work this moment, thereby can gather in the direction of difference, data after the demand collection are more accurate, and everyone also can belong to geographical group direction when belonging to blood margin group direction, business margin group direction and interest margin group direction, consequently, carry out the collection mode of mutual coverage, the information after the collection is more accurate.
Referring to fig. 1, the development unit includes a code reuse module, a component reuse module, and a system reuse module, the code reuse module is implemented by using homomorphic mapping and can be modified when the code reuse module is mapped, the component reuse module uses a platform of homomorphic development components, and the components are all described by using XML language, the system reuse module summarizes, simplifies, and analyzes the requirements proposed by the user to form a formalized specification, and searches a system analysis diagram with the highest matching degree from a component library, and stores the analysis diagram into the component library as a component for subsequent use, and the code reuse mode is: putting the code to be reused in a public folder, and setting the called function directory as the public folder when developing software, wherein the component reuse mode is as follows: the method comprises the following steps of encapsulating the components of the existing data in objects one by one, and establishing a derived class by developers to inherit the information in the objects, thereby realizing the reuse of the components, wherein the system reuse mode is as follows: dynamically packaging the index numbers of the data sub-objects and the method sub-objects, determining the data sub-objects and the method sub-objects in each model object through the index numbers, establishing a matching relation table of the data and the method, providing the interface of the model for software developers, and directly calling the software developers.
In the embodiment of the application, the development unit adopts a code reuse module, a component reuse module and a homomorphic reuse mode of the system reuse module, the code reuse module can finish the quick realization of software, and can modify during homomorphic mapping, thereby being capable of correcting the existing problems, the component reuse module can adopt the existing component framework to finish the software, thereby being capable of establishing the software in the early period, and describing by adopting XML language, the retrieval efficiency of the component can be increased, the system reuse module arranges the requirements, and the requirements are displayed on a specification at the moment, the matching of a system analysis diagram is carried out more quickly later, and further the development process of the whole software can be increased.
Referring to fig. 1, the test unit includes an integrated test module, a functional test module and a system test module, the integrated test module tests a page, detects whether the style of each element in the page is consistent with the style in the demand information, detects information provided in the page, determines whether the page information is accurate, stores qualified data, and sends unqualified data to a defect unit, the integrated test module can detect the page information in the software, because a client sees the page layout after opening the software, the information in the page is ensured to be accurate, the client can be good at the first time, the satisfaction of the software is improved, then the information in the page is tested, the information is ensured to be accurate, the trust degree of the software is improved, the unqualified part is sent to the defect unit, and the defect unit can modify the unqualified part, so that the client can meet the demand, and the benign progress of the software development process is facilitated.
Furthermore, when the functional test module is used for testing, the developed software is in a full running state, the running limit of a software system and the problems occurring in full running are tested, the detected problem data are sent to the defect unit, and when the software system is in the full running state, the problems which do not occur in flat-peak running are gradually revealed, so that the software is fully run in advance, and the problems occurring in the using process and the problems of no countermeasures are avoided when the number of users is large after the official upper limit of the software is reached.
Further, when the system test module runs, software is combined with computer hardware, data supporting the software and workers in a formal environment, the software is run and tested in an actual running environment, the software is tested in an equivalence class division mode in a black box test, the test standard is the definition of software requirement specification specifications on each requirement function, all possible input data are divided into a plurality of mutually disjoint subsets according to the software requirement specification specifications, the subsets are called equivalence classes, then a few representative data are selected from each equivalence class to be used as test cases, positive and negative tests are carried out, all data can be divided, and therefore the representative data are selected, testing can be carried out quickly, and software development efficiency can be improved.
Referring to fig. 2, the test unit includes the following operation steps:
s1, a defect unit receives problem data of a test unit and hands over the problem data to a programmer;
s2, receiving problem data by a programmer, repairing software defects, and sending repaired software to a test unit after repairing the defects;
s3, the testing unit receives the software after the defect repair and carries out software testing again;
and S4, when the testing unit tests that the software has defects again, executing the step S1 and the step S2, and when the testing unit tests that the software has no defects, completing software development.
Furthermore, the requirement unit collects software use suggestion information of a client and sends the software use suggestion information to the change unit, the change unit receives the software use suggestion information sent by the requirement unit and generates change information, the change unit changes object attributes and object behaviors of software in operation according to the change information, the change unit is arranged, the requirement unit can collect the requirement information required by the client before software development and can also finish the software development, the change unit sorts the collected suggestion information during the operation of the client, and the object attributes and the object behaviors of the software are changed at the moment so as to be continuously updated, and the subsequent requirements of the client can be met.
Referring to fig. 1, the change unit includes an unconditional change module, a conditional change module, and a non-change module, when the change information conforms to the unconditional change module, the unconditional change requirement is executed unconditionally, when the change information conforms to the conditional change module, the conditional change module determines whether the change information satisfies a condition for executing the change, if so, the change requirement is executed, otherwise, the execution is rejected, the change condition is a condition set by an auditor, when the change information is the non-change module, the execution is rejected, the determination criterion of the unconditional change module is whether the change requirement is a branching version change, when the analysis version is modified, the software change is directly performed, the determination criterion of the conditional change module is whether the change is a software internal data change, when the change requirement is the software data change, the auditor changes, the determination criterion of the non-change module is whether the software source data, and when the software source data is the software source data, the change is not possible.
The change unit comprises an unconditional change module, a conditional change module and a non-changeable module, wherein the unconditional change module is mainly applied to objects with small change influence, such as modification of branch versions, the whole software cannot be influenced at the moment, the requirements of customers can be met, so that the change can be directly carried out, when the unconditional change is carried out, the audit is carried out by an auditor, when the unconditional change is carried out, the software can be changed at the moment, the change of data in the software is avoided, the integral operation of the software is prevented from being wrong, and when the change information is software source data, the change information is directly rejected at the moment, so that the time is saved.
The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. The procedures or functions according to the embodiments of the present application are generated in whole or in part when a computer instruction or a computer program is loaded or executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium, an optical medium or a semiconductor medium. The semiconductor medium may be a solid state disk.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
And finally: the above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that are within the spirit and principle of the present invention are intended to be included in the scope of the present invention.

Claims (10)

1. A management system for a software development process, comprising: the system comprises a demand unit, a development unit, a test unit, a defect unit and a change unit, wherein the demand unit collects the demands of customers so as to plan the functional targets of developed software, the development unit develops target software according to the demands collected by the demand unit, the test unit tests the developed target software, the defect unit modifies the defects tested by the test unit, and the change unit collects the change demands of the customers and changes the target software;
the demand unit comprises an acquisition module, a review module and a prediction module, wherein the acquisition module acquires the demand information of a client and sends the demand information to the review module, the review module reviews the demand information of the client, the reviewed demand information is sent to the estimation module for prediction processing, and the demand information qualified in the prediction processing generates a demand specification and enters the development unit for formal software development;
the evaluation criteria in the evaluation module are feasibility Q, rationality p1, consistency p2 and traceability p3, and the calculation formula is
Figure QLYQS_1
Where M is the final review score, k1, k2, k3 are weights, and k1+ k2+ k3>0, the score criteria of the rationality p1, the consistency p2 and the traceability p3 are between 1 and 100, the score criteria of Q is 1 or 0, and when the score of K is 80 or more, the evaluation is passed.
2. A management system for a software development process according to claim 1, characterized in that: the acquisition module comprises an individual demand system, a collective demand system and a functional information system, the individual demand system acquires the individual demand information of a target client to software, the collective demand system acquires the collective demand information, the functional information system acquires the functional information which can be realized by the current stage data, and matches the demands acquired by the individual demand system, the collective demand system and the functional information system, and when the two can be matched, the demand acquisition is completed.
3. A management system for a software development process according to claim 2, characterized in that: the collective demand system comprises a blood margin group direction, a land margin group direction, a business margin group direction and an interest margin group direction, and the demand information of the blood margin group direction, the land margin group direction, the business margin group direction and the interest margin group direction is collected in a mode of simultaneous and mutual coverage.
4. A management system for a software development process according to claim 1, characterized in that: the development unit comprises a code reuse module, a component reuse module and a system reuse module, the code reuse module is realized by adopting homomorphic mapping and can be modified during mapping, the component reuse module adopts a platform of homomorphic development components, all the components are described by adopting XML language, the system reuse module summarizes, simplifies and analyzes the requirements proposed by a user to form a formalized specification, and searches a system analysis diagram with the highest matching degree from a component library so as to store the analysis diagram into the component library and serve as a component for subsequent use.
5. A management system for a software development process according to claim 1, characterized in that: the testing unit comprises an integrated testing module, a functional testing module and a system testing module, the integrated testing module tests the page, detects whether the style of each element in the page is consistent with the style in the demand information, detects the information provided in the page, judges whether the page information is accurate, stores qualified data, and sends unqualified data to the defect unit.
6. A management system for a software development process according to claim 5, characterized in that: when the function test module is used for testing, the developed software is in a full running state, the running limit of a software system and the problems generated when the software system runs fully are tested, and the detected problem data are sent to the defect unit.
7. A management system for a software development process according to claim 6, characterized in that: when the system test module runs, software is combined with computer hardware, data of supporting software and workers in a formal environment, the software is run and tested in an actual running environment, the software is tested in an equivalence class division mode in a black box test, and the test standard is the definition of a software requirement specification on each required function.
8. The management system for the software development process according to claim 1, wherein the test unit comprises the following operating steps:
s1, a defective unit receives problem data of a test unit and hands over the problem data to a programmer;
s2, receiving problem data by a programmer, repairing software defects, and sending repaired software to a test unit after repairing the defects;
s3, the testing unit receives the software after the defect repair and carries out software testing again;
and S4, when the testing unit tests the software again to have defects, executing the step S1 and the step S2, and when the testing unit tests the software to have no defects, completing software development.
9. A management system for a software development process according to claim 1, characterized in that: the system comprises a demand unit, a change unit and a change unit, wherein the demand unit collects software use suggestion information of a client and sends the software use suggestion information to the change unit, the change unit receives the software use suggestion information sent by the demand unit and generates change information, and the change unit changes object attributes and object behaviors in the software operation according to the change information.
10. A management system for a software development process according to claim 1, characterized in that: the change unit comprises an unconditional change module, a conditional change module and a non-changeable module, when the change information accords with the unconditional change module, the unconditional execution change requirement is carried out at the moment, when the change information accords with the conditional change module, the conditional change module judges whether the change information meets the condition for executing the change or not, the change requirement is executed when the change information meets the condition, otherwise, the execution is refused, the change condition is the condition set by a verifier, and when the change information is the non-changeable module, the execution is refused at the moment.
CN202310147040.8A 2023-02-22 2023-02-22 Management system for software development process Withdrawn CN115840560A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310147040.8A CN115840560A (en) 2023-02-22 2023-02-22 Management system for software development process

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310147040.8A CN115840560A (en) 2023-02-22 2023-02-22 Management system for software development process

Publications (1)

Publication Number Publication Date
CN115840560A true CN115840560A (en) 2023-03-24

Family

ID=85580044

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310147040.8A Withdrawn CN115840560A (en) 2023-02-22 2023-02-22 Management system for software development process

Country Status (1)

Country Link
CN (1) CN115840560A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116974950A (en) * 2023-09-25 2023-10-31 卓望数码技术(深圳)有限公司 Method, system, equipment and medium for analyzing general software test requirement

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116974950A (en) * 2023-09-25 2023-10-31 卓望数码技术(深圳)有限公司 Method, system, equipment and medium for analyzing general software test requirement

Similar Documents

Publication Publication Date Title
Meneely et al. Predicting failures with developer networks and social network analysis
US20070282876A1 (en) Method for service offering comparitive it management activity complexity benchmarking
US20190243912A1 (en) Rapid design, development, and reuse of blockchain environment and smart contracts
CN110968437A (en) Method, device, equipment and medium for parallel execution of single contract based on Java intelligent contract
US20230032058A1 (en) Ann-based program testing method, testing system and application
Boranbayev et al. Development of a software system to ensure the reliability and fault tolerance in information systems based on expert estimates
US9208006B2 (en) Recovery Maturity Model (RMM) for readiness-based control of disaster recovery testing
CN112433944A (en) Service testing method, device, computer equipment and storage medium
CN108897686B (en) Full-entry automatic testing method and device
CN115840560A (en) Management system for software development process
US8601431B2 (en) Method and system for identifying software applications for offshore testing
Kubler et al. Decision support system for blockchain (DLT) platform selection based on ITU recommendations: A systematic literature review approach
Dias-Neto et al. Supporting the combined selection of model-based testing techniques
CN110221933A (en) Aacode defect assists restorative procedure and system
CN114201328A (en) Fault processing method and device based on artificial intelligence, electronic equipment and medium
CN117236304A (en) Method for realizing Excel general import based on template configuration
CN111859985B (en) AI customer service model test method and device, electronic equipment and storage medium
US20080195453A1 (en) Organisational Representational System
US20240119394A1 (en) Application modernization assessment system
CN115982055B (en) Test method special for java language development program
CN113791980B (en) Conversion analysis method, device and equipment for test cases and storage medium
Belay Challenges of Large-ScaleSoftware Testing and the Role of Quality Characteristics: Empirical Study
CN117874768A (en) Container cluster risk analysis and vulnerability assessment method and device based on environment awareness
CN113791980A (en) Test case conversion analysis method, device, equipment and storage medium
CN117194382A (en) Middle-stage data processing method and device, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
WW01 Invention patent application withdrawn after publication

Application publication date: 20230324

WW01 Invention patent application withdrawn after publication