Software engineering twinning project analysis
Last week, we completed a personal project programming. This week ,, our team sincere cooperation, concerted efforts, through unremitting efforts, the final completion of the project team. And this project, we learned a lot. Summarized as follows:
- Selected compiler is very important that we bear team project, initially using java, use the eclipse compiler, the design of the interface, it is troublesome, and finally chose to use C #, use VisualStudio, it is convenient to complete the interface design.
- About the class diagram design, for the first time, we follow their own ideas, arbitrary, leading to the complex relationship class, let's look at themselves dazzled, then we abandoned the first project, started slowly combing between classes relations, re-design, and finally ended up in this new version, compared to before, I feel a lot of clear thinking project
- About normative codes, code compare the two of us, each has its advantages, but also have unreasonable, although we are bound by this project, the two improvements to the code specifications, but the improvement is still not enough.
Feelings and experiences:
Programming code first collaboration with others, feel the code normative importance of good programming code specification helps to improve efficiency, help us quickly understand the code, to complete the work. The first time, because the code normative issues, we spent a lot of time. Second, the importance of the algorithm, the subject of our personal projects generated using a binary tree method to generate the title, then knot the time of programming, but also ready to change back randomly generated, and finally contrast use, or feel the binary tree method is better, not only efficient, but also for computing the answer ah is also very simple.