preface

By 2010, the level of domestic information has made a qualitative leap. IT project investment, construction is everywhere, has penetrated into every aspect of our life. Thanks to the development of computer hardware and software, the influence of information technology is profound, direct and important to us.

There is an important change worth mentioning. After the bubble of IT industry, our users have changed from ignorant era to users with independent experience. The era of what IT manufacturers say is what is gone. This is how IT projects have evolved, from the early days of web portals to today’s personalized personal blogging sites.

From waterfall model to iterative model, from process oriented to service oriented, from traditional project management to agile process management, the development and progress of software engineering and so on, these are the things that our generation of project stakeholders have experienced, and we continue to explore, discover and practice the process. In this process, the generation of project stakeholders also experienced a history from less to more. The responsibilities of each role, the things dealt with, are developing with the development of information projects. On this road, theory and practice are combined. Theory guides practice, and practice in turn influences and revises theory. This is consistent with the development of some information projects, such as ERP, which are constantly improving themselves, adjusting their roles and drawing their own stage with the development of information construction.

The perfection of the role of project personnel is also a sign of the maturity of software engineering. Software engineering has put forward a series of theories, methods, languages and tools to solve some problems in the process of software development. However, due to the inherent complexity, variability and invisibility of software, the problems of long software development cycle, high cost and low quality still exist. In order to make the software project can be successfully completed according to the scheduled cost, schedule and quality, the software management method analyzes, manages and controls the cost, personnel, schedule, quality, risk and documentation. The software project management is beneficial to transform the individual development ability of the developer into the development ability of the enterprise. The higher the software development ability of the enterprise, the more mature the software production of the enterprise tends to be, and the less its development risk is. Software project management has been recognized as one of the core competitiveness of software development enterprises.

In order to improve the level of project construction and management, the author thinks it is necessary to give a detailed description of the role of project personnel to help those beginners who are still ignorant and those engineers who need to improve the experience of project construction process. This series of articles has been written for that purpose. Due to the author’s limited level, the problems in the article are inevitable, welcome everyone’s criticism and advice.

The author’s word

From the perspective of software engineering, I have always wanted to write relevant guide articles for each role in the project team, to summarize the responsibilities and requirements of each role, and to make preliminary preparations for entrepreneurship. These are roles that I’m sure you’ll cover in the project. Alternatively, the division of roles is less detailed due to the size of the project. In some small projects, it is often one person who holds multiple positions, but he himself did not think so much, just for the project and in the project role. These project roles, WHICH I have experienced, are recorded based on learning and experience. Of course, these roles have the knowledge and content, is my experience summary, naturally there are shortcomings, welcome everyone’s advice.

For project staff, I categorize the following roles:

The party a.

Chapter 1. Account Manager

Chapter 2. Users

2. Party b

Chapter 3. Software Engineers

Chapter 4. Software Designer

Chapter 5. Software profiler

Chapter 6. Front End Designer

Chapter 7. Database Engineer

Chapter 8. Software Configuration Engineer (SCM)

Chapter 9. Software Quality Engineer (SQA)

Chapter 10. Requirements analyst

Chapter 11. SEO Engineers

Chapter 12. System Architect

Chapter 13. Technical Manager

Chapter 14. Project Manager

Chapter 15. Product Manager

Chapter 16. Copywriter (basic processing of project documents)

Chapter 17. Safety Engineer

3. Party c

Chapter 18. Supervisor

Note: this role classification is a summary of personal experience, please point out the omission.