EE308 Lab12

sunshine1211111 2021-12-19 01:12:15

The Link Your Class	https://bbs.csdn.net/forums/MUEE308FZ
The Link of Requirement of This Assignment	LAB 12 Course Summary-CSDN社区
The Aim of This Assignment	Course Summary
MU STU ID and FZU STU ID	19105274_831901203

Requirements

Please recall your first assignment in the summer vacation and your imagination of the software engineering course
1. Comparing with the course objectives and expectations of my first blog, I declare that I do a few parts to enhance the ability and employment competitiveness of computer major through practical exercise as a matter of fact. In details, I learn a bit of knowledge more than before, such as codes, both the front end and back end databases. Even though not so much, also know how to draw some kinds of UML diagrams, write a few blogs and PPTs and so on.
2. Summarize the practice and improvement of this course, including the following contents:

Just 5-10 lines of code I have completed in this software engineering practice
For each operation of software engineering practice , I probably take 1-5 hours to complete.
The sprint plan assignments impressed me most, because there are so much UML diagrams need to draw, such many sprint blogs to write……
18 hours I spent on soft work practice. About 2 hours per week on average.
I learn a bit of knowledge more than before, such as codes, both the front end and back end databases. Even though not so much, also know how to draw some kinds of UML diagrams, write a few blogs and PPTs and so on.

Write your own ‘The Mythical Man-Month’, which means write experience summary and case analysis in project practice (e.g., personal project, team project).

In project practice，as a matter of fact, For the first time, I realized the separation of the front and back ends, I also continue to assist in convening relevant meetings, discuss and studied the relevant contents, clarify our own respective tasks ,Code Review , Test Reporting , Size Measurement and draw class diagram, use case diagram, sequence diagram, state diagram and activity diagram. Searched the open source community for some interfaces for obtaining sources and information. In this sprint, I believe that profound significance for personal development and future team cooperation.

What do you want to suggest and tell the next practice, or for you at the beginning of school, for you in your freshman year, and for Mr. Zhang at the beginning of school? And expectations for future generations. In particular, do you want to change team players in the next term?

This journey may be a little tough, a few difficult, but also interesting and impressive. Also can be able to enhance the ability and employment competitiveness of computer major through practical exercise.

In accordance with the factors that condition a situation.

Please analyze your team. Software engineering practice is a rare serious team cooperation experience in universities. ‘The construction law’ says that there are several stages of team development. Has your team experienced them and finally reached the "creation" stage?

My team experienced them and finally reached the "creation" stage. Our teamwork maybe not contribute in a balanced statement. But we are co-operated enough.

How to prove that you have learned software engineering?

EE308 Lab9:EE308 Lab 9-CSDN社区

EE308 Lab11:EE308 Lab11-CSDN社区

Sprint Summary：Sprint Summary-CSDN社区

Sprint Collection :Sprint Collections-CSDN社区

And so on……

＊(Optional) Read the classic papers on code quality in software engineering, select one or several from the following literature, and make a reading note in combination with your own reality (for example, how about the quality of your own code, is it a big mud ball, and how to measure the quality of your own code)? Select one or more of the following reference papers:

[1] Stamelos I, Angelis L, Oikonomou A, et al. Code quality analysis in open source software development[J]. Information Systems Journal, 2002, 12(1): 43-60.

In this paper, the author focuses on the relationship between the average number of component statements, loop complexity, maximum nesting level, number of basic paths, number of unconditional jumps, annotation frequency, vocabulary frequency, program length, number of component I / O nodes and open source code quality.

I usually pay attention to the granularity of functions and components when writing programs to make them as appropriate as possible. Therefore, after self checking the code, I find that the average number of component statements and program length of my code are relatively appropriate.

Programmers are required to consider the quality of structural code when intervening in code.The project coordinator evaluates the quality of the code returned by the programmer according to predefined criteria.When serious problems occur in the project, the project coordinator needs to take appropriate code reorganization decisions