Table of contents

1. Requirement Elicitation: Key Elements

2. What is a Requirement?

2.1. User Requirements

2.2. Functional Requirements

2.2.1. Process oriented

2.2.2. Information oriented

2.3. Nonfunctional Requirements

2.4. Requirements definition report

2.5. Requirement Definition example

3. Interviews

3.1. Interview Structure

3.1.1. Top-Down

3.1.2. Bottom-up (specific to broad; useful for collecting details)

3.2. Advantages

3.3. Disadvantages

3.4. Question Types

3.4.1. Open-Ended Questions

3.4.1.1. Example

3.4.1.2. Advantages

3.4.1.3. Disadvantages

3.4.2. Closed Interview Questions

3.4.2.1. Example

3.4.2.2. Advantages

3.4.2.3. Disadvantages

3.4.3. Probing questions

3.4.3.1. Example

4. Questionnaires

4.1. Designing the Questionnaire

4.2. Order of Questions

4.3. Advantages

4.4. Disadvantages

4.5. Questionnaires Types

4.5.1. Fixed-format questions

4.5.2. Free-format questions

4.6. Questionnaire Language

5. Document Analysis

6. Observation

7. Requirements freezing

8. Summary

Interviews

Questionnaire

Document Analysis

Observation

Type of Information

As-Is

Improve To-be

As-Is

As-Is

As-Is

Depth of Information

High

Medium

Low

Low

Breadth of Information

Low

High

High

Low

User involvement

Medium

Low

Low

Low

Cost

Medium

Low

Low

Low-Medium

1. Requirement Elicitation: Key Elements

  1. The main users of the system
  2. The functionalities carried-out or operated by each and everyone of the users
  3. The data required by each user activities and the results generated by the same
  4. All the requirements of the system

2. What is a Requirement?

  1. A statement of what the system must do; or
  2. A statement of characteristics the system must have
  3. Types of requirements:

-> what the users need to do (user requirements);

-> what the software should do (functional requirements);

-> characteristics the system should have (nonfunctional requirements); and

-> how the system should be built (system requirements).

2.1. User Requirements

  1. What the user needs to do to complete a needed job or task
  2. Focus on user tasks that are integral to business operations
  3. Understanding user tasks helps reveal ways that the new system can support those tasks

2.2. Functional Requirements

  1. A process the system should perform as a part of supporting a user task, or
  2. Information the system should provide as the user performs a task
  3. Specify the support the system will provide to the user in fulfilling his/her work tasks

2.2.1. Process oriented

  1. A process the system must perform or a process the system must do.
  2. Checking available inventory before completing an order
  3. Users should be able to login to the system

2.2.2. Information oriented

  1. information the system must contain
  2. All the sales details should be stored for  months
  3. All customer details should be maintained

2.3. Nonfunctional Requirements

behavioral properties the system must have

  1. Operational – physical and technical operating environment
  2. Performance – speed, capacity, and reliability needs
  3. Security – access restrictions, needed safeguards
  4. Cultural and political – issues that will affect the final system

2.4. Requirements definition report

  1. Text document listing requirements in outline form

2.5. Requirement Definition example

FR1: Search for a product using the product name

Input: The product name

Process:

1.The user enter the product name on the search bar

2.The user clicks the search button

3.The system reads the name entered by the user

4.The system search all the available products with the name entered by the user

5.Format and display the available products to the user

Output: the list of matching products

3. Interviews

  1. Most important and most used fact-finding technique
  2. The systems analysts collects information from individuals face to face
  3. Type of interviews

1.One-to-one interviews

2.Group interviews

  1. Who should be interviewed?

-> Managers in early project stages to get broad understanding

-> Staff can provide details and specifics later.

-> Political issues are important – may be necessary to interview influential people, even if they are not too knowledgeable

3.1. Interview Structure

3.1.1. Top-Down

  1. Begins with generalized, open-ended questions
  2. Concludes by narrowing the possible responses using closed questions
  3. Provides an easy, non-threatening way to begin an interview

3.1.2. Bottom-up (specific to broad; useful for collecting details)

  1. Begins with very detailed, often closed questions
  2. Expands by allowing open-ended questions and more generalized responses
  3. Is useful if interviewees need to be warmed up to the topic or seem reluctant to address the topic

3.2. Advantages

  1. Interviewee can respond freely and openly to questions.
  2. Interviewee can be asked for more feedback.        
  3. Questions can be adapted or reworded for each individual.        
  4. Interviewee’s nonverbal communication can be observed.

3.3. Disadvantages

  1. Very time-consuming, and therefore costly, fact-finding approach.
  2. Success is highly dependent on the systems analyst's human relations skills.        
  3. May be impractical due to the location of interviewees.

3.4. Question Types

  1. Open-ended
  2. Closed
  3. probing

