Software Engineering MCQs with Answers

Practice Software Engineering MCQs with answers, explanations, filters, and quiz schema for BS students.

Software Engineering MCQs with Answers | Quiz
Total Questions200
Schema MarkupQuiz + Q&A
AnswersHidden
BrandingElecturesAI

Showing 200 of 200 questions.

Note: This page includes JSON-LD Quiz markup with a schema entry for every question. Ranking still depends on content quality, indexing, site authority, internal linking, page speed, and search intent match.
Q1Week 1: Introduction

Which concept is defined as “the systematic, disciplined, and measurable approach to the development, operation, and maintenance of software”?

  1. ASoftware Engineering
  2. BGeneric Software Product
  3. CSoftware
  4. DCustomized Software Product
Q2Week 1: Introduction

Which concept is defined as “a collection of programs, data, and documentation that performs useful tasks for users or organizations”?

  1. ASoftware Crisis
  2. BSoftware
  3. CProfessional Software Development
  4. DSoftware Engineering
Q3Week 1: Introduction

Which concept is defined as “the difficulty of building reliable software on time, within budget, and according to user needs”?

  1. AProfessional Software Development
  2. BSoftware Engineering
  3. CSoftware Crisis
  4. DSoftware Product
Q4Week 1: Introduction

Which concept is defined as “software development carried out using planned processes, standards, teamwork, documentation, testing, and maintenance”?

  1. ASoftware Product
  2. BSoftware
  3. CCustomized Software Product
  4. DProfessional Software Development
Q5Week 1: Introduction

Which concept is defined as “software delivered to customers or users as a complete solution, including code, configuration, and documentation”?

  1. ASoftware Product
  2. BGeneric Software Product
  3. CCustomized Software Product
  4. DSoftware
Q6Week 1: Introduction

Which concept is defined as “software developed for a broad market and sold to many different customers”?

  1. ASoftware Product
  2. BGeneric Software Product
  3. CProfessional Software Development
  4. DSoftware Engineering
Q7Week 1: Introduction

Which concept is defined as “software developed for a particular customer according to specific requirements”?

  1. AGeneric Software Product
  2. BSoftware Product
  3. CCustomized Software Product
  4. DProfessional Software Development
Q8Week 2: CASE Tools

Which concept is defined as “the practical application of principles, methods, and tools to plan, build, test, and maintain software”?

  1. AVersion Control System
  2. BGit
  3. CModeling Tool
  4. DSoftware Engineering Practice
Q9Week 2: CASE Tools

Which concept is defined as “Computer-Aided Software Engineering tools that support software activities such as modeling, design, coding, testing, and documentation”?

  1. ACASE Tools
  2. BGit
  3. CSoftware Engineering Practice
  4. DPrototyping Tool
Q10Week 2: CASE Tools

Which concept is defined as “a software tool used to create diagrams such as use case, class, sequence, and activity diagrams”?

  1. AGit
  2. BModeling Tool
  3. CPrototyping Tool
  4. DSoftware Engineering Practice
Q11Week 2: CASE Tools

Which concept is defined as “a tool used to create an early sample or mockup of a software product for feedback and refinement”?

  1. ASoftware Engineering Practice
  2. BVersion Control System
  3. CPrototyping Tool
  4. DModeling Tool
Q12Week 2: CASE Tools

Which concept is defined as “a software application that combines code editing, debugging, building, and testing features for developers”?

  1. AModeling Tool
  2. BCASE Tools
  3. CSoftware Engineering Practice
  4. DIntegrated Development Environment
Q13Week 2: CASE Tools

Which concept is defined as “a tool that records changes to source code and helps teams collaborate safely”?

  1. AVersion Control System
  2. BPrototyping Tool
  3. CCASE Tools
  4. DModeling Tool
Q14Week 2: CASE Tools

Which concept is defined as “a distributed version control system commonly used to track code changes and collaborate on software projects”?

  1. AVersion Control System
  2. BGit
  3. CSoftware Engineering Practice
  4. DIntegrated Development Environment
Q15Week 3: Development Phases

Which concept is defined as “the overall sequence of phases used to plan, analyze, design, implement, test, deploy, and maintain software”?

  1. ARequirement Phase
  2. BGeneric Software Product
  3. CSoftware Development Life Cycle
  4. DSoftware Testing
Q16Week 3: Development Phases

Which concept is defined as “the stage in which user needs, system services, and constraints are discovered and documented”?

  1. ASoftware Development Life Cycle
  2. BTestable Requirement
  3. CContinuous Integration
  4. DRequirement Phase
Q17Week 4: Design & Models

Which concept is defined as “the stage in which the system structure, components, interfaces, and data design are planned”?

  1. ADesign Phase
  2. BImplementation Phase
  3. CUML
  4. DActivity Diagram
Q18Week 4: Design & Models

Which concept is defined as “the stage in which the software design is converted into executable code”?

  1. ADesign Phase
  2. BImplementation Phase
  3. CSprint Backlog
  4. DRequirements Management
Q19Week 5: Integration & Maintenance

Which concept is defined as “the process of combining software components and checking that they work together correctly”?

  1. ACorrective Maintenance
  2. BPreventive Maintenance
  3. CIntegration
  4. DPerfective Maintenance
Q20Week 5: Integration & Maintenance

Which concept is defined as “the process of modifying software after delivery to keep it useful, correct, and aligned with changing needs”?

  1. AAdaptive Maintenance
  2. BCorrective Maintenance
  3. CIntegration
  4. DSoftware Evolution
Q21Week 5: Integration & Maintenance

Which concept is defined as “the activities performed after delivery to fix faults, improve performance, adapt to changes, or prevent future problems”?

  1. ASoftware Maintenance
  2. BPreventive Maintenance
  3. CSoftware Evolution
  4. DIntegration
Q22Week 5: Integration & Maintenance

Which concept is defined as “maintenance performed to fix faults discovered after software has been delivered”?

  1. AIntegration
  2. BCorrective Maintenance
  3. CAdaptive Maintenance
  4. DSoftware Maintenance
Q23Week 5: Integration & Maintenance

Which concept is defined as “maintenance performed to modify software so it works in a changed environment”?

  1. APerfective Maintenance
  2. BIntegration
  3. CAdaptive Maintenance
  4. DSoftware Evolution
Q24Week 5: Integration & Maintenance

Which concept is defined as “maintenance performed to improve performance, usability, or functionality based on user needs”?

  1. ASoftware Maintenance
  2. BIntegration
  3. CSoftware Evolution
  4. DPerfective Maintenance
Q25Week 5: Integration & Maintenance

Which concept is defined as “maintenance performed to improve maintainability and reduce the chance of future faults”?

  1. APreventive Maintenance
  2. BCorrective Maintenance
  3. CIntegration
  4. DPerfective Maintenance
