Q: 1 __________ approach of system development is easy to accommodate product changes, but not suitable for large, high-risk, or mission-critical projects?
Rapid Application Development (RAD)
Spiral
Agile
Prototype
[ Option C ]
Q: 2 Project requests are evaluated in the ______________ phase of System Development Life Cycle.
Preliminary Investigation
System Testing
System Design
Requirement Analysis
[ Option A ]
The Preliminary Investigation phase is the first step in the System Development Life Cycle (SDLC). This phase acts like a screening process to decide if a project should move forward. During this phase, the system analyst evaluates:
Q: 3 The Spiral model combines features of:
Waterfall and Agile models.
Prototyping and Iterative models.
Incremental and Waterfall models.
Prototyping and Waterfall models.
[ Option D ]
The Spiral Model integrates the structured nature of Waterfall with the risk assessment and iterative approach of Prototyping.
Q: 4 A generic process framework for software engineering defines five framework activities. A ______________ executes each of these five framework activities in sequence.
evolutionary flow
parallel process flow
linear process flow
iterative flow
[ Option C ]
A generic process framework in software engineering consists of five main framework activities, usually, Communication, Planning, Modeling, Construction, Deployment. When these activities are carried out one after another in a strict sequence, it is called a Linear Process Flow.
The linear process flow means, no overlaps, one activity must finish before the next begins, follows a straight, step-by-step path. This is very similar to the Waterfall Model.
Q: 5 Which of the following is not a part of the four activities that are fundamental to software engineering?
Software Specification
Software Design and Implementation
Software Evolution
Software Cohesion
[ Option D ]
In Software Engineering, there are four fundamental activities that guide the development and maintenance of software systems.
| ACTIVITY | MEANING |
|---|---|
| Software Specification | Defining what the software should do and the requirements it must satisfy. |
| Software Design and Implementation | Designing the system architecture and writing the actual code to implement the design. |
| Software Validation | Ensuring that the software meets the specified requirements and works correctly. |
| Software Evolution | Modifying and updating software to adapt to changing requirements or fix defects after deployment. |
Q: 6 ____________ is a usable system or system component that is built quickly and at lesser cost and with the intention of modifying or replacing it by a full-scale and fully operational system.
Approved system
Increment
Prototype
Spiral
[ Option C ]
When developing a new system, it is often helpful to build a quick, small, and low-cost version of the actual system first. This early version is called a Prototype.
A prototype is working model of the system. It is created with the intention of being modified, refined, or replaced later by a full-scale, fully operational system.
In system or software development, building the full system at once can be costly and risky if requirements are unclear. To address this, a Prototype is made as an early version that may not have all features but represents essential aspects of the system.
Q: 7 In the Waterfall model, each phase:
Overlaps with the next phase.
Has no defined order.
Must be completed before the next begins.
Executed in reverse order.
[ Option C ]
The Waterfall Model is a linear sequential model where each phase must be finished before the next one starts.
Q: 8 The first phase of SDLC is:
System Design.
Implementation.
System Analysis.
Requirement Identification.
[ Option D ]
SDLC begins with identifying user and system requirements to define the scope and objectives of the system.
Q: 9 Which of the following general problem solving step is equivalent to system analysis in the software development process?
Design the chosen problem
Implement the chosen solution
Identify the solution requirements and expectations
Identify the problem
[ Option C ]
In software development, system analysis involves understanding what the system must do by gathering functional and non-functional requirements from users and stakeholders. It focuses on identifying solution requirements and expectations, not on designing or implementing the system.
Q: 10 Which of the following activity is not involved in the design of database during system designing phase of System Development Life Cycle?
Physical Layout Design
Data Modeling
Conceptual Modeling
Input/output Volume
[ Option D ]
During the System Designing phase of the System Development Life Cycle (SDLC), the database design focuses on how data will be stored, organized, and structured. This includes creating models that describe data elements, their relationships, and the final physical storage format.
| ACTIVITY | PURPOSE |
|---|---|
| Conceptual Modeling | Defines what data the system needs at a high-level using ER diagrams (entities, attributes, relationships). |
| Data Modeling | Converts the conceptual model into detailed database structures such as tables, fields, keys, and relationships. |
| Physical Layout Design | Decides how the data will be physically stored on disk (indexing, file organization, partitioning, storage formats). |
However, the Input/Output Volume is not part of database design. It relates to system performance and workload analysis.
Q: 11 Which one of the following is not a software process model?
Linear Sequential Model
Prototype Model
The Spiral Model
COCOMO Model
[ Option D ]
A software process model is a structured approach that defines the sequence of steps or phases to be followed for systematic software development.
| Software Process Model | Description |
|---|---|
| Linear Sequential Model | A structured, step-by-step approach where each phase is completed before the next begins, best for well-defined projects but inflexible to changes. |
| Prototype Model | Builds a working prototype early to clarify requirements and gather user feedback, useful when requirements are unclear but may extend development time due to multiple iterations. |
| Spiral Model | Risk-driven iterative model combining repeated development cycles with risk analysis at each stage. It suitable for large and complex projects requiring risk management and frequent refinement. |
| Agile Model | Emphasizes flexibility, collaboration, and iterative incremental delivery through frequent releases and feedback, ideal for projects with evolving requirements. |
| Incremental Model | Develops the system in small, manageable parts called increments; each increment goes through requirement, design, testing, and implementation, enabling early partial delivery and adaptation. |
| V Model | A variation of the waterfall model emphasizing Verification and Validation. In this, every development phase has a corresponding testing phase, ensuring systematic testing but less flexible for changes. |
The COCOMO (Constructive Cost Model) is a well-known software cost estimation model developed by Barry W. Boehm in the late 1970s. It helps predict the amount of effort, time, and resources required to complete a software development project based on software size, usually measured in lines of code (LOC).
| COCOMO Level | Description |
|---|---|
| Basic COCOMO | Provides a quick, rough estimate of effort based mainly on project size (KLOC). It uses a simple formula and does not consider factors like reliability or personnel experience. |
| Intermediate COCOMO | Extends Basic COCOMO by including 15 cost factors such as product complexity, hardware constraints, and personnel capability to improve estimation accuracy. |
| Detailed COCOMO | Further extends Intermediate COCOMO by assessing the impact of cost drivers on each phase of the software development process. It divides the software into modules, estimating effort for each, enabling precise and phase-wise estimation. |
Q: 12 Choose the correct option considering the assertion and reason in context of software engineering.
Assertion (A): The Spiral Model supports progressive refinement of the software product through multiple iterations.
Reason (R): Each pass through the planning region in spiral allows for feedback-based adjustments to cost, schedule, and the number of iterations.
Both (A) and (R) are true, and (R) is the correct explanation of (A).
Both (A) and (R) are true, but (R) is not the correct explanation of (A).
(A) is true, but (R) is false.
(A) is false, but (R) is true.
[ Option A ]
The Spiral Model is an evolutionary software development process model that combines features of both iterative development and the waterfall model. It focuses on risk management and progressive refinement of the software through multiple iterations (spirals).
Each loop (or spiral) of the model consists of four main phases, Planning, Risk Analysis, Engineering, and Evaluation. During each pass through the planning region, teams gather feedback, reassess risks, and adjust cost, schedule, and number of iterations based on real project outcomes.
Q: 13 The _____________ approach of system development is not suitable for accommodating changes as it follows all sequential steps.
Agile
Prototyping
Waterfall
Rapid Application Development (RAD)
[ Option C ]
The Waterfall approach to system development is sequential and linear, meaning each phase must be completed fully before the next begins. This method follows a strict sequence of steps such as requirement gathering, design, implementation, testing, and maintenance. Due to its rigid structure, it is not suitable for accommodating changes easily once a phase is completed.
Q: 14 Consider Column – I and Column – II in the context of various activities of a generic process framework for software engineering.
| Column – I | Column – II |
|---|---|
| a. Communication | i. Coding and Testing |
| b. Planning | ii. Requirement Gathering |
| c. Construction | iii. Delivery and Feedback |
| d. Deployment | iv. Risk, Resources and Schedules |
Which of the following is the most suitable match of Column – I and Column – II?
a – ii , b – iv, c – i, d – iii
a – ii, b – iii, c – iv, d – i
a – iii, b – iv, c – i, d – ii
a – iv, b – i, c – ii, d – iii
[ Option A ]
In the generic process framework for software engineering, the software development process is divided into several important activities, each having a specific purpose.
Communication : This is the first step of software development where interaction takes place between developers and customers. The goal is to understand what the customer needs. Therefore, it involves requirement gathering and analysis.
Planning : After gathering requirements, the next step is to plan the project activities. This includes identifying risks, resources, and schedules to ensure the project is completed on time and within budget.
Construction : This phase involves Coding and Testing of the software. Developers write the actual code and then test it to make sure it functions correctly and meets requirements.
Deployment : After successful testing, the software is delivered to the customer, and feedback is collected for future improvements.
Q: 15 The first step to the system study project is to-
Define system performance criteria
Describe information needs
Staff for the study project
Announce the study project
[ Option B ]
In a system study project, the very first step is to describe the information needs of users and the organization. This step is crucial because it helps in identifying what data is required, how it should be processed, and what outputs are necessary for decision-making.
Once the information needs are clearly understood, other steps such as defining system performance criteria, staffing for the study project, and officially announcing the project can be carried out effectively. Without properly identifying user requirements at the start, the system cannot be designed to meet organizational goals.
Thank you so much for taking the time to read my Computer Science MCQs section carefully. Your support and interest mean a lot, and I truly appreciate you being part of this journey. Stay connected for more insights and updates! If you'd like to explore more tutorials and insights, check out my YouTube channel.
Don’t forget to subscribe and stay connected for future updates.