CN104809065A - Development method for user software - Google Patents
Development method for user software Download PDFInfo
- Publication number
- CN104809065A CN104809065A CN201510207707.4A CN201510207707A CN104809065A CN 104809065 A CN104809065 A CN 104809065A CN 201510207707 A CN201510207707 A CN 201510207707A CN 104809065 A CN104809065 A CN 104809065A
- Authority
- CN
- China
- Prior art keywords
- test
- client
- program code
- software
- server end
- 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
Landscapes
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a development method for user software. The development method comprises the following steps of based on feedback and suggestions of users to the functions required by to-be-developed software, creating a program code of the functions required by to-be-developed software; after the program code is self inspected, saving files based on program defects and quality audit, correcting the tested program and returning the corrected program to a second client for secondary testing until no defects are found in the test result; transmitting the tested program to a second server end for saving and recording the test result; acquiring the program code which is saved by the second server end and has no defect, performing application test and randomly investigating test experience and improvement suggestions in the application test process; after the application test is ended, transmitting the test experience and improvement suggestions obtained by random investigation to a first client. According to the development method for the user software, the defects of high workload, poor flexibility, low working efficiency and the like in the prior art can be overcome, so that the advantages of low workload, good debugging flexibility and high working efficiency are realized.
Description
Technical field
The present invention relates to field of computer technology, particularly, relate to a kind of development approach of user software.
Background technology
Software development is the process requiring the software section built in software systems or system according to user.Software development is a systems engineering comprising demand seizure, demand analysis, design, realization and test.Software generally realizes with certain programming language.Usual employing SDK (Software Development Kit) can be developed.Software is divided into system software and application software, and having more than is comprise the program that can run on computers, and the file relevant to these programs is generally also considered to a part for software.The general process of ideas on software design and method, comprise the function of design software and the algorithm of realization and method, software general structure design and modular design, programming and debugging, program uniting and adjustment and test and write, submission program.
The performance history of often kind of software product, needs very multi-person synergy to complete, debug and revise.In existing software development process, the work of developer and tester disconnects, and amendment debugged program is loaded down with trivial details, very flexible.
Realizing in process of the present invention, inventor finds at least to exist in prior art that workload is large, debug flexibility is poor and the defect such as inefficiency.
Summary of the invention
The object of the invention is to, for the problems referred to above, propose a kind of development approach of user software, to realize the advantage that workload is little, debug flexibility good and work efficiency is high.
For achieving the above object, the technical solution used in the present invention is: a kind of development approach of user software, comprising:
(1) the mode of questionnaire by inquiry, obtains feedback and suggestion that user treats the required function that develops software;
In the first client, treat feedback and the suggestion of the required function that develops software based on user, create the program code of software required function to be developed, after carrying out self-inspection, the program code of serial connection is sent to server end;
At first server end, the program code created is preserved;
In the second client, obtain the program code that server end is preserved, test;
At second server end, test gained bugs is preserved;
In the 3rd client, code quality examination & verification is carried out to the program code created, create quality audit file;
At the 3rd server end, the quality audit file created is preserved;
(2) in the first client, obtain the bugs that second server end is preserved, obtain the quality audit file that the 3rd server end is preserved simultaneously;
Based on bugs and quality audit file, the program after test is revised, and returns the second client and carry out second test, until test result does not have defect, then be sent to second server end and carry out preservations also logging test results;
(3), in the 4th client, what obtain that second service end preserves does not have defective program code, carries out application test, and in application test process the meeting of random searching test body and improvement idea; After application test terminates, the test body meeting obtain random searching and improvement idea, be sent to the first client;
In the first client, based on test body meeting obtained and improvement idea, after being optimized process to not having defective program code, re-start three tests, and until after testing for three times and there is no defect, carry out finalizing a text, deposit, labeling;
(4) software protection step is set:
In the 5th client, start the operating system to perform boot action based on software program of finalizing a text, then then detect the hidden file recorded in final version program code, read the sequence code of server, and therewith whether sequence code is identical to judge the content of above-mentioned hidden file; If identical, then proceed boot action; Otherwise, if different, then stop carrying out boot action.
The development approach of the user software of various embodiments of the present invention, owing to comprising: feedback and the suggestion for the treatment of the required function that develops software based on user, create the program code of software required function to be developed, after carrying out self-inspection, preserve based on bugs and quality audit file, the program after test is revised, and returns the second client and carry out second test, until test result does not have defect, then be sent to second server end and carry out preservation logging test results; What obtain that second service end preserves does not have defective program code, carries out application test, and in application test process the meeting of random searching test body and improvement idea; After application test terminates, the test body meeting obtain random searching and improvement idea, be sent to the first client; Thus can overcome in prior art that workload is large, debug flexibility is poor and ineffective defect, to realize the advantage that workload is little, debug flexibility good and work efficiency is high.
Other features and advantages of the present invention will be set forth in the following description, and, partly become apparent from instructions, or understand by implementing the present invention.
Below by embodiment, technical scheme of the present invention is described in further detail.
Embodiment
Below the preferred embodiments of the present invention are described, should be appreciated that preferred embodiment described herein is only for instruction and explanation of the present invention, is not intended to limit the present invention.
According to the embodiment of the present invention, provide a kind of development approach of user software, comprising:
(1) the mode of questionnaire by inquiry, obtains feedback and suggestion that user treats the required function that develops software;
In the first client, treat feedback and the suggestion of the required function that develops software based on user, create the program code of software required function to be developed, after carrying out self-inspection, the program code of serial connection is sent to server end;
At first server end, the program code created is preserved;
In the second client, obtain the program code that server end is preserved, test;
At second server end, test gained bugs is preserved;
In the 3rd client, code quality examination & verification is carried out to the program code created, create quality audit file;
At the 3rd server end, the quality audit file created is preserved;
(2) in the first client, obtain the bugs that second server end is preserved, obtain the quality audit file that the 3rd server end is preserved simultaneously;
Based on bugs and quality audit file, the program after test is revised, and returns the second client and carry out second test, until test result does not have defect, then be sent to second server end and carry out preservations also logging test results;
(3), in the 4th client, what obtain that second service end preserves does not have defective program code, carries out application test, and in application test process the meeting of random searching test body and improvement idea; After application test terminates, the test body meeting obtain random searching and improvement idea, be sent to the first client;
In the first client, based on test body meeting obtained and improvement idea, after being optimized process to not having defective program code, re-start three tests, and until after testing for three times and there is no defect, carry out finalizing a text, deposit, labeling;
(4) software protection step is set:
In the 5th client, start the operating system to perform boot action based on software program of finalizing a text, then then detect the hidden file recorded in final version program code, read the sequence code of server, and therewith whether sequence code is identical to judge the content of above-mentioned hidden file; If identical, then proceed boot action; Otherwise, if different, then stop carrying out boot action.
Technical scheme of the present invention, by the establishment of program code, test and modification being arranged in a work system, make developer and tester can carry out software development and debugging in a work system, like this, the communication of developer and commissioning staff is flexible, exploitation and debug time can be saved, improve debugging efficiency, decrease developer and the workload of commissioning staff in communication and error logging.
Last it is noted that the foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, although with reference to previous embodiment to invention has been detailed description, for a person skilled in the art, it still can be modified to the technical scheme described in foregoing embodiments, or carries out equivalent replacement to wherein portion of techniques feature.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (1)
1. a development approach for user software, is characterized in that, comprising:
(1) the mode of questionnaire by inquiry, obtains feedback and suggestion that user treats the required function that develops software;
In the first client, treat feedback and the suggestion of the required function that develops software based on user, create the program code of software required function to be developed, after carrying out self-inspection, the program code of serial connection is sent to server end;
At first server end, the program code created is preserved;
In the second client, obtain the program code that server end is preserved, test;
At second server end, test gained bugs is preserved;
In the 3rd client, code quality examination & verification is carried out to the program code created, create quality audit file;
At the 3rd server end, the quality audit file created is preserved;
(2) in the first client, obtain the bugs that second server end is preserved, obtain the quality audit file that the 3rd server end is preserved simultaneously;
Based on bugs and quality audit file, the program after test is revised, and returns the second client and carry out second test, until test result does not have defect, then be sent to second server end and carry out preservations also logging test results;
(3), in the 4th client, what obtain that second service end preserves does not have defective program code, carries out application test, and in application test process the meeting of random searching test body and improvement idea; After application test terminates, the test body meeting obtain random searching and improvement idea, be sent to the first client;
In the first client, based on test body meeting obtained and improvement idea, after being optimized process to not having defective program code, re-start three tests, and until after testing for three times and there is no defect, carry out finalizing a text, deposit, labeling;
(4) software protection step is set:
In the 5th client, start the operating system to perform boot action based on software program of finalizing a text, then then detect the hidden file recorded in final version program code, read the sequence code of server, and therewith whether sequence code is identical to judge the content of above-mentioned hidden file; If identical, then proceed boot action; Otherwise, if different, then stop carrying out boot action.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510207707.4A CN104809065A (en) | 2015-04-27 | 2015-04-27 | Development method for user software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510207707.4A CN104809065A (en) | 2015-04-27 | 2015-04-27 | Development method for user software |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104809065A true CN104809065A (en) | 2015-07-29 |
Family
ID=53693907
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510207707.4A Pending CN104809065A (en) | 2015-04-27 | 2015-04-27 | Development method for user software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104809065A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101201882A (en) * | 2006-12-14 | 2008-06-18 | 英业达股份有限公司 | Software protection method |
| CN101470844A (en) * | 2007-12-26 | 2009-07-01 | 上海网环信息科技有限公司 | User information feedback method and system update early-warning feedback method |
| CN101814026A (en) * | 2010-01-11 | 2010-08-25 | 北京世纪高通科技有限公司 | Software development system and method |
| CN102236748A (en) * | 2010-04-26 | 2011-11-09 | 张逸瑞 | Computer software protection method |
-
2015
- 2015-04-27 CN CN201510207707.4A patent/CN104809065A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101201882A (en) * | 2006-12-14 | 2008-06-18 | 英业达股份有限公司 | Software protection method |
| CN101470844A (en) * | 2007-12-26 | 2009-07-01 | 上海网环信息科技有限公司 | User information feedback method and system update early-warning feedback method |
| CN101814026A (en) * | 2010-01-11 | 2010-08-25 | 北京世纪高通科技有限公司 | Software development system and method |
| CN102236748A (en) * | 2010-04-26 | 2011-11-09 | 张逸瑞 | Computer software protection method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109726093B (en) | Method, apparatus and computer program product for executing test cases | |
| Papadakis et al. | Metallaxis‐FL: mutation‐based fault localization | |
| US8370816B2 (en) | Device, method and computer program product for evaluating a debugger script | |
| US8898647B2 (en) | Method and apparatus for test coverage analysis | |
| Pinto et al. | Understanding myths and realities of test-suite evolution | |
| EP3619611B1 (en) | Conditional debugging of server-side production code | |
| US20180129590A1 (en) | System and method for determining test coverage | |
| CN105718251B (en) | Multilingual SDK automates realization method and system | |
| US20100199263A1 (en) | Test case pattern matching | |
| CN104793942A (en) | Method for developing client software | |
| US10268572B2 (en) | Interactive software program repair | |
| Kintis et al. | Using data flow patterns for equivalent mutant detection | |
| CN108572892B (en) | PowerPC multi-core processor-based offline test method and device | |
| CN103176903B (en) | The test method and equipment of MapReduce distributed system program | |
| CN104820591A (en) | Universal development method for autonomously upgraded software | |
| CN104793952A (en) | Method for developing client software | |
| CN104850396A (en) | Development method of client software | |
| CN104820594A (en) | Universal development method of software | |
| CN104809065A (en) | Development method for user software | |
| CN104794055A (en) | Development method for common software | |
| CN104793939A (en) | Method for developing automatically-updated client software | |
| CN104793944A (en) | Method for automatic updating software development | |
| CN104793947A (en) | Universal method for developing automatically-updated client software | |
| CN104793940A (en) | Universal method for independent update software development | |
| CN104820590A (en) | Development method for autonomously upgraded software of client end |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20150729 |
|
| RJ01 | Rejection of invention patent application after publication |