On software project management information system

Of: FOODS Zhuya Jiang Li Qiong Zhao GRIDS

Abstract: This paper describes the construction of information system software Project Management concept, in-depth study of the organizational model of software Project Management, content, configuration management, quality management, risk management and personnel management, and gives the software project plan template .

Paper Keywords: software Project Management, software configuration management, software project plan

An organizational model of software Project Management

1.1 Project Management Committee. Project Management, Project Management Committee is the highest decision making body - as the General Manager, Deputy General Managers. Main duties are as follows: (1) according to the project management project management-related systems, (2) The Authority the implementation of project management related systems, (3) of the project approval, project decision-making to withdraw, (4) the appointment of project management team leader, project assessment director silkworm Committee, the project team.

1.2 The project management team. Project Management Group Project Management Committee - composed of general managers by the company. Main duties are as follows: (1) The drafting of the project management system, (2) organizational phase of the project evaluation, (3) save the project during the relevant documents and data: (4) make recommendations to optimize project management.

1.3 Project Review Group. Project Review Committee is responsible for project management team can be under the development review team and product review panels - like the company technical experts and market experts. Main duties are as follows: (1) the assessment of project feasibility report , (2) marketing plan and stage of the assessment report, (3) stages of the development plan and the assessment report, (4) end of the project, the project summary report of the assessment.

1.4 Software Product Group. Main responsibilities are: arrangements for the project management committee is responsible for project specific software development and market Research and marketing.

2, the contents of software project management
The early eighties of the twentieth century, well-known software engineering expert B. W. Boehm summed up the software development required to follow the seven basic principles, with the ocean, we Helmet parts of project management, they should follow these seven principles. They are: (1) using a phased life cycle plan strict management, (2) adhere to the stage of evaluation, (3) strict product control, (4) using modern programming techniques, (5) should be able to clearly review the results, (6) staff development team should be concise, (7) recognize the continued the need to improve software engineering practice.

3 write <"Software project plan>>

<"Software Project Plan>> General should include the following
(1) Introduction. A aims, scope and objectives of the purpose of pages: the scope of description, the main function, performance, management and technical constraints. (2) project estimate. Using historical data, b using assessment techniques, c workload cost, time estimates. (3) risk management strategies. Risk Identification, d when the risk of, e Gang risk management Plan: Risk Plan risk monitoring and risk management. (4) schedule. a project work breakdown structure, b limit diagram ( Gantt chart), c Pa source table. (5) project resources. a person, b hardware and software, c special resources. (6) personnel organization. a structure, b management reports. (7) tracking and control mechanisms. a quality assurance and control, b change management and control. (8) Appendix.

4 Software configuration management
Software configuration management functions to be provided: in IS090003 in the following description:
Uniquely identify each version of the software items, logo products together constitute a complete version of each specific item version of the software to control two or more independent work in parallel with a given item updates the software to control by two or more persons to work independently while the software on a given item updates: by request - or more complex products updates location coordinate, identify and track all of the measures and changes, these measures and changes is asked from the beginning until the release of, the change request or problem caused.

5 Software Quality Management

Jing 5.1 software quality assurance plan. During the software development front. Need to have - a <"Software Quality Assurance Plan>>. Generally include: (1) planning purposes, (2) references, (3) management. organizational tasks a, b responsibilities. (4) document. a purpose, b required software engineering documents, d is also a document, (5) standards and conventions. a purpose, b Convention (6) review and audit. a purpose, b review requirements. software requirements from Slap review, design review, software verification and validation assessment, functional assessment, management review, internal process reviews, management reviews. (7) test. (8) report or correct activities. (9) tools, techniques and methods. (10) media control. (11) supplier control. (12) record, collect, maintain and confidential. (13) training. (14) risk management.

5.2 The basic principles of quality management. Quality control of all processes, process control, the starting point is to prevent failure, quality management, the central task is to establish and implement a documented quality system and continuous quality improvement, and effective quality system should meet the customer and the organization internal needs and interests of both sides, regular evaluation of the quality system, improve the quality of management lies in leadership.