Q26Week 6: Plan-Driven & Agile

Which concept is defined as “a development approach in which activities, deliverables, and schedules are planned in detail before major implementation begins”?

  1. AAgile Manifesto
  2. BPlan-Driven Development
  3. CScrum
  4. DUser Story
Q27Week 6: Plan-Driven & Agile

Which concept is defined as “an iterative and flexible approach that emphasizes customer collaboration, working software, frequent delivery, and response to change”?

  1. AExtreme Programming
  2. BAgile Manifesto
  3. CAgile Software Development
  4. DContinuous Integration
Q28Week 6: Plan-Driven & Agile

Which concept is defined as “a set of values and principles that prioritize individuals, working software, customer collaboration, and responding to change”?

  1. AAgile Software Development
  2. BPair Programming
  3. CDaily Scrum
  4. DAgile Manifesto
Q29Week 6: Plan-Driven & Agile

Which concept is defined as “an agile framework in which teams work in short iterations called sprints to deliver increments of software”?

  1. AScrum
  2. BPair Programming
  3. CContinuous Integration
  4. DDaily Scrum
Q30Week 6: Plan-Driven & Agile

Which concept is defined as “a short fixed time period in Scrum during which a team builds a usable product increment”?

  1. AProduct Backlog
  2. BSprint
  3. CRefactoring
  4. DExtreme Programming
Q31Week 6: Plan-Driven & Agile

Which concept is defined as “an ordered list of desired features, fixes, and improvements for a software product”?

  1. AExtreme Programming
  2. BRefactoring
  3. CProduct Backlog
  4. DSprint
Q32Week 6: Plan-Driven & Agile

Which concept is defined as “the selected set of backlog items and tasks a team commits to complete during a sprint”?

  1. AAgile Software Development
  2. BUser Story
  3. CTest-Driven Development
  4. DSprint Backlog
Q33Week 6: Plan-Driven & Agile

Which concept is defined as “a short daily meeting in Scrum used to inspect progress and plan the next work”?

  1. ADaily Scrum
  2. BAgile Manifesto
  3. CUser Story
  4. DSprint
Q34Week 6: Plan-Driven & Agile

Which concept is defined as “a short requirement written from the user's perspective describing a need and its value”?

  1. ARefactoring
  2. BUser Story
  3. CAgile Software Development
  4. DSprint
Q35Week 6: Plan-Driven & Agile

Which concept is defined as “an agile method that emphasizes practices such as pair programming, test-driven development, refactoring, and continuous integration”?

  1. ARefactoring
  2. BAgile Manifesto
  3. CExtreme Programming
  4. DPlan-Driven Development
Q36Week 6: Plan-Driven & Agile

Which concept is defined as “a development practice in which two programmers work together at one workstation, with one writing code and the other reviewing”?

  1. AAgile Software Development
  2. BUser Story
  3. CAgile Manifesto
  4. DPair Programming
Q37Week 6: Plan-Driven & Agile

Which concept is defined as “a practice in which tests are written before code so that development is guided by expected behavior”?

  1. ATest-Driven Development
  2. BProduct Backlog
  3. CExtreme Programming
  4. DScrum
Q38Week 6: Plan-Driven & Agile

Which concept is defined as “the process of improving the internal structure of code without changing its external behavior”?

  1. AScrum
  2. BRefactoring
  3. CSprint Backlog
  4. DUser Story
Q39Week 6: Plan-Driven & Agile

Which concept is defined as “a practice where code changes are frequently merged and automatically built and tested”?

  1. AAgile Software Development
  2. BRefactoring
  3. CContinuous Integration
  4. DPair Programming
Q40Week 7: V&V and RUP

Which concept is defined as “checking whether the software product is being built correctly according to specifications”?

  1. APrototype Model
  2. BRational Unified Process
  3. CTransition Phase
  4. DVerification
Q41Week 7: V&V and RUP

Which concept is defined as “checking whether the software product satisfies user needs and intended use”?

  1. AValidation
  2. BWaterfall Model
  3. CElaboration Phase
  4. DRational Unified Process
Q42Week 7: V&V and RUP

Which concept is defined as “an iterative software process framework organized into inception, elaboration, construction, and transition phases”?

  1. AValidation
  2. BRational Unified Process
  3. CWaterfall Model
  4. DIncremental Model
Q43Week 7: V&V and RUP

Which concept is defined as “the RUP phase that establishes project scope, business case, main requirements, and initial feasibility”?

  1. AWaterfall Model
  2. BPrototype Model
  3. CInception Phase
  4. DSpiral Model
Q44Week 7: V&V and RUP

Which concept is defined as “the RUP phase that refines requirements, addresses major risks, and establishes the system architecture”?

  1. AConstruction Phase
  2. BRational Unified Process
  3. CWaterfall Model
  4. DElaboration Phase
Q45Week 7: V&V and RUP

Which concept is defined as “the RUP phase in which the system is built, integrated, and tested into a complete product”?

  1. AConstruction Phase
  2. BElaboration Phase
  3. CValidation
  4. DVerification
Q46Week 7: V&V and RUP

Which concept is defined as “the RUP phase in which the software is delivered to users and adjusted based on operational feedback”?

  1. ASpiral Model
  2. BTransition Phase
  3. CValidation
  4. DConstruction Phase
Q47Week 7: V&V and RUP

Which concept is defined as “a sequential process model in which development flows through phases such as requirements, design, implementation, testing, and maintenance”?

  1. AConstruction Phase
  2. BTransition Phase
  3. CWaterfall Model
  4. DElaboration Phase
Q48Week 7: V&V and RUP

Which concept is defined as “a process model in which software is developed and delivered in small increments of functionality”?

  1. AElaboration Phase
  2. BTransition Phase
  3. CValidation
  4. DIncremental Model
Q49Week 7: V&V and RUP

Which concept is defined as “a risk-driven process model that combines iterative development with systematic risk analysis”?

  1. ASpiral Model
  2. BTransition Phase
  3. CInception Phase
  4. DConstruction Phase
Q50Week 7: V&V and RUP

Which concept is defined as “a process model that uses an early working version to clarify requirements and gather user feedback”?

  1. AVerification
  2. BPrototype Model
  3. CValidation
  4. DElaboration Phase
Q51Week 8: Requirements

Which concept is defined as “the process of discovering, analyzing, documenting, validating, and managing system requirements”?

  1. ANon-Functional Requirement
  2. BSoftware Requirements Specification
  3. CRequirements Engineering
  4. DFunctional Requirement
Q52Week 8: Requirements

Which concept is defined as “a requirement that describes a service, behavior, or function the system must provide”?

  1. ADomain Requirement
  2. BNon-Functional Requirement
  3. CRequirements Engineering
  4. DFunctional Requirement
