《面向对象思考过程》英文第三版——IT专业人士的必读

面向对象

需积分: 11 163 浏览量更新于2024-07-21 1 收藏 4.67MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"面向对象思考过程英文第三版" 是一本针对软件开发人员的编程思想指南，主要探讨了面向对象编程的核心概念和技术。这本书是Developer's Library系列的一部分，该系列旨在为专业程序员提供高质量的参考和教程，帮助他们更好地理解和应用日常工作中使用的编程语言和技术。面向对象编程（Object-Oriented Programming，OOP）是一种编程范式，它基于“对象”的概念，这些对象封装了数据和操作这些数据的方法。这种编程方法论强调通过类和对象来组织代码，以提高可重用性、模块化和代码的易维护性。在面向对象思考过程中，作者可能会深入讲解以下关键概念： 1. **类与对象**：类是创建对象的蓝图，它定义了一组属性（数据成员）和方法（行为）。对象是类的实例，具有特定的属性值和可以执行的方法。 2. **封装**：封装是面向对象编程的基本原则之一，它隐藏了对象内部的实现细节，只对外提供接口进行交互，增强了代码的安全性和可维护性。 3. **继承**：继承允许子类从父类中继承属性和方法，减少了代码重复，使得类之间能够共享代码，并且方便扩展。 4. **多态**：多态是指同一消息可以被不同类型的对象响应，它增强了程序的灵活性和可扩展性，允许开发者编写更通用的代码。 5. **抽象**：抽象是将复杂系统简化为易于管理的模型，通过定义接口或抽象类，关注主要功能，忽略次要细节。书中可能还会讨论一些具体的技术和语言特性，如C++、Java或Objective-C中的面向对象特性。例如，`Programming in Objective-C`，这是一本专注于苹果平台开发的书籍，可能会涵盖Objective-C语言的语法、内存管理、Objective-C的类别、协议等特性。此外，Developer's Library系列中还包括其他技术领域的书籍，如`PHP & MySQL Web Development`、`MySQL`、`Linux Kernel Development`、`Python Essential Reference`、`PostgreSQL`，它们分别涵盖了动态网站开发、数据库管理、操作系统内核、Python编程和关系型数据库等内容，展示了这个系列的广泛覆盖和专业深度。面向对象思考过程的第三版可能对OOP的最新趋势和最佳实践进行了更新，适合那些希望深化面向对象设计理解的开发者阅读。读者可以通过本书提升自己的编程思维，学习如何更有效地设计和实现面向对象的软件系统。

资源详情

资源推荐

Dedication

To S h ar o n , S t ac y, S t ep h a n i e, an d D uf f y

Acknowledgments

As with the first two editions, this book required the combined efforts of many people. I

would like to take the time to acknowledge as many of these people as possible, for

without them, this book would never have happened.

First and foremost, I would like to thank my wife Sharon for all of her help. Not only

did she provide support and encouragement throughout this lengthy process, she is also

the first line editor for all of my writing.

I would also like to thank my mom and the rest of my family for their continued

support.

I have really enjoyed working with the people at Pearson on all three editions of this

book.Working with editors Mark Taber, Seth Kerney,Vanessa Evans, and Songlin Qiu has

been a pleasure.

A special thanks goes to Jon Upchurch for his help with much of the code as well as

the technical editing of the manuscript.

Finally, thanks to my daughters, Stacy and Stephanie, and my cat Duffy for keeping

me on my toes.

Introduction

This Book’s Scope

As the title indicates, this book is about the object-oriented (OO) thought process. Obvi-

ously, choosing the theme and title of the book are important decisions; however, these

decisions were not all that simple. Numerous books deal with various levels of object ori-

entation. Several popular books deal with topics including OO analysis, OO design, OO

programming, design patterns, OO data (XML), the Unified Modeling Language (UML),

OO Internet development, various OO programming languages, and many other topics

related to OO development.

However, while pouring over all of these books, many people forget that all of these

topics are built on a single foundation: how you think in OO ways. It is unfortunate, but

software professionals often dive into these books without taking the appropriate time

and effort to really understand the concepts behind the content.

I contend that learning OO concepts is not accomplished by learning a specific devel-

opment method or a set of tools. Doing things in an OO manner is, simply put, a way of

thinking.This book is all about the OO thought process.

Separating the methods and tools from the OO thought process is not easy. Many peo-

ple are introduced to OO concepts via one of these methods or tools. For example, years

ago, most C programmers were first introduced to object orientation by migrating di-

rectly to C++—before they were even remotely exposed to OO concepts. Other soft-

ware professionals were first introduced to object orientation by presentations that

included object models using UML—again, before they were even exposed directly to

OO concepts. It is not unusual to find that programming books and courses defer OO

concepts until later in the learning process.

It is important to understand the significant difference between learning OO concepts

and using the methods and tools that support the paradigm.This came into focus for me

before I worked on the first edition of this book when I read articles such as Craig Lar-

man’s “What the UML Is—and Isn’t,” In this article he states,

Unfortunately, in the context of software engineering and the UML diagramming language,

acquiring the skills to read and write UML notation seems to sometimes be equated with

skill in object-oriented analysis and design. Of course, this is not so, and the latter is much

more important than the former. Therefore, I recommend seeking education and educational

materials in which intellectual skill in object-oriented analysis and design is paramount

rather than UML notation or the use of a case tool.

Introduction

Although learning a modeling language is an important step, it is much more impor-

