Requirement FAQs:


Q: Is requirement a singular documented physical and functional need that a particular design?

A: Yes, and product or process must be able to perform.

Q: Are requirements developed before design and implementation?

A: Yes.

Q: Are requirements also an important input into the verification process?

A: Yes, since tests should trace back to specific requirements.

Q: Are requirements allowed but if not adequately tracked or preceding steps are not throttled by additional oversight or handled as a cost and potential program failure?

A: Yes, and then requirements changes are easy and likely to happen.

Q: Are requirements an illusion created by misrepresenting design decisions as requirements in situations where no real requirements are evident?

A: Yes.

Q: Are requirements typically classified into types produced at different stages in a development progression?

A: Yes, and with the taxonomy depending on the overall model being used.

Q: Are requirements prone to issues of ambiguity?

A: Yes, and incompleteness, and inconsistency.

Q: Are requirements altered before the system is complete?

A: Yes.

Q: Are requirements closely linked?

A: Yes, a product requirement could be said to specify the automation required to support a process requirement while a process requirement could be said to specify the activities required to support a product requirement.

Q: Is requirement stating what the system must do?

A: Yes.

Q: Are requirements subject to rules of data integrity then accuracy/correctness and validity/authorization are also worthy attributes?

A: Yes.

Q: Are requirements and how they should be managed and used?

A: Yes.

Q: Are requirements usually written as a means for communication between the different stakeholders?

A: Yes.

Q: Are requirements used as inputs into the design stages of product development?

A: Yes.

Q: Are requirements variously stated by different writers?

A: Yes, and with each writer generally emphasizing the characteristics most appropriate to their general discussion or the specific technology domain being addressed.

Q: Are requirements incrementally developed in parallel with design and implementation?

A: Yes.

Q: Were requirements crafted?

A: Yes, so they begin an effort to backtrack and re-baseline the project.