Understanding of software project management

Software project management involves the entire software engineering, which is mainly the whole process of the project scope of the determination and evaluation, risk, resource assessment, as well as determine the tasks to be completed, to ensure that the task is completed on time, while reducing unnecessary overhead and development cycle, do is the initial overall planning. Because just involved in this field, also looked at a few articles and related information, so the summary of this inevitably bring some of their own views, if there is similar, purely coincidental.

I think the management of software projects should include the following aspects: 1. Risk assessment, 2. Cost budgeting, 3. Customer communication process, 4. Requirement analysis, 5. Object-oriented program design, 6. Development management, 7. Product delivery.

1. Risk Assessment:

The risk of software project refers to the cost budget, development progress, technical difficulty, economic feasibility and safety management in the whole project cycle. These issues can affect the implementation of the entire project. The risk of software project is divided into six aspects, such as product scale risk, need risk, related risk, technical risk, management risk and security risk.

　　scale risk: the size of software scale and the size of the whole software risk proportional relationship, how to determine how much reuse software, how to ensure that the communication between the software modules and other problems and product risk is closely related. demand risk: often at the beginning of software determination, the need for software is uncertain, not to mention in the whole software development process, the software needs may also change a certain degree, how to start to more accurately determine the needs of software, this is a difficult point. related risks: Some risk is determined by the external conditions of the project, such as market change, the availability of personnel, team members and other factors can make the project risk greater, the control of external risks can effectively alleviate the blunder of decision-making. Technical Risk: technical risk is often due to the lack of appropriate training for team members, new new methods of new technology tools, and other areas of knowledge. managing Risk: people tend to turn a blind eye to their mistakes, so there are some inherent flaws in the project Risk management plan written by some of the project managers that are inherently deficient: the definition of the plan and the task is not clear enough, the actual project is not very understanding, Overestimate the ability of the team, and the information exchange of the bottom staff is not timely and so on. Security Risk: for a software, it is itself a collection of people, is a creative product, to prevent others to steal for the company is sometimes a matter of survival, so the legal protection of it is very important, but also to avoid the occurrence of infringement of other people's intellectual property rights.

2. Cost Budget:

There are two approaches to cost budgeting: a top-down approach and a bottom-up approach. The former is through the high-level according to experience to assign the corresponding task and assigned to the following employees, the bottom of the staff is only passive to accept the task to complete the task, and can not actually participate in the development of the project management process, once the upper set goals deviation, the loss will be very huge. The latter is through the allocation of existing resources, can use the resources of the rational decomposition, it can achieve the purpose of saving money, but this process is often more time than the former.

3. Customer's communication process:

The customer communication stage can be divided into the following processes: Requirements identification phase, program development phase, project implementation phase, end stage. In the demand identification phase through the actual conversation with the customer or questionnaire, standardized document display and other ways to understand the customer's approximate needs, and develop the corresponding requirements of the text analysis to the customer audit. Actually participate in understanding the logic of the customer's business, design a reasonable user interface for different users and communicate with customers in time to get more accurate documents, and also standardize the requirement document so that the customer can read and tell the customer the development situation and actual cost in real time. The main task of the planning phase is to work with customers to develop a pre-operational project plan, taking into account risk aversion. The project implementation phase through the software team and the customer co-lead, real-time customer participation in the evaluation of software, and according to customer service requirements to modify, tell the customer the consequences of the changes and various risks to reduce the need to change the purpose. The end phase of this phase is mainly the handover of project results, and the delivery of the system to maintenance personnel, to help customers achieve business objectives, settlement of various payments. After completing these tasks, the project evaluation should be carried out to review the results of the project and summarize the project experience.

4. Demand Analysis:

The main task of the requirement analysis phase is to determine the comprehensive requirements of the system, make the corresponding documents and extract the requirements specification of the software, and analyze the data requirements of the system including conceptual model, data dictionary, normalization, export the system concrete logic model, and develop the original system.

5. Object-Oriented Programming:

The principle of design should be to ensure that the single principle of the class, to ensure that each class only do one thing, to ensure that each class, modules and functions have a corresponding excuse, so that there is a good extension, should be guaranteed high coupling within the class, low coupling between classes. UML Modeling: (1) Business object Extraction (2) According to the SRS, CRC and other implementation of the use Case Modeling (3) to achieve a business sequence diagram (4) to establish a class diagram, based on the use cases diagram to establish the association between objects (5) to draw an activity diagram, to achieve collaboration diagram, State diagram

6. Development Management:

The management of the development process should first establish the corresponding project plan, set up the overall structure, control the project's extensibility, establish the foundation of the project start-up and assign the development task, deploy the development progress of the corresponding project, and do the test work to ensure the project accuracy. Ensure the rationality and efficiency of the development team, supervise the project quality in real time, and make the appropriate project modification.

7. Product Delivery:

Before the end of the project to deliver the user, the project should be a post-quality review, inviting a typical user to experience the product, to ensure that the project can be delivered by quality, after the delivery of the product should be a final report of the product, this report should include: Project view at the beginning of the project, evaluation of the project and supporting information, The scope of the project, the development process, the meeting records in the project development process, the project change report and its reasons, the project communication process document, the project audit and the customer acceptance report, the project members appearance, the project final result. It should also include a summary of the project.

Understanding of software project management