CS Free MCQ Bank

[ Option D ]

A questionnaire is a fact-finding technique where the analyst prepares a set of structured questions and distributes them to many users. Because users can fill them out independently, this technique allows analysts to:

• Collect data from a large number of people.
• Gather information quickly.
• Reach people who may not be available for interviews.
• Standardize responses for easier comparison.

This is why questionnaires are preferred when the analyst needs large-scale data collection in less time.

[ Option B ]

Functional requirements define system behavior and the specific operations the system performs.

[ Option D ]

During the requirements analysis phase of software engineering, the main goal is to understand what the system should do, not how it will be built. The requirements analysis focuses on describing the system in terms of information, functions, and behavior.

1. The Information Domain deals with the data that the system must handle, such as what information is input, stored, processed, and output.
2. The Functional Domain specifies the operations or functions the software must perform,  describing what services or features are required by the user.
3. The Behavioral Domain explains how the system behaves in response to external events or user interactions, often represented using state diagrams or sequence diagrams.

However, the Architectural Domain is not part of the requirements model. It comes later in the design phase, where the system overall structure and organization are defined.

[ Option D ]

The System Requirements Specification (SRS) document is prepared by the System Analyst at the end of the Systems Requirement Analysis phase of the System Development Life Cycle (SDLC). This phase involves:

• Gathering and analyzing user requirements.
• Understanding functional and non-functional needs.
• Documenting what the system should do.

[ Option B ]

A DFD visually depicts the flow of data within a system, including sources, processes, and data stores.

[ Option D ]

Operational Feasibility assesses whether the proposed system can be effectively used by the employees and integrated into the existing organizational environment. It examines how well the solution satisfies the identified requirements, problem-solving ability, user acceptance, and operational workflow compatibility.

[ Option C ]

The Software Requirements Specification (SRS) document is also known as the black box specification. It describes the what of the system, i.e., the functionality and requirements without detailing the internal workings or implementation (hence, "black box").

[ Option D ]

The document that contains the user system requirements is the SRS (Software Requirements Specification) document. The SRS document details the functional and non-functional requirements of the system from the user's perspective. It serves as a contract between the client and the developers, outlining what the software should do and how it should perform.
DDD (Detailed Design Document), contains detailed design of modules, algorithms, and data structures.
SDD (Software Design Document), Provides high-level and low-level design details.

[ Option D ]

In the System Requirements Specification (SRS) document, the behavioral description details how the system responds to external events and internal controls. This includes system reactions to triggers, user interactions, and control mechanisms that govern system processing.

[ Option B ]

Economic feasibility evaluates whether project benefits outweigh its costs.

[ Option A ]

Technical feasibility is carried out by System Analysts to evaluate whether the current technology, tools, and resources are sufficient and suitable for developing and implementing the proposed system. 
It assesses the availability, capability, and compatibility of hardware, software, infrastructure, and technical expertise required to build the system.

[ Option B ]

A System Requirements Specification (SRS) document focuses on what the system should do, not how it will do it. It typically includes, functional requirements, non-functional attributes (performance, reliability, security, usability, etc.) and schedule and budget.
Design Solutions, on the other hand, describe how the system will be implemented. This is part of the System Design phase and is not included in SRS.

[ Option C ]

Financial Feasibility Study evaluates whether finances are available to implement the proposed system and whether the project will be cost-effective. A Financial Feasibility Study (Economic Feasibility) answers two main questions:

• Do we have enough money to build the proposed system?
• Will the system be cost-effective or economically beneficial?

[ Option B ]

Information Gathering is the process of collecting facts, opinions, and requirements from stakeholders, users, or sources to understand a problem or design a system. It is a crucial step in software engineering, system analysis, and research because decisions made later depend on accurate and complete information. The main objectives are to:

• Understand user needs and expectations.
• Identify problems, constraints, and requirements.
• Collect reliable data for designing effective solutions.

In the context of information gathering, different types of questions are designed to capture different kinds of responses from participants:

[ Option C ]

When software is being developed, we must check whether it is being built correctly according to the required functions and design. This checking process is called Verification.

• “Are we building the product right?”
• Checking correctness of the software during development
• Ensuring that each function is implemented properly
• Activities like reviews, inspections, walkthroughs, static testing
• Verification does not require running the program. It checks documents, code, and design to ensure correctness.

On the other hand, Validation is the process of checking whether the final software product meets customer needs and expectations. It ensures that the system performs the intended functions in the actual working environment and satisfies all user requirements.

[ Option B ]

In software engineering, Feasibility Study is an essential step in the Software Development Life Cycle (SDLC) that helps determine whether a project is practically achievable before full-scale development begins. The four solid dimensions of software feasibility are:

1. Financial Feasibility (Finance): Evaluates whether the project is economically viable, i.e., if the expected benefits outweigh the costs of development, operation, and maintenance.
2. Technical Feasibility (Technology): Determines whether the required technology, tools, and expertise are available to successfully build and implement the system.
3. Time Feasibility (Time): Assesses whether the project can be completed within the given deadline or schedule constraints.
4. Resource Feasibility (Resources): Examines the availability of human resources, hardware, software, and infrastructure necessary to execute the project.