Methods of Identifying System Requirements

Only available on StudyMode
  • Download(s) : 802
  • Published : October 7, 2010
Open Document
Text Preview
Adzraku Setsoafia Edem
B020909031
BIT Level 200 morning
System Analysis & Design (ICT 231)

Five Methods for Identifying System Requirement and How They are Applied in any System Development Venture

System requirement are the specification that define the functions or performance to be provided by a system logically and physically. The objective of identifying the system requirement is to understand the business functions and develop a system with the necessary specification that will meet those functions. To develop any system the systems analyst needs to collect facts and all relevant information to identify or clarify what the organization wants out of the system to accomplish their objectives or goals.

For the success of any systems analyst in building a system to help an organization to accomplish its goals, is depended on the accuracy of available information in the development of that system, system requirement can be identified with the help of certain methods or techniques. These techniques use in the identification of system requirement are Interviews, Questionnaires, Observations, Reviews and Sampling. Interviews

This technique is used by the systems analyst to identify and understand the system requirement from groups and individuals of the organization. The analyst selects the groups and individuals who are related with the system for the interview. In this technique the systems analyst tries to find out how the current system works and the problems that the users perceive in the current system and what the users want from the new or upgrade system. These requirements that are identified through the interviews are accurate and reliable, as the analyst discover the area of misunderstanding, description of activities and problems faced by the current system. However, in interviews a list of specific and detailed questions are prepared and discussed continuously the system requirement is understood and documented by the systems analyst. Therefore for the systems analyst to conduct a good and effective interview, he/she needs to organize the interview in three parts i.e. Preparations for the interview, Conducting the interview and Following up the interview. For the preparation of the interview the systems analyst needs to: * Establish the goals and objectives for the interview

* Determine correct user(s) to be involved
* Prepare a list of questions and issues to be discussed
* Review related documents and material involved
* Inform all participant of objectives and goals about the interview During the interview the systems analyst needs to
* Look for exception and error conditions
* Probe for more specific details
* Take notes on very relevant information
* Identify and document unanswered open questions or items After the interview the systems analyst must
* Review notes for accuracy, understanding and completeness * Identify areas that need further clarification
* Transfer information to the appropriate document and models The advantage of this method is that, questions are more flexible and answers are easily clarified, which gains the confidence of the interviewee and may enhance the quality of information gathering. It’s disadvantage is that, it is time consuming and expensive, which may not be suitable for identifying the system requirement for large number of users Observations

This method involves examining procedures as they are carried out. The systems analyst observes how work and procedures are carried out in the existing system; this enables the analyst to witness first hand information of how the work is actually done and what is involved. See the system in action gives the analyst additional perspective and a better understanding of the system’s procedures. Personal observations also allow the analyst to verify statements made in interviews and determine whether procedures really operate as they are described.

These personal...
tracking img