The second part management process standardization management procedure specification is divided into two parts: the project management process specification, configuration and change management process specification. 7 Process Management Process Code 7.1 Process Overview Process Management Process As shown in the following figure, the management process runs through the software development process, and it has also been itself with its iteration of the development process. 7.2 Project Preparation 7.3 7.3.1 Overview Project Preparation Activity is only once in the software development process, that is, in the first iteration of the initial phase of the project, and it is the earliest activity. 7.3.2 Determining and Assessing Risk Executive Role Project Manager Activity Description Project Manager determines potential risks, analyzing risks, identifying risk priorities and develop risk avoidance and reducing strategies, filling out the "Risk List"; Products "Risk List" (draft) 7.3.3 Starting Project Executive Role Project Manager Activity Description Assignment Project Review and Change Control Committee members; officially appoint project managers by the project review and change control committee; assigning project planning teams (project planning team is the project team that will implement the first phase of work The initial member. The plan team is identified, ratified and assigned by the project manager and project review and change control committee. Usually, the project plan team may include project managers, architect designers, system analysts, leaders, test leaders, configuration Administrator, domain expert); formally or informal forms stipulate the appointment rules of the technical supervision team and the leader; approve the project acceptance standard, for the software projects that have clear contract requirements, the requirements of the contract can be used as acceptance standards; Form a "Software Development Plan" section; formulate the first iteration of iterations for the initial stage, form an "iterative plan"; the product "software development plan" first draft; the first iteration of the initial stage "iteration plan". 7.3.4 Defining Project Organizations Equipped with 7.3.5 Executive Role Project Manager Event Description Project Manager determines the ladder of the project group, management, demand, analysis design, quality assurance, etc., and determine the roles and responsibilities required for each ladder. For projects with small scale, the project manager can directly define the number of personnel required, the person's skills, write the part of the "Software Development Plan" section. "Software Development Plan" of the product update; 7.3.6 Develop Quality Assurance Program Executive Role Project Manager Activity Description Ensure the quality objectives of the project (the project manager need to develop quality objectives, but should ensure that the object is presented); Ensure role and responsibilities; determine quality assurance tasks and schedules, quality assurance activities mainly refer to various review, scheduled review and acceptance review; form "Quality Assurance Program"; Products "Quality Assurance Program"; 7.3.7 Planning and Iteration Execute a role project manager activity description definition project stage milestone; define a milestone target; define the number, length and target of iteration within the stage (determined how many iterations will be arranged for each project stage, determine the relative workload assigned to each iteration, determine Each iterative goal); improve the milestone date and size (improve the estimation based on the information obtained at the end of the first phase); determine the project resource requirements (determination role and quantity), define the number of resources required for the project and Type (assignment by phase / iteration); update "Software Development Plan" based on the above content.
Product Update "Software Development Plan"; 7.3.8 Developing Software Development Plan Executive Role Project Manager Activity Description The "Software Development Plan" is formed according to the above.
Product Update "Software Development Plan"; 7.3.9 Preparation of Development Case Enforcement Role Process Engineer Activity Description According to the Nature, Progress Requirements of Projects, the Progress Requirements, etc .; Products "Development Case" 7.3.11 review Executive Role Project Recurrent Event Description Arrangement The time of the project plan review; distributes the conference materials (risk list, software development plan); convene a project plan review meeting; decided to form a "review record" according to the decision of the retrieval. Products "Review Record" 7.4 Plan Next Depending on Seventy 7.4.1 Overview Plan the next iteration. 7.4.2 Planning Next Iterative Enforcement Role Project Manager Activity Description Determines the range of iterations, that is, what use cases need to be prioritized, which non-functional requirements need to be given priority; define iterative activities, that is, the range determined according to the above-determined range determined to be executed (Parties in the core workflow); determine the products to be generated by this iteration; these responsibilities correspond to personnel; form an "iterative plan";
Products "Iterative Plan" 7.4.3 Develop Software Development Plan Executive Role Project Manager Activity Description Improves milestones and develops a more accurate stage plan (to consider the number of use cases that have been determined, the complexity of the determined use case is determined Waiting, etc., "Software Development Plan" for the product update; * Note: This activity is not required 7.5 management iteration 7.5.1 Overview to overview daily management. 7.5.2 Personnel Equipped with 7.5.3 Executive Role Project Manager Activity Description Personnel and Roles; Appoint Technical Supervision Group Leaders and other group members; write corresponding relationships into the "Software Development Plan" section; product update "Software Development Plan"; 7.5.4 Launch Iterative Enforcement Role Project Manager Activity Description Distributes people to work packages; acquires and assigns non-person resources (such as posts, computers, etc.); issued a work order; 7.5.5 Evaluation Iterative Enforcement Role Project Manager Event Description Evaluation Iterative Results, Iterate Iterative Targets 7.5.7 Review Executive Role Project Recurrent Activity Description Arrangement The time of the project plan review meeting; distributes the conference materials (risk list, software development plan); convene a project plan review meeting; decided to form a "review record" according to the decision of the Review Conference. Product "Review Record"; 7.6 Monitoring and Control Project 7.6.1 Overview This activity is mainly monitoring project changes, processing change requests; not all changes need to be submitted and reviewed to the project review and change control committee; general impact less Change, such as the repair of slight defects can be directly determined by the project manager. 7.6.2 Detection Project Status Enforcement Role Project Manager Activity Description According to the "Iterative Plan" and "Software Development Plan" to detect the status of the project (including progress, risk resolution, etc.), and report to the project review through a variety of ways. Products None; 7.6.3 Arrangement and Distribution Work Enforcement Role Project Rejudes Activity Description Assign Change Request to iteration (General Important Extended Request will be extended to the next iteration or even more late iteration, and defect repair is usually in this time Iterations are completed; allocate duties; describe work and expected results; develop schedules; modify the current iterative plan, and reflect the influence of future iterations in the software development plan; issue work orders; 7.7 Determine and assess the risk execution role project manager activities describe the project manager to identify potential risks, analyze risks, determine the priority of risk, and develop risk avoidance and reducing strategies, fill in the "Risk List". Products "Risk List" (Update) 7.8 Phase 7.8.1 Overview This activity is only executed while the stage is closed. 7.8.2 Prepare for the stage to prepare 7.8.3 Execute a role project manager activity Description Check the status of the desired workpiece; delivery of products (see "Appendix 1 Project Milestones"); Products "Software Development Plan" (delivery) "Status Assessment" (recently iterative, delivery); "Iterative Assessment" (recent iterative formation, delivery); 7.8.4 Lifecycle Milestone 7.8.5 Review Executive Role Project Complex Event Description Arrangement Life Cycle Milestone review meeting schedule; distribution of conference materials; convene life cycle milestones; record decision; product "Review Record"; 7.9 Project Tail 7.9.1 Overview This activity is only implemented when the project is only.
7.9.2 Preparation for Project Collection 7.9.3 Executive Role Project Manager Event Description as an active schedule, this time schedule should be included in the software development plan; check the review after the project; complete the acceptance operations; "Software Development Plan" (delivery); "Status Assessment" (recent iteration formation, delivery); "Iterative Assessment" (recent iteration formation, delivery); 7.9.4 Project Acceptance 7.9.5 Review Role Project Reviewer activities describe the schedule of the arrangement of the project acceptance review meeting; distribute conference materials; convene a project acceptance review meeting; record decision; product "Review Record"; 8 Configuration and Change Management Process Specification 8.1 Process Overview Configuration and Change Management Process As shown below The first two activities, "Plan Project Configuration and Change Control" and "Create Project CM Environment" are mainly called at the beginning of project development, and other workflows are called according to the progress of the software development lifecycle. 8.2 Program Project Configuration and Change Control 8.2.1 Overview 8.2.2 Developing a CM Policy Execution Role Configuration Administrator Activity Description Determining Configuration Identifier Method; Determine Baseline Method: Establish a baseline milestone, establish a baseline mark; determine a product catalog structure; determine a backup Saving method; determine the configuration status reporting requirements: Select the report based on the change request to determine the frequency; the product is not. 8.2.3 Establishing Change Control Process Perform Role Configuration Administrator Event Description Establishment Change Request Process: (1) Complete Change Request Single, Submit Change Request (2) Analysis, Evaluation Change Request (3) Assignment Role Resolution Change Request (4) Save Change history development Change Review Notification Protocol; Products "Configuration Management Plan". 8.2.4 Write a CM Scheme Enforcement Role Configuration Administrator Event Description Writing a CM Program; reviewing and approve the CM program; maintaining a CM program; Products "Configuration Management Plan." 8.3 Creating an item CM Environment 8.3.1 Overview 8.3.2 Setting the CM Environment Enforcement Role Configuration Administrator Event Describes the Settings Hardware Environment; Create a product directory structure on the project repository according to the configuration management plan; Products Repository. 8.3.3 Creating an integrated work area Executive Role Configuration Administrator activity Description After configuring an administrator set a project repository, create an integrated work area; product integration workspace. 8.4 Delivery and Change Configuration Item 8.4.1 Overview 8.4.2 Creating a Development Work Area Performing Role Any Role Activity Description Any role Before starting your own daily work, you should create your own development workspace on the set project repository; Product development work area. 8.4.3 Performing Daily Development Enforcement Roles Any Role Activity Description According to the project manager, the work list is performed on its own development workspace, including: check, check, add, delivery, and update workspaces The development work area of the product update. 8.4.4 Delivery Development Executive Role Any Role Active Description After completing the work content on the assignment work, the development of the development (change) content is delivered to the integrated workspace, including: From the development workspace, and check into the integrated workspace, Notify other people; the product updated integrated work area. 8.4.5 Updating Development Workspace Executive Role Any Role Activity Description According to the configuration administrator's notification, you update your own development workspace from the integrated workspace Check Out. The product update is developed. 8.4.6 Establishing a baseline execution role Configuration Administrator activity Description The completed work list delivered according to any role, from the development of CHECK IN in the development work area to the integrated development work area, and establish a baseline, notify other people to update their own development Workspace; product baseline.
8.4.7 Promotion Base Operating Role Configuration Administrator Activity Description When the product reaches a certain maturity, stability or quality level, or a milestone, a milestone can be promoted after consultation with the project manager, these tasks include: Determining baseline tags , Promotion baseline in the integrated work area; product baseline. 8.5 Administration Baseline and Release 8.5.1 Overview Establish a baseline and promotion baseline. 8.5.2 Creating a Deployment Unit Performs Role Configuration Administrator Activity Description Configuration Administrator Creating a copy of the workpiece from the project repository according to the list of materials lists according to the list of materials; configuration administrators establish or establish or establish or establish or establish or build or Promotion baseline; product deployment unit. 8.6 Auditing Report Configuration Status 8.6.1 Overview 8.6.2 Reporting Configuration Status Perform Role Configuration Administrator Activity Description Depending on the Stage and Time Report Statistics Project Repository Changes in Status Status Status in the Status Status, Quantitative Configuration Reports (Can be generated directly by ClearQuest); Products "Configuration Status Report". 8.6.3 Performing a Configuration Audit Role Configuration Administrator Event Description Physical Configuration Audit: Prepare all of the list of workpieces given in a development case Review product directory structure contains each workpiece report results Function Configuration Audit: List the product function review Whether there is a test result report results product "Configuration Review Results". 8.7 Management Change Requests 8.7.1 Overview Changes will affect project projects, especially the change in scalability, and other changes in demand often have a big impact on the project. This process should be strictly followed when this change occurs. Smaller changes, especially some modifications, and project managers can organize themselves. 8.7.2 Submission Change Request Performing Role Any Role Activity Description Complete Change Request Single Submit Change Request, Change Request Single Status is Submit Product Change Request Single (Submitted). 8.7.3 Updating Change Request Performing Roles Any Role Activity Description Receive Change Request Form (Denuated or Rejective) Update and Reissue Change Request Products "Change Request Single" (Updated). 8.7.4 Reic 8.7.5 Trial Request Enforcement Role Project Review and Change Control Committee Event Description Prepare to Review Change Demand; Arrangement The time of the review meeting; review the submitted change request; Products "Change Request Single" ). 8.7.6 Confirmation Repeated 8.7.7 Live Revision Request Enforcement Role Project Review and Change Control Committee Activity Description Prepare Doubt Doubt Required Repeated or Rejected Change Request; Specify CCB represents a change request for repetitive or rejection; update change request Status: (1) Change requests that have been confirmed repeated or rejected should be turned off, and the change request submitter; (2) requires the author to provide more information, or update the change request information, the reason is not a reasons, re-submit With the CCB review; the product "change request order" (rejected).
(The second part management process specification is over, the third part will be published later for the technical process specification)
