Software Project role guide-Opening

 

Preface

 

To2010So far, there has been a qualitative leap in the informatization level in China.ItProject investment and construction are everywhere and have penetrated into all aspects of our lives. This is due to the development of computer hardware and software. The influence of informatization is far-reaching, direct, and important to us.

"Times New Roman"> an important change is worth mentioning, it "Times New Roman"> after the bubble of the industry, our users have become ignorant, transformed into a user with independent experience, By it "Times New Roman"> The Age Of What vendors say is past. it "Times New Roman"> the development of the project is like this, from the early portal website, the personalized personal blog website can be seen from today.

from Waterfall Model to iterative model, from process-oriented to service-oriented, from traditional project management to agile process management, and the development and progress of software engineering, these are all things that our stakeholders have experienced and are also the process of continuous exploration, discovery, and practice. In this process, the generation of the Project stakeholder role has also gone through the history from less to more. The responsibilities and actions of each role are evolving along with the development of information projects. On this road, theory and practice are combined. The theory guides practice, and practices in turn affect and revise the theory. This is related to some information projects, such as ERP MSO-Hansi-font-family: "Times New Roman"> the development of requirements is consistent, they are constantly improving themselves with the development of information construction, constantly adjusting their roles, and constantly drawing their own stages.

the improvement of project personnel roles also marks the maturity of software engineering. the software engineering community has put forward a series of Theories, Methods, languages, and tools to solve several problems in the software development process. However, due to the inherent complexity, variability, and invisibility of the software, problems such as long software development cycles, high costs, and low quality still exist. The software management method analyzes, manages, and controls costs, personnel, progress, quality, risks, and documents to ensure that software projects are successfully completed according to the predefined costs, schedules, and quality. Software project management helps developers transform their personal development capabilities into enterprise the higher the software development capability of an enterprise, it indicates that the software production of this enterprise tends to mature, and the lower the development risk. Software project management is already 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 project personnel role to help beginners who are still in the ignorant stage, and those engineers who need to improve the project construction experience. This seriesArticleIt is written for this purpose. Due to the limited level of the author, the problems in this article are inevitable. You are welcome to criticize and advise.

 

 

Author's remarks

 

From the software engineering perspective, I have always wanted to write relevant guidance articles for each role in the project team, so as to summarize the responsibilities and requirements of each role, 2. Prepare for start-up. These roles are believed to be involved in the project. Or, the division of roles is not so detailed due to the project size. In some small projects, a single person often has multiple roles, but he does not think so much, that is, to assume the project role for the purpose of the project. I have experienced these project roles and recorded them based on my learning experience. Of course, the knowledge and content of these roles are summed up by my experience. Naturally, there are some shortcomings. Thank you for your advice.

 

For project personnel, I have assigned the following roles:

1.
Software Engineer (ProgramMember );

2.
Software designers (Senior programmers );

3.
Software Tester;

4.
Front-End Interface Designer (UIDesigner, artist );

5.
Database engineer;

6.
Software Configuration Engineer (SCM);

7.
Software Quality Engineer (SQA);

8.
Requirement Analyst (System Analyst );

9.
System Architect;

10.
Technical Manager;

11.
Project Manager;

12.
Product Manager;

13.
Copywriting personnel (Basic Handling of project documents );

14.
Customer owner; (Do You Know How To Be a customer and a user ?)

15.
User;

 

Note: This role category is a summary of my personal experience. Please point out the omissions.