Software Engineering 3 - words/knowledge needed for 11-16 of the "Multible choice"

Question 1

Shortly explain Recovery testing

Answer 1

Recovery testing:

Recovery testing evaluates how well a system can recover from abnormal situations such as crashes, hardware failures, or data corruption.
It confronts the program with failure scenarios to ensure it can restore itself to normal operations or minimize data loss.

Question 2

Shortly explain Security testing

Answer 2

Security testing:

Focuses on assessing the system’s ability to protect against unauthorized access, breaches, or vulnerabilities.
It ensures data confidentiality, integrity, and availability.

Question 3

Shortly explain Stress testing

Answer 3

Stress testing:

Involves testing the system under extreme conditions (e.g., heavy loads, limited resources) to see how it behaves beyond its normal capacity.
While this confronts the system with challenging situations, it is not explicitly about abnormal conditions but rather high loads.

Question 4

Shortly explain Performance testing

Answer 4

Performance testing:

Measures the speed, responsiveness, and stability of the software under various loads.
It focuses on meeting performance requirements rather than handling failures.

Question 5

Shortly explain Usage testing

Answer 5

Usage testing:

Evaluates the software by simulating real-world user scenarios to ensure the application works as expected under normal use.
It does not directly address abnormal conditions.

Question 6

Explain the 4 key elements of product backlog

Answer 6

Key Elements of a Product Backlog:

• Description
  Clearly defines what each item is.
  Includes essential details from the user’s perspective to guide the Development Team.
• Value
  Indicates how much business or user value the item provides.
  Helps prioritize items based on their impact.
• Estimate
  Reflects the effort required by the Development Team to complete each item.
  Used for planning and resource allocation.
• Order (Priority)
  Arranges items in a stacked rank from highest to lowest priority.
  Ensures the team focuses on the most important items first.

Question 7

Explain User stories

Answer 7

User stories are short, simple descriptions of a deliverable told
from the perspective of the user.

Question 8

Explain Epics

Answer 8

Epics are a collection of user stories.

Question 9

Explain the “I” in I.N.V.E.S.T.

Answer 9

• Independent: The story’s completion is not dependent on another
  story.

Question 10

Explain the “N” in I.N.V.E.S.T.

Answer 10

• Negotiable: There is room for discussion about this item.

Question 11

Explain the “V” in I.N.V.E.S.T.

Answer 11

• Valuable: Completing the user story has to deliver value.

Question 12

Explain the “E” in I.N.V.E.S.T.

Answer 12

• Estimable: The Definition of Done must be clear so that the team can give each user story an estimate.

Question 13

Explain the “S” in I.N.V.E.S.T.

Answer 13

• Small: Each user story needs to be able to fit within a planned Sprint.

Question 14

Explain the “T” in I.N.V.E.S.T.

Answer 14

• Testable: A test can be conducted to check that it meets the criteria.

Question 15

Mention the 4 key processes of Product Backlog

Answer 15

Key processes of Product Backlog:
*Description: Each item should have a clear description.
*Value: Items should reflect their business value.
*Prioritization: Items are ordered based on importance.
*Estimation: Effort for each item is estimated.

Question 16

Explain Backlog Refinement

Answer 16

Backlog Refinement is the process of updating and
organizing the Product Backlog.

Question 17

What are the 5 Goals of Backlog Refinement?

Answer 17

Goals of Backlog Refinement:
*Ensure relevant items are included.
*Remove outdated or completed items.
*Prioritize items by value and effort.
*Define clear acceptance criteria for high-priority items.
*Provide effort estimates to aid planning.

Question 18

Mention 5 Scrum benefits

Answer 18

▪ The product is broken down into a set of manageable and
understandable chunks.
▪ Unstable requirements do not hold up progress.
▪ The whole team have visibility of everything and consequently team communication is improved.
▪ Customers see on-time delivery of increments and gain
feedback on how the product works.
▪ Trust between customers and developers is established and a positive culture is created in which everyone expects the project to succeed.

