Requirements definition is one of the most important parts of any project. As mo
ID: 3885209 • Letter: R
Question
Requirements definition is one of the most important parts of any project. As most of the activities that will follow are related to the requirements that were collected and formalized, we can say that any imprecision that takes place during this process can lead to problems down the road to developing the system.
In relation to this, answer the following questions:
What are some ways in which you can ensure that the requirements are complete and accurate?
What would you do if you realized that some of the requirements were incorrect?
How could you fix such inaccuracies?
Explanation / Answer
Hi,
Using below criteria we can make sure that the collected requirements are accurate-
The requirement should be-
a) Correct - The requirement should serve the business objective or goal
b) Unambiguous - The requirement has only one interpretation. It should be clear and should not have any ambiguity.
c) Complete - the requirement is self contained with no missing information
d) Consistent - the requirement is externally consistent with its documented sources such as higher-level goals and requirements
e) Verifiable - the requirement should be testable and testers should be able validate it
f) Modifiable - The requirement should have the property that it can be modified whenever needed.
g) Traceable - The requirements are required to be mapped to the set of Test Cases. Each requirment should be mapped to the test cases written for it. Thisinformation is collected in requirements tracability matrix.
what would you do if you realized that some of the requirements were incorrect?
The answer depends on at what phase of project we have come to know that requirement is incorrect.
If the requirement error is detected during the requirements gathering phase, we can notify the Business Users/Analyst about the error in requirment by using an appropriate format for reporting. Post that we can schedule another meeting with Business user to help correcting the requirements error.
If the requirements error is detected during the project design phase or implementation phase, it is very difficult to correct and re-implement in the project. In that case, the requirement can either be dropped or it need to be fixed as a production fix once the issue is identified in the production incident.
How to fix requirement inaccuracies-
1.Making the cuctomer to think about and sign off on the completed software requirements specification, to align expectations and ensure that both parties have a clear understanding of the deliverable.
2. Need to facilitate meeting to discuss on the requirement inaccuracy and to find out the gaps in understanding.a
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.