Amoy vote project summary
1.1 The purpose write Amoy right into every software development has been basically completed. This summary report writing project development, in order to facilitate the development of our custom in the future development of the project to better implementation of the project ; I have more information to standardize our development process and improve our future project development the development efficiency.
1.2 Background Amoy Zuozuo software to solve groups due to less empty classroom caused a meeting to find a classroom, the students find difficult to study room; target population is the application of Changchun University of classroom teachers, each class community, ordinary students; this software the range of applications include (not limited to) each of the main teaching building North Lake campus of Changchun University; this software product will be present in the pre-replenishment system of Changchun University Course Scheduling system, the latter will be developed as a stand-alone software, and all content self-contained ; the main purpose is to help meet classroom needs, community needs and events to help students achieve quickly find the right classroom.
1.3 References
"Construction of modern software engineering methods," third edition, Zou Yan, China Industry and Information Publishing Group
Second, the development of job evaluation
2.1 Evaluation of productivity 1. Software development lasted four weeks; 2. More repetitive development ; 3. For student needs to understand is not very thorough. Based on the above, the efficiency of the development of this project is not very high, on the contrary there is a considerable waste some time. 2.2 Evaluation of product features through our Gold Merlin Group No. joint collaborative efforts, Amoy Zuozuo software has been very good to complete the requirements analysis . After the trial observation of the software , the software development is quite successful in , but still there are some problems, because these problems are manifold. Such as: early needs analysis change frequently , the user also needs to understand there are some problems, which we need to use some time to maintain the panellists new issues raised and existing bug. Overall, this software development is quite successful. 2.3 summary of the technical methods of binding pair programming specification, standard naming conventions, comment convention, named member functions, etc. , in the future development of the project, we had better be able to pair programming according to specifications , and moreHao 's specification named correlation function . By way of panel discussions developed for this group of amateur crew mode, this mode lets everyone follow the guidance and organization of the team captain. Choose their own good as well as listen to the captain of the team scheduled to complete the task, you can better a newly formed team fused together. Increase the level of understanding of the team and enhance team efficiency. Also allows team members in amateur just for fun, the training environment, everyone can try out different roles, we can discuss relatively equally. In designing the human-machine interface, by using the PS drawing tools, the login screen mapping software and interface mapping out internal information, to facilitate the latter part of UI designers more good ideas to master architecture system architecture's better meet user 's functional requirements.
Third, Lessons Learned
3.1 development team in software engineering after the establishment of the project, to establish a project development team as soon as possible. Solidarity project team members collaborate, communicate with each other is very important to learn from each other's strengths and each other technical team members, the team's ability to continue to improve. Thus, in the development process of the project, the team will not be trapped problem fixed. In addition, there must be a person in charge of the project team, the project leader must be able to well users and members to develop communication and coordination between , in order to better understand user functional requirements. Human memory is always limited, so we asked the team members to make possible the preparation of a number of development documents that we use often to be found late in the project development information. The project team morale is a factor in the success of the project , we need to keep the momentum to develop our team, our team continue to grow. 3. 2 demand for research after the project is established, to the needs of research and analysis phase. 1. The project team with the user's overall organizational structure, the relationship of the persons concerned, duties , if not a good enough to understand the situation , so that the team can not be very good to complete finishing with the needs of households, or use household real functional requirements, so since we planted the mines for yourselfThe impact of the project development cycle, which requires us to go in-depth understanding of user needs. 2 . We should try to let users also participate in the project development team in the past, that is to say we want a user to put himself into the project development team in the past, this way, we have users authenticity demand, reliability will be greatly improved , it will not lay a trap for the late-stage development of the project . 3 . In the research process requirements, if the lack of adequate user involvement, such research needs is a failure. Many programmers do not want to participate in the user 's needs research to go, and why? Very simple, and user communication is better to communicate with the code easier interesting. Despite this, we still have to go and with a sufficient amount of time users to communicate, understand their real needs. Many users also true, they themselves do not want to participate in the research needs of the project, although the current situation so that we still have to strive to make the user to participate in the research needs in the past. 4 . Fuzzy demand, that is, ambiguous requirement specification is the most terrible problem. The first refers to the many users demand explanation had different interpretations; one refers to a single reader can be more than one way to interpret a requirements specification. Needle on this case, requires our teamTo be able to staff from many angles to analyze user different needs, sorting out final demand and user acknowledgment, set ultimately authentic needs, we must not by virtue of our own single- side surface of understanding to set standing user of final demand. 5 . Proper risk management and control work. Team members will have more or less a private matter, such as PubMed, test forty-six civil service exam and other things, in the part of the task assigned to take into account each group of students a reasonable allocation of related tasks. 6 . Demand research tool selection, users are generally quite interesting graphics, so we in the research process, I want to try using a graphical 's interface and user communication needs. For example, can be used PS software , the user 's needs they want to become the interface map, the user needs to convert an activity diagram and flow chart , the meaning of the expression is more intuitive.