It is the process of designing classes by assigning well-defined responsibilities to each class. 

It means that each class should be responsible for handling its own data.

It means that the class that is responsible for storing data is different from the class that is responsible for manipulating that data.

It helps ensure encapsulation and reusability.

It can be used to determine which class should implement which part of an application function.

book title, book author, book ISBN, book borrowed status

borrowing a book, returning a book, displaying book info, displaying member info

library, member, book

member name, member ID, member’s borrowed book list

Grouping attributes associated with students, units, and enrolment into three separate classes.

Ensuring that the fields in the Unit class cannot be directly accessed from outside that class, but only via methods.

In reality, a course unit has lots of different attributes (e.g. prerequisites, assessments, learning outcomes), but only three are represented in the Unit class.

Using the private access modifier when defining fields such as name, address, phoneNo, and email.

Grouping attributes associated with students, units, and enrolment into three separate classes.

Having a separate class just to keep track of information relating to particular course units.

Keeping all the information relating to a Unit private, so that outside the class it is only accessible via public methods.

Only including information about a Student that is directly relevant to their course enrolment

Most of the classes in this diagram are client classes. This is bad design, as the number of client classes should be minimised in software design.

Most of the classes in this diagram are server classes. This is bad design, as the number of server classes should be minimised in software design.

Most of the classes in this diagram are server classes. This is good design, as the number of client classes should be minimised in software design.

Most of the classes in the diagram are client classes. This is good design, as the number of server classes should be minimised in software design.

In reality, a course unit has lots of different attributes (e.g. prerequisites, assessments, learning outcomes), but only three are represented in the Unit class.

Keeping all the information relating to a Unit private, so that outside the class it is only accessible via methods.

Having a separate class just to keep track of information relating to particular course units.

Grouping attributes associated with students, units, and enrolment into three separate classes.

It can help determine necessary interactions between classes.

It gives an example of an activity that the software needs to perform.

It can help establish which nouns in the specification should/should not be classes.

It is best carried out by an individual programmer, rather than in a team.

The Enrolment class is both a server and a client class, and the Student class is only a client class.

The Enrolment class is only a server class, and the Student class is only a client class.

The Enrolment class is both a server and a client class, and the Student class is only a server class.

The Enrolment class is only a client class, and the Student class is only a server class.