Monday, September 7, 2009

Requirements Elicitation - Part 2

By Katlego Raboshakga

Requirements elicitation forms the foundation of any software development project and this process often comes with a lot of problems. These problems are often not fully addressed or resolved and this results in them running into the subsequent phases of systems development with the result being that the system does not meet user expectations. The means of executing elicitation activities and iterating between them is unfortunately still not thoroughly understood.

According to Christel and Kang, requirement elicitation problems can be categorized into three groups: problems of scope, in which requirements either go beyond the scope of the project or do not address the entire scope; problem of understanding between the project team and users and the problem of volatility, which is the changing nature of requirements. These problems are further perpetuated by the lack of sufficient communication between the stakeholders involved and the analysts.

To address the problem of scope, the analysts must focus on the analysis of the organisation as well as the objective of the system. This will give them an idea of where the system fits in the organisation as well as what the system hopes to achieve.

Communication is the key to addressing the problem of understanding. The analysts need to be aware that stakeholders come from different backgrounds and therefore will have a different understanding of the concepts used. All issues must be properly articulated until consensus is reached.

As requirements change, the elicitation process should be revisited to address the evolving requirements and to make sure that the system is aligned to these evolving user needs.

The problems mentioned above are only some of the many problems in requirements elicitation. Other elicitation challenges include the stakeholders’ unwillingness to change to a new product, unspoken or assumed requirements, limited time and many more. Selecting the right techniques and encouraging continuous communication can help to mitigate many of the elicitation problems encountered.

References:

Christel M., And Kang K, Issues in Requirements Elicitation, Available from http://www.sei.cmu.edu/pub/documents/92.reports/pdf/tr12.92.pdf, (Accessed 25 August 2009)

http://ezinearticles.com/?Challenges-in-Requirements-Elicitation&id=1901199, (Accessed 01 September 2009)

http://faculty.kfupm.edu.sa/ICS/elish/files/Chapter8_The_Challenge_of_Requirements_Elicitation.pdf, (Accessed 03 September 2009)

No comments:

Post a Comment