BSA 375 Week 2 DQ 2 - contradicting stakeholder...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
Requirements elicitation refers to the process of communicating with system users, customers, and  system-development stakeholders to determine system requirements. Different elicitation techniques may  be needed to interact with stakeholders and collect user requirements from them. Incomplete,  inconsistent, and incorrect requirements could lead to disastrous results. The fact that human nature plays  a part makes requirements elicitation prone to errors due to the unpredictability factor. Articulating real  requirements can be a challenge for users on quite a few occasions when they aren’t certain about what  exactly they want from the new system. Some of the other challenges associated with requirements  elicitation include: assumptions, access to key stakeholders, insufficient time to contact stakeholders, 
Background image of page 1
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: contradicting stakeholder requirements, and suboptimal support from stakeholders. An important part of overcoming such challenges in the requirements elicitation process is to encourage customers, users, and developers towards communicating and cooperating with one another. Making use of the right elicitation techniques therefore becomes an important part of successfully gathering requirements from users. An iterative approach becomes an important way of considering, eliminating, modifying, or combining requirements to a level that is satisfactory to all the concerned parties. It makes requirements elicitation a continuous learning process which improves itself through repeated feedback. Reference:
View Full Document

{[ snackBarMessage ]}

Ask a homework question - tutors are online