Requirement Development Process

The requirement development process is a critical aspect of software development that involves the identification, gathering, and documentation of functional and non-functional requirements for a software project. The process begins with defining the project's vision and scope and concludes with the documentation of the requirements in a baseline document. In this article, we will explore each step of the requirement development process and explain their importance.

1. Define the Project’s Vision and Scope

The first step in the requirement development process is to define the project's vision and scope. This involves identifying the goals, objectives, and purpose of the project. It is essential to have a clear understanding of what the project aims to achieve and what is included in the project. The project's scope should be well-defined to ensure that the requirements are focused on the project's objectives.

2. Identify User Classes

The next step is to identify the user classes or the types of users who will be using the software. This includes customers, employees, administrators, and any other groups that will interact with the software. Each user class will have different needs and requirements that must be addressed in the development process.

3. Identify Appropriate Representatives from the User Classes

Once the user classes have been identified, the next step is to identify appropriate representatives from each user class. These representatives will provide input on the requirements, ensuring that they are aligned with the user's needs. It is crucial to select representatives who have a deep understanding of the user's needs and can effectively communicate them to the development team.

4. Identify the Requirements Decision-Makers and Their Decision-Making Process

In this step, it is essential to identify the decision-makers who will be responsible for approving the requirements. This includes understanding their decision-making process and the criteria they will use to evaluate the requirements. Knowing this information will ensure that the requirements meet the necessary criteria for approval.

5. Select the Elicitation Techniques That You Will Use

Elicitation techniques are used to gather information from stakeholders, including user representatives and decision-makers. There are various elicitation techniques available, including brainstorming, focus groups, interviews, and surveys. It is essential to select the appropriate elicitation techniques based on the project's needs and the stakeholders' preferences.

6. Apply the Elicitation Techniques to Develop and Prioritize the Use Cases for a Portion of the System

The next step is to apply the selected elicitation techniques to develop and prioritize the use cases for a portion of the system. Use cases are scenarios that describe how the user will interact with the software. They help to define the functional requirements of the software.

7. Gather Information about Quality Characteristics and Non-Functional Requirements from Users

In this step, information about quality characteristics and non-functional requirements, such as performance, reliability, and security, is gathered from the users. These requirements are essential for ensuring that the software meets the user's needs beyond just the functional requirements.

8. Elaborate the Use Cases into the Necessary Functional Requirements and Document Them

Once the use cases have been developed and prioritized, the next step is to elaborate on them to identify the necessary functional requirements. This involves breaking down the use cases into smaller components and documenting each component's requirements.

9. Review the Use Case Descriptions and the Functional Requirements

In this step, the use case descriptions and the functional requirements are reviewed to ensure that they are complete, accurate, and meet the user's needs.

10. Develop Analysis Models If Needed to Clarify the Elicitation Participants’ Understanding of Portions of the Requirements

If there are portions of the requirements that are not well understood by the stakeholders, analysis models can be developed to clarify them. Analysis models include diagrams, such as ctivity diagrams, state diagrams, and sequence diagrams, that help to illustrate the system's behavior.

11. Develop and Evaluate User Interface

In this step, the development team should create user interface prototypes for portions of the requirements that are not clearly understood. User interface prototypes are mockups or designs that simulate how the user interface will look and function. The prototypes should be presented to the appropriate stakeholders for evaluation and feedback.

12. Develop conceptual test cases from the use cases.

After developing the functional requirements, it is essential to develop conceptual test cases from the use cases to ensure that the system meets the user's requirements. Test cases should be developed for each functional requirement, and each test case should have clear acceptance criteria.

13. Use the test cases to verify the quality of the use cases, functional requirements, analysis models, and prototypes.

The developed test cases should be used to verify the quality of the use cases, functional requirements, analysis models, and prototypes. Each test case should be executed, and the results should be analyzed to ensure that the requirements have been met. Any issues or defects found should be documented and tracked until they are resolved.

14. Repeat steps 6 through 14 for the other portions of the system until the team concludes that requirements elicitation is as complete as it needs to be.

Once the requirements for one portion of the system have been completed, the team should repeat steps 6 through 14 for the other portions of the system until they are satisfied that requirements elicitation is as complete as it needs to be. This process ensures that the system meets the user's needs, and all requirements have been captured.

15. Baseline the documented requirements.

Once the requirements have been finalized, they should be baselined to establish a point of reference for all stakeholders. This means that any changes to the requirements after the baseline should be carefully evaluated and approved by the appropriate decision-makers.

Conclusion

The requirement development process is a critical part of software development. It ensures that all stakeholders understand the user's needs and expectations and that these are translated into a functional and technical specification that guides the development team. By following the steps outlined above, software development teams can be confident that the system they develop will meet the user's requirements and be of high quality.

Source:

"When Telepathy Won't Do: Requirements Engineering Key Practices" is an article written by Karl E. Wiegers. The article focuses on the key practices of requirements engineering and provides practical guidance for software development teams to effectively gather, document, and manage requirements. The steps outlined in this article are based on the practices and concepts discussed in Wiegers' article. The article is a valuable resource for software development teams looking to improve their requirements engineering processes and ensure the success of their projects.