CSC/ECE 517 Fall 2007/wiki3 3 ab

Topic

Take the principle of Separation of Responsibility and catalog the information on it available on the Web. Find good descriptions and good, concise, understandable examples. Tell which you consider the best to present to a class.

Introduction

Separation of Responsibility

In Object-Oriented Design (OOD), Separation of Concern is well known as a principle or process of breaking computer program codes into different components that have little coupling with each other and have strong cohesion. Following this principle, a class should have one clearly defined responsibility. In separation of concern, there are two important concepts: Separation of Responsibility and Separation of knowledge (information and environment hiding).

Separation of responsibility states that specific functionality or specific actions are assigned to design components and are not distributed throughout a design [3], in another word, each individual object should have as few responsibilities as possible, ideally one responsibility per object.

Principle of Separation of Responsibility

There are several principles of Separation of Responsibility [1]:

• Single Responsibility Principle (SRP). Different responsibilities should be divided among different objects, in another word, one object should have only one responsibility in ideal situation. We can only say A class should have only one reason to change. We want to focus classes, functions, etc. so that there is only one reason for them to change. This is why many people separate their application into layers. For example, The data access layer provides persistence and re-hydration of business objects. The business layer is all about business rules. And, the presentation layer is only about presenting information to the user. Hopefully a change in one layer won't cause a ripple effect of changes in other layers, or at least, keep the impact to a minimum.[9]
• Encapsulation. One class should be responsible for knowing and maintaining a set of data, even if that data is used by many other classes. In another word, Data should be kept in only one place.
• Expert pattern. The object that contains the necessary data to perform a task should be the object that manipulates the data.
• The Dry principle. Code should not be duplicated. A given functionality should be implemented only in one place in the system.

Example

Java Example

There is an Java example of principle of Separation of responsibility[4].

public void createCustomer(Map requestParameters) {
	Customer customer = new Customer();
	customer.setName = requestParameters.get("name");

	//Check if a customer was already registered with that name
	if (customerService.getCustomerByName(customer.getName()) != null) {
		System.out.println("Customer already exists");
		return;
	}
	customer.setShoppingCart(new ShoppingCart());

	customerService.save(customer);
}

The method name is create. While others viewing the the code will expect to have a create function. But instead it has three functionality, creates a customer, checks if it's already exist and then save it. It should divide these functionality into 4 methods.

1. bindValidateAndSave The application method. It tells what to do rather than how's done.
2. bindCustomer bind and add new shoppingCart.
3. validateCustomer validate if customer exist.
4. saveCustomer save customer

The last method saveCustomer has only 1 line of code, why were we let it become a individual method? Although it might not improve readability for programmers, it’s a paradigm shift in how the method is addressed. Because it calls customerService.save(). it’s responsible that the save method is actually called right. Instead if we let it delegate to a newly extracted method (saveCustomer) it isn’t responsible for the explicit saving.

Reference

1. Elegance and classes
2. Separation of concerns
3. A Logical Theory of Interfaces and Objects
4. Java by Experience
5. OO Programming By Example
6. TDD Design Starter Kit – Responsibilities, Cohesion, and Coupling
7. Benefits of the Three-Tiered Architecture
8. Single-Responsibility Principle
9. [1]
10. [2]
11. [3]