These System Analysis multiple-choice questions and their answers will help you strengthen your grip on the subject of System Analysis. You can prepare for an upcoming exam or job interview with these System Analysis MCQs.
So scroll down and start answering.
A. Design
B. Analysis
C. Development
D. Problem/Opportunity Identification
A. Interview
B. Record reviews
C. Questionnaire
D. Third party enquiry
A. The twelve same decisions are marked "Don't Cares"
B. Conditions Y and Z are redundant and are removed
C. Those four columns can be combined into one
D. Condition X is redundant and is removed
A. Not as good for many of the new types of interactive and highly complex applications
B. Fairly rigid approach
C. Can easily go back to previous phases
D. Good for traditional type of projects
A. Most-Likely Time
B. Pessimistic Time
C. Expected Time
D. Optimistic Time
A. Performance
B. Outputs
C. User Interfaces
D. Inputs
A. Data Element
B. Data Store
C. Data Sink
D. Data Source
A. Unit testing, module testing, integration testing, system testing, acceptance testing
B. Unit testing, system testing, module testing, integration testing, acceptance testing
C. Unit testing, integration testing, system testing, module testing, acceptance testing
D. Unit testing, volume testing, integration testing, system testing, acceptance testing
A. Actor
B. Use case
C. Component
D. Class
A. Use Case Diagram
B. Requirements specifications
C. Design specification
D. Interfaces
A. Very Large Data
B. Meaningful data
C. Data about data
D. Data dictionary
A. Storage
B. Input
C. Output
D. Processing
A. Design Report
B. Feasibility Study
C. Design Specification
D. Systems Analysis
A. Destination
B. Source
C. Data Flow
D. Data Store
A. White Box Testing
B. Grey Box Testing
C. Blue Box Testing
D. Black Box Testing
A. Decision Flow Diagram
B. Decision Feauture Diagram
C. Data Finding Diagram
D. Data Flow Diagram
A. State
B. Instance
C. Behavior
D. Class
A. Macros
B. Subroutines
C. Routines
D. Code
A. Structured Analysis
B. Agile Methodology
C. Iterative Prototyping
D. Joint Application Design
A. The org chart
B. What processes will be used
C. Who generates data and who processes it
D. The attributes of the data generated
A. These are bound at runtime
B. These may be inherited
C. These are defined in protocols
D. These are pre-defined
A. Data Flow
B. Source
C. Destination
D. Data Store
A. Collaboration diagram
B. Activity diagram
C. Sequence diagram
D. State diagram
A. Enhances understanding of what the system must accomplish
B. Provides rapid feedback from user
C. Helps validate requirements with fewer errors
D. It automates System testing
A. Receipt Printer
B. Cash Tray
C. Transaction Roll
D. Security Camera
A. A first responder
B. An abstract class
C. A base class
D. A nullity class
A. Communication Diagram
B. Package Diagram
C. Timing Diagram
D. Sequence Diagram
A. Expanding a process into several sub processes with greater detail
B. Splitting the DFD into different levels
C. Making the DFD symmetric
D. Summarize the DFD down to it's essential components
A. Decision Table
B. Structured Chart
C. Decision Tree
D. Data Flow Diagram
A. #
B. &
C. @
D. 0%
A. nodes and branches
B. Segmented DFD
C. consequences of various depicted alternates
D. pictorial depiction of alternate conditions
A. Prototyping
B. Spiral method
C. Rapid application development
D. Structured analysis development
A. State diagrams
B. Structure diagrams
C. Routing diagrams
D. Network diagrams
A. Level 2 diagram
B. Level n diagram
C. Level 0 diagram
D. Level 1 diagram
A. Non-Ambiguousness
B. Predictability
C. Completeness
D. Verifiability
A. Continuous Data
B. Output Data
C. Input Data
D. Context Data
A. consistency guideline
B. completeness guideline
C. timing guideline
D. iterative development guideline
A. Customer
B. Book
C. Notifications Server
D. iPhone
A. Backward-from-Requirements
B. Forward-from-Requirements
C. Backward-to-Requirements
D. Forward-to-Requirements
A. Warehouse Storage System
B. Stamp Collection System
C. Books Cataloguing System
D. Factory Order-Processing System
A. A use case is a scenario for understanding the requirements
B. It is an interaction between the users and the system
C. It captures the responsibility of the system to its users
D. It represents the flow of activities of various processes in the system.
A. Diamonds
B. Circles
C. Rectangles
D. Ellipses
A. An aggregation
B. An extend
C. An include
D. A generalization
A. Physical Model
B. Data Model
C. Process Model
D. Logical Model
A. Interface descriptions, data model, context diagram, class diagram
B. Project scope, use cases, interface descriptions, context diagram
C. Project scope, use cases, class diagram, context diagram
D. Use cases, interface descriptions, class diagram, project scope
A. A Sports Statistics System
B. An Elevator Control System
C. A Payroll System
D. An Employee Management System
A. This is a "Don't Care" combination
B. If implemented the toy will malfunction
C. The Systems Analyst has made an error
D. The corresponding Action/Response cells are 'Impossible'
A. A design pattern conforming to CBA
B. A self-contained collaborating set of objects
C. An object that fully implements all methods/member functions
D. An App
A. Key-Value Pairs
B. Linked Lists
C. Algorithms
D. Use Cases
A. Can have an abstract actor
B. Should have two actors
C. Cannot be drawn
D. Will have a disjunction symbol