Management of Computer Software Engineering

Paper Keywords: software project management organizational structure of the user developers
Abstract: The analysis of the characteristics of software products, software project management may be involved in the discussion of personnel, organization, user, control, documentation and other content.

I. Introduction
Software project management has not attracted enough attention. The reason: The first is a traditional concept, project management is not valued by the people; the other hand, is an emerging software engineering disciplines, software engineering management of the problems are just been proposed. Meanwhile, the special nature of software products to make software project management involves many disciplines. So. on software project management, it is also a lack of experience and technology. But the fact is, the consequences of failure by the management procedures error than more serious consequences. very few software project implementation process to accurately meet the intended objectives, schedule and budget, which also illustrates the importance of software project management.

Second, software engineering rental, content management
The current low level of production automation software, in the human Development process is the decisive factor, therefore, largely a software project management people management. We can according to the characteristics of software products. Analytics software process management under the specific content of , which includes developers, organizations, users, documentation and other parties and management.

(A) the developer
Software developers are generally divided into: project leader, systems analyst, senior programmer, junior programmer, data and other supporting staff. According to the scale of the project were small, one person may wear many hats, but the duties must be clear. people with different responsibilities, different quality requirements. If the project leader needs organized and ability to judge and make decisions on major issues the ability to; systems analyst is to have general skills, analytical ability and social activity; programmer requires skilled programming capabilities. who should be concise, candidates must be cautious. the software life cycle activities in all price segments of the division of labor and each other. Therefore, both categories of personnel required to select competent, but also to each other is good to meet. a harmonious working atmosphere is not very difficult to complete a complex software projects.

(B) Organization
Organization does not mean a simple set of developers. This organization requirements: good structure and reasonable division of labor and effective staff communication. Software Development organization is no consistent pattern. Following is a brief three organizations.

1. The main organizational machine programmer. IBM company's main software system programmers group is structured on the thinking embodied in the organization. Its purpose is to ensure coordination and unity of the whole group. A senior engineer (main programmer) chair to plan, coordinate and review all the technical activities of groups. technical staff (typically 25 people) responsible for the analysis and Development activities, a back-up engineers to support the work of engineers and the project continued, engineers can replace the work to reduce possible losses.

2. Expert. Group stressed that each person's ability, to each person as an expert, by these experts, a Development agency. Although this organizational structure can play the enthusiasm of all staff, but often coordination difficulties may occur, choose this way to be careful.

3. Democratic organization. Democratic organization engaged in all aspects of work by the staff of head rotation. Obviously, this organizational structure to mobilize the enthusiasm and creativity of individuals is commendable. However, due to the head too much information "transfer "does not meet the direction of software engineering.

(C) User
We develop software for the user, in the Development process from beginning to end user must be close cooperation and support. As project leader, to pay special attention to keep in touch with the user to grasp the user's psychological and dynamic. To prevent the user from a variety of dry find and resistance. Links to Research Papers Download http://www.hi138.com 1. users are not active, do not match. This performance usually stems from the use of advanced technology skeptical users, their psychological conflict emotions manifested in action negative, indifferent. In the requirements phase, the work these people do is very important in business through their backbone in order to truly understand the requirements of users. make them aware of that: the development of computers and application of the inevitable trend of modernization, the use of computers will bring huge economic benefits: they learn new techniques and methods to replace obsolete or out of some of the possible expertise.

2. Users seeking quick comprehensive. This performance comes from a positive attitude towards the use of a computer person. Some of them who want to be able to use the computer one morning and spend all-around computer. To recognize them; development of a software project is not can be done overnight, and software engineering does not depend on human wave tactics can increase the duration. In addition, even if your computer can handle it, the system can not, under the all-inclusive, Tandaqiuquan. to do what under the existing conditions. If systems large and will be very complex, very long development time for delay, it may cause a system failure or poor performance.

3. User needs change. In the software development process, the user may have made new demands and changes you asked for. From software engineering point of view do not want to have this change. But in fact, the requirements do not allow users to make changes is not possible. because on the one hand everyone a process of understanding new things, not all of a sudden a comprehensive, accurate requirements: the other party and also take into account the relationship with the user. the change from the user To correctly deal with: software engineering to the interpretation of the law of the user and, where possible under the conditions of partial or conditional meet the reasonable requirements of users. For example: after the end of the software requirements analysis phase of software design standard population have been identified, then user requirements to lead to significant changes in design objectives of the changes, especially the latter part of software development, generally can not meet the requirements of this change. to the users to explain the inherent laws of the project, but if the user's performance and other local parties and the requirements, as long as is reasonable, it must be considered.

4 control. Who is development control officers to control within the organization. Is to ensure that the enthusiasm of developers and stability. Officers frequently change the software or mobile will increase opportunities for the error. At least to ensure that each phase of the project or the software project software life cycle at every stage of relative stability in personnel. Also note that each developer to play the enthusiasm and creativity. financial control to the preparation of detailed budget. and in all stages of funding accounted for. in funding for out of control, software project will not have the financial guarantee. quality control and review each stage on the meaning and function is the same, this is no longer in the narrative.

5. Documentation. Development process after the various activities should be reflected in the documentation on the. At every stage of documentation is the basis for the subsequent stages of work, but also on the front of the stage of the review. A large extent, software engineering management Documentation is on management to achieve. Therefore, to the preliminary design of the development process, intermediate process, the final results of the establishment as a complete set of documentation. document standardization is an important aspect of document management.

III Conclusion
In today's era of software engineering, each project involves a large number of human and material resources, management issues become increasingly prominent. In practice, whether formal management issues. Are consciously or unconsciously, to the management, only management good or bad is different. With the increasing size of software. developers along with the increase in development time and a corresponding growth. As for the large scale, personnel, development of software projects for a long time, must have good management and seek to determine the time and within budget effectively, rational organization of human and material resources. completion scheduled by the software project. Links to Research Papers Download http://www.hi138.com