Q53Week 8: Requirements

Which concept is defined as “a requirement that defines quality attributes or constraints such as performance, security, reliability, or usability”?

  1. ANon-Functional Requirement
  2. BRequirements Engineering
  3. CDomain Requirement
  4. DFunctional Requirement
Q54Week 8: Requirements

Which concept is defined as “a requirement that comes from the application domain and reflects domain rules, policies, or constraints”?

  1. ANon-Functional Requirement
  2. BDomain Requirement
  3. CRequirements Engineering
  4. DFunctional Requirement
Q55Week 8: Requirements

Which concept is defined as “a formal document that describes functional requirements, non-functional requirements, constraints, and system behavior”?

  1. AFunctional Requirement
  2. BDomain Requirement
  3. CSoftware Requirements Specification
  4. DNon-Functional Requirement
Q56Week 9: Requirements Process

Which concept is defined as “a person or group affected by the system or involved in its development, operation, or use”?

  1. AFeasibility Study
  2. BRequirements Discovery
  3. CQuestionnaire
  4. DStakeholder
Q57Week 9: Requirements Process

Which concept is defined as “an early investigation that determines whether a proposed software system is practical, useful, affordable, and technically possible”?

  1. AFeasibility Study
  2. BInterview
  3. CQuestionnaire
  4. DStakeholder
Q58Week 9: Requirements Process

Which concept is defined as “the activity of gathering requirements from stakeholders through interviews, observation, workshops, documents, and other techniques”?

  1. AObservation
  2. BRequirements Elicitation
  3. CRequirements Discovery
  4. DInterview
Q59Week 9: Requirements Process

Which concept is defined as “the process of finding real user needs, problems, constraints, and expectations for a system”?

  1. AObservation
  2. BQuestionnaire
  3. CRequirements Discovery
  4. DFeasibility Study
Q60Week 9: Requirements Process

Which concept is defined as “a requirements elicitation technique in which analysts ask stakeholders structured or open-ended questions”?

  1. AFeasibility Study
  2. BRequirements Elicitation
  3. CQuestionnaire
  4. DInterview
Q61Week 9: Requirements Process

Which concept is defined as “a requirements elicitation technique in which analysts watch users perform tasks in their real work environment”?

  1. AObservation
  2. BRequirements Elicitation
  3. CRequirements Discovery
  4. DFeasibility Study
Q62Week 9: Requirements Process

Which concept is defined as “a requirements elicitation technique that collects information from many stakeholders through written questions”?

  1. AObservation
  2. BQuestionnaire
  3. CStakeholder
  4. DRequirements Discovery
Q63Week 10: Requirements Validation

Which concept is defined as “checking that documented requirements are complete, consistent, clear, and testable”?

  1. AAmbiguous Requirement
  2. BTestable Requirement
  3. CRequirements Verification
  4. DRequirements Validation
Q64Week 10: Requirements Validation

Which concept is defined as “checking that requirements accurately reflect what stakeholders really need from the system”?

  1. ARequirements Verification
  2. BTestable Requirement
  3. CRequirements Traceability Matrix
  4. DRequirements Validation
Q65Week 10: Requirements Validation

Which concept is defined as “the process of controlling requirement changes and maintaining traceability throughout the project”?

  1. ARequirements Management
  2. BTestable Requirement
  3. CRequirements Verification
  4. DAmbiguous Requirement
Q66Week 10: Requirements Validation

Which concept is defined as “a table that links requirements to design elements, code modules, test cases, and project deliverables”?

  1. ARequirements Validation
  2. BRequirements Traceability Matrix
  3. CTestable Requirement
  4. DRequirements Verification
Q67Week 10: Requirements Validation

Which concept is defined as “a requirement that can be interpreted in more than one way and may cause misunderstanding”?

  1. ARequirements Validation
  2. BTestable Requirement
  3. CAmbiguous Requirement
  4. DRequirements Traceability Matrix
Q68Week 10: Requirements Validation

Which concept is defined as “a requirement written so that it can be verified through inspection, test, demonstration, or analysis”?

  1. ARequirements Validation
  2. BAmbiguous Requirement
  3. CRequirements Management
  4. DTestable Requirement
Q69Week 11: System Models

Which concept is defined as “an abstract representation of a system that helps stakeholders understand structure, behavior, context, or interactions”?

  1. ASystem Model
  2. BObject-Oriented Model
  3. CUse Case Diagram
  4. DContext Model
Q70Week 11: System Models

Which concept is defined as “a model showing the system boundary and its relationship with external systems, users, or organizations”?

  1. AClass Diagram
  2. BContext Model
  3. CState Machine Diagram
  4. DSequence Diagram
Q71Week 11: System Models

Which concept is defined as “a model that shows how users, objects, or components communicate with one another”?

  1. ABehavioral Model
  2. BModel-Driven Engineering
  3. CInteraction Model
  4. DObject-Oriented Model
Q72Week 11: System Models

Which concept is defined as “a UML diagram that shows actors, system functions, and relationships between users and system services”?

  1. AContext Model
  2. BClass Diagram
  3. CInteraction Model
  4. DUse Case Diagram
Q73Week 11: System Models

Which concept is defined as “a UML diagram that shows the time-ordered messages exchanged between objects or components”?

  1. ASequence Diagram
  2. BBehavioral Model
  3. CInteraction Model
  4. DModel-Driven Engineering
Q74Week 11: System Models

Which concept is defined as “a model that describes the static organization of classes, objects, components, or data in a system”?

  1. AModel-Driven Engineering
  2. BStructural Model
  3. CClass Diagram
  4. DSystem Model
Q75Week 11: System Models

Which concept is defined as “a UML diagram that represents classes, attributes, operations, and relationships in an object-oriented system”?

  1. AStructural Model
  2. BContext Model
  3. CClass Diagram
  4. DSystem Model
Q76Week 11: System Models

Which concept is defined as “a model that describes the dynamic behavior of a system in response to events or activities”?

  1. ASequence Diagram
  2. BModel-Driven Engineering
  3. CUML
  4. DBehavioral Model
Q77Week 11: System Models

Which concept is defined as “a UML diagram that shows states of an object and transitions caused by events”?

  1. AState Machine Diagram
  2. BSystem Model
  3. CActivity Diagram
  4. DInteraction Model
Q78Week 11: System Models

Which concept is defined as “a UML diagram that shows workflows, activities, decisions, and parallel processes”?

  1. AInteraction Model
  2. BActivity Diagram
  3. CClass Diagram
  4. DState Machine Diagram
Q79Week 11: System Models

Which concept is defined as “a model that represents software as interacting objects that contain data and behavior”?

  1. AUse Case Diagram
  2. BSystem Model
  3. CObject-Oriented Model
  4. DStructural Model
