Quiz one

1. 1. What is the fundamental difference between software engineering and general software development?

• Software engineering focuses on the systematic approach to software development.

• General software development is faster than software engineering.

• Software engineering does not consider user requirements.

• General software development is less costly.

2. Define "software" in the context of software engineering.

• Hardware components of a computer.

• Computer programs, data, and documentation.

• User interfaces of applications.

• Algorithms used in programming.

Which of the following is NOT an essential attribute of good software?

• Maintainability

• Efficiency

• Complexity

• Reliability

Give an example of a software product classified as "system software."

• Microsoft Word

• Windows operating system

• Adobe Photoshop

• Google Chrome

5. 5. What is the primary goal of software design?

• Writing code quickly

• Producing detailed documentation

• Creating a plan for coding

• Defining a software solution that meets requirements

6. 6. What does the SDLC acronym stand for in the context of software engineering?

• Software Design and Lifecycle

• System Development Lifecycle

• Software Development and Life Cycle

• System Design and Lifecycle

What is software?

• The physical components of a computer

• Instructions that tell a computer what to do

• The data and information stored on a computer

• The electrical circuits inside a computer

Which phase of the software development life cycle (SDLC) involves coding, testing, and debugging the software?

• Requirements Analysis

• Design

• Implementation

• Maintenance

During which SDLC phase are software specifications and architecture designed, including decisions on technology, database structure, and system components?

• Testing Phase

• Maintenance Phase

• Design Phase

• Deployment Phase

What is the primary objective of the "Maintenance Phase" in the SDLC?

• To create the initial version of the software

• To identify and address issues that arise after the software is in use

• To gather requirements from stakeholders

• To design the software's user interface