Software Project Management (CMM) Experience Tarrel (2)
2.2.9 Project Acceptance 2.2.10 Project Release 2.3 Project Organization 3 Development Work Specification 3.1 Overall Planning Phase 3.1.1 Project Demand Report 3.1.1 Work Definition 3. 1.1.2 Pre-sequence work and input results 3.1.1.3 Concrete work content 3.1.1.3.1 Information collection (optional) 3.1.1.3.2 Data research (optional 3.1.1.3.3 Project Demand Report 3.1.1.3.4 Project Demand Report Discussion 3.1.1.3.5 Project Demand Report Discussion 3.1.1.3.6 Project Demand Report Modification 3.1.1.3.7 Project Demand Report Acceptance 3.1.1.4 Participants and Responsibilities 3.1.1.5 Output Achievements and Back Brass 3.1.2 Technical Feasibility Experiment (Optional) 3.1.3 Project Project 3.2 Project Project 3.2.1 Project Application 3.2.2 Project Evaluation 3.2.3 Project Scheduling Scheme 3.2.4 Project Project Approval 3. 3 Demand Analysis 3.3.1 Data Collection 3.3.2 Requirements Analysis 3.3.3 Discussion Preparation 3.3.4 Demand Analysis Discussion 3.3.5 Requirements Analysis Modification 3.3.6 Demand Analysis Acceptance 3 .4 System Analysis 3.4.1 System Analysis Preparation 3.4.2 Determining Problem Domain 3.4.3 Requirements Modeling 3.4.4 Establishment Analysis Object Model 3.4.5 System Analysis Merge 3.4.6 System Analysis Test 3.4.7 System Analysis Modification (After test) 3.4.8 System Analysis Acceptance 3.5 System Design 3.5.1 System Design All 3.5.2 Interface Design 3.5.3 Establishment Design Model 3.5.4 System Design Merge 3.5.5 Object Holding Design 3.5.6 Detailed Design 3.5.7 System Design Test 3.5.8 System Design Modification (After test) 3.5.9 System Design Acceptance 3.6 Coding Implementation 3.6.1 Coding Preparation 3.6.2 Coding 3.6.3 Coding Unit Test (Test Work) 3.6.5 After Code Modification 3.6.5 Coding Tune 3.6.
6 Integrated Test (Test Work) 3.6.7 After IC Testing Coding Modification 3.6.8 System Test (Test Work) 3.6.9 System Test Post Coding Modification 3.6.10 Code Acceptance 3.7 Project Test 3.7.1 System Analysis Test 3.7.2 System Design Test 3.7.3 Project Test Scheme 3.7.4 Unit Test 3.7.5 Integration Test 3.7.6 System Test 3.8 Documentation 3.8.1 Development Documentation 3.8.2 User Documentation 3.8.3 Promotion Data Writing 3.9 Project Acceptance 3.10 Project Release 4 Project Work Summary 4.1 Project Tasks 4.1. 1 Total Tasks 4.1.2 Stage Tasks 4.2 Output Achievement 2 Development Specification Overview 2.1 Application Project Management Management Development Process Product Department Accepted Development Tasks All in the form of project, including: new product development, Product maintenance (wrong modification, functional enhancement, improvement of defects, etc.), product customization development and maintenance, etc., full use of project management methods for control and management. According to the scale of the project and the difficulty of being large, small and simple. The completion period of each project should be controlled within 6 months, and the project size is controlled within 60 people. Excessive projects need to be split into multiple small items to complete. 30 people have been called a big project, and 10 items within 10 people are called small projects. Each project should be split into a working stage according to the specific situation, ie the milestone to effectively control and detect the project progress. 2.2 Standard Standard Development Work 2.2.1 Overall Planning Comprehensive Planning Project Work, Determining Target Market, Technical Indicators and Application Requirements, Define Project Work Scope and Delivery Achievements, and Clarify Overall Vision and Implementation of Project Realization Program; determine the feasibility of new technologies in the project; clarify the various resources and costs of the project to estimate projects. 2.2.2 Project Project The Product Department has applied for the application for development projects to submit the project information. A series of risk assessments for the project by the company. Through the risk assessment project, the product department is made by the product department, implemented time schedule, resources (person / equipment, internal / external), technology, funds and fees, etc., relevant resources and fund usage plans must be listed in detail. Finally, all project application materials, risk assessment reports and product schedules must be reported to the company's superior leadership examination and approval, and conduct project reviews. Projects can enter formal development work. 2.2.3 Requirements Analysis According to the design idea of the work range and application programs defined by the project demand report, the application plan will be further refined into the application, and how the various services included in the computer system will be done, and the business process. Related theories, operational formulas, principles, business data, document report formats, etc. 2.2.4 System Analysis According to the analysis of project requirements, the computer system that will meet the needs of user needs is analyzed.
In the system analysis, the problem domain for object-oriented analysis technology (OOA) is used, and each problem domain is analyzed and abstracted. It produces the correct understanding of the relationship between them and the relationship between them. The classes and objects required for system liability, define these classes and object properties and services, and the structure, static contacts, and dynamic contacts formed thereon. Finally generate an object-oriented analysis model that meets user needs and can directly reflect the problem domain and system responsibility. 2.2.5 System Design According to the analysis and system analysis of project requirements, the system-oriented design technology (OOD) is used to perform system design for human-oriented human-machine interface, data storage, task management, etc. in the specific implementation. It mainly includes UI design, object design and database table design. 2.2.6 Encoding Implementation According to the result of the system design, the program encoding (OOP) is used to implement the content of the system design. The encoding process is to define the properties of the object with a specific data structure, and use the specific language to implement the algorithm represented by the service flowchart. The object classes and relationships formed in the object design phase are finally converted into special programming languages, databases, or hardware implementations. 2.2.7 Project Test The system analysis, system design, program coding, etc. use object-oriented methods to test (OOT). The test work of the project runs through the entire development process of the project. Mainly include: Analysis (OOA) Test, Design (OOD) Test and Coding (OOP) Test, and Integrated Test and System Test. 2.2.8 Document Production The documentation that follows the project development process mainly includes three categories: (1) development documentation: analysis, design, coding, testing, various development management documents, etc.; (2) User Document: Online Help , Installation guide, manual, technical manual, training materials, etc .; (3) publicity information: product introduction information, product white paper, product promotional PPT, demo disc, etc. 2.2.9 Project Acceptance The completed item is accepted according to the acceptance step. The situation of the project during the acceptance process is evaluated. 2.2.2.10 Project Release Publish Projects are sent to the project, and organize the contents of the project containing the contents of the project and release the product release notice. 2.3 Project Organization Each project specifies a project manager for management, and specifies an analysis, the designer (from the analysis design group) is responsible for the management of technical issues. When the task involves the operation of multiple functions (some projects may only involve only a single function group), the project manager is coordinated by the project work arrangement and the team leader of the function group, and the team leader to the function group will help arrange this group. The project work undertakes, specifying the personnel in the group to complete the relevant work. The project manager summarizes the progress plan of the entire project based on the arrangements of various functions, and controls the projects according to the final project plan. The project needs to be tracked, summarized in accordance with the requirements of project management, and the staff of each function group must give active support and cooperation on these work. Product committees (or product department) Normally, organizers personnel examine projects to ensure the progress and quality of the project.