tant to learn OO skills first. Learning UML before OO concepts is similar to learning

how to read an electrical diagram without first knowing anything about electricity.

The same problem occurs with programming languages. As stated earlier, many C

programmers moved into the realm of object orientation by migrating to C++ before

being directly exposed to OO concepts.This would always come out in an interview.

Many times developers who claim to be C++ programmers are simply C programmers

using C++ compilers. Even now, with languages such as C# .NET,VB .NET, and Java

well established, a few key questions in a job interview can quickly uncover a lack of

OO understanding.

Early versions of Visual Basic are not OO. C is not OO, and C++ was developed to be

backward compatible with C. Because of this, it is quite possible to use a C++ compiler

(writing only C syntax) while forsaking all of C++’s OO features. Even worse, a pro-

grammer can use just enough OO features to make a program incomprehensible to OO

and non-OO programmers alike.

Thus, it is of vital importance that while you’re on the road to OO development, you

first learn the fundamental OO concepts. Resist the temptation to jump directly into a

programming language (such as VB .NET, C++, C# .NET or Java) or a modeling lan-

guage (such as UML), and take the time to learn the object-oriented thought process.

In my first class in Smalltalk in the late 1980s, the instructor told the class that the new

OO paradigm was a totally new way of thinking (despite the fact that it has been around since

the 60s). He went on to say that although all of us were most likely very good program-

mers, about 10%–20% of us would never really grasp the OO way of doing things. If this

statement is indeed true, it is most likely because some people never really take the time

to make the paradigm shift and learn the underlying OO concepts.

What’s New in the Third Edition

As stated often in this introduction, my vision for the first edition was primarily a con-

ceptual book.Although I still adhere to this goal for the second and third editions, I have

included several application topics that fit well with object-oriented concepts. For the

third edition I expand on many of the topics of the second edition and well as include

totally new chapters.These revised and updated concepts

XML is used for object communication.

Object persistence and serialization.

XML integrated into the languages object definition.

Adding properties to attributes.

XML-based Internet applications.

Client/Server technologies.

Expanded code examples in Java, C# .NET and VB .NET.

This Book’s Scope

The chapters that cover these topics are still conceptual in nature; however, many of the

chapters include Java code that shows how these concepts are implemented. In this third

edition, a code appendix is included that presents the chapter’s examples in C# .NET and

Visual Basic .NET.

The Intended Audience

This book is a general introduction to fundamental OO concepts with code examples to

reinforce the concepts. One of the most difficult juggling acts was to keep the material

conceptual while still providing a solid, technical code base.The goal of this book is to al-

low a reader to understand the concepts and technology without having a compiler at

hand. However, if you do have a compiler available, then there is code to be investigated.

The intended audience includes business managers, designers, developers, program-

mers, project managers, and anyone who wants to gain a general understanding of what

object orientation is all about. Reading this book should provide a strong foundation for

moving to other books covering more advanced OO topics.

Of these more advanced books, one of my favorites remains Object-Oriented Design in

Java by Stephen Gilbert and Bill McCarty. I really like the approach of the book, and have

used it as a textbook in classes I have taught on OO concepts. I cite Object-Oriented De-

you complete this one.

Other books that I have found very helpful include Effective C++ by Scott Meyers,

Classical and Object-Oriented Software Engineering by Stephen R. Schach, Thinking in C++

by Bruce Eckel, UML Distilled by Martin Flower, and Java Design by Peter Coad and

Mark Mayfield.

The conceptual nature of this book provides a unique perspective in regards to other

computer technology books.While books that focus on specific technologies, such as

programming languages, struggle with the pace of change, this book has the luxury of

presenting established concepts that, while certainly being fine-tuned, do not experience

radical changes.With this in mind, many of the books that were referenced several years

ago, are still referenced because the concepts are still fundamentally the same.

This Book’s Scope

It should be obvious by now that I am a firm believer in becoming comfortable with the

object-oriented thought process before jumping into a programming language or model-

ing language.This book is filled with examples of code and UML diagrams; however, you

do not need to know a specific programming language or UML to read it.After all I have

said about learning the concepts first, why is there so much Java, C# .NET, and VB .NET

code and so many UML diagrams? First, they are all great for illustrating OO concepts.

Second, both are vital to the OO process and should be addressed at an introductory

level.The key is not to focus on Java, C# .NET, and VB .NET or UML, but to use them

as aids in the understanding of the underlying concepts.

剩余346页未读，继续阅读

无法显示昵称

粉丝: 6
资源: 16

《面向对象思考过程》英文第三版——IT专业人士的必读

面向对象分析与设计第三版

面向对象分析与设计 （中文第三版）

面向对象分析与设计第三版中文

c++面向对象程序设计第三版答案谭浩强

c面向对象程序设计第三版答案谭浩强

思考-面向过程还是面向对象？

java面向对象程序设计第三版耿祥义第一章笔记

c++m面向对象程序设计谭浩强第二版

python面向过程 面向对象

html面向对象还是面向过程

面向对象和面向过程的区别

java面向对象和面向过程的区别

面向过程和面向对象区别

面向对象和面向过程c

面向对象面向过程的区别

java面向对象程序设计第三版耿祥义

面向对象和面向过程的区别，面向对象的好处

python面向过程面向对象

c++面向对象和面向过程

java面向对象程序设计第三版耿祥义第一章

最新资源

面向对象分析与设计（中文第三版）

python面向过程面向对象