Soft Industry University community work projects personal summary
table of Contents
Second, the personal work summary
preliminary work:
Since only three people in our group, early functional for community needs analysis, design UML diagrams, database design, etc. are meeting to discuss together the last completed. In fact, beginning in the beginning of the work, but later found that about these designs is better to discuss with the fast, a person needs to consider what is difficult to complete. Further prototyping the outset blade made a prototype of app. Blade designed for beginning or proved very useful, it can be straightforward to express the desired effect as soon as possible.
interface:
app interface I mainly do, landing, my personal information, change passwords, president of the management association of members of management, event management, task management interface. As well as some changes of late. When writing interface because we usually use mobile phones has seen numerous app's interface, it will go to imitate, do not write yourself out of absolute imitation out looking. I also prepared the third prototype of the blog.
Write code section:
This semester just in Android mobile application development, write this program just to this course of study conducted a test, I wrote most of the activities of management whether to view the activities of the state has been approved, creating a new activity content, refresh the view the new activities are created successfully function. There is one final completion of the integration code, modify some errors and unreasonable. The most time-consuming integration code or the last, because a block of code written by someone else to understand and integrate some errors because it found.
Third, project experience and summary
First, this is the first time a complete step by step to do a project from start analysis and design, personal harvest is still great, I feel more deeply embodied in several places in the beginning of the project needs analysis, the entire process is completed panel discussions, all kinds of loopholes in the code and version management jobs last checked between members found.
Project needs analysis:
Because the front of the teacher gave us a long time to do this project needs analysis, also repeatedly stressed the importance of needs analysis, and we did not understand at the beginning, when given the demand of what the real needs are, after many thoughts correct just write out the share of demand report, I was impressed. The completion of a project must first set requirements, user needs willingness on software problems, analyze the target software system in many aspects of functionality, performance, data, etc. should be achieved. Only later do demand clear every step will be clear.
group discussion:
Although the large-scale operations to meet only twice a mandatory requirement, in fact, we discussed all the time to complete the big jobs in the process, most of the discussion can solve the problem by himself can not solve, a lot of times you encounter a bottleneck think very, very difficult to achieve may be just walked into a misunderstanding, this time to ask the crew might be able to find the right ideas, the other in the preparation of procedures, although different for each person to write specific content, but the method could achieve the same so that mutual learning their way to try a variety of online method more efficient than own one.
Code version management:
The big job so I really appreciate the version management is so important, because the basic version of Android studio controls of different codes used in the two versions of each combination code does not result in universal waste have spent a long time, some features have been implemented long ago, but after a difficult combination to run caused a lot of trouble.
test:
Many unreasonable honest examination when the teacher pointed out is I never thought of, because this part of the schedule function is not compact, and finally did not leave much time to consider the details and not enough time to test the function of the overall objective It is to carry out, often just want to test the correct branch and ignore the other errors, leading to emerged with the result there are many unreasonable. So pay attention to the test.
Fourth, curriculum recommendations
About big job:
In this lesson, you learn the whole process is in most big job in. From requirements analysis start to the final realization, the teacher gave us a lot of suggestions, let us at least take a lot of detours, but I think, because we in the morning this class with fewer people so there are so many opportunities to ask the teacher if the class of people more than one, a teacher who is difficult to take into account all of the group, one by one to supervise the progress of the project, so I think in this one big job, perhaps for a way to keep mutual supervision among student groups learn from each other. Can I let each group at every stage of the project came about some of the arrangements, completion, and other technical ideas, especially in terms of prototyping such as requirements analysis, if we talked about are not clear about someone else failed to understand is definitely a problem so that all the other groups can look for vulnerabilities, and to learn about other people's ideas of the group, in addition to whether you can make one or two groups do better modules to complete a detailed sharing, sharing methods to achieve what thoughts like .About the class:
When the class is often attracted Zhu teacher talked about in textbooks are not truths, there are some things you can listen to the impact of future life, it is recommended that the teacher speak something can broaden their field of vision.