View the software development process from the YH Project

Project name: general commercial cash register system project member based on YH cash register system: Cui Jackie Chan, Jiang Qian LAN, Li Xiang, and Liu Shuijing project completion degree: 100%, started to enter the maintenance work
It took five months to complete the project. Although the project is not much different from your own expectations, there is a gap in the end. In addition, it takes too much time and is exhausted. In the future, we need to use "quick development and product iteration" to lead the team to develop projects.
During project development, continuous learning, exploration, and practice have greatly improved the thinking, technology, and problem solving ideas, there are many gains.
Before development, I referred to a lot of documents about the software development process. Some of them were vague and some were different. After such a complete development process, let's talk about the software development process that I understand first.
What is the process of software development?As we all know, the software development process is generally divided into five stages. Then I will start from these five phases in sequence:
[Analysis phase]

The teacher assigned us a task and assigned it to the group. The project is officially started. Familiar with the original system, divide modules to analyze the database of the original system, compare the functions, although time-consuming, but can clearly understand the functional logic and general implementation of the system. Determine the structure of the system and the development method: BS, Cs, classic three-layer, MVC, design mode analysis requirements + new requirements, draw a prototype diagram, write requirements by file (function module, user)

[Design phase]

Draw an example diagram to clarify the relationship between users and Use Cases

Use development tools to design the system's prototype diagram design database and generate entity classes

Package chart, class chart, writing method, parameter, comment

Draw the sequence diagram and write the design document for the shunye logic.

[Encoding stage]

First, build a project framework based on the package diagram. SVN version control for source code. Improve the most basic entity classes. You can use tools to complete the process. Modify and improve the UI Layer. Synchronization of coding starts based on the division of labor, which is discussed in the following topic. Unit testing should be done well

[Test phase]

Before the unit test is completed during the encoding process, make sure that the test is complete. Make sure that the database is created. SQL file, database initialization. SQL file, empty and zero auto-increment mark. SQL file. Integrated Testing, record bug fixes, fix a regression test with a flag, and repeat it multiple times.

[Operation and Maintenance]

Create a user archive table, including user details, contact information, system version information, and configuration information. Create a maintenance record table, including time, user information, bug information, solution status, solution description, solution (telephone guidance, on-site deployment, QQ remote, etc.) to create a requirement record table, record users' new requirements, establish maintenance solutions, and record the solutions to each new problem so that others can take over the maintenance. Create a version update record, including the time (front-end/back-end,) version number, current version number, update content (which bugs are fixed), modifier, approver, and approval time

Each stage should have a stage review. Due to limited experience, we have only two acceptance attempts throughout the development process. The mid-stage Acceptance refers to the pre-encoding acceptance. If the acceptance prototype, requirement, and design meet the project requirements, the acceptance can be continued. Otherwise, rework will be performed. Completion Acceptance: the acceptance before the end of the project. The functions, performance, flexibility, and other aspects of the Acceptance System.
This is my understanding of the software development process by leading this software development. It is inevitable that there are some similarities or inconsistencies, which are for reference only. If you are interested, leave a message for discussion.