Class diagrams in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a class diagram in software engineering?

A class diagram is a visual representation that shows the structure of a system by displaying its classes, their attributes, methods, and the relationships between them.

beginner

Name the three main parts of a class box in a class diagram.

The three main parts are: 1) Class name at the top, 2) Attributes (properties) in the middle, 3) Methods (functions) at the bottom.

beginner

What does an association relationship represent in a class diagram?

An association shows a connection or link between two classes, indicating that objects of one class use or communicate with objects of another class.

intermediate

Explain the difference between inheritance and composition in class diagrams.

Inheritance means one class (child) inherits attributes and methods from another class (parent), showing an 'is-a' relationship. Composition means one class contains another class as a part, showing a 'has-a' relationship where the part cannot exist independently of the whole.

beginner

Why are class diagrams useful in software development?

Class diagrams help developers understand and plan the system's structure clearly. They make it easier to communicate ideas, design the system, and find errors early before coding.

Which part of a class diagram shows the functions a class can perform?

A Attributes section

B Relationship section

C Class name section

D Methods section

The methods section lists the functions or operations that a class can perform.

What type of relationship in a class diagram represents 'is-a'?

A Association

B Aggregation

C Inheritance

D Composition

Inheritance shows an 'is-a' relationship where a child class inherits from a parent class.

In a class diagram, what does a solid diamond at one end of a line represent?

A Composition

B Aggregation

C Inheritance

D Association

A solid diamond indicates composition, meaning a strong 'has-a' relationship where the part cannot exist without the whole.

Which of the following is NOT typically shown in a class diagram?

A Class methods

B Object state changes over time

C Class attributes

D Relationships between classes

Class diagrams show structure, not behavior or state changes over time, which are shown in other diagrams like state diagrams.

What does an open arrowhead on a line between classes usually indicate?

A Inheritance

B Aggregation

C Dependency

D Association

An open arrowhead points to the parent class in an inheritance relationship.

Describe the main components of a class diagram and explain their purpose.

Think about how a class is shown and what information it holds.

Explain how inheritance and composition differ in class diagrams and give a real-life example for each.

Consider 'is-a' vs 'has-a' relationships.

Practice

1. What is the main purpose of a class diagram in software engineering?

easy

A. To visually represent classes, their attributes, and methods

B. To write the actual code for classes

C. To test the software for bugs

D. To deploy the software to users

Solution

1. Step 1: Understand the role of class diagrams

   Class diagrams are used to show the structure of software by representing classes, their attributes, and methods visually.

2. Step 2: Differentiate from other software activities

   Writing code, testing, and deployment are separate steps and not the purpose of class diagrams.

3. Final Answer:

   To visually represent classes, their attributes, and methods -> Option A

4. Quick Check:

   Class diagram = Visual class structure [OK]

Hint: Class diagrams show structure, not code or testing [OK]

Common Mistakes:

• Confusing class diagrams with coding
• Thinking class diagrams are for testing
• Assuming class diagrams handle deployment

2. Which of the following is the correct way to represent a class name in a class diagram?

easy

A. In a circle with the class name inside

B. As a list of methods only

C. As a flowchart with arrows

D. In a box with the class name at the top, centered and bold

Solution

1. Step 1: Recall class diagram structure

   Class diagrams use boxes divided into sections; the top section shows the class name, usually centered and bold.

2. Step 2: Eliminate incorrect shapes

   Circles and flowcharts are not used to represent classes in class diagrams.

3. Final Answer:

   In a box with the class name at the top, centered and bold -> Option D

4. Quick Check:

   Class name = Box top, centered, bold [OK]

Hint: Class name is always at the top of the box [OK]

Common Mistakes:

• Using circles instead of boxes
• Listing only methods without class name
• Confusing class diagrams with flowcharts

3. Given a class diagram showing a class Car with attributes make, model, and method start(), what does this tell you about the Car class?

medium

A. The class has data about make and model and can perform the start action

B. The class only stores data but cannot perform any actions

C. The class only has methods but no data

D. The class is incomplete and cannot be used

Solution

1. Step 1: Interpret attributes and methods in class diagram

   Attributes like make and model represent data stored in the class. Methods like start() represent actions the class can perform.

2. Step 2: Understand class completeness

   Having both attributes and methods means the class stores data and can perform actions, so it is usable.

3. Final Answer:

   The class has data about make and model and can perform the start action -> Option A

4. Quick Check:

   Attributes + Methods = Data + Actions [OK]

Hint: Attributes = data, Methods = actions [OK]

Common Mistakes:

• Thinking attributes are actions
• Assuming methods are data
• Believing class is incomplete without more info

4. A class diagram shows a class Person with attributes name and age, but the method section is missing. What is the best way to fix this?

medium

A. Remove the attributes since methods are missing

B. Add relevant methods like getName() and getAge() to the method section

C. Change the class name to PersonMethods

D. Leave it as is; methods are optional

Solution

1. Step 1: Identify missing method section

   Class diagrams should show both attributes and methods to fully describe a class.

2. Step 2: Add appropriate methods

   Adding methods like getName() and getAge() provides ways to access the attributes, completing the class design.

3. Final Answer:

   Add relevant methods like getName() and getAge() to the method section -> Option B

4. Quick Check:

   Complete class = Attributes + Methods [OK]

Hint: Methods complete the class design, add them [OK]

Common Mistakes:

• Thinking methods are optional
• Removing attributes instead of adding methods
• Changing class name unnecessarily

5. You have a class diagram with classes Student and Course. How would you represent that a student can enroll in multiple courses and each course can have many students?

hard

A. Use a one-to-one association between Student and Course

B. Use inheritance where Student inherits from Course

C. Use a many-to-many association between Student and Course

D. Use a dependency arrow from Course to Student

Solution

1. Step 1: Understand relationship types in class diagrams

   A many-to-many association means multiple students can enroll in multiple courses, and vice versa.

2. Step 2: Identify correct representation

   Inheritance means one class is a type of another, which is not true here. One-to-one or dependency do not express many-to-many relationships.

3. Final Answer:

   Use a many-to-many association between Student and Course -> Option C

4. Quick Check:

   Many-to-many = Multiple students & courses [OK]

Hint: Many-to-many means multiple on both sides [OK]

Common Mistakes:

• Confusing inheritance with association
• Using one-to-one for many relationships
• Using dependency instead of association