EE308-Lab12-Course Summary

EE308-Lab12-Course Summary

EE308-Lab12-Course Summary

• Format Description
• Self-analysis
• The Mythical Man-Month
• Team Analysis
• Learning software engineering prove
• What I want to say

Format Description The link Your Classhttps://bbs.csdn.net/forums/MUEE308FZThe link of Requirement of This Assignmenthttps://bbs.csdn.net/topics/603781458The goal of this assignmentSummary of the course Self-analysis

1. The software engineering course lasts more than 18 weeks from the beginning of my junior in university. Overall, I have gained a lot from it. When I first knew that I would have this course, I was super exciting because I am a big fan of computer programing and I always dream of creating my own software. Through this course, my team members and I successfully realized the development of small program, in addition, my code ability has been strengthened, team cooperation ability has also improved a lot, which all are in line with my expectations.
2. When it comes to shortcomings, the functions of our small program have not been fully realized because of time, only about 90% of them have been completed. As the team leader, part of this is due to my failure to properly distribute the work of team members and timely supervise them. In addition, I was in charge of the back end crawler, and part of my code was not well developed due to the rush to deliver. There is still a lot of room for improvement and iteration.
3. In a whole process, the amount of programming code I have is estimated 1000 lines.
4. The final Alpha sprint and the mission delivery and presentation all impressed me. Alpha Sprint we experienced a painful but slow harvest of seven days, the success of the small program to achieve most of the functions, it is very rewarding. When the task was delivered, we showed the vlog carefully shot and edited by everyone to record our mental journey. It was not only the explanation of the course tasks, but also the record of good memories of cooperation.
5. I spent more than 300 hours in software engineering skills practice. An average of 15-18 hours per week.
6. I strengthened my Python programming skills and learned some database languages like MySQL in the process of interaction with classmates at the front end.
7. The time spent on each operation of a software engineering practice:

OperationTime (h)Bobing game design7Prototype design6UML diagram drawing8Project plannning4Project discussion7Project function realization180Project improvement20Unittest5 The Mythical Man-Month

There are lots of experience of this project I can share with you guys. I am in charge of the github repository information crawling work, which seems relatively simple but still has a lot of details to deal with.

1. One is that there will always be an error in the crawl process, and the process of typing code is actually a process of constantly fixing bugs. It was very tiring, but I was very happy when I saw the climb succeed.
2. The second point is that I used github’s official API for crawling, unlike my previous attempts. The team used Python language, but the official documents provided references to Java, and there were very limited reference materials available on the Internet, which greatly increased my difficulty, and finally succeed in continuous exploration.
3. Third, I may need to change the format of the output data store to meet the needs of my classmates who are responsible for the back-end database and Django.

Team Analysis

1. To be honest, I got a great team with 5 great team members. At first we were very confused. We were all new to the game, so we didn’t know where to start. From determining the function of wechat small program, to the division of labor in the direction of front-end and back-end crawler, and then to the successful docking, finally completed an imperfect but complete small program. Through meetings and experiments, we have honed our will and ability. When we encountered serious difficulties and mistakes, we encouraged and helped each other and solved problems one after another together.
2. Like Python and js css programming, Blog writting, Vedio clipping. We gave full play to the strengths and characteristics of each member. Maybe this is the meaning of teamwork. Nobody can finish a great task alone, many hands make a nice work.
3. At last, this course gave us a great chance to experience what the software designing team work is like in a real company. We follow exactly the same process under the guidance of our teachers and teaching assistants which gave us an early taste of social work in the future.

Learning software engineering prove

1. All the meetings and cooperation have been record in the CSDN blog:
   AlphaSprint Summary
2. All the data and coding can be found in Github:
   https://github.com/jyw2000-jyw/EE308-AlphaSprint

What I want to say

As saying goes, ‘A slow sparrow should make an early start’ . I am not a talented computer programmer. So I must start early, and once I have set my own goal, I must go for it as long as I still can. The team cooperation was impressive, I got more familiar with other 5 of my classmates. And all of them are aggressive and persistant in work. We worked together and learned from each other. If I get another chance, I will choose to be in the same group with them. At last, I want to say thanks to my teacher and TAs as well as my teammates.