char2
1. After the system is launched, if users never ask questions or demands, it can only prove that the system is not used. The real ideal state is that the customer has been asking questions, the project team has solved it, and it has been repeated;
2. The project team's understanding of the requirements is 0 at the beginning. The customer initially understands the requirements, and there will be changes in requirements after use. This is normal, indicating that the user understands the requirements again;
The project team needs to understand the requirements in a very short period of time, have strong business learning ability, and plan a software system that truly meets their needs.
3. There are three levels involved in demand analysis:
Background: Why this project? Why did the client want to do this project? What would happen without this project?
Needs: What customer problems have been solved, what people and units are involved, what are the goals, what are the scopes, and what are the success criteria?
Requirements specification: divided into functional requirements and non-functional requirements;