Software Engineering Project Experience Learning Summary

Through the CASE in last week's class, our team members have been greatly inspired. The following is a summary of their experiences:

1. Lack of overall staffing arrangements. Although our Group basically puts all the team members at work in the project process, we did not detail the task decomposition in advance, so we did not clarify the work tasks of everyone, as a result, personnel coordination is messy during the project process.

2. The project progress is not monitored. From start to end, there was no established time point, no planning of the time, no specific extent of the project needs to be carried out in a certain period of time, and the project was not completed at the end of the project time.

3. No workflow is set.

In the project process, we did not define the production process of the product, and did not implement process-based operations. When six products are created together, there is no sequential flow operation in the product production process. As a result, at the end of the project, due to the lack of 5 minutes, all products lack the last process and almost no finished products. If it is a process-based production, at least four or five finished products cannot be produced as required, even if the time is not enough, the risk can be minimized.

4. The relationship between product quality and project progress has not been properly handled. Quality and time are a contradiction. There is no perfect product within the specified time. We have not balanced the relationship between product quality and project progress. In the early stage of the project, the product quality standards were set too high, and it took a lot of time to make the product more exquisite, resulting in the end time of the project being insufficient.

5. Insufficient communication among the team members. Each team member only concentrates on their own tasks and does not communicate with other team members about their work progress and difficulties.

 

In some aspects, our team is doing well, such as controlling project costs, evaluating project difficulty, and grasping project requirements.

 

Sense Thank you The teacher gave us this opportunity to experience the project from the beginning to the end. The wonderful comments from the teacher also taught us a lot of things; his interpretation of software engineering concepts and processes gave us a deeper understanding of software engineering.