WorksheetsSoftware Process Quiz
Total questions: 100
Worksheet time: 50mins
Which of the following best defines a software process?
A sequence of steps for writing code
A structured set of activities for software development
A tool for debugging software
A testing mechanism
The main aim of a software process is to:
Reduce testing time
Provide a systematic approach to software development
Eliminate documentation
Avoid customer involvement
Which of the following is NOT a software process activity?
Specification
Design and implementation
Deployment
Compilation
In software engineering, a 'process framework' defines:
A specific programming language
A set of umbrella activities
A debugging technique
A testing strategy
Which activity ensures that customer requirements are well-understood?
Deployment
Requirement engineering
Maintenance
Debugging
Software process improvement focuses mainly on:
Cost reduction and quality enhancement
Using new programming languages
Replacing the project manager
Eliminating testing
Which is NOT an objective of software processes?
Maintain quality
Increase productivity
Random development without planning
Reduce risks
A software process must be:
Informal and inconsistent
Well-defined and repeatable
Dependent only on coding
Focused only on testing
Which model views software as an evolving entity?
Build and Fix
Evolutionary process
Waterfall
Spiral
The role of process metrics is to:
Count the number of programmers
Measure software development activities
Debug errors
Replace documentation
Which of the following is an example of a prescriptive process model?
Waterfall
Agile
Kanban
Extreme Programming
The key elements of a software process are:
People, process, tools
Code, debug, compile
Test, deploy, delete
User, server, database
The Waterfall model is also known as:
Linear Sequential Model
Spiral Model
V-Model
Agile
A disadvantage of the Waterfall model is:
Too much flexibility
No early prototype is produced
Iterations are encouraged
Continuous customer involvement
Which process model is risk-driven?
Spiral Model
Waterfall Model
Incremental Model
Agile
The Incremental model delivers:
The whole system at once
Small functional parts of the system in steps
Only prototypes
No usable software
In the Spiral model, each loop represents:
A coding session
A phase of the software process
A debugging cycle
Only requirement gathering
The V-model emphasizes:
Verification and validation
Coding speed
Customer isolation
Elimination of design
The Prototyping model is most useful when:
Requirements are well defined
Requirements are unclear
There is no customer
Testing is not needed
RAD stands for:
Rapid Application Development
Random Application Design
Reliable Application Deployment
Real Agile Design
Which model combines prototyping with iterative development?
Incremental Model
Spiral Model
Agile
Waterfall
Agile models primarily focus on:
Documentation
Customer collaboration
Testing only
Debugging
The Build-and-Fix model is:
Highly recommended for large projects
An outdated and unreliable model
A variation of the spiral model
Used in safety-critical systems
Which model is best suited for systems with high risk?
Spiral
Waterfall
Prototyping
V-model
Evolutionary models include:
Incremental and Spiral
Waterfall and V-model
Agile and Waterfall
RAD and Waterfall
The Unified Process (UP) is:
A framework for iterative software development
A debugging technique
A testing method
A programming language
The UP was popularized by:
Booch, Rumbaugh, Jacobson
Dijkstra and Knuth
Martin Fowler
Barry Boehm
The UP is based on:
Agile principles
Object-oriented design and UML
Linear waterfall
Functional programming
The Unified Process lifecycle has how many phases?
2
3
4
5
The four phases of UP are:
Inception, Elaboration, Construction, Transition
Planning, Design, Coding, Testing
Requirement, Design, Debugging, Maintenance
Initiation, Execution, Closure, Monitoring
In UP, the Inception phase focuses on:
Detailed coding
Scope definition and feasibility
Deployment
Debugging
The Elaboration phase deals with:
Identifying system architecture
Final user training
Deployment only
Bug fixing
In UP, the Construction phase is:
Building the actual product
Requirement collection
Deployment
Retirement
The Transition phase involves:
Delivering the system to the user
Gathering requirements
Debugging
Creating prototypes
The UP is best described as:
Iterative and incremental
Linear sequential
Non-iterative
Prototype-only
A key artifact in UP is:
Use case model
Test case only
Compilation log
Source code only
Which diagramming language is tightly linked with UP?
UML
BPMN
ERD
Flowchart
Umbrella activities are:
Support activities across all process phases
Initial coding activities
Debugging activities only
Deployment activities
Which of the following is NOT an umbrella activity?
Risk management
Coding
Quality assurance
Documentation
Software project management is considered a:
Framework activity
Umbrella activity
Debugging step
Maintenance activity
Software configuration management (SCM) ensures:
No changes to software
Controlled changes to software
Debugging only
No user involvement
Which umbrella activity deals with checking compliance to standards?
Software quality assurance
Deployment
Requirement gathering
Debugging
Risk management primarily addresses:
Identifying and mitigating risks
Coding errors
Documentation
Debugging
Documentation serves as:
A way to record process artifacts
A debugging tool
A deployment method
A test case
Metrics and measurement provide:
Quantitative insights into process and product
Debugging solutions
Coding speed
End-user training
Which umbrella activity is critical for team collaboration?
Project management
Debugging
Testing
Deployment
Reusability management ensures:
Existing components can be reused
Testing is eliminated
Documentation is avoided
Debugging is skipped
Which umbrella activity focuses on user training and manuals?
Documentation
Risk management
Quality assurance
Debugging
Software quality assurance (SQA) includes:
Standards, reviews, and testing
Coding
Debugging only
End-user training
Software quality assurance (SQA) includes:
Standards, reviews, and testing
Coding
Debugging only
End-user training
Requirement Engineering is primarily concerned with:
Writing code
Gathering, analyzing, and managing requirements
Testing software
Debugging
Which of the following is NOT a step in Requirement Engineering?
Requirement elicitation
Requirement analysis
Requirement validation
Coding
Functional requirements describe:
How the system should behave
Performance measures
Coding practices
Testing frameworks
Non-functional requirements include:
Reliability, performance, security
User login function
Payment gateway
Data entry screen
Requirement validation ensures:
Requirements meet customer needs
Testing is eliminated
Debugging is reduced
Cost is minimized
Requirement specification is documented in:
SRS (Software Requirement Specification)
Design Document
Source Code
Test Case
A good requirement must be:
Ambiguous
Testable
Incomplete
Inconsistent
Which requirement model is user-centric?
Use case model
ER diagram
Flowchart
Pseudocode
Traceability matrix is used for:
Mapping requirements to design/test
Debugging
Deployment
Code compilation
Requirement creep refers to:
Uncontrolled changes in requirements
Debugging
System maintenance
Prototype building
The first step in requirement engineering is:
Requirement elicitation
Validation
Specification
Testing
Requirement conflicts are resolved during:
Requirement analysis
Deployment
Debugging
Maintenance
A requirement that specifies response time belongs to:
Non-functional requirement
Functional requirement
Use case
Debugging
Requirement gathering is also called:
Requirement elicitation
Requirement specification
Requirement validation
Requirement design
The main goal of requirement gathering is:
Collect accurate customer needs
Debug code
Test modules
Compile software
Which of the following is NOT a requirement gathering technique?
Interviews
Questionnaires
Coding
Brainstorming
Observation as a requirement gathering technique is useful for:
Understanding current processes
Debugging errors
Testing software
Deployment
Stakeholders are:
Only programmers
Anyone affected by the system
Only testers
Only managers
The key challenge in requirement gathering is:
Communication gap between users and developers
Writing source code
Debugging errors
Testing
Prototyping during requirement gathering helps:
Clarify unclear requirements
Replace documentation
Debug software
Test only
Which gathering technique is most suitable for large groups?
Brainstorming
Interview
Observation
Coding
Ethnography in requirement gathering involves:
Immersing in the user's environment
Debugging
Testing
Deployment
Requirement workshops are also known as:
Joint Application Development (JAD)
Debugging sessions
Testing workshops
Deployment sessions
The biggest risk in poor requirement gathering is:
Project failure
Faster coding
Increased debugging
Better testing
Document created after requirement gathering:
Requirement specification
Test case
Deployment plan
Debugging log
A use case represents:
A sequence of interactions between user and system
A debugging technique
A test case
A design diagram
The main elements of a use case are:
Actor, system, interaction
Code, debug, compile
User, test, deploy
Requirement, design, test
Actors in a use case can be:
Human users or external systems
Only programmers
Only end-users
Only databases
The primary diagram for use cases is:
UML Use Case Diagram
Flowchart
ER Diagram
DFD
A use case scenario describes:
A specific instance of system interaction
Source code
Debugging steps
Testing plan
Which is NOT part of a use case description?
Preconditions
Postconditions
Coding syntax
Main flow
An "extend" relationship in use cases means:
Optional behavior extending a base use case
Compulsory sequence
Debugging
Deployment
An "include" relationship in use cases represents:
Mandatory sub-use case reuse
Debugging
Prototyping
Testing
Which of the following best represents a use case?
"User logs in to the system"
"User writes code in Java"
"System compiles the program"
"Database is created"
Use cases are mainly used in which phase?
Requirement analysis
Coding
Debugging
Testing
A use case diagram shows:
Interactions between actors and system
Only data flow
Only code structure
Debugging steps
Use cases help in:
Capturing functional requirements
Capturing non-functional requirements
Coding standards
Debugging errors
Which UML relationship represents inheritance among use cases?
Generalization
Extend
Include
Association
SCRUM is a framework for:
Agile project management
Debugging
Coding
Testing
The time-boxed iteration in Scrum is called:
Sprint
Loop
Cycle
Prototype
Who is responsible for maximizing product value in Scrum?
Product Owner
Scrum Master
Development Team
Stakeholders
Who ensures Scrum principles are followed?
Scrum Master
Product Owner
Stakeholders
Developer
The Scrum artifact representing prioritized work is:
Product Backlog
Sprint Backlog
Burndown chart
Kanban board
The Sprint backlog is:
Subset of product backlog chosen for a sprint
The complete backlog
Debugging log
Deployment list
A Kanban board visualizes:
Work in progress
Code compilation
Debugging steps
Test cases
The main focus of Kanban is:
Limiting Work in Progress (WIP)
Debugging
User training
Coding speed
Which Scrum meeting is held daily?
Daily Stand-up
Sprint Retrospective
Sprint Review
Product Planning
Sprint Retrospective focuses on:
Process improvement
Code debugging
Deployment
Requirement gathering
In Kanban, tasks move across columns representing:
Stages of workflow
Debugging steps
Coding lines
Testing tools
Which Scrum event inspects the product increment?
Sprint Review
Daily Stand-up
Retrospective
Planning
