What are software requirements?

Software requirements: This is the process of gathering the requirements from the clients and documenting them.

All the requirements needed for the development and testing of the model are defined in this phase.

Requirement engineering encompasses seven steps:

• Inception
• Elicitation
• Elaboration
• Negotiation
• Specification
• Validation
• Management

Let’s take the example of an electric car model and discuss all the steps of the software requirement process in the shot.

Inception: Inception is the first step in the requirement engineering process. In this step, the engineer goes through questions to start the model.

It plays a vital role in requirement engineering.

Example: If we want to build a project based on an Electric car, we will ask the following questions :

• What is the use of the project?
• Who is beneficial to this project?
• What are the suggestions of the clients about the project?

Elicitation: An essential part of elicitation is establishing a business goal.

• It is used to engage with the clients, customers and discuss the effects of the model.

Example: If we want to build an Electric car, we should have a plan to implement it. At the same time, we should interact with our clients.

Elaboration: The information attained from the inception and elicitation phases is expanded and refined in this step.

It refines all the aspects of the software model.

Example : If we have ten ideas to implement the Electric car concept, we will refine all the ideas. Then we select one that is efficient and the best for the end-users.

Refinement is based on the model requirements.

Negotiation: It is the stage where the customer and the software engineer go through a set of discussions to correct the errors or modify the software’s content.

• The customers, users, and other stakeholders are asked to rank requirements and then discuss conflicts in priority.

• After the discussions, the team decides which process should be implemented by taking the opinion of all the team members.

Example: If we implement one of the electric car models, a team will intensely discuss this model and schedule meetings to resolve the issues.

Specification: A specification may be a written document, a set of graphical models, a prototype, or a combination of these.

Example: After our electric car is built, we then document all the steps involved in making our model successful. We will try to make a graphical model for our project if possible.

Validation: In this step, the quality of the products is tested.

• If any errors are encountered in the model, the review team will correct them in this step. This step is generally done in the presence of a technical review team.

Example: They test the quality of the electric car by asking questions like:

• How many kilometers will the vehicle go?
• Will the parts be strong enough to defend the wall?

According to the quality, they give the rating for the vehicle.

If the quality is low, we try to implement it again.

Management: Requirements management is a set of activities that help the project team identify, control, and track requirements and changes as the project proceeds.

Example: If we want to change the sensors in our car and add new long-life batteries, we implement this step.