Software Engineering Quiz 2: 3 December 2023 (September 2023 term)

1. A

   Requirements gathering

2. B

   Design

3. C

   Development

4. D

   Testing

5. E

   Maintenance

1. A

   Strong emphasis on documentation

2. B

   Ability to accommodate changing requirements

3. C

   Faster development with no need for testing

4. D

   Strict adherence to a fixed project plan

1. A

   To ensure the software complies with industry standards and regulations.

2. B

   To identify and fix defects introduced during recent code changes without causing new issues.

3. C

   To test the software's performance under extreme conditions.

4. D

   To test the software against its initial requirements.

1. A

   A form of documentation used for project management

2. B

   A list of tasks assigned to developers

3. C

   A detailed description of how the code is structured

4. D

   A way to express software requirements from an end-user perspective

1. A

   Questionnaires

2. B

   Focus group

3. C

   Documentations

4. D

   Naturalistic observations

1. A

   Write requirements in a technical language to ensure precision.

2. B

   Use ambiguous language to allow for flexibility during development.

3. C

   Ensure that requirements are clear, unambiguous, and understandable by both technical and non-technical stakeholders.

4. D

   Only specify high-level requirements to provide flexibility to developers.

1. A

   Efficiency

2. B

   Consistency

3. C

   Novelty

4. D

   Learnability

1. A

   Low-fidelity paper prototyping

2. B

   Wizard of Oz prototyping

3. C

   High-fidelity interactive prototyping

4. D

   Storyboard prototyping

1. A

   Ensuring that the user interface is visually appealing.

2. B

   Maintaining uniformity in the way similar actions or elements are presented to users.

3. C

   Offering real-time feedback to users during their interactions.

4. D

   Allowing users to easily undo any action they take.

1. A

   To encourage open and collaborative communication among team members.

2. B

   To provide a quick and rough estimate of project costs.

3. C

   To combine estimates from multiple experts to reach a consensus estimate.

4. D

   To create a detailed work breakdown structure.

1. A

   Transferring the risk to a third party, such as an insurance company.

2. B

   Eliminating the risk entirely from the project.

3. C

   Implementing actions to reduce the impact or probability of a risk occurring.

4. D

   Ignoring the risk and hoping it won't affect the project.

1. A

   Scrum Master

2. B

   Product Owner

3. C

   Stakeholder

4. D

   Team Lead

1. A

   To provide status updates to upper management.

2. B

   To discuss long-term project planning.

3. C

   To identify and address impediments to progress.

4. D

   To review the final deliverables of the sprint.

1. A

   To automatically generate code from design diagrams.

2. B

   To assist developers in understanding and comprehending complex software designs.

3. C

   To simulate user interactions with the software.

4. D

   To identify and fix design flaws in existing software.

1. A

   Class diagram

2. B

   Sequence diagram

3. C

   State diagram

4. D

   Use case diagram

1. A

   A specific instance of a class.

2. B

   A module, package, or subsystem that encapsulates related functionality.

3. C

   A sequence of method calls.

4. D

   A control flow within a system.

Select all that apply.

1. A

   Input manipulation

2. B

   Reverse strategy

3. C

   Forward strategy

4. D

   Blackbox debugging

Select all that apply.

1. A

   Cyclomatic complexity

2. B

   Raw metrics

3. C

   Halstead’s metrics

4. D

   Code smell

Select all that apply.

1. A

   Debugging is only necessary during the initial development phase.

2. B

   Debugging involves identifying and fixing issues or defects in the code.

3. C

   Debugging can be done without the use of debugging tools or breakpoints.

4. D

   Code may run correctly during debugging but fail in production.

Select all that apply.

1. A

   The relationship between class Payment and class Order is association.

2. B

   The relationship between class Payment and class UPIPayment is composition.

3. C

   The relationship between class Order and class Item is inheritance.

4. D

   The relationship between class Payment and class CardPayment is inheritance.

Select all that apply.

1. A

   Singleton

2. B

   Factory Method

3. C

   Adapter

4. D

   Decorator

5. E

   Observer

Select all that apply.

1. A

   Factory design pattern

2. B

   Builder design pattern

3. C

   Adapter design pattern

4. D

   Facade design pattern