For example, what does a librarian want in your library management system? What would you do without your system? How to do it with the system? What is the problem to be solved? What about readers, curators and others?
2. Solution provision, software starting point, process scheme, provided functions, solved problems, software interface, etc.
3. Confirm the requirements through prototype, interface diagram and detailed discussion with users.
4. Write requirements specification, generally including use case diagram, activity diagram, use case specification, interface prototype, etc.
Use case specifications include:
Use case name, performer, preconditions, postconditions, main process scoring process, abnormal process, rule constraints, etc.