Wayground logo

Free Printable Worksheets

Font size

S
M
L
XL
Worksheets

Software Development Practices Quiz

Total questions: 46

Worksheet time: 23mins

Name
Class
Date
1.

What is the importance of planning & requirement analysis phase?

a)
It allows the team to begin development immediately without defining scope, budget, or timelines.
b)
It focuses mainly on selecting technologies while postponing stakeholder communication and risk assessment.
c)
It guarantees the project will avoid all changes by eliminating the need for reviews or requirement updates.
d)
It ensures the right product is built within the agreed scope, budget, and timeline, while reducing misunderstandings, rework, costs, and project risks.
2.

What is the importance of design phase?

a)
It is important because it reduces errors and costs, clarifies requirements, guides development, and helps ensure the final product meets user and business needs.
b)
It is important because it focuses mainly on aesthetics and minimizes planning for development.
c)
It is important because it increases flexibility by avoiding documentation, testing, and cost considerations.
d)
It is important because it allows development to begin without defining requirements or user needs.
3.

Which phase of the SDLC involves gathering and understanding stakeholder needs?

a)

Implementation

b)

Testing

c)

Requirement Analysis

d)

Deployment

4.

What is the primary goal of the Software Development Life Cycle (SDLC)?

a)

Produce a software that meets or exceeds customer expectations

b)

Maximizing profit

c)

Developing software as quickly as possible

d)

Reducing development costs

5.

What are the popular SDLC models in industry now?

a)
Popular SDLC models include Waterfall, V-Model, Spiral, and Prototype, with Waterfall and V-Model currently dominating software products.
b)
Popular SDLC models include Agile (especially Scrum and Kanban), DevOps with CI/CD, iterative and incremental development, Waterfall, V-Model, and Spiral. Agile and DevOps are currently the most widely adopted for software products.
c)
Popular SDLC models include Prototyping, RAD, Big Bang, and Code-and-Fix, with Big Bang being the most widely adopted.
d)
Popular SDLC models include Scrum, Kanban, Lean, and Six Sigma, while traditional models are rarely used in industry.
6.

What is waterfall model?

a)
The waterfall model is an agile method that delivers small software increments through frequent customer feedback and short sprints.
b)
The waterfall model is a linear software development approach involving distinct sequential phases such as requirements, design, implementation, testing, deployment, and maintenance.
c)
The waterfall model is a risk-driven process that prioritizes rapid prototyping before defining detailed requirements and design.
d)
The waterfall model is an iterative approach where requirements and phases are continuously revised throughout development.
7.

List ONE (1) advantage of waterfall model.

a)
It requires minimal planning because requirements can change at any time.
b)
It delivers a working product continuously throughout the development process.
c)
It allows changes to be made easily during every development phase.
d)
It is simple to understand and manage because each phase is completed sequentially.
8.

List ONE (1) disadvantage of waterfall model.

a)
Changes are easy and inexpensive to make after a phase is completed.
b)
Customer feedback is continuously incorporated throughout development.
c)
Changes are difficult and costly to make after a phase is completed.
d)
Testing begins early and occurs throughout every development phase.
9.

Define Agile SDLC model.

a)
The Agile SDLC model is an iterative and incremental approach to software development in which teams deliver working software in short cycles, continuously incorporating customer feedback and adapting to changing requirements.
b)
The Agile SDLC model uses fixed requirements and discourages changes once the development process has started.
c)
The Agile SDLC model focuses on delivering the entire software product at the end of development without customer involvement.
d)
The Agile SDLC model follows a linear process in which each development phase is completed once before the next begins.
10.

In agile, which TWO (2) activities are done concurrently?

a)

Development

b)

Testing

c)

Design

d)

Deploy

11.

What is Agile Manifesto?