Q80Week 11: System Models

Which concept is defined as “an approach in which models are central development artifacts and may be used to generate code or system components”?

  1. AObject-Oriented Model
  2. BUse Case Diagram
  3. CActivity Diagram
  4. DModel-Driven Engineering
Q81Week 11: System Models

Which concept is defined as “Unified Modeling Language, a standard visual language for modeling software structure and behavior”?

  1. AUML
  2. BInteraction Model
  3. CClass Diagram
  4. DSequence Diagram
Q82Week 12: Software Design

Which concept is defined as “the process of defining the overall structure of a software system, including major components and their relationships”?

  1. AMVC Architecture
  2. BArchitectural Design
  3. CObserver Pattern
  4. DClient-Server Architecture
Q83Week 12: Software Design

Which concept is defined as “an architectural pattern that organizes a system into layers where each layer provides services to the layer above”?

  1. ADeployment Design
  2. BSingleton Pattern
  3. CLayered Architecture
  4. DClient-Server Architecture
Q84Week 12: Software Design

Which concept is defined as “an architecture where clients request services and servers provide resources, processing, or data”?

  1. AComponent-Level Design
  2. BDeployment Design
  3. CObserver Pattern
  4. DClient-Server Architecture
Q85Week 12: Software Design

Which concept is defined as “an architectural pattern that separates a system into model, view, and controller responsibilities”?

  1. AMVC Architecture
  2. BInterface Design
  3. CDesign Pattern
  4. DClient-Server Architecture
Q86Week 12: Software Design

Which concept is defined as “the design of how users, components, or systems interact with software through screens, APIs, or communication points”?

  1. AObserver Pattern
  2. BInterface Design
  3. CDeployment Design
  4. DLayered Architecture
Q87Week 12: Software Design

Which concept is defined as “the design of individual software components, their logic, data structures, interfaces, and responsibilities”?

  1. AMVC Architecture
  2. BInterface Design
  3. CComponent-Level Design
  4. DLayered Architecture
Q88Week 12: Software Design

Which concept is defined as “the design of how software components are placed on hardware nodes, servers, devices, or cloud infrastructure”?

  1. AClient-Server Architecture
  2. BMVC Architecture
  3. CLayered Architecture
  4. DDeployment Design
Q89Week 12: Software Design

Which concept is defined as “a reusable solution to a common software design problem in a particular context”?

  1. ADesign Pattern
  2. BInterface Design
  3. CDeployment Design
  4. DClient-Server Architecture
Q90Week 12: Software Design

Which concept is defined as “a design pattern that ensures a class has only one instance and provides a global access point to it”?

  1. AClient-Server Architecture
  2. BSingleton Pattern
  3. CComponent-Level Design
  4. DMVC Architecture
Q91Week 12: Software Design

Which concept is defined as “a design pattern that defines an interface for creating objects while allowing subclasses or methods to decide the concrete class”?

  1. ADeployment Design
  2. BObserver Pattern
  3. CFactory Method Pattern
  4. DArchitectural Design
Q92Week 12: Software Design

Which concept is defined as “a design pattern in which objects are notified automatically when another object's state changes”?

  1. ASingleton Pattern
  2. BDeployment Design
  3. CInterface Design
  4. DObserver Pattern
Q93Week 13: Software Testing

Which concept is defined as “the process of executing or evaluating software to find defects and assess whether it meets requirements”?

  1. ASoftware Testing
  2. BIntegration Testing
  3. CSystem Testing
  4. DSoftware Quality Assurance
Q94Week 13: Software Testing

Which concept is defined as “testing individual functions, methods, classes, or components in isolation”?

  1. ASystem Testing
  2. BUnit Testing
  3. CSoftware Testing
  4. DSoftware Quality Assurance
Q95Week 13: Software Testing

Which concept is defined as “testing combined components to find faults in their interfaces and interactions”?

  1. ASoftware Quality Assurance
  2. BSoftware Testing
  3. CIntegration Testing
  4. DUnit Testing
Q96Week 13: Software Testing

Which concept is defined as “testing the complete integrated system to evaluate whether it satisfies specified requirements”?

  1. ASoftware Testing
  2. BSoftware Quality Assurance
  3. CIntegration Testing
  4. DSystem Testing
Q97Week 14: Acceptance & Test Types

Which concept is defined as “testing based on the internal structure, logic, paths, or code of the software”?

  1. AWhite-Box Testing
  2. BRegression Testing
  3. CAlpha Testing
  4. DUser Testing
Q98Week 14: Acceptance & Test Types

Which concept is defined as “testing based on inputs and outputs without knowledge of the internal code structure”?

  1. AWhite-Box Testing
  2. BBlack-Box Testing
  3. CRegression Testing
  4. DUser Testing
Q99Week 14: Acceptance & Test Types

Which concept is defined as “testing performed to determine whether the system is ready for delivery and acceptable to users or customers”?

  1. ABlack-Box Testing
  2. BUser Testing
  3. CAcceptance Testing
  4. DBeta Testing
Q100Week 14: Acceptance & Test Types

Which concept is defined as “acceptance testing performed by internal users or testers before wider external release”?

  1. AUser Testing
  2. BTest Case
  3. CBlack-Box Testing
  4. DAlpha Testing
Q101Week 14: Acceptance & Test Types

Which concept is defined as “testing performed by selected real users in a real environment before final release”?

  1. ABeta Testing
  2. BBlack-Box Testing
  3. CRegression Testing
  4. DAcceptance Testing
Q102Week 14: Acceptance & Test Types

Which concept is defined as “testing where real or representative users evaluate the software for usefulness, usability, and correctness”?

  1. AAcceptance Testing
  2. BUser Testing
  3. CTest Case
  4. DWhite-Box Testing
Q103Week 14: Acceptance & Test Types

Which concept is defined as “a documented set of inputs, steps, expected results, and conditions used to verify software behavior”?

  1. ABlack-Box Testing
  2. BAlpha Testing
  3. CTest Case
  4. DAcceptance Testing
Q104Week 14: Acceptance & Test Types

Which concept is defined as “testing performed after changes to ensure that existing functionality still works correctly”?

  1. AAlpha Testing
  2. BUser Testing
  3. CBlack-Box Testing
  4. DRegression Testing
Q105Week 13: Software Testing

Which concept is defined as “planned and systematic activities that ensure software processes and products meet defined quality standards”?

  1. ASoftware Quality Assurance
  2. BUnit Testing
  3. CSoftware Testing
  4. DSystem Testing
Q106Week 15: Project Management

Which concept is defined as “the planning, organizing, monitoring, and controlling of software project activities, resources, risks, and deliverables”?

  1. AMilestone
  2. BSoftware Project Management
  3. CGantt Chart
  4. DProject Planning
