{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}


requirements%20analysis%20research%20paper - Griffith 1...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Griffith 1 Abina Griffith Professor Krudys IST 352 27 November 2006 Requirements Analysis in Software Development Requirements analysis plays a crucial role throughout the software development process. This paper will thoroughly examine the role of requirements analysis, four traditional approaches to requirements analysis that an analyst may use and comparing and contrasting these approaches. In addition, I will discuss some new approaches to requirements analysis that are currently becoming more commonly used by analysts. After providing this in depth information of requirements analysis in software development, I will briefly summarize what I’ve learned. Requirements analysis is “the process of analyzing the information needs of the end users, the organizational environment, and any system presently being used, developing the functional requirements of a system that can meet the needs of the end users” ( www.gates.comm.virginia.edu/rrn2n/teaching/sdlc.htm ). These requirements are then documented in various forms such as email, executable prototypes or documents and are often referred to throughout the software development process. Meaning software analysts are using these documents as guidelines in order to meet end user requirements and needs. The software must entail efficient features such as reliability, feasibility and speed. In addition analysts need to determine whether too much of the system’s resources are being utilized in order for it to function properly. These micro features are essential in enabling end users to use the software feasibly which would include the software performing an assigned task. Though meeting the end
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Griffith 2 users needs is vital in developing sufficient software that is compatible with a system, there have been many problems using requirements analysis. Though requirements analysis is a process that facilitates software analysts designing sufficient software for end users, there have been numerous problems creating software that is compatible with future systems. According to Tom DeMarco, he states in his journal “numerous studies have shown that over half of the software development projects don’t work.” ( http://jiludwig.com/HCI_Journal_article.html ) In other words, when end users are using the software, it is not meeting their functionality expectations. This is due to information not being properly clarified. This is referred to as the requirements elicitation process, which means there is difficulty obtaining information for requirements out of the end users. When end users are asked about the kind of processes they would like the software to perform, they are able to identify their wants but not their needs. Though software analysts are verbally asking direct questions to the end users and are written down as a guideline for analysts to follow, these requests made by the users are not being automated. Therefore, when software analysts are developing software for future systems, it will never meet the users needs due to them not accurately stating what they need. Though analysts may follow the requirements elicitation
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}