OOP Exam UPDATED ACTUAL Exam
Questions and CORRECT Answers
Why did software development evolve to consider multiple stakeholders? - CORRECT
ANSWER - As software became integral to business and user activities, balancing
conflicting needs of project managers, developers, and users became crucial for sustainable and
effective software design.
What historical inefficiencies led to better integration of design and architecture processes? -
CORRECT ANSWER - The separation of design and architecture caused misalignments,
making software impractical or hard to use. Integration emerged to address these inefficiencies.
What problem does considering different stakeholders in software address? - CORRECT
ANSWER - It resolves conflicts among priorities, such as speed vs. stability, by aligning
goals to create software that meets diverse needs.
What are the signs of bad software architecture? - CORRECT ANSWER - Rigidity,
fragility, immobility, and causality, all indicating inefficiency, difficulty in modification, and
instability.
How does software architecture address scalability and maintainability? - CORRECT
ANSWER - By using modular designs, abstraction, and principles like the Open-Closed
Principle and Dependency Inversion, ensuring adaptability and clarity.
What strategies balance developer, manager, and user interests? - CORRECT ANSWER -
Automating processes for developers, ensuring modifiability and stability for managers, and
designing intuitive, fast interfaces for users.
What are some trade-offs in addressing stakeholders' needs? - CORRECT ANSWER -
Balancing quick delivery for managers against stable environments for developers can lead to
compromises in quality or speed.
,Why might stakeholder-driven architecture not always be ideal? - CORRECT ANSWER -
It risks overemphasis on one group's needs, leading to neglect of others, e.g., focusing too much
on user interface while ignoring backend scalability.
When is stakeholder-driven architecture particularly effective? - CORRECT ANSWER -
In large-scale projects where diverse perspectives ensure comprehensive design, balancing
usability, performance, and maintainability.
When might focusing on stakeholders' perspectives fail? - CORRECT ANSWER - In small
projects with limited resources, where over-accommodation could overcomplicate the design.
What makes software 'good' for users? - CORRECT ANSWER - Reliable, fast, visually
appealing, and intuitive interfaces that meet functional needs seamlessly.
What makes software 'good' for developers? - CORRECT ANSWER - Modern tools,
readable and maintainable code, and environments that minimize repetitive tasks through
automation.
What makes software 'good' for project managers? - CORRECT ANSWER - Predictability,
scalability, and ease of modification for future updates or features.
What is the Open-Closed Principle, and why is it critical? - CORRECT ANSWER - It
ensures that software entities are open for extension but closed for modification, enabling
scalability without risking existing functionality.
How does the Dependency Inversion Principle reduce stakeholder conflicts? - CORRECT
ANSWER - By decoupling high-level policies from low-level details, it ensures changes in
implementation don't disrupt overall system logic.
What risks come with neglecting long-term architectural planning? - CORRECT
ANSWER - Accumulation of technical debt, reduced scalability, and increased
maintenance costs.
,How can conflicts between developers and project managers be mitigated? - CORRECT
ANSWER - By involving developers early in architectural decisions and maintaining
transparent timelines and expectations.
What is 'rigidity' in software? - CORRECT ANSWER - Rigidity means software is hard to
change because its parts are tightly connected.
How does 'rigidity' impact software maintenance? - CORRECT ANSWER - It makes
updates risky, as changes can break existing features.
What is 'fragility' in software? - CORRECT ANSWER - Fragility occurs when a small
change causes problems in unrelated parts of the system.
How does 'fragility' appear in software? - CORRECT ANSWER - It shows a lack of
separation between components.
What is 'immobility' in software? - CORRECT ANSWER - Immobility means software
parts can't be reused due to poor design.
Why is 'immobility' a problem? - CORRECT ANSWER - It increases time and effort
needed to develop new features.
What is 'causality' in software? - CORRECT ANSWER - Causality means overly complex
processes that force developers to use shortcuts or workarounds.
How does 'causality' harm software? - CORRECT ANSWER - It creates inconsistent and
unmanageable workflows.
Why did developers focus on diagnosing bad software symptoms? - CORRECT
ANSWER - To address problems with systems that were hard to scale, change, or
maintain.
, What historical issue highlighted 'rigidity'? - CORRECT ANSWER - Legacy systems that
couldn't adapt to modern needs.
What does identifying 'rigidity' help fix? - CORRECT ANSWER - It stops tightly
connected code from blocking future changes.
Why is solving 'fragility' important? - CORRECT ANSWER - It prevents small changes
from causing widespread system failures.
How does resolving 'immobility' improve software? - CORRECT ANSWER - It makes
components reusable and easier to work with.
What reduces software rigidity? - CORRECT ANSWER - Modular design and limiting
direct dependencies.
How can fragility be reduced? - CORRECT ANSWER - By creating clear boundaries
between software parts.
What approach avoids immobility? - CORRECT ANSWER - Designing for abstraction
and reuse from the start.
What is the risk of too much abstraction in software? - CORRECT ANSWER - It can
make the system overly complex and slow.
What problems can arise when fixing rigidity? - CORRECT ANSWER - Changes may
introduce new bugs or unintended side effects.
When is fixing 'fragility' most useful? - CORRECT ANSWER - In systems updated often
or used by many people.
Questions and CORRECT Answers
Why did software development evolve to consider multiple stakeholders? - CORRECT
ANSWER - As software became integral to business and user activities, balancing
conflicting needs of project managers, developers, and users became crucial for sustainable and
effective software design.
What historical inefficiencies led to better integration of design and architecture processes? -
CORRECT ANSWER - The separation of design and architecture caused misalignments,
making software impractical or hard to use. Integration emerged to address these inefficiencies.
What problem does considering different stakeholders in software address? - CORRECT
ANSWER - It resolves conflicts among priorities, such as speed vs. stability, by aligning
goals to create software that meets diverse needs.
What are the signs of bad software architecture? - CORRECT ANSWER - Rigidity,
fragility, immobility, and causality, all indicating inefficiency, difficulty in modification, and
instability.
How does software architecture address scalability and maintainability? - CORRECT
ANSWER - By using modular designs, abstraction, and principles like the Open-Closed
Principle and Dependency Inversion, ensuring adaptability and clarity.
What strategies balance developer, manager, and user interests? - CORRECT ANSWER -
Automating processes for developers, ensuring modifiability and stability for managers, and
designing intuitive, fast interfaces for users.
What are some trade-offs in addressing stakeholders' needs? - CORRECT ANSWER -
Balancing quick delivery for managers against stable environments for developers can lead to
compromises in quality or speed.
,Why might stakeholder-driven architecture not always be ideal? - CORRECT ANSWER -
It risks overemphasis on one group's needs, leading to neglect of others, e.g., focusing too much
on user interface while ignoring backend scalability.
When is stakeholder-driven architecture particularly effective? - CORRECT ANSWER -
In large-scale projects where diverse perspectives ensure comprehensive design, balancing
usability, performance, and maintainability.
When might focusing on stakeholders' perspectives fail? - CORRECT ANSWER - In small
projects with limited resources, where over-accommodation could overcomplicate the design.
What makes software 'good' for users? - CORRECT ANSWER - Reliable, fast, visually
appealing, and intuitive interfaces that meet functional needs seamlessly.
What makes software 'good' for developers? - CORRECT ANSWER - Modern tools,
readable and maintainable code, and environments that minimize repetitive tasks through
automation.
What makes software 'good' for project managers? - CORRECT ANSWER - Predictability,
scalability, and ease of modification for future updates or features.
What is the Open-Closed Principle, and why is it critical? - CORRECT ANSWER - It
ensures that software entities are open for extension but closed for modification, enabling
scalability without risking existing functionality.
How does the Dependency Inversion Principle reduce stakeholder conflicts? - CORRECT
ANSWER - By decoupling high-level policies from low-level details, it ensures changes in
implementation don't disrupt overall system logic.
What risks come with neglecting long-term architectural planning? - CORRECT
ANSWER - Accumulation of technical debt, reduced scalability, and increased
maintenance costs.
,How can conflicts between developers and project managers be mitigated? - CORRECT
ANSWER - By involving developers early in architectural decisions and maintaining
transparent timelines and expectations.
What is 'rigidity' in software? - CORRECT ANSWER - Rigidity means software is hard to
change because its parts are tightly connected.
How does 'rigidity' impact software maintenance? - CORRECT ANSWER - It makes
updates risky, as changes can break existing features.
What is 'fragility' in software? - CORRECT ANSWER - Fragility occurs when a small
change causes problems in unrelated parts of the system.
How does 'fragility' appear in software? - CORRECT ANSWER - It shows a lack of
separation between components.
What is 'immobility' in software? - CORRECT ANSWER - Immobility means software
parts can't be reused due to poor design.
Why is 'immobility' a problem? - CORRECT ANSWER - It increases time and effort
needed to develop new features.
What is 'causality' in software? - CORRECT ANSWER - Causality means overly complex
processes that force developers to use shortcuts or workarounds.
How does 'causality' harm software? - CORRECT ANSWER - It creates inconsistent and
unmanageable workflows.
Why did developers focus on diagnosing bad software symptoms? - CORRECT
ANSWER - To address problems with systems that were hard to scale, change, or
maintain.
, What historical issue highlighted 'rigidity'? - CORRECT ANSWER - Legacy systems that
couldn't adapt to modern needs.
What does identifying 'rigidity' help fix? - CORRECT ANSWER - It stops tightly
connected code from blocking future changes.
Why is solving 'fragility' important? - CORRECT ANSWER - It prevents small changes
from causing widespread system failures.
How does resolving 'immobility' improve software? - CORRECT ANSWER - It makes
components reusable and easier to work with.
What reduces software rigidity? - CORRECT ANSWER - Modular design and limiting
direct dependencies.
How can fragility be reduced? - CORRECT ANSWER - By creating clear boundaries
between software parts.
What approach avoids immobility? - CORRECT ANSWER - Designing for abstraction
and reuse from the start.
What is the risk of too much abstraction in software? - CORRECT ANSWER - It can
make the system overly complex and slow.
What problems can arise when fixing rigidity? - CORRECT ANSWER - Changes may
introduce new bugs or unintended side effects.
When is fixing 'fragility' most useful? - CORRECT ANSWER - In systems updated often
or used by many people.
