Software Engineering (3) Course Summary Report

My knowledge and experience of the soft workers:

1. Demand analysis is important, a good demand positioning can bring clear goals, full of drive, and after the user affirmation. In the early stages of finalizing the project, our group decided to do the academic data API, that is, considering that the information center does not have a perfect data interface (I do not mean to be sarcastic), and other school assistants in the project team due to the time relationship, will not be able to carry out cumbersome crawler data processing. It turns out that our needs are analyzed correctly, and a good demand analysis is half the project's success.

2. It is important to develop progress planning. The challenge of software engineering is not the challenge of mathematical logic, but the challenge of managing people and managing time. At the beginning of the project, our team was clear: since to do API, will start early, when other project team started to do school assistants, take out some of the interface, only so that our API can survive, otherwise our project is dead end. But knowing and actually doing is two different things--the members of the group are busy with everything else, and we're not even ready for an interface document when the other group is about to start!! Had to stay up late to drive out some API interfaces and developer manuals.

3. The user manual is important. The user manual is like a reassurance that you can keep a campus application developer. Our user manuals are as semantically clear as possible and detailed slightly properly. In fact, we didn't get too much complaining about the user manual from the developer.

4. User feedback is important. We immediately established an Exchange group after the API was released. This helps us to get useful feedback from developers in a timely manner. Every time we get feedback from developers, whether it's criticism or affirmation, we're happy-our work is not just there, it's being watched. This inspires us to make the API better!

5. Leader is important. Zhangtian leader has a deep understanding of JS, he enabled ES7 for the API. This is not just a relentless pursuit of the technology stack, it's a very sensible move.--ES7 async/await syntax drastically reduces the difficulty of writing asynchronous tasks, allowing other students in the group to develop and test quickly. In addition, he introduced ESlint and Travil CI to ensure the consistency of the Code style, which was also affirmed by the display of the site judges. A good technical leader can lead the team to work together to complete a project of a good project, and let the members of the group feel satisfied and accomplished.

My recommendations for the course:

We are all novices in the software engineering industry. It is difficult for the same students to have experienced classmates-Zhangtian is the exception. Beginners get together to make a project, it is difficult to have a substantial improvement-the level of vision is similar, from each other hard to learn things. The delivery of the project can be satisfactory and not much. Therefore, I suggest--the next soft engineering class, contact with the project of the Internet company engineer as a mentor, a mentor to lead one or two teams to guide students to develop a project for the company. After the project is delivered, these engineers issue a written evaluation of the students, and the teacher and the TA score according to the written evaluation.

Software Engineering (3) Course Summary Report