Question 19

Explain Entity-Relationship Diagram (ERD) (in UML:S)

Answer 19

Entity-Relationship Diagram (ERD):
- ERDs are used to model the data relationships in a system.
- It shows entities (objects or tables), their attributes (properties), and relationships (connections) between entities.
- Common in database design to visualize how data will be stored and linked.
- Example: A “Customer” entity relates to “Orders” via a one-to-many relationship.

Question 20

Explain Data Flow Diagram (DFD) (in UML:S)

Answer 20

Data Flow Diagram (DFD):
- DFDs represent the flow of data through a system.
- It shows processes (functions), data stores (files, databases), data flows (arrows), and external entities (users, systems).
- Used to visualize how data is input, processed, and output in a system.
- Example: Data flows from “User” → “Login Process” → “Database.”

Question 21

Explain State Diagram (in UML:S)

Answer 21

State Diagram:
- A State Diagram shows how a system or object transitions between different states based on internal or external events.
- States represent conditions (e.g., “Idle,” “Active,” “Error”).
- Transitions are triggered by events or actions (e.g., “User Logs In”).
- Example: A vending machine transitions from “Waiting” → “Dispensing” → “Idle.”

Question 22

Explain Database Schema (in UML:S)

Answer 22

Database Schema:
- A blueprint of a database that defines its structure.
It includes tables, fields (columns), data types, primary keys, foreign keys, and constraints.
- Represents how data is stored and organized for efficient access.
- Example: A table “Students” with fields: ID (PK), Name, and Age.

Question 23

What is the main focus of Entity-Relationship Diagram (ERD)? (in UML:S)

Answer 23

Relationships between entities

Question 24

What is the main focus of Data Flow Diagram (DFD)? (in UML:S)

Answer 24

The flow of data.

Question 25

What is the main focus State Diagrams? (in UML:S)

Answer 25

State changes due to events.

Question 26

What is the main focus Database Schema (in UML:S)

Answer 26

The physical structure of stored data.

Question 27

Explain Specification-Based Testing / Black Box Testing

Answer 27

Specification-Based Testing / Black Box Testing:
- Focuses on testing functionality of the software without knowledge of its internal code.
- Test cases are derived from specifications, inputs, and expected outputs.
- Example: Testing if a login system works correctly based on valid/invalid credentials.

Question 28

Explain Validation Testing

Answer 28

Validation Testing:
- Ensures the software meets user requirements and expectations.
- Answers the question: “Are we building the right product?”
- Typically performed near the end of the development lifecycle.

Question 29

Explain Verification Testing

Answer 29

Verification Testing:
- Confirms the software meets design and technical specifications.
- Answers the question: “Are we building the product correctly?”
- Involves code reviews, inspections, and white-box testing.

Question 30

Explain Unit Testing

Answer 30

Unit Testing:
- Tests individual components or units of the software in isolation.
- Ensures each function or module works as expected.
- Typically performed by developers using white-box techniques.

Question 31

Stress Testing

Answer 31

Stress Testing:
- Evaluates the software’s behavior under extreme conditions (e.g., high load or heavy data).
- Checks system stability, reliability, and performance limits.
- Example: Testing how a website performs under heavy traffic.

Question 32

Coupling is a Metrics for good code design, explain it

Answer 32

Coupling - Measures the level of dependency between modules. Low coupling is desirable for maintainability.

Question 33

Primitiveness is a Metrics for good code design, explain it

Answer 33

Primitiveness - Refers to designing functions or modules to perform a single, well-defined task.

Question 34

Sufficiency is a Metrics for good code design, explain it

Answer 34

Sufficiency - Ensures the module has all the necessary elements to perform its responsibilities.

Question 35

Completeness is a Metrics for good code design, explain it

Answer 35

Completeness - Ensures the code satisfies all required functionality and design specifications.