Software Engineering: Basic Quiz!

2.

One can choose the Waterfall Model if the project development schedule is tight.

True
False

Correct Answer

A. False

Explanation

The Waterfall Model is a sequential and linear approach to project management, where each phase is completed before moving onto the next. This model is not suitable for projects with tight schedules because it does not allow for flexibility or adaptation. The Waterfall Model requires extensive planning and documentation upfront, which can be time-consuming. In contrast, Agile methodologies are better suited for projects with tight schedules as they allow for iterative development, frequent feedback, and the ability to adapt to changing requirements. Therefore, the given statement is false.

Rate this question:

1

3.

Which of the following is not the characteristic of software?

Software does not wear out
Software is flexible
Software is not manufactured
Software is always correct

Correct Answer

A. Software is always correct

Explanation

The given answer states that "Software is always correct" is not a characteristic of software. This is because software can have bugs or errors, and it may not always function as intended. Software development involves testing and debugging to identify and fix these issues, making it clear that software is not always correct.

Rate this question:

4.

Waterfall model is not suitable for?

Small Projects
Complex Projects
Accommodating change
None of Above

Correct Answer

A. Accommodating change

Explanation

The waterfall model is a sequential and linear approach to software development, where each phase must be completed before moving on to the next. This makes it difficult to accommodate changes or modifications during the development process. Any changes requested after the initial planning phase would require going back to the beginning and repeating all the previous steps. Therefore, the waterfall model is not suitable for accommodating change in the project requirements.

Rate this question:

5.

One of the developers myth is:

Changes are easy to accommodate
A general statement of objectives from the customer is all that is needed to begin a software project
Once a program is written, our work is finished
We have all the standards available, that will be sufficient to develop a program.

Correct Answer

A. Once a program is written, our work is finished

Explanation

This statement reflects a common myth among developers that once they have written a program, their work is complete. However, in reality, software development is an ongoing process that involves maintenance, bug fixes, updates, and improvements even after the initial program is written. The development cycle continues as new requirements arise, technology evolves, and user feedback is received. Therefore, considering the program as a finished product after its initial creation is a misconception.

Rate this question:

6.

What is the final result of the requirements analysis and specifications phase?

Data flow diagram
SRS Document
Coding the project
User Manual

Correct Answer

A. SRS Document

Explanation

The final result of the requirements analysis and specifications phase is the SRS (Software Requirements Specification) Document. This document outlines the detailed requirements and specifications for the project, including the functional and non-functional requirements, system architecture, user interface, and any other relevant information. It serves as a reference for the development team to understand and implement the project accurately. The SRS Document is crucial for ensuring that the final product meets the client's expectations and serves as a foundation for the subsequent phases of the software development lifecycle.

Rate this question:

7.

Which of the following is the most important phase of the Software Development Life Cycle (SDLC)?

Requirements analysis
Coding
Testing
Designing

Correct Answer

A. Requirements analysis

Explanation

Requirements analysis is the most important phase of the Software Development Life Cycle (SDLC) because it involves gathering and understanding the needs and expectations of the stakeholders. It is during this phase that the project scope is defined, and the requirements are documented and analyzed. This phase sets the foundation for the entire development process, as it helps in identifying the goals, constraints, and functionalities of the software system. Without proper requirements analysis, the development team may not be able to deliver a product that meets the expectations of the stakeholders, leading to project failure.

Rate this question:

8.

What is a prototype?

Mini model of existing system
Mini model of the proposed system
Working model of existing system.
None of the above.

Correct Answer

A. Mini model of the proposed system

Explanation

A prototype is a mini model of the proposed system. It is a preliminary version that is created to test and evaluate the design and functionality of the system before it is fully developed. The prototype allows stakeholders to visualize and understand the system's features, identify potential issues, and make necessary modifications. It helps in gathering feedback and making improvements early in the development process, ultimately leading to a more effective and efficient final product.

Rate this question:

9.

Which of the following is not a named phase in the software development life cycle?

Assessment
Maintenance
Development
Testing

Correct Answer

A. Assessment

Explanation

Assessment is not a named phase in the software development life cycle. The software development life cycle typically consists of phases such as planning, requirements gathering, design, development, testing, deployment, and maintenance. Assessment, on the other hand, is not a specific phase in this cycle. It may be a part of the planning or requirements gathering phase, but it is not a distinct phase on its own.

Rate this question:

10.

RAD Model was proposed by?

IBM
Motorola
Microsoft
Lucent Technologies

Correct Answer

A. IBM

Explanation

The RAD (Rapid Application Development) model was proposed by IBM. The RAD model is an iterative and incremental software development approach that focuses on quick prototyping and feedback from users. It aims to reduce the development time and deliver software in a shorter span by involving users in the development process. IBM's proposal of the RAD model has greatly influenced the software development industry, leading to faster and more efficient development cycles.

Rate this question:

Software Engineering: Basic Quiz!

Which model doesn’t allow defining requirements early in the cycle?

Quiz Preview

One can choose the Waterfall Model if the project development schedule is tight.

Which of the following is not the characteristic of software?

Waterfall model is not suitable for?

One of the developers myth is:

What is the final result of the requirements analysis and specifications phase?

Which of the following is the most important phase of the Software Development Life Cycle (SDLC)?

What is a prototype?

Which of the following is not a named phase in the software development life cycle?

RAD Model was proposed by?