Software Development Process Specification Part 1 Overview 1 Purpose This specification is to make the entire software product development stage clear, clear, task specific, easy standardization, systematic, and engineering, which is beneficial to improve the control and management of software life cycles, and improve Development software quality, shorten development time, reduce development and maintenance, make software development activities more scientific, more effective. 2 Applicable range This specification is applicable to the development of software products in the formal project form; excluding demand acquisition, on-site debugging and other content. This specification is divided into two parts: technical process norms and management process specifications, which apply to technical activities and management activities in software development. 3 Process Model This specification uses the software development process model for cropping RUP development process. 4 Environment Modeling Language Using UML As Modeling Language Modeling Tools Adopting Rational Rose as Modeling Tool Configuration Management Tools Adoption SourceSafe / CVS as a configuration management tool, the project manager determines according to the specific situation. The change and defect management tools use ClearQuest as a Change and Defect Management Tool Demand Management Tool Using RequisitePro as a Demand Management Tool Unit Tool Tool Recommended using Purify, Quantitify, PurifyCovervage, BoundChecker and other tools, how to choose from the project manager is determined by the project manager. Quote Specification "C Coding Specification" Guide "Demand Modeling Guide", "Analysis Guide", "Design Guide", "Implementation Model Guide", "Database Timming Guide" 5 Role Division Division and Organization Software Process All of the specific roles; the roles and organizations involved in this process are as follows: System analyst management demand Find participants and use cases Determine performance requirements Establishing a use case model Structure example engineer Detailed Description Case Detailed Description Software demand use case analysis case Design Demand Reviewer Review Needs User Interface Designer Design User Interface Arrangement Boundary Class * General Interface Designer Does Not Participate in Interface Partial Substrate Designers Determine Demand Priority Architecture Analysis Architecture Structure Realization and Organizational Learning Codes Specification Designer Design Subsystem Design Database Designer Generating Data Model Design Reviewer Review Design Architecture Reviewer Review Frame Programmer Realizing Component Debugging Unit Test Implementation Test Development Installation Software Code Reviewer Review Code (This role can be tested by technical supervision team) test Develop a test plan design test implementation test assessment test configuration administrator to establish a change control process review change request to confirm the repeated or rejected change request management baseline process engineer to develop a case-enabled development case project manager to develop software development plans to develop an iterative plan to develop a risk management plan Coordination Project Operation Project Review and Change Control Committee The Committee is a administrative team responsible for overseeing projects and control changes; when performing review tasks, the Chairman of the Committee may assign a special person (project recurrence). It is recommended that the committee consists of project managers, architect designers, demand provisions and 3 to 5 people with project approval authority, and the chairman's position should have certain authority in demand and technology. The President conducts the review of the meeting to evaluate the change request according to the actual needs, and the project is reviewed and project plan review. The committee has three basic tasks: change control to clear the baseline of the product, review the changes of the baseline, final approval, veto or extension execution. All changes to the configuration items that have established baselines are approved. The purpose of the team is to ensure that all proposed changes have been properly technically analyzed and reviewed and the preparation has been recorded. Project approval and plan review project examination; project plan review; iterative plan review. Acceptance reciprocation test; life cycle milestone review; project acceptance review;
