EE308 LAB 12 Course Summary

The Link Your Class	EE308 MIEC
The Link of Requirement of This Assignment	LAB 12 Course Summary
The Aim of This Assignment	Course Summary
MU STU ID and FZU STU ID	19103387_831902225

Summary

(1) Compared with the course objectives and expectations of your first blog, “I hope to enhance the ability and employment competitiveness of computer major through practical exercise”. Compared with the current learning and practice, in what aspects have you achieved your expectations and objectives, what are the deficiencies and why?

After learning the course of software engineering, I think my code ability has been further strengthened, not to complete the task, but to enable everyone in a project to understand it. In addition, I have a deeper understanding of teamwork.

(2) Summarize the practice and improvement of this course.

• In this course, my code volume is about 2000 to 3000 lines.
• Time spent

Previous Lab	Content	Time
Lab 1	Self introduction & Course plan	45 min
Lab 2	Extract keywords in C/C++	1060 min
Lab 3	Design the Bobing software interface	910 min
Lab 4	Bobing software	3105 min
Lab 5	The development of a oral calculation program	125 min
Lab 6	Team presentation & Selected topic report	1 week
Lab 7	Demand analysis & Prototype design	738 min
Lab 8	Alpha Sprint	2 weeks
Lab 9	UML Exercises	240 min
Lab 10	Alpha Sprint Improvements	1 week
Lab 11	Software Testing	120 min

• Lab 2 is the most impressive because it has the freshness that I just came into contact with the course of software engineering, and it was completed by me alone without consulting any data, which cost me a lot of energy.

• I spend at least 20 hours a week on software engineering experiments outside the lab.

• I learned how to test my code performance and know how to use Unity, C#, Processing and Wechat Developer Tools.

• In terms of team collaboration programming, I have mastered the code specifications, and will write notes in difficult places for easy understanding.

The Mythical Man-Month

Let’s briefly talk about the precautions in team programming, according to their own good, give play to their strengths, determine their own division of labor, communicate with teammates, docking with the team leader, when there is a problem, look for information, self-study, ask teammates, help together.

Suggestions

For exercises, it is better to plan exercises reasonably according to the students’ learning situation and available time, rather than blindly pursuing results.

Team analysis

In my opinion, although our team has various shortcomings and shortcomings, it is still an excellent team in general. We are in the embryonic stage of team building and the first collaborative programming period. We just got to know each other and cooperated for the first time In the ALPHA sprint period, the team experienced a transition from the running-in stage to the standardization stage, and gradually developed from a team full of doubts and conflicts with low efficiency to a standardized team with established rules, clear goals and sufficient confidence The team was able to work together to create something meaningful and complete the project as it progressed from ALPHA to now.

Prove

Here are links to all our CSDN experiments this semester to prove our learning progress.

Lab	Link
lab 1	Self introduction & Course plan
lab 2	Extract keywords in C/C++
lab 3	Design the Bobing software interface
lab 4	Bobing software
lab 5	The development of a oral calculation program
lab 6	Team presentation & Selected topic report
lab 7	Demand analysis & Prototype design
lab 8	Alpha Sprint
lab 9	UML Exercises
lab 10	Alpha Sprint Improvements
lab 11	Software Testing
lab 12	Course Summary

Personality

Good bye, Software Engineering.