Q107Week 15: Project Management

Which concept is defined as “the process of defining project scope, tasks, resources, schedule, risks, and deliverables”?

  1. ADeliverable
  2. BPERT Chart
  3. CProject Planning
  4. DRisk Management
Q108Week 15: Project Management

Which concept is defined as “the process of identifying dependencies and ordering project activities logically”?

  1. ASoftware Project Management
  2. BRisk Management
  3. CProject Planning
  4. DActivity Sequencing
Q109Week 15: Project Management

Which concept is defined as “a bar chart used to show project tasks, durations, and schedules over time”?

  1. AGantt Chart
  2. BPERT Chart
  3. CActivity Sequencing
  4. DDeliverable
Q110Week 15: Project Management

Which concept is defined as “a network diagram used to analyze task dependencies and estimate project completion time”?

  1. ASoftware Project Management
  2. BPERT Chart
  3. CRisk Management
  4. DDeliverable
Q111Week 15: Project Management

Which concept is defined as “a significant point or event in a project schedule used to track progress”?

  1. AProject Planning
  2. BRisk Management
  3. CMilestone
  4. DGantt Chart
Q112Week 15: Project Management

Which concept is defined as “a tangible or verifiable output produced by a project activity or phase”?

  1. AProject Planning
  2. BActivity Sequencing
  3. CSoftware Project Management
  4. DDeliverable
Q113Week 15: Project Management

Which concept is defined as “the process of identifying, analyzing, planning for, and monitoring project risks”?

  1. ARisk Management
  2. BProject Planning
  3. CActivity Sequencing
  4. DSoftware Project Management
Q114Week 16: Planning & Cost

Which concept is defined as “the process of estimating, budgeting, and controlling project costs”?

  1. AProposal Writing
  2. BProject Cost Management
  3. CCost Estimation
  4. DCOCOMO
Q115Week 16: Planning & Cost

Which concept is defined as “the process of predicting the effort, time, resources, and money required to complete a software project”?

  1. AFunction Point Analysis
  2. BProject Cost Management
  3. CCost Estimation
  4. DScope
Q116Week 16: Planning & Cost

Which concept is defined as “a software cost estimation model that estimates effort and schedule based mainly on software size and project factors”?

  1. AProject Cost Management
  2. BCost Estimation
  3. CProposal Writing
  4. DCOCOMO
Q117Week 16: Planning & Cost

Which concept is defined as “a size estimation technique that measures software functionality from the user's perspective”?

  1. AFunction Point Analysis
  2. BCost Estimation
  3. CCOCOMO
  4. DScope
Q118Week 16: Planning & Cost

Which concept is defined as “the activity of preparing a formal document that presents a project idea, objectives, scope, schedule, cost, and expected outcomes”?

  1. AProject Cost Management
  2. BProposal Writing
  3. CCOCOMO
  4. DScope
Q119Week 16: Planning & Cost

Which concept is defined as “the boundary of what a software project will and will not include”?

  1. ACOCOMO
  2. BCost Estimation
  3. CScope
  4. DFunction Point Analysis
Q120Course Review

Which concept is defined as “the process of controlling and tracking changes to software artifacts throughout the life cycle”?

  1. ABaseline
  2. BContinuous Deployment
  3. CReengineering
  4. DSoftware Configuration Management
Q121Course Review

Which concept is defined as “an approved version of a software artifact that serves as a reference point for future changes”?

  1. ABaseline
  2. BContinuous Deployment
  3. CDevOps
  4. DChange Control
Q122Course Review

Which concept is defined as “a formal process for evaluating, approving, implementing, and tracking changes to software artifacts”?

  1. ACMMI
  2. BChange Control
  3. CContinuous Deployment
  4. DSoftware Configuration Management
Q123Course Review

Which concept is defined as “the process of assembling software components into a working version for testing or release”?

  1. AChange Control
  2. BSoftware Configuration Management
  3. CBuild Management
  4. DCMMI
Q124Course Review

Which concept is defined as “the systematic effort to evaluate and improve software development processes for better quality, productivity, and predictability”?

  1. ABuild Management
  2. BCMMI
  3. CChange Control
  4. DSoftware Process Improvement
Q125Course Review

Which concept is defined as “Capability Maturity Model Integration, a framework used to improve and assess organizational software process maturity”?

  1. ACMMI
  2. BContinuous Deployment
  3. CBaseline
  4. DSoftware Process Improvement
Q126Course Review

Which concept is defined as “the process of analyzing and transforming existing software to improve its structure, maintainability, or functionality”?

  1. ASoftware Configuration Management
  2. BReengineering
  3. CBaseline
  4. DBuild Management
Q127Course Review

Which concept is defined as “a development and operations approach that emphasizes collaboration, automation, continuous delivery, and reliable deployment”?

  1. AContinuous Deployment
  2. BBaseline
  3. CDevOps
  4. DSoftware Configuration Management
Q128Course Review

Which concept is defined as “a practice in which approved code changes are automatically released to production or users”?

  1. ABuild Management
  2. BChange Control
  3. CAPI
  4. DContinuous Deployment
Q129Course Review

Which concept is defined as “an Application Programming Interface that defines how software components or systems communicate with one another”?

  1. AAPI
  2. BDevOps
  3. CCMMI
  4. DBuild Management
Q130Week 1: Introduction

Which statement best describes Software Engineering?

  1. ASoftware developed for a particular customer according to specific requirements.
  2. BThe systematic, disciplined, and measurable approach to the development, operation, and maintenance of software.
  3. CA collection of programs, data, and documentation that performs useful tasks for users or organizations.
  4. DSoftware developed for a broad market and sold to many different customers.
Q131Week 1: Introduction

Which statement best describes Software?

  1. ASoftware delivered to customers or users as a complete solution, including code, configuration, and documentation.
  2. BSoftware development carried out using planned processes, standards, teamwork, documentation, testing, and maintenance.
  3. CA collection of programs, data, and documentation that performs useful tasks for users or organizations.
  4. DThe systematic, disciplined, and measurable approach to the development, operation, and maintenance of software.
Q132Week 1: Introduction

Which statement best describes Software Crisis?

  1. AThe systematic, disciplined, and measurable approach to the development, operation, and maintenance of software.
  2. BSoftware delivered to customers or users as a complete solution, including code, configuration, and documentation.
  3. CSoftware developed for a broad market and sold to many different customers.
  4. DThe difficulty of building reliable software on time, within budget, and according to user needs.
Q133Week 1: Introduction

Which statement best describes Professional Software Development?

  1. ASoftware development carried out using planned processes, standards, teamwork, documentation, testing, and maintenance.
  2. BA collection of programs, data, and documentation that performs useful tasks for users or organizations.
  3. CSoftware developed for a broad market and sold to many different customers.
  4. DSoftware developed for a particular customer according to specific requirements.