5.3 Software Review. Software Review is not in software development after completion of the assessment, but in all stages of software development for review. Because in all phases of software development, students may be wrong, if these errors are not detected and corrected, will not to expand. may eventually lead to the development of failure. Software Review is a very important job, is currently the least developed countries attach importance to the work. reposted elsewhere in the Research Papers Download http://www.hi138.com 5.4 test. Testing - unit testing Province as test integration, including system testing. If the test results and expected results do not - caused, it is likely to be found in the system error, the testing process will have the following basic documents: (1) Test Plan: OK test scope, methodology and resources required. (2) test: a detailed description of each test and test procedures related to the program and data (including test data and expected results). (3) test results: the line of each test results go one document, if you run an error report should be a problem, and must be found to solve the problem debugging.

6 Risk Management Software

6.1 Risk classification. According to risk, we can face into the wind project risks (costs, time extended, etc.), technology risk (immature technology, etc.), business risk (sales issues), strategic risk (the company a change in business strategy), management risk (the maturity of corporate managers, etc.), budget risk (the accuracy of the budget, etc.). In addition, we can risk into the known risks (such as staff turnover, etc.), can be forecast risk (derived from past experience may be at risk) and unpredictable risks.

6.2 Wind face recognition. Risk project checklist. Mainly involves checking the following aspects: (1) Product size Face wind examination, (2) business impact risk inspection, (3) risks associated with customer inspection, (4) Risk check, (5) technology risk checks, (6) the development of environmental risk inspection, (7) model and experience with the staff about the risk of inspection.

6.3 Risk Assessment. Risk assessment carried out mainly from the following seven aspects: (1) the likelihood, (2) place the results (impact) (3) the establishment - the risk that the possibility of a scale (eg, very rare, rare, common, probably, most likely), (4) describe the consequences of risk, (5) the impact of products and projects, (6) to determine the accuracy of risk assessment, (7) According to the limited impact of the scheduled queue. In addition to the performance of each risk, scope, time to make judgments as accurately as possible.

6.4 Risk evaluation. The main basis for risk assessment of three factors: risk description, risk probability and risk. From the cost schedule and performance evaluation of three aspects of risk. Determine the project's suspension point, stop point and then - times risk assessment.

6.5 Risk control and monitoring. Risk managers to control and monitor the main depend on the experience to implement. For example, the probability of a developer's turnover is 0.7, the project will result in after-service - given the impact, the risk control and monitoring The strategy is as follows: (1) in consultation with the serving staff to determine the flow of reasons. (2) before the start of the project, to link the work of these reasons include air flow control scheme face. (3) start of the project, good people will flow prepared to take - some measures to ensure that officers once they left, the project can continue. (4) develop documentation standards and establish - a mechanism to ensure timely document production. (5) detailed review of all work fine, so that more were completed according to plan their work schedule. (6) train technical staff for each key SUI reserve personnel. In considering the cost of risk, the decision whether to adopt the above strategy.

7 people management
7.1 pairs of project manager requirements. (1) enables the ability to play every member group, (2) - set of organizational capacity, (3) to each member of the team a sense of accomplishment, (4) the ability to propose solutions to problems, (5) understanding of the issues have a certain depth, (6) To enable members know the importance of software quality.

7.2 The staff of communication. (1) formal non-personal way, such as formal meetings, (2) formal communication between individuals, such as formal discussions among members (generally do not form a resolution), (3) of informal personal exchanges, such as the free exchange between individuals, (4) electronic communication, such as E-MAIL. (E-mail), BBS (electronic bulletin board system), (5) members of the network, such as members of groups or companies outside the relevant personnel with experience outside the exchange. In practice, that, (5) the most efficient communication , followed by (1).

7.3 Human Resources Management in risk management. Every company in the personnel management may be at risk, such as recruitment failure caused by employee dissatisfaction with the new policy, technical backbone of the sudden departure, etc., these events will affect the company's normal operation would even cause a fatal blow to the company. How to prevent the occurrence of these risks, we should study the issue. Links http://www.hi138.com Research Papers Download