Chapter 3 - Requirements Determination

Question 1

What questions are answered during the analysis phase of the SDLC?

Answer 1

During the analysis phase of the SDLC, the questions of WHO will use the system, WHAT the system will do, WHERE and WHEN it will be used are all answered.

Question 2

What goes on during the analysis phase of the SDLC?

Answer 2

During the analysis phase, the project team investigates the current system (as-is system), identifies any room for improvement, and develops a concept for the new system (to-be system).

Question 3

What is a requirement?

Answer 3

A requirement is a statement of what the system must do, or what characteristics it needs to have.

Question 4

What is requirements determination, and why is it important?

Answer 4

Requirements determination is the process of transforming the system request’s high-level statement of business requirements into more detailed, precise list of what the new system must do. It is important, because these requirements are what ensures that the new system will actually provide the expected value to the business.

Question 5

What are the five main categories of requirements?

Answer 5

The main categories of requirements are:

• Business requirements (what the business needs)
• User requirements (what the users need to do)
• Functional requirements (what the software should do)
• Non-Functional requirements (characteristics the system should have)
• System requirements (how the system should be built)

Question 6

What is the difference between a functional and a non-functional requirement?

Answer 6

The difference between a functional and a non-functional requirement is that a functional requirement is about a something the system must be able to do, a non-functional requirement is about an attribute or capability the system must have.

Question 7

What is a lesser-recognized aspect of requirements determination?

Answer 7

A lesser-recognized aspect of requirements determination is that of building political support and establishing trust.

Question 8

What are the five commonly-used requirement-gathering techniques?

Answer 8

The five commonly-used requirement-gathering techniques are:

• Interviews
• JAD Sessions
• Questionnaires
• Document Analysis
• Observation

Question 9

How does the interview process work as far as requirements-gathering?

Answer 9

The interview, which is by far the most common requirements-gathering technique, goes through several common steps:

• Select Interviewees (key stakeholders, including users, managers, project project sponsor, etc)
• Design Questions (choosing between open-ended, closed ended, and probing questions)
• Preparation
• Conducting the Interview
• Post-Interview Follow-Up

Question 10

Compare the roles of unstructured and structured interviews.

Answer 10

An unstructured interview is one that uses primarily open-ended questions, trying to gather a broad and roughly defined set of information. This is generally followed by structured interviews, which ask specific sets of closed-ended questions, trying to narrow down specific pieces of information).

Question 11

Compare the roles of the top-down and bottom-up interview.

Answer 11

A top-down interview begins with very high-level (i.e. broad) questions, and narrows in focus to more specific questions. A bottom-up interview begins with specific questions, and broadens the scope. Generally, the top-down approach is usable, but bottom-up can be useful if most general information is known, or if the interviewee doesn’t feel comfortable answering broad questions.

Question 12

What are some good ways to prepare for an interview?

Answer 12

Some good ways to prepare for an interview are to:

• Prepare a general interview plan
• Confirm areas of knowledge (don’t ask questions the interviewee cannot answer)
• Prioritize questions in case of time shortages
• Prepare the interviewee (send a schedule, reason for the interview, and areas that they will be asked about beforehand)

Question 13

What are some good things to do during an interview?

Answer 13

Some good tips to follow during an interview are to:

• Appear professional and unbiased
• Record all information given
• Understand all the issues being discussed
• Divide facts from opinions
• Allow the interviewee to ask questions
• Explain the follow-up process

Question 14

What should be done as a part of a post-interview follow-up?

Answer 14

The post-interview follow-up should include an interview report. This report should have notes on the interview, and the interviewee should be requested to review them and provide any clarification or updates that they might think is appropriate.

Question 15

What is Joint Application Development (JAD)?

Answer 15

Joint Application Development is an information gathering technique that works with the project team, users, and management all at one time to identify system requirements. It can reduce scope creep by as much as 50%, but requires a JAD facilitator. Sessions can go anywhere from half a day to several weeks.

Question 16

What are the primary jobs of the JAD facilitator?

Answer 16

A JAD facilitator is responsible for keeping each JAD session on track and following the agenda, for ensuring the group understands all technical terms and jargon, and to record the group’s input on a public display. The facilitator must remain neutral through the entire process.

Question 17

What is a questionnaire, and how is it used?

Answer 17

A questionnaire is a set of written questions for obtaining information from individuals. The process for using questionnaires for requirements gathering are:

• Selecting participants
• Designing the questionnaire
• Administering the questionnaire
• Questionnaire follow-up

Question 18

What is document analysis?

Answer 18

Document analysis is a method for requirements gathering, by reviewing what documentation exists for the as-is system, and noting what differences there are between what’s documented (known as the “formal system”) and what is (known as the “informal system”). Often, this gives a very solid indication of what needs to be changed.

Question 19

How is observation used for requirement gathering?

Answer 19

Observation is done by maintaining a low profile, and simply observing the normal day-to-day routine involved in the processes being studied. This generally supplements formal interviews.

Question 20

What is problem analysis?

Answer 20

Problem analysis is the most straightforward of the methods of requirements analysis. It involves asking users and managers to identify problems with the as-is system, and suggest solutions in the to-be system.

Question 21

What is root cause analysis?

Answer 21

Root cause analysis is a form of requirements analysis, focusing on resolving the root cause of a problem, that is, what’s actually causing the issue, and not just addressing the symptoms of the issue.

Question 22

What is duration analysis?

Answer 22

Duration analysis is a form of requirements analysis, wherein the steps of a process are timed, and compared to how long the process takes to complete in total. There is often a large disparity there, generally because multiple people work on different steps.

Question 23

What is process integration?

Answer 23

Process integration is when a process is changed so that fewer people work on the input.

Question 24

What is activity-based costing?

Answer 24

Activity-based costing is a form of requirements analysis is when the cost of each major process or step in a business process is examined, as opposed to the time taken. This allows for improvement to be focused on the most costly steps or processes.

Question 25

What is informal benchmarking?

Answer 25

Informal benchmarking is a form of requirements analysis, wherein a process that is performed by the as-is system is sought out elsewhere, either within the business or in other businesses, to see how it is performed. This allows for comparisons to be made as to the as-is system’s efficiency.

Question 26

What is outcome analysis?

Answer 26

Outcome analysis is a form of requirements analysis that focuses on understanding what outcomes provide value to customers. The focus on the customer perspective, and their ultimate outcome of using the system. People don’t want a paperclip, they want their papers to stay together.

Question 27

What is technology analysis?

Answer 27

Technology analysis is a form of requirements analysis that begins with analysts and managers come up with a list of interesting technologies, and then attempts to find uses for them that would benefit the business.

Question 28

What is activity elimination?

Answer 28

Activity elimination is a form of requirements analysis where analysts and managers work to see if they can find a way to eliminate each and every business process, and how the functions those processes support could continue without them, and what effects might occur.