Q134Week 1: Introduction

Which statement best describes Software Product?

  1. ASoftware developed for a broad market and sold to many different customers.
  2. BSoftware delivered to customers or users as a complete solution, including code, configuration, and documentation.
  3. CSoftware developed for a particular customer according to specific requirements.
  4. DA collection of programs, data, and documentation that performs useful tasks for users or organizations.
Q135Week 1: Introduction

Which statement best describes Generic Software Product?

  1. AA collection of programs, data, and documentation that performs useful tasks for users or organizations.
  2. BThe systematic, disciplined, and measurable approach to the development, operation, and maintenance of software.
  3. CSoftware developed for a broad market and sold to many different customers.
  4. DSoftware developed for a particular customer according to specific requirements.
Q136Week 1: Introduction

Which statement best describes Customized Software Product?

  1. AThe difficulty of building reliable software on time, within budget, and according to user needs.
  2. BSoftware development carried out using planned processes, standards, teamwork, documentation, testing, and maintenance.
  3. CA collection of programs, data, and documentation that performs useful tasks for users or organizations.
  4. DSoftware developed for a particular customer according to specific requirements.
Q137Week 2: CASE Tools

Which statement best describes Software Engineering Practice?

  1. AThe practical application of principles, methods, and tools to plan, build, test, and maintain software.
  2. BA software tool used to create diagrams such as use case, class, sequence, and activity diagrams.
  3. CA distributed version control system commonly used to track code changes and collaborate on software projects.
  4. DA tool that records changes to source code and helps teams collaborate safely.
Q138Week 2: CASE Tools

Which statement best describes CASE Tools?

  1. AA software tool used to create diagrams such as use case, class, sequence, and activity diagrams.
  2. BComputer-Aided Software Engineering tools that support software activities such as modeling, design, coding, testing, and documentation.
  3. CA tool used to create an early sample or mockup of a software product for feedback and refinement.
  4. DA software application that combines code editing, debugging, building, and testing features for developers.
Q139Week 2: CASE Tools

Which statement best describes Modeling Tool?

  1. AA distributed version control system commonly used to track code changes and collaborate on software projects.
  2. BComputer-Aided Software Engineering tools that support software activities such as modeling, design, coding, testing, and documentation.
  3. CA software tool used to create diagrams such as use case, class, sequence, and activity diagrams.
  4. DThe practical application of principles, methods, and tools to plan, build, test, and maintain software.
Q140Week 2: CASE Tools

Which statement best describes Prototyping Tool?

  1. AA software tool used to create diagrams such as use case, class, sequence, and activity diagrams.
  2. BA software application that combines code editing, debugging, building, and testing features for developers.
  3. CComputer-Aided Software Engineering tools that support software activities such as modeling, design, coding, testing, and documentation.
  4. DA tool used to create an early sample or mockup of a software product for feedback and refinement.
Q141Week 2: CASE Tools

Which statement best describes Integrated Development Environment?

  1. AA software application that combines code editing, debugging, building, and testing features for developers.
  2. BA tool that records changes to source code and helps teams collaborate safely.
  3. CA tool used to create an early sample or mockup of a software product for feedback and refinement.
  4. DComputer-Aided Software Engineering tools that support software activities such as modeling, design, coding, testing, and documentation.
Q142Week 2: CASE Tools

Which statement best describes Version Control System?

  1. AA tool used to create an early sample or mockup of a software product for feedback and refinement.
  2. BA tool that records changes to source code and helps teams collaborate safely.
  3. CA software application that combines code editing, debugging, building, and testing features for developers.
  4. DA distributed version control system commonly used to track code changes and collaborate on software projects.
Q143Week 2: CASE Tools

Which statement best describes Git?

  1. AComputer-Aided Software Engineering tools that support software activities such as modeling, design, coding, testing, and documentation.
  2. BA software tool used to create diagrams such as use case, class, sequence, and activity diagrams.
  3. CA distributed version control system commonly used to track code changes and collaborate on software projects.
  4. DA software application that combines code editing, debugging, building, and testing features for developers.
Q144Week 3: Development Phases

Which statement best describes Software Development Life Cycle?

  1. AThe stage in which user needs, system services, and constraints are discovered and documented.
  2. BA formal process for evaluating, approving, implementing, and tracking changes to software artifacts.
  3. CAcceptance testing performed by internal users or testers before wider external release.
  4. DThe overall sequence of phases used to plan, analyze, design, implement, test, deploy, and maintain software.
Q145Week 3: Development Phases

Which statement best describes Requirement Phase?

  1. AThe stage in which user needs, system services, and constraints are discovered and documented.
  2. BThe overall sequence of phases used to plan, analyze, design, implement, test, deploy, and maintain software.
  3. CThe RUP phase in which the software is delivered to users and adjusted based on operational feedback.
  4. DMaintenance performed to improve maintainability and reduce the chance of future faults.
Q146Week 4: Design & Models

Which statement best describes Design Phase?

  1. AThe stage in which the software design is converted into executable code.
  2. BThe stage in which the system structure, components, interfaces, and data design are planned.
  3. CThe process of predicting the effort, time, resources, and money required to complete a software project.
  4. DAn approved version of a software artifact that serves as a reference point for future changes.
Q147Week 4: Design & Models

Which statement best describes Implementation Phase?

  1. AThe stage in which the system structure, components, interfaces, and data design are planned.
  2. BA short daily meeting in Scrum used to inspect progress and plan the next work.
  3. CThe stage in which the software design is converted into executable code.
  4. DTesting combined components to find faults in their interfaces and interactions.
Q148Week 5: Integration & Maintenance

Which statement best describes Integration?

  1. AMaintenance performed to improve maintainability and reduce the chance of future faults.
  2. BThe activities performed after delivery to fix faults, improve performance, adapt to changes, or prevent future problems.
  3. CMaintenance performed to modify software so it works in a changed environment.
  4. DThe process of combining software components and checking that they work together correctly.
Q149Week 5: Integration & Maintenance

Which statement best describes Software Evolution?

  1. AThe process of modifying software after delivery to keep it useful, correct, and aligned with changing needs.
  2. BMaintenance performed to modify software so it works in a changed environment.
  3. CMaintenance performed to improve maintainability and reduce the chance of future faults.
  4. DMaintenance performed to improve performance, usability, or functionality based on user needs.
Q150Week 5: Integration & Maintenance

Which statement best describes Software Maintenance?

  1. AMaintenance performed to improve performance, usability, or functionality based on user needs.
  2. BThe activities performed after delivery to fix faults, improve performance, adapt to changes, or prevent future problems.
  3. CMaintenance performed to fix faults discovered after software has been delivered.
  4. DThe process of combining software components and checking that they work together correctly.
