Introduction to the requirements analysis process of software engineering

Software Requirements Engineering Process (SREP), this paper briefly lists and illustrates the key points of work in the whole software requirements engineering process.

First, start

1. The project manager specifies the specific requirements for the process form according to the project characteristics;

2. Project Manager to develop project criteria, including: DTS (defect type), TRA (risk type), TRS (type of requirement), etc., in the process table by standard reference.

Second, the plan

1. The Plan manager estimates the requirement development time;

2. The Plan Manager completes: SPT (Progress Plan), TPT (Task Plan), the plan data into the PDS (Project plan summary).

Iii. Acquisition of requirements

1. Software Requirement Engineer collects the system summary information, fills in the Req (needs obtains the general picture);

2. Software requirements Engineers collect user needs, classify and clearly write requirements to REA (demand acquisition/analysis), RES (requirement acquisition plot), UiR (user interaction requirements);

3. Check the requirements acquisition process and fill out rec (demand access check);

4. If the inspection does not pass, from 1. Start the process afresh;

5. Software requirements Engineers fill in TRL (Time log), PIP (Process improvement recommendations);

6. The Plan manager collates this stage data, input SPT, TPT.

Iv. Demand Analysis

1. Software Requirements engineer needs analysis, set up analysis model, data dictionary and Project glossary, complete REA (analysis of the specific requirements of the model, please refer to the Structural analysis and object-oriented analysis of the specific work instructions);

2. Software requirements engineers will find the requirements of conflict, overlap, redundancy or contradictions, recorded in NCR;

3. Check requirement analysis, complete RAC (requirement analysis and inspection);

4. If the inspection does not pass, starting from 1 to start the process;

5. Software Requirements engineer to fill in TRL, PIP;

6. Planning Manager to organize data, input TPT, SPT.

V. Consultations

1. Software Requirements Engineers use NCR, negotiate with stakeholders to resolve problems identified in the requirements analysis, and input the resolution into NCR;

2. Software Requirements engineer According to the resolution, modify REA and other related documents;

3. If new requirements are introduced, the needs analysis phase needs to be renewed;

4. Software Requirements engineer to fill in TRL, PIP;

5. Planning Manager to organize data, input TPT, SPT.

Vi. Review of Needs

1. The person in charge of the review team formulates checklists, assigns inspection tasks to members, and formulates a review schedule;

2. The reviewers individually review the assigned content, and the problems identified will be entered into the DRL (defect log);

3. The person in charge of the Review Group organizes the review meeting, each group member submits DRL and discusses;

4. The Review Panel submits the inspection report in IRF form;

5. Software requirements engineers to revise the relevant documents according to IRF;

6. Planning Manager to organize data, input TPT, SPT.

VII. Requirements Document Preparation

1. Software requirements engineers take into account functional requirements and non-functional requirements, the preparation of "Software requirements manual"

For the writing format and requirements of the software Requirement specification, please refer to the specific work instructions.

2. Use RDC to check whether the software requirements specification is comprehensive, correct and enforceable;

3. If the inspection does not pass, starting from 1 to start the process;

4. Software Requirements engineer to fill in TRL, PIP;

5. Planning Manager to organize data, input TPT, SPT.