Software Engineer role guide-[1] responsibilities

This seriesArticleDirectory:Http://www.cnblogs.com/lzhdim/archive/2010/06/10/1755376.html

Directory of this series of articles:Http://www.cnblogs.com/lzhdim/archive/2010/06/10/1755418.html

The1ChapterSoftware Engineer Guide

 

Putting the software engineer in the first place is definitely not deprecated. This is why rankings are not sequential. Project Members are not distinguished by their identities, because they are a team, and only a group of Members can be successful. In fact, software engineers are the greatest project members. The success or failure of a project is inseparable from that of the project. The quality of the project is also inseparable from that of the project. Although in the layered structure of project implementation, it is in the most basic level.

1.1, Responsibilities

 Project members have their own responsibilities. The projects that each person is responsible for are irreplaceable. Their responsibilities are naturally different, but some are complementary. However, for some projects, some project roles have to have multiple roles due to manpower issues, so their responsibilities are mixed. Although the Division of boundaries is not so detailed, it is an effective method, because sometimes a role in the project team may ask other roles to solve the problems encountered in the project.

The responsibilities of software engineers are roughly divided into the following:

L
fully understand the requirements in this document

L
participate in System Overview design and detailed design

L
participate in the preparation of outline design and detailed design documents

L
system module code

L
system unit test module code

L
participate in system unit module test

L
participate in system module overall test

L
Participate in Writing user manual documents

Many people think that software engineers are responsible for writingCodeThis is only the most basic responsibility. The software engineer also participates in other project activities and plays a secondary role.

software coding begins with understanding requirements. First, you must understand the requirements, analyze the requirements, convert them into module design, establish a module model, and then convert them into module code. During this period, you need to participate in the Outline Design and detailed design of the system. This is the modeling work that can only be performed on the basis of understanding the requirements. Later, the project implementation phase began. At this time, the coding of the system module was started, and the unit test code was compiled to prepare for subsequent testing. Next, it is the module unit test and the overall test, which need to be carried out with the tester. Finally, you also need to participate in the preparation of user manual documents, because the software engineers are most familiar with the requirements involved.

of course, this is "Understanding requirements - MSO-Hansi-font-family: "Times New Roman" "> Design - "Times New Roman" "> encoding - test, the term of the iterative model is used here.

This cycle also reflects the daily work of software engineers. From here, it seems boring. Especially under the pressure of strict programming specifications, the coding work of software engineers seems boring. The concept of full code migrant workers is actually not. A system must have standardized management and standardized development. Therefore, code writing is an important task. You can findProgramming LanguageFeatures, optimizations, fun, and so on, especially when you use new learning knowledge to efficiently deal with a module. Only software engineers can understand this taste.