Click here to start
Table of contents
2
Slide 2
Slide 3
OBJECTIVES
Slide 5
2.1 Introduction
2.2 First Program in C++: Printing a Line of Text
2.2 First Program in C++: Printing a Line of Text (Cont.)
Outline
Good Programming Practice 2.1
Slide 11
Common Programming Error 2.1
Good Programming Practice 2.2
Slide 14
Slide 15
Slide 16
Common Programming Error 2.2
Slide 18
Slide 19
Good Programming Practice 2.3
Fig. 2.2 | Escape sequences.
Good Programming Practice 2.4
Good Programming Practice 2.5
2.3 Modifying Our First C++ Program
Slide 25
Slide 26
2.4 Another C++ Program: Adding Integers
Slide 28
2.4 Another C++ Program: Adding Integers (Cont.)
Good Programming Practice 2.6
Good Programming Practice 2.7
Portability Tip 2.1
Good Programming Practice 2.8
Good Programming Practice 2.9
Good Programming Practice 2.10
Error-Prevention Tip 2.1
Good Programming Practice 2.11
Good Programming Practice 2.12
Slide 39
Error-Prevention Tip 2.2
Slide 41
Good Programming Practice 2.13
Slide 43
2.5 Memory Concept
Fig. 2.6 | Memory location showing the name and value of variable number1.
Fig. 2.7 | Memory locations after storing values for number1 and number2.
Fig. 2.8 | Memory locations after calculating and storing the sum of number1 and number2.
2.6 Arithmetic
Common Programming Error 2.3
2.6 Arithmetic (Cont.)
Fig. 2.9 | Arithmetic operators.
Slide 52
Fig. 2.10 | Precedence of arithmetic operators.
Common Programming Error 2.4
Good Programming Practice 2.14
Fig. 2.11 | Order in which a second-degree polynomial is evaluated.
2.7 Decision Making: Equality and Relational Operators
Fig. 2.12 | Equality and relational operators.
Common Programming Error 2.5
Common Programming Error 2.6
Slide 61
Common Programming Error 2.7
Slide 63
Slide 64
Good Programming Practice 2.15
Good Programming Practice 2.16
Good Programming Practice 2.17
Common Programming Error 2.8
Common Programming Error 2.9
Good Programming Practice 2.18
Fig. 2.14 | Precedence and associativity of the operators discussed so far.
Good Programming Practice 2.19
2.8 (Optional) Software Engineering Case Study: Examining the ATM Requirements Document
2.8 (Optional) Software Engineering Case Study (Cont.)
Fig. 2.15 | Automated teller machine user interface.
Fig. 2.16 | ATM main menu.
Fig. 2.17 | ATM withdrawal menu.
Slide 78
Fig. 2.18 | Use case diagram for the ATM system from the user’s perspective.
Fig. 2.19 | Use case diagram for a modified version of our ATM system that also allows users to transfer money between accounts.
Slide 81
Slide 82
Author:
Dr. J
E-mail:
Juliano@csuChico.edu
Homepage:
http://www.ecst.csuchico.edu/~juliano