Examining The Importance Of Requirement Elicitation Information Technology Essay
Requirements elicitation is a process during which”analyst must interact with the stakeholders in many different types of elicitation sessions to draw out the user requirements for a project” (Tagbo, 2011).Hossenlopp and Hass, (2008) defined requirement elication as ” the process of gathering business requirements for a new business solution”. According to Hossenlopp and Hass, (2008), activities involved in requirement elicitation process are intended to draw out and acquire requirements for business soulutions from ” buisness experts”. Unlike Tagbo (2011),Hossenlopp and Hass (2008) definition is specific and confined confined the source information(business requirement) to business expert
Why is requirement elicitation important?
Requirement elicitation is a critical activity in the requirement development process. It discovers the requirements of stakeholders. This means it is where analyst identifies what the users or owners of the system to build want to see. The success or failure of this process is based on recognizing the relevant stakeholders and detecting and discovering their needs as well as the quality of requirements (Sajjad&Hanif, 2010). A study on requirement engineering conducted byDavis, Fuller, Tremblay, && Berndt, in 2006, found “accurately capturing system requirements is the major factor in the failure of 90% of large software projects”. Their conclusion was in line with earlier work by Lindquist (2005) who concluded “poor requirements management can be attributed to 71 percent of software projects that fail; greater than bad technology, missed deadlines, and change management issues”. An insight from these two conclusions is that requirement elicitation determines the success or failure of a project and proper requirement elicitation is prerequisite for project success and therefore, without complete, clear and consistent requirement project is doomed to failure.The cost of a failed project is an enormous expense to firms. A study by Browne and Rogich (2001) found that failed or abandoned systems cost $100 Billion in the USA alone in 2000. The cost of failed project is not limited to financial cost but has lasting consequences on the system during its lifespan.Fixing mistakes made at requirements elicitation stage accounts for 75 percent of all error removal costs (Urquhart, 2001). In the following figure we show the impact of invalid requirements on software development.
Figure 1: Requirement -software failure. Retrieved March 23, 2011, from: http://www.scarpedia.com/general/requirement-elicitation/
This figure shows the result of a study conducted by the Standish Group in 1995. In the study, 8000 software projects from 352 companies were studied. The study exposed that in more the 50% software project failures the reason lies somewhere in requirements (Requirement Engineering, 2010).
Types 0f requirement elicitation
Requirement elicitation is divided into; Greenfield engineering, R-engineering and interface engineering (Requirement Engineering, 2010). We first start with the description of Greenfield engineering followed the other two.
Greenfield Engineering: is requirement elicitation used when new system is to be built. No Preceding system exists so requirements are pull out from Client and End User. This type of engineering is reliant onUser needs (Requirement Engineering, 2010).
Re-Engineering: unlikeGreenfieldengineering, this type of requirement elicitation is used when a system exists. Existing system is re-design and re-implemented using a newer technology. It is technology oriented type (Requirement Engineering, 2010).
Interface Engineering: It is a type of requirement elicitation where the system and its functionality remain the same but the environment in which the system operates is modified. It is dependent on new market needs (Requirement Engineering, 2010).
Requirement Elicitation Challenges
This section of the paper deals with the underlying challenges to requirement elicitation. Three syndromes have been identified by Leffingwell and Widring, which posses challenge to requirement elicitation. These syndromes are the “Yes, But”, “Undiscovered Ruins”, and the “User and the Developer” syndrome. The earlier part of this section will be looking at these syndromes and the latter will give details to other challenges found in requirement elicitation.
The “Yes, But” syndrome
Stated by Leffingwell and Widring that, this kind of problem; stems from the natural reaction of users; when they get to see the final developed software product. In the initial implementation of the product, users are expected to accept the software as what they where hopping for, or have additional requirements for the product, for example when the users have their first interaction with the system they have that yes, but, wouldn’t be nice if… kind of comments which indicates that the system is not what they really expected.
“Undiscovered Ruins” syndrome
“In many ways, the search for requirement is like a search for undiscovered ruins: the more you find, the more you know remain” (Leffingwell & Widring, 2003, p. 64) Thus software developers struggle to determine when they are done with software elicitation. This makes it difficult for developers to determine when they have found all the requirement that are material.
“User and the Developer” syndrome
A big gap of communication exist between users and developers thus there’s a “user and the developer” syndrome. Leffingwell and Widring states that the syndrome arises since the users and the developers might be coming from different worlds, in terms of the languages they are speaking, the differences in their backgrounds, motivations and objectives.
Other Challenges to elicitation
The following are the challenges identified by Maté and Silva (2005), in requirement elicitation. These are:
The initial scope of the project is not sufficiently defined and such is open to interpretation and assumptions.
Stakeholders do not know what their real needs are and are therefore limited in their ability to support the investigation of the solution domain
Stakeholders do not understand or appreciate the needs of other stakeholders; users may only be concerned with those factors that affect them directly.
The analyst is unfamiliar with the problem or solution domain and does not understand the needs of the users and the processes to be addressed.
Requirements generated from stakeholders can be vague, lacking specifics, and not represented in such a way as can be measured or tested.
Only very limited guidelines and tool support exist for the process of equipments elicitation.Order Now