ASE Course summary by Feng Xiaoyun

Beginning of the beginning, interview the blog of the previous ASE class:http://www.cnblogs.com/legs/p/4894362.html and Beihang University soft M1 inspection: http://www.cnblogs.com/legs/p /4973542.html;

Finally, write down this summary, sedimentation reflection, and self-openness;

In fact this is the same thing: Nevermore future.

Specific project implementation See our top blog: http://www.cnblogs.com/legs/p/5149065.html

Specific project analysis in the report has been described in detail, several other students also have a summary of the basic cover, so the focus of the summary is not the project itself ~

Project selection:

In fact, this part is my most want to vomit groove, (before class to our proposal: http://www.cnblogs.com/legs/p/4892151.html and some of the program in the class), finally everyone ran the UWP platform Bing Dictionary. In fact, everyone's research may not be in-depth, it is likely that the following bingdict have meat to eat. Our group would like to do some of their own work, so did not choose the Bing Dictionary project to the UWP platform transplant, but combined with the program submitted by Qunshan classmate, and Bing Dictionary search word function, to complete a new online word function, so did some research on the word, Also discussed with the head of the Bing dictionary, including our final PDF reader program, which was finalized at that time. But the resulting series of tears about Adobe,foxit has to be Chen's blood, is another several long story.

In the project selection process, beginner's mind is still good, but also made a positive effort to prepare for the preliminary, but the technical investigation is not enough, for some technical issues too optimistic.

Team organization:

The method of construction outlines the different team development models, and if we have to choose one, our team should be "amateur theater mode". Not only because we have no experience in software development, or even the corresponding knowledge reserves are insufficient. Take me for example, C # and Xmal are doing while learning ~ So after the topic is determined, we first to the software of the various functional modules have been segmented, and define the interface data format, to facilitate the various modules "multi-point flowering, go hand in hand" (http://www.cnblogs.com/legs/ p/4930117.html). The reality is to achieve such a purpose: their own study, non-interference. In order to prevent a person from being absent, the project was shut down, and we made the most of the effort in each direction, arranging the manpower. This has a significant effect on the early stages of the project, but it also planted seeds for later problems. In fact, such a pattern of their respective roles, more suitable to build on a stable and mature development process and professional development staff based on the so-called "Symphony Mode" under the real increase in productivity.

In this project, each team member chooses a different role, and as the project progresses, the task is dynamically assigned.

Curriculum advancement:

Pre-two personal projects, taking up a long time, the pressure is also relatively large, the last estimate of power when it is to improve the programming ability and enter the learning State, and service in the final results determined.

But the course for the team project seems to be more and more chicken, after all, when the class autumn Feng teacher said things, we are half understand, and we in the process of the project to be solved urgently, but not the course on a short one or two hours can be solved. The teacher can share the experience with us, help us to point the minefield, finally each pit all jumps to also have to be oneself. Teachers can show us the direction of development of advanced productive forces, and the detailed use of GIT,TFS has to be "practical knowledge"; However, it seems to be the course, although we are toddlers, but l always have to walk. Oh, I seem to understand why the curriculum should put the teacher-student relationship in the first section: Coaches and students-details can be read the construction of the law of the 5th to 13th page, educational developments, progress together ~

The course is promoted to the project, and the content of the course is extracted from the project. Those who understand, write down, those who do not understand, will eventually understand ~ after all, our ultimate goal is to run ~

Project implementation:

This is a very worthwhile to be recorded in the story ~ Project inspection, the autumn Fung teacher said.

But the pits are deep and complex, and not part of my responsibility, so it's just a list. Thanks to Yimeimei, don't forget to quit.

"Amateur Theater Mode", everything seems to be orderly, the first big pit came: the students responsible for logical control, decided to use DLLs to call each other methods to achieve the interaction of each part of the code, in A nutshell, A, a, B will be compiled into a DLL, where a dll,b also tune a DLL. Note that this is a deep pit;

The idea is to design the plug-in, but it is not fully researched and the existing technology does not support it. (then being review by various challenge), and then decided to take advantage of Win32 Adobe's Reader implementation, note that this is another deep pit;

In the Alpha release when the project completely do not know where to go, Qiu Feng teacher enthusiasm open brain hole, help us design Planb,plan C,plan D ... Unexpectedly later suddenly steady, successful implementation of the Foxit SDK call. However, due to copyright issues, doomed cannot release~

Deep pit, can't bear to say: one in the beta process to complete a PDF reader, and the art of the issue of a violent discussion of the story ~ a never do release version of the last server who did not understand the story ~

On this road, we seem to be restricting, and seems to be the right path gradually away, seriously recalled, it is indeed worth chewing repeatedly. But grief, must be after the pain set.

Team work:

Oh, team, we are also an "amateur troupe", What, I am pm, responsible for more Bo and urge more Bo? A joke ~

In fact, the model of our team is driven by each other, after all, after all, the task of separation, can control the overall situation there is no manpower. So quarrels, compromises, unavoidable ~ but the understanding of each other's tasks, the patience of each other. For example, my first responsibility for the translation of the dictionary, is to parse the online Search Word API return interpretation, extracted from the JSON format after the completion of the data format conversion stitching into a string, the control module is willing to receive, so later the POPUI data conversion must be completed. This not only reduces the efficiency, but also artificially separates the dictionaries and our software. So from this point on, we and the dictionary leader did not contact again, the search term is only as a tool exists. The teacher in review is always deeds can be combined with other parts of the dictionary, so we added the ability to import and export new words list. After all, from the data format, they are already two things ~ For example, do not set up testers, their own design of the module, their own environment all-round debugging, testing good, but also to wait for each other to do well before the test ~ For example, each classmate to go back to the exam or other, delayed the work process, the project stalled ... In fact, you can set up a test, but also control the overall situation, coordination of the positions of all parties, pm~ However, our actual PM, but only to complete their own project volunteer responsible for the various matters in the group, a lot of things in the group are also heated negotiations, the result of friendly compromise ~

We are a rice ball, but also a growing team.

Personal progress:

Blog can be checked, my tasks are completed smoothly, back to school time is short, the team project is not in my part is restricted or dragged.

Finally, the art part was questioned, I only said, delete the picture is just a comment on the thing ~

From small white to pseudo-white, my technical road forward a big step ~

About teamwork, learn about software development process, go through it firsthand, and benefit from it ~

Lessons learned:

Must fully investigate, in the case of limited time, rely on the standard as far as possible mature;

Establish a scientific and effective management mechanism, including version control and personnel control;

Balance projects and work, important things will not become urgent things;

Team work ability first, communication first;

Communicate with people outside the team, listen to their suggestions and help the project grow;

ASE Course summary by Feng Xiaoyun