Q151Week 5: Integration & Maintenance

Which statement best describes Corrective Maintenance?

  1. AThe activities performed after delivery to fix faults, improve performance, adapt to changes, or prevent future problems.
  2. BMaintenance performed to improve performance, usability, or functionality based on user needs.
  3. CMaintenance performed to fix faults discovered after software has been delivered.
  4. DMaintenance performed to modify software so it works in a changed environment.
Q152Week 5: Integration & Maintenance

Which statement best describes Adaptive Maintenance?

  1. AThe activities performed after delivery to fix faults, improve performance, adapt to changes, or prevent future problems.
  2. BMaintenance performed to improve performance, usability, or functionality based on user needs.
  3. CMaintenance performed to fix faults discovered after software has been delivered.
  4. DMaintenance performed to modify software so it works in a changed environment.
Q153Week 5: Integration & Maintenance

Which statement best describes Perfective Maintenance?

  1. AMaintenance performed to improve performance, usability, or functionality based on user needs.
  2. BThe activities performed after delivery to fix faults, improve performance, adapt to changes, or prevent future problems.
  3. CThe process of modifying software after delivery to keep it useful, correct, and aligned with changing needs.
  4. DMaintenance performed to fix faults discovered after software has been delivered.
Q154Week 5: Integration & Maintenance

Which statement best describes Preventive Maintenance?

  1. AThe process of combining software components and checking that they work together correctly.
  2. BMaintenance performed to improve maintainability and reduce the chance of future faults.
  3. CThe process of modifying software after delivery to keep it useful, correct, and aligned with changing needs.
  4. DMaintenance performed to fix faults discovered after software has been delivered.
Q155Week 6: Plan-Driven & Agile

Which statement best describes Plan-Driven Development?

  1. AAn agile method that emphasizes practices such as pair programming, test-driven development, refactoring, and continuous integration.
  2. BThe process of improving the internal structure of code without changing its external behavior.
  3. CA development approach in which activities, deliverables, and schedules are planned in detail before major implementation begins.
  4. DA development practice in which two programmers work together at one workstation, with one writing code and the other reviewing.
Q156Week 6: Plan-Driven & Agile

Which statement best describes Agile Software Development?

  1. AA development approach in which activities, deliverables, and schedules are planned in detail before major implementation begins.
  2. BA practice in which tests are written before code so that development is guided by expected behavior.
  3. CA set of values and principles that prioritize individuals, working software, customer collaboration, and responding to change.
  4. DAn iterative and flexible approach that emphasizes customer collaboration, working software, frequent delivery, and response to change.
Q157Week 6: Plan-Driven & Agile

Which statement best describes Agile Manifesto?

  1. AA set of values and principles that prioritize individuals, working software, customer collaboration, and responding to change.
  2. BA practice where code changes are frequently merged and automatically built and tested.
  3. CAn iterative and flexible approach that emphasizes customer collaboration, working software, frequent delivery, and response to change.
  4. DAn agile framework in which teams work in short iterations called sprints to deliver increments of software.
Q158Week 6: Plan-Driven & Agile

Which statement best describes Scrum?

  1. AAn iterative and flexible approach that emphasizes customer collaboration, working software, frequent delivery, and response to change.
  2. BAn agile framework in which teams work in short iterations called sprints to deliver increments of software.
  3. CAn ordered list of desired features, fixes, and improvements for a software product.
  4. DThe process of improving the internal structure of code without changing its external behavior.
Q159Week 6: Plan-Driven & Agile

A team wants frequent customer feedback and the ability to respond quickly to changing requirements. Which approach is most suitable?

  1. APair Programming
  2. BTest-Driven Development
  3. CAgile Software Development
  4. DSprint Backlog
Q160Week 7: V&V and RUP

A university project follows requirements, design, coding, testing, and maintenance one after another with little iteration. Which process model is being used?

  1. ASpiral Model
  2. BIncremental Model
  3. CVerification
  4. DWaterfall Model
Q161Week 7: V&V and RUP

A team builds a quick working screen so users can give feedback before full development. Which model or technique is this?

  1. APrototype Model
  2. BTransition Phase
  3. CIncremental Model
  4. DWaterfall Model
Q162Week 6: Plan-Driven & Agile

A developer writes automated tests before writing the production code. Which practice is being followed?

  1. AAgile Manifesto
  2. BTest-Driven Development
  3. CRefactoring
  4. DContinuous Integration
Q163Week 6: Plan-Driven & Agile

Two programmers work together on the same task, where one writes code and the other reviews continuously. Which practice is this?

  1. ARefactoring
  2. BProduct Backlog
  3. CPair Programming
  4. DSprint Backlog
Q164Week 6: Plan-Driven & Agile

A product owner maintains an ordered list of features, bugs, and improvements for future work. What is this list called?

  1. APlan-Driven Development
  2. BScrum
  3. CRefactoring
  4. DProduct Backlog
Q165Week 6: Plan-Driven & Agile

During a sprint, the team uses a selected list of tasks they plan to finish before the sprint ends. What is it called?

  1. ASprint Backlog
  2. BTest-Driven Development
  3. CUser Story
  4. DPlan-Driven Development
Q166Week 6: Plan-Driven & Agile

A team meets for a short daily meeting to discuss progress, blockers, and the next work. Which Scrum event is this?

  1. APair Programming
  2. BDaily Scrum
  3. CUser Story
  4. DRefactoring
Q167Week 8: Requirements

A requirement says the system shall allow students to register for courses online. What type of requirement is this?

  1. ARequirements Engineering
  2. BDomain Requirement
  3. CFunctional Requirement
  4. DSoftware Requirements Specification
Q168Week 8: Requirements

A requirement says the system must respond within two seconds and protect user passwords. What type of requirement is this?

  1. ARequirements Engineering
  2. BDomain Requirement
  3. CFunctional Requirement
  4. DNon-Functional Requirement
Q169Week 9: Requirements Process

An analyst watches office staff performing real work to understand hidden requirements. Which elicitation technique is being used?

  1. AObservation
  2. BInterview
  3. CRequirements Discovery
  4. DRequirements Elicitation
Q170Week 10: Requirements Validation

A requirements document is checked for clarity, consistency, completeness, and testability. Which activity is this?

  1. ATestable Requirement
  2. BRequirements Verification
  3. CRequirements Management
  4. DAmbiguous Requirement
Q171Week 10: Requirements Validation

Stakeholders review requirements to confirm that they reflect real needs. Which activity is this?

  1. AAmbiguous Requirement
  2. BTestable Requirement
  3. CRequirements Validation
  4. DRequirements Traceability Matrix
Q172Week 11: System Models

