I. Background and Introduction
In the City College, the presence of more than a dozen twenty large and small communities, although you can get a range of information to the community through micro-channel public number, but not an overview of all societies and all activities; the president can not co-ordinated to manage this community; for administrators, activity approval, community applications, etc. too cumbersome.
The project is mainly used for the overall management societies, there are three roles: members (ie, the average student), president, administrator.
This project members operations that can be performed: modify personal information, view event announcements, registration activities, see the information society, received the approval of the administrator sent the results of the message.
President of operations that can be performed (including any operating members that can be performed): Delete community members, management activities under their own communities, application activity or cancel or modify the activity event information; internal and external announcement announcement under the management of their own communities; add members ; modify the information society.
Administrators operations that can be performed: Modify the administrator information; approve modification request information society; community approval application activity, activity modification information, Cancellations activities; increased community; the dissolution of the community; to increase site; deletion of the site; reset students password.
The project has been implemented in 95 percent of the functional requirements document as required, the web version is already available as a basic community management software to use.
Second, the project Links
Progress: http://129.211.28.105:8080/society/
github：https://github.com/BrocaZ/SE_ClubManager
Requirements Document: https://www.cnblogs.com/z31701005/p/11788032.html
Design Document: https://www.cnblogs.com/z31701005/p/11878888.html
Prototype Document: https://www.cnblogs.com/z31701005/p/11974276.html
First meeting: https://www.cnblogs.com/z31701005/p/11890061.html
Second meeting: https://www.cnblogs.com/z31701005/p/11936117.html
Work of three projects
Phase I: Design requirements
Writing requirements documents section.
The second stage: the design phase
Timing diagram drawing section.
The third stage: interface prototype stage
Early: the selection of static web templates to modify, to complete my community page modify and large frame members, is responsible for the integration of a page, a prototype of the web server deployment. After Log dynamic interface, and easy to implement initial team members page the other students as dynamic web pages written on this basis.
:( mid mid-president of the page is divided into pages and pages administrator) is responsible for implementation and administrator page dynamic front and rear ends of the connection, the process will be to modify the layout of some small places, and is responsible for the president pages and pages of administrators integration, while integrating some features to test their side to ensure that the function can be used normally.
Late late :( most basic molding process) to add pop majority can think of, including login, review, delete, add, etc. about twenty pop, secondary testing process and fix some small code problem, do something to make the page appear more reasonable page branch changes. After discussion to add some extra features, usually the other members write, I just write the administrator change the password, password reset page and site to achieve community search function, part of the code to modify the database password encryption and decryption of students and some community logo the dynamic implementation, other times responsible for the integration of all pages, the function code, the final finishing stage test report appearing in small problem I have here a unified corrected.
ps: After the end of the deployment of the servers website and database after completion of the final version of the Web page, found after deployment runs very slowly, so give up, or choose a local show.
Fourth, the project experience and summary
In this group the big job, I understand the basic processes of software development time, and appreciate the importance of teamwork, the following are some of my personal experience (reflection) and summary.
- preliminary design legacy issues: the design of the database design and various functions are not in place at the beginning, I think the main reason is to reflect in the design phase is not complete, the database field is changed about three versions before deciding, with the advance of progress in the latter function is also constantly increasing, modify.
- time allocation problem: the whole course of the project, to promote the early slow, late lead time is tight, a little unreasonable allocation of time, some feel the order of the design process a little upside down.
- the division of labor: the division of labor is not so clear in our group, four people working on a web page, almost all of the work related to the function of static pages, dynamic pages and back. Upon completion of the project review process, I feel a bit confusing division of labor, like the other group a clearer division of labor would be better in the future work must pay attention to.
- Resource management issues: I am responsible for post-integration project content, our resource management with git, but the process will be a lot of problems, the more versions behind will find very confusing, not easy to control, because of the emergence of another classmate modify the function or some page layout at the same time, another classmate also modify the content, content dare not pull down the cover, since there may be one thing, I changed the a and B, you changed the a and C, take over exactly the same thing we did not, so sometimes in the process of doing integration in, spend a lot of time to confirm the version of the problem the program to ensure that the changes we are integrated together (integration of people feel the pain).
- the group AC: Most of our group in order to exchange the main line, the line meets less, may still like the other modes of communication lines once a week at the conference will be better. In the late modification of the process issue piecemeal, it would be more prone you made me a language situation, three chat box jumping, will feel a little difficult to control.
- Testing: link is relatively fragmented, but also all have to do something, by doing propose amendments to me, I would be unified modifications.
- Incomplete: upload local images unrealized, head of personnel for the realization of dynamic, modify picture and other functions to achieve. (Mainly related with the picture content to achieve)
最后，还是感谢团队里所有人都在努力地推进该项目的进行，在后期网页的实现过程中没有人懈怠，每个人都做了很多内容。但对比其他组的工作，我们的不足非常的多也非常的明显，并且感觉技术含量没有那么高，大多数时间还是在“苦干”，在今后的学习过程中还是应该更多地开拓自己的视野，学习和使用其他更新的内容。
五、对课程的意见和建议
朱勇老师的软工课的大多环节设计都还是很完善的，并且老师上课也很用心，让我们学到了很多内容。没有什么意见，但在经过思考后提出一些建议。
- 感觉团队项目的时间会比较少，个人项目其实可以往前再推一周，因为其实往前推一周的时间也是足以完成个人项目的，但团队项目有多一周就会更宽裕，也可以有更多的时间去完善。
- 可以添加测试环节，因为现在没有完整的测试环节，大家的测试可能都比较零散。
- 可以在初期准备的时间里，增加一个组内角色细分的模块，把分工更明确的在早期确定下来，有人主做技术内容有人主做整体统筹规划。