table of Contents
First, Links
- schedule
- github
- Requirements Document
- Design Document
- Prototype Document
- The first meeting
- The second meeting record
- Third meeting
Second, the personal work summary
Final acceptance day approaches, the project has been completed almost the same. To be a summary of their work.
2.1 The main work
2.1.1 the requirements phase
Participate in requirements and write requirements documents.
This is the first time so needs careful discussion and written records, he had never realized the significance and importance of the written requirements document, the document just so wrong that needs to vent his father's party platform requirements. I did not expect the requirements document so important guiding significance for the late and decisive implementation phase.
Had written, just to complete the task, but now the completion stage and then come back to see the requirements document, can feel a lot of places can be refined, there are a lot of things is not clear and it seems there is little sense that the teacher wants the detailed and specific, can directly make another set of documents to achieve, what kind of a requirements document.
2.1.2 design stage
According to the requirements document drawing class diagrams.
I was naive to think that they look at the requirements document has covered it all. The results forgot to return to the front-end needs of many functions. In fact, can also be seen from the data flow diagram and timing diagram, there is a sense of very low front end, we had to write this design just only focus on how to achieve the back-end. This deletion results in time to the late teamwork, division of labor out of whack. The lack of a function to write a function, but fortunately, just four people team group in a roar on the finished thing. But even if only four people, and later version control, conflict resolution, also confused. Division coordinated the feeling is not very good beginning, covering the design phase is also not comprehensive enough, leading to the back step by step, bit of a mess.
2.1.3 implementation phase
Primarily responsible for implementing the backend.
The main achievement of associations and related classes, as well as administrator audit and message code, as well as the vast majority of front-end functions needed, basically every java file to encroach again. After a bit of data but also improve the database, password encryption, test projects.
The rear end is java + mysql, using a JDBC. This is probably the teacher said it manual labor children.
In addition to Zheng Ke also, we have three other individuals does not seem to experience in the development of similar projects, so we completed according to Zheng Ke also familiar way. The entire project is implemented by the front and rear side of the connection jsp tip is html + css. Very simple, very practical implementation.
The biggest problem encountered in the implementation phase may be a division of labor, division of labor within the planned completion of the well, the problem is there is a lot of work outside of the plan, then the division of labor is ambiguous, what version control is problematic, to finally give up with git , and direct the group and then send the code to call a person a unified modification. This leads to imbalance in the workload to some extent. The whole process, to achieve the division stage, do not know how to do, or you may want a balanced workload is delusional?
2.1.4 As leader
Responsible for the writing of all documents, including records of meetings and submit jobs. roll the dice roll out of me, it is a leader in name only. Super-conscious division of labor, even rushing to a job. deadline reminders do not even me the most is our four delays that, thanks to the super complete without delay the remaining three personal style. Tuesdays regular meeting was finished, they started doing the evening, the group's daily group chat and private chat no how broken, methodical progress in order to advance. Most of my procrastination, then three of them continue to spur progress, even if it is a week of my job also came close to being the first to get rid of Luo Lingjie.
2.2 summary
Completion of the final product is satisfactory, we have been trying to complete can now be completed, and no regrets.
After reading the other group blog, with the bigwigs of the gap is still have to admit. Technology stack itself too thin, did not learn a lot of new technology in this project. But the good news came at the whole software engineering process, the overall context will clear a lot, but also a team in a lot of running, but also look at other people's blog, and continue to reflect on their own and recognize their own and others' gap . Or rewarding.
Third, of course feedback
- Feeling good blog is this one, a few other subjects so often showcase platform for the job. See other people's blog, from other people learn a lot of work in, and deeply felt and bigwigs gaps and their deficiencies.
(But it is now search engine search name, will come out a bunch of links to blog Park, degree of shame a little high ah) - Whether individual or team work great work, or want to give the opportunity to set a good show, but also to give them a bonus opportunity.
- Community calendar outstanding job blog, I think can be retained, even prepared for the archives, so that a complete record of the process. It should allow the next dry when similar tasks to save a lot of effort to search. As our group sessions with some of the previous teacher said ink painting knife prototype. Also, you mentioned a couple of times but we still have not seen the last of Kim Yi Lin Jingdong similar to their big job, If we have a complete record of the blog should be able to benefit.
- In addition to the content on the books practiced in the job, the other really listen to much, it's not clear in the end how the final exam, but the exam still persist, the teacher probably still have their own considerations. But still have feedback about the book is very new, ppt, but the brain is now also left the impression of a class that is probably a vivid stories and examples, in fact, just fine.
Fourth, the team members
| Full name | student ID |
|---|---|
| Luo Lingjie | 31701002 |
| Wangqiu Hong | 31701004 |
| Zheng Shi Yu | 31701005 |
| Zheng Ke also | 31701373 |