Chapter 3 - Requirements Determination Flashcards
What questions are answered during the analysis phase of the SDLC?
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.
What goes on during the analysis phase of the SDLC?
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).
What is a requirement?
A requirement is a statement of what the system must do, or what characteristics it needs to have.
What is requirements determination, and why is it important?
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.
What are the five main categories of requirements?
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)
What is the difference between a functional and a non-functional requirement?
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.
What is a lesser-recognized aspect of requirements determination?
A lesser-recognized aspect of requirements determination is that of building political support and establishing trust.
What are the five commonly-used requirement-gathering techniques?
The five commonly-used requirement-gathering techniques are:
- Interviews
- JAD Sessions
- Questionnaires
- Document Analysis
- Observation
How does the interview process work as far as requirements-gathering?
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
Compare the roles of unstructured and structured interviews.
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).
Compare the roles of the top-down and bottom-up interview.
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.
What are some good ways to prepare for an interview?
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)
What are some good things to do during an interview?
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
What should be done as a part of a post-interview follow-up?
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.
What is Joint Application Development (JAD)?
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.
What are the primary jobs of the JAD facilitator?
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.
What is a questionnaire, and how is it used?
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
What is document analysis?
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.
How is observation used for requirement gathering?
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.
What is problem analysis?
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.
What is root cause analysis?
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.
What is duration analysis?
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.
What is process integration?
Process integration is when a process is changed so that fewer people work on the input.
What is activity-based costing?
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.
