Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
618 views2 pages

Object-Oriented Design Principle Violations

The document discusses five principles of object-oriented design: abstraction, encapsulation, decomposition and modularization, coupling and cohesion, and sufficiency, completeness and primitiveness. It then presents ten scenarios and asks which design principle(s) are violated in each scenario. The principles relate to proper abstraction and encapsulation of code, separation of concerns through modularization, loose coupling and strong cohesion of modules, and designs that are simple, complete and sufficient.

Uploaded by

programing master
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
618 views2 pages

Object-Oriented Design Principle Violations

The document discusses five principles of object-oriented design: abstraction, encapsulation, decomposition and modularization, coupling and cohesion, and sufficiency, completeness and primitiveness. It then presents ten scenarios and asks which design principle(s) are violated in each scenario. The principles relate to proper abstraction and encapsulation of code, separation of concerns through modularization, loose coupling and strong cohesion of modules, and designs that are simple, complete and sufficient.

Uploaded by

programing master
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Software Engineering(CE/IT602)

Practical-4

Objective: Identify the design principle that is being violated in relation to the
given scenario.
Note: A good object oriented design not only meets the specified requirements but
also addresses implicit requirements. There are five design principles which
address most of the implicit requirements:

1.Abstraction: Focus on solving a problem by considering the relevant details


and ignoring the irrelevant.

2.Encapsulation ​Wrapping the internal details, thereby making these details


inaccessible. Encapsulation separates interface and implementation, specifying
only the public interface to the clients, hiding the details of Implementation.

3.Decomposition and Modularization: ​Dividing the problem into


smaller, independent, interactive subtasks for placing different functionalities in
different components.

4.Coupling & Cohesion: ​Coupling is the degree to which modules are


dependent on each other. Cohesion is the degree to which a module has a single,
well defined task or responsibility. A good design is one with loose coupling and
strong cohesion.

5.Sufficiency, Completeness and Primitiveness: ​Design should


ensure the completeness and sufficiency with respect to the given specifications in
a very simple way as possible.

1
Problem: Which of the following design principle(s) have been violated in the
following scenarios?
1. Abstraction
2. Decomposition and Modularization
3. Coupling & Cohesion
4. Encapsulation
5. Sufficiency, Completeness and Primitiveness
6. All

No. Description Principle Violated

1 Important information of a module is directly


accessible by other modules

2 Too many global variables in the program after


implementing the design

3 Code breaks in unexpected places

4 Unfulfilled requirements in the code after the design


has been implemented

5 Cyclic dependency among classes

6 Huge class doing too many unrelated


operations

7 Several un-related functionalities/tasks are carried


out by a single module

8 All data of all classes in public

9 Design resulting in spaghetti code

10 An algorithm documented as part of design is not


understandable by the programmers

You might also like