a)
The Agile Manifesto is a formal project management framework with defined phases, schedules, and documentation requirements.
b)
The Agile Manifesto is a set of coding standards focused on improving software architecture, testing, and technical performance.
c)
The Agile Manifesto is a twelve-step process that prioritizes detailed planning, fixed requirements, and strict adherence to project plans.
d)
The Agile Manifesto is a statement of four values and twelve principles for developing software iteratively and adaptively. It prioritizes individuals and interactions, working software, customer collaboration, and responding to change.
12.

List any FOUR (4) principles of Agile Manifesto?

a)

Customer collaboration, responding to change, frequent delivery, and welcoming changing requirements

b)

Detailed documentation, fixed requirements, annual delivery, and strict contracts

c)

Individual competition, fixed plans, centralized decisions, and limited customer feedback

d)

Long release cycles, extensive upfront planning, fixed scope, and formal approval gates

13.

List any TWO (2) popular agile methods.

a)

Scrum and Kanban

b)

Waterfall and Spiral

c)

PRINCE2 and Six Sigma

d)

Critical Path and Gantt Chart

14.

List any THREE (3) advantages of agile model.

a)

Fixed requirements, no customer involvement, and lengthy development cycles

b)

Extensive documentation, rigid planning, and delayed testing

c)

Flexibility to change, frequent delivery, and continuous customer feedback

d)

Higher risk, less collaboration, and limited customer feedback

15.

List any TWO (2) disadvantages of agile model.

a)

Faster delivery and improved collaboration among team members

b)

Flexible requirements and continuous customer feedback

c)

Early testing and frequent delivery of working software

d)

Less predictable final cost and scope, and requires frequent customer involvement

16.

Define DevOps model.

a)
The DevOps model is a software development approach that unifies development and IT operations to deliver software faster and more reliably through collaboration, automation, continuous integration, continuous delivery, and monitoring.
b)
The DevOps model separates development and IT operations to deliver software through independent planning, manual testing, and scheduled releases.
c)
The DevOps model is a software development method that prioritizes coding speed while minimizing collaboration, automation, and operational monitoring.
d)
The DevOps model is a hardware management approach that focuses on infrastructure procurement, documentation, and long-term maintenance.
17.

List the SEVEN (7) stages of DevOps life cycle.

a)

Analyze, Design, Code, Test, Debug, Publish, Retire

b)

Plan, Code, Test, Build, Market, Deploy, Archive

c)

Plan, Design, Develop, Document, Review, Market, Maintain

d)

Plan, Code, Build, Test, Release, Deploy, Operate

18.

List TWO (2) advantages of DevOps model.

a)

Longer development cycles and increased communication barriers

b)

More manual processes and slower deployment

c)

Faster software delivery and improved collaboration between development and operations teams

d)

Less automation and reduced software reliability

19.

List TWO (2) advantages of DevOps model.

a)

Faster delivery of features

b)

More stable operating environments

c)

Improved communication and collaboration

d)

More time to innovate (rather than fix/maintain)

20.

List TWO (2) disadvantages of DevOps model.

a)

DevOps professionals or expert developers are less available

b)

Expensive

c)

Adopting DevOps technology is hard to manage in a short time

d)

Lack of DevOps knowledge can be a problem in the continuous integration of automation projects

21.

List any THREE (3) agile tools.

a)

Agilo

b)

JIRA

c)

Trello

d)

GitHub

e)

Kanban

22.

List any THREE (3) DevOps tools.

a)

Docker

b)

Jenkins

c)

Git

d)

Puppet

e)

Ansible

23.

What is requirement gathering?

a)
Requirement gathering is the process of implementing and testing the features and functions of a project or system.
b)
Requirement gathering is the process of designing the technical architecture and components for a project or system.
c)
Requirement gathering is the process of documenting the completed work and measuring project outcomes.
d)
Requirement gathering is the process of collecting and defining the needs, expectations, and constraints of stakeholders for a project or system.
24.

Who are the stakeholders of a software project. Give TWO (2) examples.

a)

Compilers and databases

b)

Operating systems and networks

c)

Source code and algorithms

d)

Customers and project managers

25.

Differentiate functional and non-functional requirements.

