C#面向对象编程入门与实践

2星需积分: 0 6 浏览量更新于2024-07-28 收藏 23.53MB PDF 举报

"《C#面向对象编程入门：从概念到实践》" 这本书《Beginning C# Object-Oriented Programming》是一本针对初学者设计的C#编程指南，专注于讲解面向对象（Object-Oriented Programming，OOP）的核心概念和实践技巧。它以一种循序渐进的方式引导读者理解并掌握C#语言在OOP领域的应用。本书的结构分为多个章节，旨在提供一个全面的学习路径。第一章是概述，对OOP的基本理念和原则进行简要介绍，帮助读者建立对面向对象编程的理解。第二章至第四章着重于设计阶段，强调如何识别类结构、模型化对象间的交互，并通过一个实际案例来演示设计过程。第五章和第六章深入讲解.NET框架和Visual Studio的使用，这是C#开发的基础环境。读者将学习如何创建和管理类，以及如何利用IDE工具来支持代码编写。第七章进一步扩展到类的层次结构，即继承和多态等面向对象的关键特性。第八章探讨对象之间的协作，包括接口和抽象类的运用，使代码更加模块化和可复用。第九章则关注集合框架，这是处理大量数据和复杂逻辑的重要工具。第十章介绍数据访问层的设计，涉及数据库操作和ORM技术。第十一章至第十四章分别介绍了Windows应用程序、Web应用程序、Web服务（Web Communication Foundation Services, WCF）的开发以及一个完整的对象-服务-对象（OSO）应用程序的构建。这些章节涵盖了从客户端到服务器端的完整开发流程。最后一章是对整个学习过程的总结回顾，可能包括复习关键概念和技巧，以及对未来进一步学习的建议。附录A提供了基础知识的补充，如语法回顾或高级主题的入门指引。《Beginning C# Object-Oriented Programming》不仅适合初学者系统学习C#，也适合有一定基础的开发者深化对OOP实践的理解，是一本实用且富有深度的教程。无论是希望通过C#学习OOP的读者，还是希望提升现有技能的开发者，都能从中受益良多。

CHAPTER 2 ■ DESIGNING OOP SOLUTIONS: IDENTIFYING THE CLASS STRUCTURE

Figure 2-2. View Flight Info use case

Along with the graphical depiction of the use case, many designers and software developers find it

helpful to provide a textual description of the use case. The textual description should be succinct and

focused on what is happening and not on how it is occurring. Sometimes any preconditions or

postconditions associated with the use case are also identified. The following text further describes the

use case diagram shown in Figure 2-2:

• Description: A customer views the flight information page. The customer enters

flight search information. After submitting the search request, the customer views

a list of flights matching the search criteria.

• Preconditions: None.

• Postconditions: The customer has the opportunity to log in and proceed to the

flight booking page.

As another example, take a look at the Reserve Seat use case shown in Figure 2-3.

Figure 2-3. Reserve Seat use case diagram

The following text further describes the use case diagram shown in Figure 2-3:

• Description: The customer enters the flight number and indicates the seats being

requested. After the customer submits the request, some confirmation

information is displayed.

• Preconditions: The customer has looked up the flight information. The customer

has logged in and is viewing the flight booking screen.

CHAPTER 2 ■ DESIGNING OOP SOLUTIONS: IDENTIFYING THE CLASS STRUCTURE

• Postconditions: The customer is sent a confirmation e-mail outlining the flight

details and the cancellation policy.

As you can see from Figure 2-3, certain relationships can exist between use cases. The Reserve Seat

use case includes the View Flight Info use case. This relationship is useful because you can use the View

Flight Info use case independently of the Reserve Flight use case. This is called inclusion. You cannot use

the Reserve Seat use case independently of the View Flight Info use case, however. This is important

information that will affect how you model the solution.

Another way that use cases relate to each other is through extension. You might have a general use

case that is the base for other use cases. The base use case is extended by other use cases. For example,

you might have a Register Customer use case that describes the core process of registering customers.

You could then develop Register Corporate Customer and Register Retail Customer use cases that extend

the base use case. The difference between extension and inclusion is that in extension the base use case

being extended is not used on its own. Figure 2-4 demonstrates how you model this in a use case

diagram.

Figure 2-4. Extending use cases

A common mistake when developing use cases is to include actions initiated by the system itself.

The emphasis of the use case is on the interaction between external entities and the system. Another

common mistake is to include a description of the technical requirements of the system. Remember that

use cases do not focus on how the system will perform the functions, but rather on what functions need

to be incorporated in the system from the user’s standpoint.

After you have developed the use cases of the system, you can begin to identify the internal system

objects that will carry out the system’s functional requirements. You do this through the use of a class

diagram.

ACTIVITY 2-1. CREATING A USE CASE DIAGRAM

After completing this activity, you should be familiar with the following:

• Producing a use case diagram to define a system’s scope.

• Using a UML modeling tool to create and document a use case diagram.

剩余370页未读，继续阅读

自然去留

粉丝: 3
资源: 31

C#面向对象编程入门与实践

Beginning C# Object-Oriented Programming, 2nd Edition

Beginning C# Object-Oriented Programming 2nd Edition.pdf

beginning-C-Sharp-object-oriented-programming.pdf

Beginning.C#.Object-Oriented.Programming,.2nd.Edition

[Beginning.C#.Object-Oriented.Programming(第1版)].源代码

Beginning C# Object-从概念到代码

Beginning.Object.Oriented.Programming.with.VB.2005.From.Novice.to.Professional.Nov.2005

Apress.Beginning.C.Sharp.Object.Oriented.Programming.2011

Beginning C# 6.0 Programming with Visual Studio 2015

Essential C# 5.0-Englis

最新资源