NEW
Font size
WorksheetsSystems Analysis Quiz
Total questions: 40
Worksheet time: 40mins
What is the first activity in the systems analysis process?
Gather detailed information.
Define requirements.
Prioritize requirements.
Develop user-interface dialogs.
Which activity involves talking to users to understand their needs?
Evaluate requirements with users.
Gather detailed information.
Design system components.
Identify the problem and obtain approval.
What is the purpose of defining requirements in systems analysis?
To understand what the system should do.
To build the system.
To test the system.
To gather information.
What is the last step in the core processes mentioned?
Complete systems tests.
Develop user-interface dialogs.
Plan and monitor the project.
Identify the problem and obtain approval.
What do systems analysts do to gather detailed information?
Read books
Interview people
Watch movies
Write reports
When are analysis activities most intensive during the system development life cycle?
First iteration
Second iteration
Third iteration
Last iteration
What is the purpose of organizing development activities in an iterative manner?
To make it more complicated
To break development into smaller steps
To finish faster
To avoid testing
What is the main reason for prioritizing system requirements?
To make the system more complex
To ensure all user requests are included
To justify the scope of the system
To reduce the number of users
What happens if an analyst does not carefully evaluate priorities?
The system becomes simpler
System requirements tend to expand
Users make fewer suggestions
The project has fewer iterations
What is 'scope creep' in the context of system requirements?
A method to reduce system size
A phenomenon where users make more suggestions
A way to prioritize user requests
A tool for developing user-interface dialogs
Why are high-priority requirements often incorporated into early project iterations?
To make the project longer
To allow analysts and users to refine parts of the system
To avoid user feedback
To reduce the number of iterations
What is one reason why users might be uncertain about system requirements?
They always know exactly what they want.
They find it difficult to interpret abstract models.
They never use diagrams.
They don't like new systems.
Why is user validation of a user interface considered simpler?
Users can see and feel the system.
It requires no user input.
It is done without any prototypes.
It is always done by analysts alone.
What can a prototype interface serve as in system development?
A final product
A requirement and starting point
A complete system
An unnecessary step
What is the purpose of evaluating requirements with users?
To ignore user input
To fully integrate and document requirements
To avoid using prototypes
To finalize the system without changes
What are system requirements?
Activities the system must perform or support
Colors of the system interface
Names of the system users
Locations where the system is used
What do functional requirements involve?
Activities the system must perform to support users' work
The color scheme of the system
The brand of the system hardware
The location of the system installation
What might users need help with when the system includes new technology?
Visualizing possibilities from the new technology
Choosing a name for the system
Deciding the color of the system
Selecting the system's location
What does the acronym FURPS stand for?
Functional, Usability, Reliability, Performance, Security
Fast, Useful, Reliable, Practical, Secure
Functional, Usable, Rapid, Performance, Safety
Flexible, Usability, Reliable, Performance, Secure
What are usability requirements related to?
Operational characteristics for users
System security
Performance speed
Data storage
What do reliability requirements describe?
System dependability
User interface design
Data storage capacity
System speed
What are functional requirements?
Activities the system must perform
Security measures
User interface designs
Data storage solutions
What does the "F" in FURPS stand for?
Functional
Funny
Fast
Friendly
What type of requirements describe the dependability of a system?
Usability requirements
Reliability requirements
Security requirements
Performance requirements
Which of the following is an example of a usability requirement?
Service outages
Two-finger slides
System security
Data processing
What does the acronym FURPS stand for?
Functional, Usability, Reliability, Performance, Security
Fast, Useful, Reliable, Practical, Secure
Flexible, Unique, Robust, Powerful, Safe
Friendly, Usable, Rapid, Precise, Strong
What is an extension of FURPS that includes design constraints?
FURPS+
FURPS-
FURPSX
FURPSY
Which of the following is a requirement category mentioned in the text?
Functional
Fictional
Fractional
Factual
What do performance requirements describe?
How fast a system responds and handles tasks
How colorful the user interface is
The number of users a system can have
The type of hardware used
What is an example of a security requirement?
Making the application colorful
Encrypting data with 1024-bit keys
Using a lot of memory
Having a fast response time
What does FURPS+ add to the original FURPS categories?
More colors
Additional categories like design constraints
Faster internet
More users
What is a design constraint for a cell phone application?
Using the Android operating system
Having a colorful screen
Allowing unlimited users
Using a lot of power
What do implementation requirements describe?
Constraints such as required programming languages and tools
Interactions among systems
Characteristics of hardware
How a system is installed and updated
What do interface requirements describe?
Interactions among systems
Constraints such as required programming languages
Characteristics of hardware
How a system is installed and updated
What do physical requirements describe?
Characteristics of hardware
Interactions among systems
Constraints such as required programming languages
How a system is installed and updated
What do supportability requirements describe?
How a system is installed, configured, monitored, and updated
Interactions among systems
Characteristics of hardware
Constraints such as required programming languages
What is the role of a systems analyst in the requirements gathering phase?
To deploy the system
To design the system architecture
To gather and document user requirements
To test the final system
Which of the following is a non-functional requirement?
System must allow data export to CSV
System must support 1000 concurrent users
System must allow users to reset passwords
System must generate monthly reports
What is the purpose of a feasibility study in system development?
To determine the system's performance speed
To test the system's security features
To assess the practicality of a proposed solution
To finalize the system's user interface design
"In the context of systems analysis, how does the iterative nature of requirements gathering and validation help mitigate the risks of scope creep, and what strategies can analysts employ to ensure high-priority requirements are addressed effectively in early iterations?"
By continuously refining requirements and incorporating user feedback, iterative development prevents scope creep, and analysts can use prioritization techniques such as MoSCoW (Must-have, Should-have, Could-have, Won’t-have) to ensure essential requirements are implemented first.
Iterative development allows analysts to gather all requirements upfront, preventing any changes later, while setting strict deadlines ensures that high-priority requirements are met first.
Scope creep is eliminated by restricting user involvement in the requirements process, and analysts can ensure high-priority features are included by focusing only on functional requirements.
Analysts prevent scope creep by avoiding requirement changes after the initial phase, and high-priority requirements are determined based on the complexity of implementation rather than business value.