a)
Functional and non-functional requirements both describe what the system does, differing only in whether they apply to users or administrators.
b)
Functional requirements define project limitations and quality standards, while non-functional requirements describe features such as logging in or generating reports.
c)
Functional requirements describe system performance, security, and reliability, while non-functional requirements specify user actions and business processes.
d)
Functional requirements state what the system must do, such as allowing users to log in or generate reports. Non-functional requirements state how well or under what constraints it must operate, such as performance, security, usability, reliability, and scalability.
26.

Classify the following requirements into functional requirement and non-functional requirement.

a)
Unable to classify the requirements because the list of requirements is missing.
b)
Classify the requirements based on their implementation cost.
c)
Unable to classify the requirements because they lack technical details.
d)
All listed requirements are functional requirements.
27.

Between Business Requirement and Performance Requirement, which one is more crucial and why?

a)
Performance requirements are more crucial because they determine system speed, while business requirements only describe general objectives.
b)
Both requirements are equally crucial because neither can influence the success of the solution without completely replacing the other.
c)
Business requirements are less crucial because technical performance alone determines whether the solution is successful.
d)
Business requirements are generally more crucial because they establish what must be achieved and why. However, performance requirements are essential to ensure the solution meets those goals effectively.
28.

List FOUR (4) types of external interface requirements.

a)

User interface

b)

Hardware interface

c)

Software interface

d)

Communications interface

29.

Which requirement must be specified when the system is going to be integrated with other components? State another objective of this requirement.

a)
Interface requirements; another objective is to ensure interoperability and compatibility between the system and the integrated components.
b)
Security requirements; another objective is to protect data and prevent unauthorized access to the system.
c)
Performance requirements; another objective is to ensure efficient processing and resource utilization within the system.
d)
Usability requirements; another objective is to ensure the system is easy to learn and operate by its users.
30.

State ONE (1) advantage of the following users’ requirement gathering method: User survey.

a)
It allows requirements to be gathered only from technical staff.
b)
It can collect requirements from a large number of users efficiently.
c)
It provides detailed observations of users’ daily tasks.
d)
It requires extensive interviews with every user.
31.

State ONE (1) advantage of the following users’ requirement gathering method: User interview.

a)
They require very little time from the users.
b)
They provide detailed and in-depth information about users’ needs.
c)
They provide quick and simple answers from all users.
d)
They eliminate the need for follow-up questions.
32.

State ONE (1) advantage of the following users’ requirement gathering method: User existing documents review.

a)
It eliminates the need to examine documents because users provide all the information directly.
b)
It provides new information even when no existing documents are available.
c)
It saves time and cost since the required information is already documented.
d)
It requires more time and cost because the information must be collected from users.
33.

State ONE (1) advantage of the following users’ requirement gathering method: User existing software review.

a)
It replaces the need to consult users, reducing communication during requirements gathering.
b)
It guarantees all user needs are included without requiring further analysis or validation.
c)
It focuses only on software faults, avoiding the identification of features relevant to user needs.
d)
It helps identify existing features that meet user needs, reducing time and effort in gathering requirements.
34.

State ONE (1) advantage of the following users’ requirement gathering method: Study user-supplied documentation.

a)
It provides brief and general information about possible future processes and requirements.
b)
It eliminates the need to consult users about their current processes and requirements.
c)
It allows developers to determine requirements without reviewing existing user procedures.
d)
It provides detailed and accurate information about the users’ current processes and requirements.
35.

What is SRD and what are the main components of it?

a)
An SRD (System Risk Document) evaluates potential project threats. Its main components include risk identification, probability ratings, impact assessments, mitigation plans, contingency procedures, monitoring activities, and escalation criteria.
b)
An SRD (Software Resource Directory) catalogs an organization’s development assets. Its main components include hardware inventories, software licenses, team assignments, budget estimates, security policies, and procurement procedures.
c)
An SRD (System Release Description) outlines a product’s deployment plan. Its main components include release schedules, versioning, installation procedures, rollout strategies, maintenance plans, and support contacts.
d)
An SRD (Software Requirements Document) describes a system’s requirements. Its main components typically include: introduction and purpose, scope, stakeholders, functional requirements, non-functional requirements, user and system interfaces, constraints, assumptions and dependencies, use cases, and acceptance criteria.
36.

