Team Project Summary

Through this software engineering team project, the members of this group have a detailed understanding of the process of development. From the very beginning of the topic, we felt deeply, as a team, how important planning is, and how difficult it is to make a team run efficiently.

At first, we all felt that for the development of a software, as long as the final production of a product can be used to complete the task, and for the project documentation and pre-design is not too much value. But in practical practice, we find that blindly writing code, without a detailed plan as a guide, will greatly reduce our development efficiency. So we re-examined the group of soft projects, from the user's needs analysis began, step by step, draw the unknown how many design drawings, also do not know how many times the discussion changed, only to get a final relatively satisfactory design. Although our group spends more time on this item, it makes us more effective in the subsequent implementation phase and provides ample time for our software testing section.

When software development is completed, we review the entire development process, only to find that software engineering is different from programming, he stressed the "project" two words, rather than to pursue what programming speed, emphasizing the overall planning from a whole, rather than just focus on a few functions, some variables. As a result, the development process between modules requires close communication, access to demand, and clear requirements, all of which are essential parts of a module before implementation, and it is these exchanges that make the development of the entire software known as a "project".

In short, after this team project, we learned a lot. In addition to the knowledge accident, more is how to run a team, including, effective communication, positive discussion and so on. These, perhaps, are a good software developers should have the basic qualities.

Team Project Summary