If you’ve spent your semester thinking that Object-Oriented Analysis and Design (OOAD) is just “Java with extra steps,” your upcoming exam might be a rude awakening. OOAD is where we stop worrying about how to write a loop and start worrying about how a system actually breathes. It’s the difference between building a shed and architecting a skyscraper.
Below is the exam paper download link
Past Paper On Object – Oriented Analysis And Design For Revision
Above is the exam paper download link
In an exam, the professor isn’t looking for a perfect piece of code; they are looking for a logical blueprint. They want to see if you can take a messy, real-world problem—like a hospital management system or an e-commerce platform—and break it down into objects, classes, and interactions that actually make sense.
To help you move from a “coder” to a “designer,” we’ve tackled the big-picture questions that define the OOAD syllabus. To wrap up your study session, you can download our full OOAD revision past paper at the bottom of this page.
Your OOAD Revision: The Questions That Define the Grade
Q: What is the real difference between Analysis and Design? This is the most common starting point. Analysis is about “doing the right thing.” You are looking at the requirements to understand what the system needs to do. Design is about “doing the thing right.” It’s where you take those requirements and decide how the technical components will fit together to solve the problem.
Q: Why do examiners love “Use Case Diagrams” so much? Because they show the “Who” and the “What” without getting bogged down in the “How.” A Use Case Diagram identifies the Actors (users or external systems) and the Use Cases (the goals they want to achieve). If you can’t draw a clear Use Case Diagram, you don’t understand the project’s scope.
Q: What is the “Is-A” vs. “Has-A” relationship? This is the litmus test for your understanding of Inheritance and Composition. If a “Car” is a “Vehicle,” you use inheritance. If a “Car” has an “Engine,” you use composition. In an exam, choosing inheritance when you should have used composition is a one-way ticket to losing marks for “low cohesion.”
Q: What are the “SOLID” principles, and do I need to memorize them? You don’t just need to memorize them; you need to breathe them. Whether it’s the Single Responsibility Principle (a class should do one thing) or the Open-Closed Principle (software should be open for extension but closed for modification), these are the rules that prevent “spaghetti design.” Expect at least one essay question on these.
Strategy: How to Use the Past Paper for Maximum Gain
Don’t just look at the diagrams in the PDF and think they look “neat.” You need to be able to recreate them from scratch. Here is your revision protocol:
-
The Class Diagram Challenge: Look at a problem description in the past paper. Before looking at the answer, try to identify at least five classes and the relationships (Associations, Aggregations, Generalizations) between them.
-
The Sequence Diagram Flow: Practice drawing how objects talk to each other over time. If a user clicks “Buy,” what happens? Does the
Orderobject talk to theInventoryobject or thePaymentobject first? -
The “Refactoring” Exercise: Look at a provided piece of “bad” design in the paper and explain why it’s bad. Is it too tightly coupled? Does it violate the Liskov Substitution Principle?
Ready to Master System Design?
OOAD is the bridge between a client’s vague idea and a developer’s working reality. It is a visual language that transcends specific programming languages. By working through a past paper, you’ll start to see the recurring patterns that make for “clean” and “maintainable” software.
We’ve curated a comprehensive revision paper that covers everything from Domain Modeling and State Machine Diagrams to Design Patterns like Singleton and Factory.