3.4.1. Open-Ended Questions

  1. Open-ended interview questions allow interviewees to respond how they wish, and to what length they wish
  2. Open-ended interview questions are appropriate when the analyst is interested in breadth and depth of reply

3.4.1.1. Example

  1. What do you think about the current system?
  2. What are some of the problems you face on a daily basis?
  3. How do you decide what types of marketing campaign to run?

3.4.1.2. Advantages

  1. Puts the interviewee at ease
  2. Allows the interviewer to pick up on the interviewee's vocabulary
  3. Provides richness of detail
  4. Reveals avenues of further questioning that may have gone untapped
  5. Provides more interest for the interviewee
  6. Allows more spontaneity
  7. Useful if the interviewer is unprepared

3.4.1.3. Disadvantages

  1. May result in too much irrelevant detail
  2. Possibly losing control of the interview
  3. May take too much time for the amount of useful information gained
  4. Potentially seeming that the interviewer is unprepared
  5. Possibly giving the impression that the interviewer is on a "fishing expedition”

3.4.2. Closed Interview Questions

  1. Closed interview questions limit the number of possible responses
  2. Closed interview questions are appropriate for generating precise, reliable data that is easy to analyze
  3. The methodology is efficient, and it requires little skill for interviewers to administer

3.4.2.1. Example

  1. How many  telephone orders are received per day?
  2. How do customers place orders?
  3. What additional information would you like the new system to provide?

3.4.2.2. Advantages

  1. Saving interview time
  2. Easily comparing interviews
  3. Getting to the point
  4. Keeping control of the interview
  5. Getting to relevant data

3.4.2.3. Disadvantages

  1. Boring for the interviewee
  2. Failure to obtain rich detailing
  3. Missing main ideas
  4. Failing to build rapport between interviewer and interviewee

3.4.3. Probing questions

  1. Probing questions elicit more detail about previous questions
  2. The purpose of probing questions is:

-> To get more meaning

-> To clarify

-> To draw out and expand on the interviewee's point

  1. May be either open-ended or closed

3.4.3.1. Example

  1. Why?
  2. Can you give me an example?
  3. Can you explain that in a bit more detail?

4. Questionnaires

  1. special-purpose documents that allow the analyst to collect information and opinions from respondents.

-> Mass produced and distributed.

-> Respondents complete the questionnaire on their own time.

  1. Facts are collected from a large number of people while maintaining uniform responses.

-> When dealing with a large audience, no other fact-finding technique can tabulate the same facts as efficiently.

4.1. Designing the Questionnaire

  1. Allow ample white space
  2. Allow ample space to write or type in responses
  3. Make it easy for respondents to clearly mark their answers
  4. Be consistent in style

4.2. Order of Questions

  1. Place most important questions first
  2. Cluster items of similar content together
  3. Introduce less controversial questions first

4.3. Advantages

  1. Most can be answered quickly (if properly designed).
  2. Relatively inexpensive.
  3. Allow individuals to maintain anonymity.
  4. Can be tabulated and analyzed quickly (if properly designed)

4.4. Disadvantages

  1. Response is often low.  How to motivate participation?        
  2. Incomplete questionnaires returned – are these worthless?
  3. Tend to be inflexible.
  4. Body language cannot be observed.        
  5. Cannot clarify a vague or incomplete answer to any question.        
  6. Difficult to prepare a successful questionnaire.

4.5. Questionnaires Types

4.5.1. Fixed-format questions

  1. Similar to a multiple choice exam question
  2. Must be able to anticipate potential answers to questions
  3. Easy to tabulate results

4.5.2. Free-format questions

  1. Like an essay question – open-ended
  2. Response is unpredictable
  3. Harder to tabulate results

4.6. Questionnaire Language

  1. Simple
  2. Specific
  3. Short
  4. Free of bias
  5. Addressed to those who are knowledgeable
  6. Technically accurate

5. Document Analysis

  1. Provides clues about existing “as-is” system
  2. Typical documents

-> Forms

-> Reports

-> Policy manuals

  1. Look for user additions to forms
  2. Look for unused form elements

6. Observation

  • Is the act of watching processes being performed, is a powerful tool to gain insight into the as-is system.
  • Users/managers often don’t remember everything they do
  • Checks validity of information gathered other ways
  • Behaviors change when people are watched
  • Careful not to ignore periodic activities

-> Weekly … Monthly … Annual

7. Requirements freezing

  1. The client requirements can change form time to time
  2. The client may request changes very late leading to Scope creep.

-> Scope creep - adding new requirements to the project after the system design has been finalized

  1. Some requirements may be difficult to be incorporated
  2. Hence “Freeze the requirements”

8. Summary

  1. There are five major information gathering techniques that all systems analysts must be able to use: Interviews, Questionnaires, Document Analysis, and Observation.
  2. Systems analysts must also know how and when to use each as well as how to combine methods.