183
社区成员
发帖
与我相关
我的任务
分享| The Link Your Class | https://bbs.csdn.net/forums/MUEE308FZ |
|---|---|
| The Link of Requirement of This Assignment | https://bbs.csdn.net/topics/603781458 |
| The Aim of This Assignment | Course Summary |
| MU STU ID and FZU STU ID | 19103620 & 831902223 |
· Know process steps of software design and development: Through the study of the course, we understand the multiple stages we need to go through in the process of designing a software, such as requirements analysis stage, overall design stage and detailed design stage.
· Improve code capability: In several LABs of the course, I have fully practiced coding, so my coding ability has been improved to a certain extent, which is not limited to a single programming language.
· Teamwork ability: In the last few experiments, my classmates and I formed a two person and five person team to carry out deeper development and practice. In the team programming task, we not only improved the ability to write code, but also realized efficient cooperation and communication with team members.
· I can't do a very comprehensive analysis of software requirements and user use cases
· Requirements are sometimes omitted when writing code.
· Count how many lines of code you have completed in this software engineering practice.
Nearly 4000 lines (3145 lines in "Bobing Game" program, 800+ lines in Team project).
· How much time does each operation of software engineering practice take? (Make a list)
| LAB1 | 2 hours |
|---|---|
| LAB2 | 20 hours |
| LAB3 | 12 hours |
| LAB4 | 57 hours |
| LAB5 | 2 hours |
| LAB6 | 5 hours |
| LAB7 | 14 hours |
| LAB8(Alpha sprint) | 40 hours |
| LAB9 | 5 hours |
| LAB10 | 10 hours |
| LAB11 | 3 hours |
| LAB12 | 3 hours |
· Which assignment impressed you most? Why?
Among all the LABs, the most impressive one was LAB4, not only because it took me the longest time, but also because I learned a lot. In this experiment, I deeply experienced the complete software development process, including the early analysis stage, the middle code writing, the later software testing and so on. At the same time, my code ability has been greatly practiced and improved in this experiment, and I also learned new software and new programming language in this experiment.
· How many hours have you spent on soft work practice? How many hours per week on average?
Add up the contents shown in the table above, there are about 173 hours for soft work practice, approximately 15 hours per week on average.
· What new software has been learned and used?
PyCharm: This is used to write code.
StarUML: This is used to draw UML diagrams.
Typora: This is used to write my blogs in Markdown file type.
Android Studio: This is used to develop my "Bobing Game" program.
· What new tools have been learned and used?
Git: This tool is used to upload development files (such as code) to the open source platform GitHub.
Wechat developer tools: This tool is used to develop and test the wechat applet.
· What new languages, platforms and methods have been learned and mastered?
New language: Python.
New platforms: Github, Gitee.
New methods: NABCD model for demand analysis, PSP table for recording, Unit test.
For the whole series of experiments, including individual projects and team projects, I feel that I am constantly improving.
In individual projects and two person projects, my main improvement lies in my code ability. In team projects, my improvement lies more in the improvement of team cooperation ability, such as how to communicate with the project leader.For example, in the alpha sprint stage, after I wrote the code according to the requirements of the first version, I was informed that the requirements of the project had changed, so I had to change my code according to the new requirements. In my communication with the project leader after several requirements changes, I understood that communication is the basis for the normal operation of a team. If there is no communication, everyone in the team will do things on their own way. In the end, the things they made may not fit each other, resulting in the result of development failure.
· To myself👦
I will tell myself to spend more free time learning, including new development software and new programming language, and practice more in the process of learning. Some problems can be found when you start doing them yourself. Learning by doing!
· To Mr.Zhang👨🏫
The experiments you arranged are very brilliant and colorful, including blogs and vlogs, but they do take up a lot of time.
· To next generation🧒
I hope you can do better than me, work harder!
· About team players👊
I like my teammates very much and appreciate them very much because they will tolerate my small mistakes. It's very pleasant to get along with them. And I communicate with them very well, so I work with them very efficiently. By the way, I do not want to change my team players.
I think our group is a very united and friendly group. Under the leadership of the team leader, each member of our team is creating his own part of the project according to the needs. And I think our group has reached the "creation" stage, here are two reasons. First, the topic we have selected has not been put forward at present, and I think it is a problem to be solved urgently. Second, in the process of doing the project, we are also constantly learning and receiving new knowledge, operating it and applying it to our own design, which is also a "creation" process.
Here are some Github repositories record my learning records.
| Github repository links |
|---|
| EE308-LAB2 (Individual assignment) |
| EE308-LAB4 (Bobing Game) |
| Project (Bilibili_Xiu_Assistant) |
This course is the most impressive course I have ever experienced !!! I have experienced a lot and learned a lot, in general, learning by doing is an unforgettable wise saying.
