The code can be reused, so the requirements can be reused, and the answer is yes. But demand is not free, and successful reuse requires us to do some work. The requirements specification is going to work. We cannot deal with only one system, so the underlying functionality between different projects is actually probably the same. We can meet potentially reusable requirements in different ways, and some will be expressed precisely so that they can be reused directly. At the beginning of the project, you can model the context scope of the target work by drawing a context range diagram to make the system visible. The visualization of requirements allows them to be reused by more people, and reuse can bring an unpredictable benefit.
The requirement specification has been identified and changed. The accreditation process is conducted countless times, quality checks each requirement individually, and the identification takes into account all requirements and the interplay between them. Identification to find missing, conflicting, and ambiguous needs. The missing demand needs to be discovered by using condition deduction, the demand of conflict, the demand of ambiguity refuses to use the words "should" and so on.
Requirements are also managed, and demand management is a systematic approach to finding, documenting, organizing, and tracking system requirements changes that can be used to capture, organize, and document system requirements and align customer and project teams with changes in system requirements. Effective demand management is the maintenance of clear requirements, the attributes that apply to each requirement type, and the traceability to other requirements and other project work.
Requirements must be traceable to maintain consistency between the product and the external use of the product, and we need to track business events and conduct user review in order to track demand.
The product has been changing, and we want to focus on reviewing your effectiveness in collecting and formulating requirements, discovering major mistakes and successes, hindsight as a feedback mechanism, good feedback mechanisms to help identify changes, post-mortem analysis to collect experience wealth, and points out the content and experience to be learned in the project. Just like our high school mistakes notebooks, the records of those wrong questions are their own mistakes, the project's post-mortem report will make you progress, perhaps also a few shortcuts, so that you do not fall in the same place a second time, even if you fall, you will stand up.
Mastering the need process read Note 06