ITSS 4330 Exam 2 | UPDATED Questions with 100%
Verified Answers
Q1: The systems development process transforms the existing (as
is) system into the _____
A: Proposed (to be) system
Q2: T/F: Requirements determination is the single most critical step
of the entire SDLC
A: True
Q3: T/F: Changes can not be made easily in the requirements
determination stage
A: False - changes can be made easily in this stage
Q4: T/F: Most (>50%) system failures are due to problems with
requirements
A: True
Q5: Purpose of Requirements Determination
A: to convert high level business requirements (from the system request) into detailed
requirements that can be used as inputs for creating models
Q6: What is a requirement?
A: a statement of what the system must do or a characteristic it must have
Q7: What does a requirement evolve into?
A: Will later evolve into a technical description of how the system will be implemented
Q8: Types of Requirements
A: 1) Functional
2) Nonfunctional
Q9: Functional Requirements
A: 1) Relates to a process or data (What?)
2) Ex: System should be able to report budget expenses, display details for a customer
account, & generate info for a shipment
Q10: Non-Functional Requirements
A: Relates to performance or usability (How?)
,Q11: Types of Non-Functional requirements
A: 1) Operational
2) Performance
3) Security
4) Cultural & Political
Q12: Examples of Operational Requirements
A: 1) The system should be able to fit in a pocket or purse
2) The system should be able to integrate with the existing inventory system
Q13: Examples of Performance Requirements
A: 1) Any interaction between the user & the system should not exceed 2 seconds
2) The system should receive updated inventory information every 15 minutes
Q14: Examples of Security Requirements
A: 1) Only direct managers can see personnel records of staff
2) Customers can see their order history only during business hours
Q15: Examples of Cultural & Political Requirements
A: 1) The system should be able to distinguish between US & European currency
2) The system shall comply with insurance industry standards
Q16: Requirements Definition
A: 1) Functional & non-functional requirements listed in outline format
2) May be prioritized
3) Provides info needed in subsequent workflows
4) Defines the scope of the system
Q17: Creating a Requirements Definition
A: 1) Determine the types of functional & non-functional requirements applicable to the
project
2) Use requirements-gathering techniques to collect details
3) Analysts work with users to verify, change, & prioritize each requirement
4) Continue this process through analysis workflow, but be careful of scope creep
5) Requirements that meet a need but are not within the current scope can be added to a
list of future enhancements
Q18: Problems in Requirements Determination
A: 1) Analyst may not have access to the correct users
2) Requirements specifications may be inadequate
3) Some requirements may not be known in the beginning
4) Verifying & validating requirements can be difficult
,Q19: Requirements Analysis
A: 1) Understand the as-is system
2) Identify improvements
3) Develop requirements for the to-be system
Q20: Requirements Analysis Approaches
A: 1) Problem analysis
2) Root cause analysis
3) Duration analysis
4) Activity-based costing
5) Informal benchmarking
6) Outcome analysis
7) Technology analysis
8) Activity elimination
Q21: Problem Analysis
A: 1) Asking the users/managers what the problems are with the existing system
2) Users often have helpful suggestions for improvement)
3) Easy to implement
Q22: Root Cause Analysis
A: 1) Determining the actual cause of the problem
2) Uses a fishbone diagram — starts with the problem & then considers potential root
causes
Q23: Duration Analysis
A: 1) Determining the total amount of time to complete a process and comparing that with
the amount of time to complete a subprocess
2) Helpful approach to see how a process can be improved
Q24: Activity-Based Costing
A: 1) Focus attention on the most costly steps
2) How can we make costly steps more efficient?
Q25: Informal Benchmarking
A: Determine how outside organizations are using processes that benefit them and try to
implement them in your organization
Q26: Outcome Analysis
A: 1) What's the final outcome the customer is looking for?
2) How can we reengineer the process to make sure the customer gets what they want?
Q27: Technology Analysis
, A: Analysts make a list of popular/new pieces of technology that can provide value to the
company
Q28: Activity Elimination
A: !) What happens if we eliminate certain substeps?
2) How can we pull this process apart & eliminate any unnecessary steps?
Q29: Purpose of Requirements Gathering Techniques
A: 1) Used to uncover all requirements (those uncovered late in the process are more
difficult to incorporate)
2) Build support & trust among users
Q30: Types of Requirements Gathering Techniques
A: 1) Interviews
2) Questionnaires
3) Observation
4) Document Analysis
Q31: T/F: Interviews are the most popular requirements gathering
technique
A: True
Q32: Interview Process
A: 1) Select people to interview & create a schedule
2) Design interview questions (open-ended, close-ended, & probing questions)
3) Prepare for the interview (unstructured vs. structured)
4) Conduct the interview (top-down vs. bottom-up)
5) Follow-up after the interview
Q33: Examples of Closed-Ended Questions
A: 1) How many telephone orders are received per day?
2) How do customers place orders?
3) What information is missing from the monthly sales report?
Q34: Examples of Open-Ended Questions
A: 1) What do you think about the current system?
2) What are some of the problems you face on a daily basis?
3) What are some the improvements you would like to see in a new system?
Q35: Examples of Probing Questions
A: 1) Why?
2) Can you give me an example?
3) Can you explain that in a bit more detail?
Verified Answers
Q1: The systems development process transforms the existing (as
is) system into the _____
A: Proposed (to be) system
Q2: T/F: Requirements determination is the single most critical step
of the entire SDLC
A: True
Q3: T/F: Changes can not be made easily in the requirements
determination stage
A: False - changes can be made easily in this stage
Q4: T/F: Most (>50%) system failures are due to problems with
requirements
A: True
Q5: Purpose of Requirements Determination
A: to convert high level business requirements (from the system request) into detailed
requirements that can be used as inputs for creating models
Q6: What is a requirement?
A: a statement of what the system must do or a characteristic it must have
Q7: What does a requirement evolve into?
A: Will later evolve into a technical description of how the system will be implemented
Q8: Types of Requirements
A: 1) Functional
2) Nonfunctional
Q9: Functional Requirements
A: 1) Relates to a process or data (What?)
2) Ex: System should be able to report budget expenses, display details for a customer
account, & generate info for a shipment
Q10: Non-Functional Requirements
A: Relates to performance or usability (How?)
,Q11: Types of Non-Functional requirements
A: 1) Operational
2) Performance
3) Security
4) Cultural & Political
Q12: Examples of Operational Requirements
A: 1) The system should be able to fit in a pocket or purse
2) The system should be able to integrate with the existing inventory system
Q13: Examples of Performance Requirements
A: 1) Any interaction between the user & the system should not exceed 2 seconds
2) The system should receive updated inventory information every 15 minutes
Q14: Examples of Security Requirements
A: 1) Only direct managers can see personnel records of staff
2) Customers can see their order history only during business hours
Q15: Examples of Cultural & Political Requirements
A: 1) The system should be able to distinguish between US & European currency
2) The system shall comply with insurance industry standards
Q16: Requirements Definition
A: 1) Functional & non-functional requirements listed in outline format
2) May be prioritized
3) Provides info needed in subsequent workflows
4) Defines the scope of the system
Q17: Creating a Requirements Definition
A: 1) Determine the types of functional & non-functional requirements applicable to the
project
2) Use requirements-gathering techniques to collect details
3) Analysts work with users to verify, change, & prioritize each requirement
4) Continue this process through analysis workflow, but be careful of scope creep
5) Requirements that meet a need but are not within the current scope can be added to a
list of future enhancements
Q18: Problems in Requirements Determination
A: 1) Analyst may not have access to the correct users
2) Requirements specifications may be inadequate
3) Some requirements may not be known in the beginning
4) Verifying & validating requirements can be difficult
,Q19: Requirements Analysis
A: 1) Understand the as-is system
2) Identify improvements
3) Develop requirements for the to-be system
Q20: Requirements Analysis Approaches
A: 1) Problem analysis
2) Root cause analysis
3) Duration analysis
4) Activity-based costing
5) Informal benchmarking
6) Outcome analysis
7) Technology analysis
8) Activity elimination
Q21: Problem Analysis
A: 1) Asking the users/managers what the problems are with the existing system
2) Users often have helpful suggestions for improvement)
3) Easy to implement
Q22: Root Cause Analysis
A: 1) Determining the actual cause of the problem
2) Uses a fishbone diagram — starts with the problem & then considers potential root
causes
Q23: Duration Analysis
A: 1) Determining the total amount of time to complete a process and comparing that with
the amount of time to complete a subprocess
2) Helpful approach to see how a process can be improved
Q24: Activity-Based Costing
A: 1) Focus attention on the most costly steps
2) How can we make costly steps more efficient?
Q25: Informal Benchmarking
A: Determine how outside organizations are using processes that benefit them and try to
implement them in your organization
Q26: Outcome Analysis
A: 1) What's the final outcome the customer is looking for?
2) How can we reengineer the process to make sure the customer gets what they want?
Q27: Technology Analysis
, A: Analysts make a list of popular/new pieces of technology that can provide value to the
company
Q28: Activity Elimination
A: !) What happens if we eliminate certain substeps?
2) How can we pull this process apart & eliminate any unnecessary steps?
Q29: Purpose of Requirements Gathering Techniques
A: 1) Used to uncover all requirements (those uncovered late in the process are more
difficult to incorporate)
2) Build support & trust among users
Q30: Types of Requirements Gathering Techniques
A: 1) Interviews
2) Questionnaires
3) Observation
4) Document Analysis
Q31: T/F: Interviews are the most popular requirements gathering
technique
A: True
Q32: Interview Process
A: 1) Select people to interview & create a schedule
2) Design interview questions (open-ended, close-ended, & probing questions)
3) Prepare for the interview (unstructured vs. structured)
4) Conduct the interview (top-down vs. bottom-up)
5) Follow-up after the interview
Q33: Examples of Closed-Ended Questions
A: 1) How many telephone orders are received per day?
2) How do customers place orders?
3) What information is missing from the monthly sales report?
Q34: Examples of Open-Ended Questions
A: 1) What do you think about the current system?
2) What are some of the problems you face on a daily basis?
3) What are some the improvements you would like to see in a new system?
Q35: Examples of Probing Questions
A: 1) Why?
2) Can you give me an example?
3) Can you explain that in a bit more detail?
