Click here to start
Table of contents
3
Slide 2
OBJECTIVES
Slide 4
3.1 Introduction
3.2 Classes, Objects, Member Functions and Data Members
3.2 Classes, Objects, Member Functions and Data Members (Cont.)
3.3 Overview of the Chapter Examples
3.4 Defining a Class With a Member Function
Outline
Common Programming Error 3.1
3.4 Defining a Class With a Member Function (Cont.)
Common Programming Error 3.2
Common Programming Error 3.3
Slide 15
Fig.3.2 | UML class diagram indicating that class GradeBook has a public displayMessage operation.
Slide 17
3.5 Defining a Member Function with a Parameter
3.5 Defining a Member Function with a Parameter (Cont.)
Slide 20
Slide 21
Slide 22
Common Programming Error 3.4
Common Programming Error 3.5
Good Programming Practice 3.1
Good Programming Practice 3.2
Fig.3.4 | UML class diagram indicating that class GradeBook has a displayMessage operation with a courseName parameter of UML type String.
3.6 Data Members, set Functions and get Functions
Slide 29
Slide 30
Slide 31
Good Programming Practice 3.3
3.6 Data Members, set Functions and get Functions (Cont.)
Software Engineering Observation 3.1
Common Programming Error 3.6
Good Programming Practice 3.4
Good Programming Practice 3.5
Software Engineering Observation 3.2
Error-Prevention Tip 3.1
Common Programming Error 3.7
Slide 41
Good Programming Practice 3.6
Software Engineering Observation 3.3
Software Engineering Observation 3.4
Slide 45
Fig.3.6 | UML class diagram for class GradeBook with a private courseName attribute and public operations setCourseName, getCourseName and displayMessage.
3.7 Initializing Objects with Constructors
Slide 48
Slide 49
Slide 50
Error-Prevention Tip 3.2
Software Engineering Observation 3.5
3.7 Initializing Objects with Constructors (Cont.)
Fig.3.8 | UML class diagram indicating that class GradeBook has a constructor with a name parameter of UML type String.
3.8 Placing a Class in a Separate File for Reusability
Slide 56
Slide 57
Slide 58
3.8 Placing a Class in a Separate File for Reusability (Cont.)
Slide 60
Error-Prevention Tip 3.3
3.9 Separating Interface from Implementation
3.9 Separating Interface from Implementation (Cont.)
Slide 64
Common Programming Error 3.8
Good Programming Practice 3.7
Error-Prevention Tip 3.4
Common Programming Error 3.9
Slide 69
Slide 70
Slide 71
Slide 72
Fig.3.14 | Compilation and linking process that produces an executable application.
3.10 Validating Data with set Functions
Slide 75
Slide 76
Slide 77
Slide 78
Slide 79
Software Engineering Observation 3.6
Error-Prevention Tip 3.5
Software Engineering Observation 3.7
3.11 (Optional) Software Engineering Case Study: Identifying the Classes in the ATM Requirements Document
Fig.3.18 | Nouns and noun phrases in the requirements document.
3.11 (Optional) Software Engineering Case Study: Identifying the Classes in the ATM Requirements Document (Cont.)
Fig.3.19 | Representing a class in the UML using a class diagram.
Fig.3.20 | Class diagram showing an association among classes.
Fig.3.21 | Multiplicity types.
Slide 89
Fig.3.22 | Class diagram showing composition relationships.
Fig.3.23 | Class diagram for the ATM system model
Fig.3.24 | Class diagram showing composition relationships of a class Car.
Fig.3.25 | Class diagram for the ATM system model including class Deposit.
Author:
Dr. J
E-mail:
Juliano@csuChico.edu
Homepage:
http://www.ecst.csuchico.edu/~juliano