What is URD and what are the main components of it?

a)
The main components are: purpose and scope; user and stakeholder profiles; functional requirements; non-functional requirements such as performance, security, and usability; use cases or user stories; assumptions and constraints; priorities; acceptance criteria; and approval or sign-off.
b)
The main components are: product vision; market analysis; team responsibilities; architecture diagrams; implementation tasks; quality metrics; support procedures; financial forecasts; and change logs.
c)
The main components are: business objectives; customer demographics; interface designs; source code; testing scripts; hardware requirements; vendor contracts; training plans; and release notes.
d)
The main components are: project goals; organizational charts; coding standards; database schemas; deployment procedures; technical specifications; budget estimates; development timelines; and maintenance schedules.
37.

What is a requirement checklist?

a)
A requirement checklist is a structured list used to document, track, and confirm that all project or product requirements have been identified and fulfilled.
b)
A requirement checklist is a summary document used to evaluate the financial performance of a completed product.
c)
A requirement checklist is a detailed schedule used to assign tasks and deadlines throughout a project.
d)
A requirement checklist is an unstructured set of ideas used to brainstorm possible project features.
38.

In a software development team, who designs the typography of the system?

a)

Product owner

b)

Team Lead

c)

Tech Lead

d)

Project manager

e)

UI Designer

39.

List THREE (3) common types of UIs.

a)

Graphical user interface

b)

Command line interface

c)

Voice-enabled interface

d)

Sound-enabled interface

40.

How can a storyboard be used in a software development process?

a)
A storyboard is used to assign programming tasks and track project deadlines, ensuring the team completes each feature on schedule.
b)
A storyboard is used to document database structures and server configurations, helping developers optimize system performance.
c)
A storyboard is used to visualize and plan user interactions and screen flow before coding, helping teams clarify requirements, improve usability, and guide implementation.
d)
A storyboard is used to write and test the final code before development begins, ensuring all functions work correctly.
41.

What are the advantages of developing storyboard design for software applications?

a)
Storyboard design clarifies user journeys, improves communication among stakeholders, identifies usability issues early, reduces development costs and rework, and provides a clear guide for implementation.
b)
Storyboard design focuses only on visual appearance, reduces stakeholder involvement, postpones testing, increases rework, and restricts implementation flexibility.
c)
Storyboard design limits user feedback, delays communication, overlooks usability issues, increases development costs, and offers little implementation guidance.
d)
Storyboard design documents technical code structures, eliminates user research, complicates collaboration, extends development timelines, and replaces implementation planning.
42.

The following figure shows ___________ page layout structure.

a)

linear

b)

hierarchical

c)

non-linear

d)

composite

43.

Explain the purpose of using a Gantt Chart

a)
A Gantt chart is used to record employee attendance, assign salaries, and manage workplace schedules.
b)
A Gantt chart is used to calculate project budgets, allocate funding, and approve financial expenses.
c)
A Gantt chart is used to design product layouts, create visual themes, and organize presentation materials.
d)
A Gantt chart is used to plan, schedule, and monitor project activities, helping teams track timelines, dependencies, and progress.
44.

What are not elements in a simple use case diagram.

a)

Actors

b)

Use case

c)

System boundary

d)

Technical details of system

45.

Who’s the main user of Unified Modeling Language? And what do they use it for.

a)

Helpdesk

b)

UIUX designers

c)

Actors

d)

Software developers or programmers

46.

Which information can be represented using a Gantt chart?

a)

Programming code, variables, and functions

b)

Database tables, records, and relationships

c)

Tasks, their durations, start and end dates, and progress

d)

Network devices, IP addresses, and protocols