体系文件-计算机软件控制程序 英文版

Control Program of Computer SoftwareControl Program of Computer Software1. PURPOSEIn order to control quality of each stage during computer development, this program was set out. 2. APPLICATIONThis program is applicable for control of embedded type software in the computer.3. OBLIGATIONSystem department is responsible for enforcement, software developer is responsible for specific execution, and quality control department is responsible for supervision & inspection.4. WORKING PROCEDURE4.1 Software design and development include:4.1.1 Development approach4.1.2 Development stages:a)Definition and analysis of software requirement;b)General design;c)Detailed design;d)Software implementation (coding and unit testing);e)Software testing (parts integration testing, verification test, system joint test).4.1.3 SchedulingCombined with the software development cycle, according to each function index of software, complexities, and working arrangement of development team, work out reasonable and effective software development schedule.4.1.4 Review and testing activitiesSystem delivery includes procedure coding, unit testing and function integration testing.System acceptance must have attendance of a project leader or a department principal.According to project implementation program, make <Test Outline> by referring to <Function Structure Diagram> (project function system diagram made by programming personnel), and check all functions item by item. In the case of ensuring all loads existed, the checking process should be strict and joint debugging must be done, and single functionrealization is not acceptable. For the function disabled temporarily, reasons need to be explained. The system can be delivered after signature and approval of project leader or department principal. Otherwise, the system can not be delivered and maintenance won’t be guaranteed in the future.4.1.5 Obligations of developerProject feasibility analysis, definition of project range and border, proposal of technical requirement and solution, definition the system, and establishment of document “Requirement Specifications” which listed system requirement in detail, such as interface, input, output, management function, safety requirement, and running mode etc.4.1.6 Document requirementsThe documents below need to be provided to department principal by project leader of software development process:Appendix: 1. <Project approval records>2. <Purchasing requisition>3. <Scheme change records>4. <Structure diagram of software functions>5. < Project test outline>4.1.7 Risk managementDeveloper should update relative documents which require to be changed in time. Developer should report to project leader in time when big deviation occurs between project progress and project plan.After checking actual situation, project leader should remake <Project approval records> and communicated with principal of development department. In case of big risk during software development process, developer should report to project leader and superior leader.4.1.8 Adoptive standard, rule, tool and technologySoftware development should comply with basic principle of project management and software engineering. Project management involves approval management, project plan and monitoring, configuration management, software quality assurance, cooperative development and management, and project closing management. Software engineeringinvolves requirement management, system design, system implementation, system testing, acceptance testing, commissioning, system acceptance, and system online.4.1.9 Requirement of configuration management4.1.10 Software design and development result should be made in software developmentplan, which should be in coordination with product development plan.4.2 Software design and development inputsOn the basic of software requirement analysis, make software requirement specifications (including interface specifications and data specifications, if necessary), the requirements as below:4.2.1 Generally software requirement specifications include: function requirement,performance requirement, data requirement, interface requirement, design restriction, security requirement, running environment, and quotative standards and rules etc.4.2.2 Review software requirement specifications in accordance with the regulations.4.2.3 The requirement should have traceability, and had better to be expressed in the formof product acceptance.4.3 Software design and development outputsThe issues below should be considered:4.3.1 Design documentsAll documents should be provided according to contract or relevant documents, generally, the basic documents below should be provided:a)Software development plan;b)Specifications of software requirementc)Description of software design;d)Software testing plan;e)Software testing report;f)Source code;g)Development summary of software project;h)User documents.4.3.2 Software support scheme and support resourcea)Rebuild and maintain code;b)Software transfer and continue to support;c)Software support and running documents include operation manual, user manual, andprogrammer manual etc.4.3.3 Safety and risk analysisa)Any potential risk or operation regulation should be marked clearly and relativedocuments should be made. Level administration for key levels of software should be regulated.b)Regulations of software copy and backup should be made and performed; emergencyrecovery plan should be made and performed.4.3.4 Coding language and coding standardsHigh-level language specified in the contact should be used, and any other language should be approved by the client.4.3.5 Software development toolsBefore using, software development tools should be confirmed and approved to ensure the acceptability of the software tolls.4.4 Software design and development reviewAccording to development design, review outputs of software development stages, including:4.4.1 Analysis and review of software requirements4.4.2 Review of project design4.4.4 Review of testing plan4.4.5 Software function and physical configuration check (software validation testingreview)The review of each stage should be carried out according to job content of the stage and intended aim, and then come to a specific conclusion. Existed issues should be improved, and the improvement should be tracked for verification by reviewer.4.5 Software design and development verification4.5.1 Function testUnit test adopts black box testing, and the single function involved in software design should be carried out long-time and much-load testing to test reliability, stability, andfunctionality of the software.4.6 Software design and development validationSoftware validation can be evidenced by system integration testing or system joint testing.Software validation testing is the final inspection, which should be controlled strictly. The control requirements listed as following:4.6.1 Make software validation plan, which should include:a)Testing requirement;b)Testing schedule;c)Implementation steps of function verificationd)Detailed testing regulations;e)Acceptance standard of software;f)Test report and treatment.4.6.2 Software testing environmentSoftware testing environment is a group of software tool during software engineering, with combination of firmware and hardware. Software tools include testing tools, such as analog software, code analyzer, and test case generator etc.Software testing should be in accordance with security requirements in the contract, and should be in line/ compatible with the environment in software requirement specifications, in case of deviation, which caused influence to the testing result should be evaluated.4.6.3 Testing documentThe documents below should be provided:a)Testing plan;b)Testing case and test regulation;c)Test conclusion report.4.6.4 Problem solving during testingSoftware change and control requirements should be carried out when issues occurred during software testing.4.6.5 Independence of testingSoftware developer or software leader are not allowed to attend testing activities, normally testing group is established to ensure disinterested testing.4.6.6 Function technical state check and physical state check of the software configurationsare normally carried out in the form of review meeting.a) Function technical state check is to verify if newly-developed software meet allrequirements specified in software requirement specifications;b) Physical state check is to verify consistency between procedure and documents.4.7 Control of software design change4.7.1 Software configuration managementSoftware design change should be incorporated software configuration management, and formed documents in relation to software configuration management should be carried out.The issues below should be noticed:a)Specify configuration management organization (person or group);b)Specify configuration management items and mark them, which include deliveredsoftware products, technical documents, executable source code, various data, system software and support software, testing case, testing data, testing results, and various administrative documents (contract, review conclusion, and audit result);c)Specify baseline (function baseline, distribution baseline, and product baseline) andestablish three databases (development database, controlled database, and product database);d)Execute key control to the controlled database, which includes seven regulations, suchas access control, read-write protection, member protection, member identification, file maintenance, change history, and failure recovery of baseline etc.e)On-the-spot report, audit, and report of the configuration management, such astraceability of audit baseline, correct reflection of requirements by the software configuration management items, software configuration management and validity of the medium, periodic copy, backup, and filing, register and report the configuration state including current state report (design state/ testing state/ working state, and edition) and history state report.4.7.2 Control of software changea)software error classification: program error, document error, and design error;b)In any stage of software development, any revision to the product in front each stageshould be filled in the software issue report and software revision report for approval, evaluating revision and influence, the influence to other module due to change, and scope of influence (program/ documents/ process/ expenditure);c)Testing should be carried out after software change.4.8 Control of software upgrading and improvementFunction improvement of the software should be informed clients in the form of website/ email, including reason, effect, operation method, download paths, and troubleshooting of abnormal case etc.5. QUALITY RECORDSSoftware development planSpecifications of software requirementDescription of software designSoftware testing planSoftware testing reportSource codeDevelopment summary of software projectUser documents。