A diagram shows actors and the main services they use in the system. Which UML diagram is this?

  1. ASequence Diagram
  2. BBehavioral Model
  3. CModel-Driven Engineering
  4. DUse Case Diagram
Q173Week 11: System Models

A diagram shows messages between objects in time order during login. Which UML diagram is this?

  1. ASequence Diagram
  2. BActivity Diagram
  3. CState Machine Diagram
  4. DObject-Oriented Model
Q174Week 11: System Models

A diagram shows classes, attributes, operations, and associations. Which UML diagram is this?

  1. AActivity Diagram
  2. BClass Diagram
  3. CBehavioral Model
  4. DInteraction Model
Q175Week 11: System Models

A diagram shows how an order changes from pending to paid, shipped, and delivered. Which diagram fits best?

  1. AModel-Driven Engineering
  2. BUse Case Diagram
  3. CState Machine Diagram
  4. DClass Diagram
Q176Week 12: Software Design

A system is divided into presentation, business logic, and data layers. Which architecture is being used?

  1. AComponent-Level Design
  2. BMVC Architecture
  3. CObserver Pattern
  4. DLayered Architecture
Q177Week 12: Software Design

An application separates data, user interface, and request-handling logic. Which architecture is this?

  1. AMVC Architecture
  2. BArchitectural Design
  3. CInterface Design
  4. DSingleton Pattern
Q178Week 12: Software Design

A team designs how components will be placed on servers, devices, or cloud nodes. Which design activity is this?

  1. AObserver Pattern
  2. BDeployment Design
  3. CArchitectural Design
  4. DFactory Method Pattern
Q179Week 12: Software Design

A class must have only one object throughout the program. Which design pattern is appropriate?

  1. AComponent-Level Design
  2. BFactory Method Pattern
  3. CSingleton Pattern
  4. DMVC Architecture
Q180Week 12: Software Design

Objects must automatically receive notifications when another object changes state. Which pattern is appropriate?

  1. AInterface Design
  2. BMVC Architecture
  3. CDesign Pattern
  4. DObserver Pattern
Q181Week 13: Software Testing

A tester checks individual functions before testing the whole system. Which testing level is this?

  1. AUnit Testing
  2. BIntegration Testing
  3. CSoftware Testing
  4. DSoftware Quality Assurance
Q182Week 13: Software Testing

After combining modules, the team tests their interfaces and communication. Which testing level is this?

  1. ASystem Testing
  2. BIntegration Testing
  3. CSoftware Testing
  4. DUnit Testing
Q183Week 13: Software Testing

The complete system is tested against specified requirements before delivery. Which testing level is this?

  1. ASoftware Testing
  2. BUnit Testing
  3. CSystem Testing
  4. DIntegration Testing
Q184Week 14: Acceptance & Test Types

A tester designs tests using the internal code paths and conditions. Which testing approach is this?

  1. AUser Testing
  2. BAlpha Testing
  3. CBlack-Box Testing
  4. DWhite-Box Testing
Q185Week 14: Acceptance & Test Types

A tester checks only inputs and expected outputs without viewing source code. Which testing approach is this?

  1. ABlack-Box Testing
  2. BRegression Testing
  3. CAlpha Testing
  4. DWhite-Box Testing
Q186Week 14: Acceptance & Test Types

Selected real users test a near-final product in their own environment before public release. Which testing type is this?

  1. AAcceptance Testing
  2. BBeta Testing
  3. CWhite-Box Testing
  4. DBlack-Box Testing
Q187Week 14: Acceptance & Test Types

A team reruns tests after a code change to ensure old features still work. Which testing is this?

  1. AAlpha Testing
  2. BAcceptance Testing
  3. CRegression Testing
  4. DBeta Testing
Q188Week 15: Project Management

A manager identifies tasks, durations, resources, risks, and deliverables before development starts. Which activity is this?

  1. ASoftware Project Management
  2. BMilestone
  3. CActivity Sequencing
  4. DProject Planning
Q189Week 15: Project Management

A project manager uses bars on a timeline to show task durations and schedule. Which chart is being used?

  1. AGantt Chart
  2. BSoftware Project Management
  3. CDeliverable
  4. DProject Planning
Q190Week 15: Project Management

A project network diagram is used to analyze activity dependencies and estimate completion time. Which chart is this?

  1. ARisk Management
  2. BPERT Chart
  3. CGantt Chart
  4. DDeliverable
Q191Week 16: Planning & Cost

A team predicts effort and schedule using software size and project factors. Which model may be used?

  1. AFunction Point Analysis
  2. BProject Cost Management
  3. CCOCOMO
  4. DProposal Writing
Q192Week 10: Requirements Validation

A requirement is linked to design, code, and test cases in a table. Which artifact is this?

  1. ARequirements Management
  2. BTestable Requirement
  3. CRequirements Validation
  4. DRequirements Traceability Matrix
Q193Course Review

An approved version of an SRS is saved as a reference point before future changes. What is it called?

  1. ABaseline
  2. BDevOps
  3. CSoftware Process Improvement
  4. DSoftware Configuration Management
Q194Course Review

A change request is reviewed, approved, implemented, and recorded formally. Which process is this?

  1. AReengineering
  2. BChange Control
  3. CSoftware Process Improvement
  4. DCMMI
Q195Course Review

A company evaluates and improves its development process to increase quality and predictability. Which activity is this?

  1. ADevOps
  2. BSoftware Configuration Management
  3. CSoftware Process Improvement
  4. DReengineering
Q196Week 6: Plan-Driven & Agile

A team automatically builds and tests code each time developers merge changes. Which practice is this?

  1. APair Programming
  2. BPlan-Driven Development
  3. CScrum
  4. DContinuous Integration
Q197Week 5: Integration & Maintenance

A software system is modified because the operating system and database versions changed. Which maintenance type is this?

  1. AAdaptive Maintenance
  2. BSoftware Maintenance
  3. CCorrective Maintenance
  4. DPreventive Maintenance
Q198Week 5: Integration & Maintenance

A delivered system is changed to add user-requested usability improvements. Which maintenance type is this?

  1. AAdaptive Maintenance
  2. BPerfective Maintenance
  3. CSoftware Evolution
  4. DCorrective Maintenance
Q199Week 16: Planning & Cost

A project proposal clearly defines objectives, scope, schedule, cost, and expected outcomes. Which activity does this represent?

  1. ACost Estimation
  2. BCOCOMO
  3. CProposal Writing
  4. DFunction Point Analysis
Q200Course Review

Which concept is most closely related to controlling changes in software artifacts?

  1. AContinuous Deployment
  2. BAPI
  3. CDevOps
  4. DSoftware Configuration Management
Software Engineering MCQ page generated for BS students study and revision by ElecturesAI.

Entrepreneurship Education MCQs with Answers

Leave a Reply

Your email address will not be published. Required fields are marked *