Pre-Test for Systems Analysis and Design Training
Quiz by MCWD Training
Feel free to use or edit a copy
includes Teacher and Student dashboards
Measure skillsfrom any curriculum
Tag the questions with any skills you have. Your dashboard will track each student's mastery of each skill.
- edit the questions
- save a copy for later
- start a class game
- automatically assign follow-up activities based on students’ scores
- assign as homework
- share a link with colleagues
- print as a bubble sheet
- Q1
An investigation is a way of handling the user’s request to change, improve or enhance an existing system. What development stages does this statement belong?
Maintenance
Analysis
Implementation
Testing
Planning
20s - Q2
This is a detailed study of the various operations of business activity (system), along with its boundaries. The objective of this phase is to determine exactly what must be done to solve the problem. Many system analysts have a technical background.
Analysis phase
Planning phase
Testing phase
Maintenance phase
Implementation phase
20s - Q3
This phase specifies HOW the system will accomplish this objective. This refers to the technical specification that will be implied in constructing the system.
System Design
System Planning
Testing Phase
Implementation Phase
20s - Q4
In this phase, the real work begins, a programmer, network engineer, and/or database developer are brought on to do the major work on the project. This work includes using a flow chart to ensure that the process of the system is properly organized.
Testing phase
Integration phase
Development phase
Implementation phase
30s - Q5
This is a way to summarize details of a system and the users within that system. It is generally shown as a graphic depiction of interactions among different elements in a system.
entity relationship diagram
sequence diagram
use case diagram
unified modelling language
20s - Q6
This is type of requirement elicitation technique used to construct a hierarchy of the tasks performed by the users and the system, and determine the knowledge used or required to carry them out.
domain analysis
task analysis
repertory
laddering
20s - Q7
What is the main purpose of encapsulation in OOP?
Method overloading
Data hiding and protection
Code organization
Code reusability
20s - Q8
What is a constructor in OOP?
A method that overloads other methods
A special method to initialize object properties
A method that is static and cannot be overridden
A method used for method chaining
20s - Q9
What is polymorphism in OOP?
The ability to have multiple methods with the same name in a class
The ability of objects to take on multiple forms
The ability to perform different operations on the same data
The ability to have multiple classes with the same name
20s - Q10
10.Which OOP principle is violated if a subclass method has a lower visibility (e.g., private) than the corresponding superclass method it overrides?
Polymorphism
Inheritance
Abstraction
Encapsulation
20s - Q11
According to the Agile Manifesto, which of the following is valued more than comprehensive documentation?
Project plans
Contract negotiation
Working software
Comprehensive documentation
20s - Q12
What does the Agile Manifesto prioritize when it mentions "Individuals and interactions over processes and tools"?
Processes and tools are more important
Individuals and interactions are more important
Both are equally important
There is no preference mentioned
30s - Q13
According to the Agile Manifesto, what is the primary measure of progress?
Contract negotiation
Project plans
Working software
Comprehensive documentation
20s - Q14
In the Agile Manifesto, what is the emphasis when it states, "Customer collaboration over contract negotiation"?
Contract negotiation is more important
Both are equally important
No preference is mentioned
Customer collaboration is more important
30s - Q15
Which Agile principle emphasizes face-to-face communication as the most efficient and effective method of conveying information?
Responding to change over following a plan
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Individuals and interactions over processes and tools
30s