C#面向对象编程入门(第1版，.NET 4.0和C# 4.0)

5星 · 超过95%的资源需积分: 0 72 浏览量更新于2024-07-26 收藏 23.53MB PDF 举报

" Beginning C# Object-Oriented Programming(第1版)" 是一本针对初学者的C#面向对象编程指南，全面覆盖了.NET 4.0和C# 4.0的相关知识。本书由Dan Clark撰写，旨在帮助读者掌握C#编程基础，并通过面向对象编程（OOP）方法学习编写高效、可重用且优雅的代码。本书通过一个案例研究，让读者体验如何将应用程序的简单模型转化为功能齐全的C#项目，涉及设计用户界面、实现业务逻辑以及与关系数据库集成等内容。全书包含超过30个实践性强的活动，涵盖了.NET框架、Windows和Web界面开发、服务导向编程，以及使用Microsoft的Visual Studio 2010、Silverlight、实体框架等工具和技术。书中章节包括： 1. 面向对象编程概述：介绍面向对象的基本概念，如封装、继承和多态。 2. 设计OOP解决方案：识别类结构：讲解如何根据需求定义类和对象。 3. 设计OOP解决方案：模拟对象交互：讨论对象之间的通信和协作。 4. 设计OOP解决方案：案例研究：通过实际项目加深理解。 5. 引入.NET框架和Visual Studio：学习.NET框架的核心组件和IDE的使用。 6. 创建类：教授如何定义和使用类。 7. 创建类层次结构：介绍继承和派生的概念。 8. 实现对象协作：讲解接口、委托和事件的应用。 9. 使用集合：探讨数组和集合类的使用。 10. 数据访问层的实现：学习数据库连接和数据操作。 11. 开发Windows应用：掌握WinForms和WPF应用开发。 12. 开发Web应用：涉足ASP.NET和Web Forms。 13. 开发和消费WCF服务：理解服务导向架构和Web服务。 14. 开发OSO应用：综合运用所学完成实际项目。 15. 总结：回顾并总结所学知识。此外，书中还涵盖了基本编程概念和异常处理，以及安装所需软件的指南，为初学者提供了全面的学习路径。通过本书，读者不仅能够掌握C#语言和.NET框架，还能深入理解面向对象编程的原理和实践，从而具备开发现代、高效的软件应用的能力。

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页未读，继续阅读

huzhouhzy

粉丝: 83
资源: 1655

C#面向对象编程入门(第1版，.NET 4.0和C# 4.0)

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

Beginning C# Object-Oriented Programming

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

./kafka-console-producer.sh --brocker-server 10.133.0.8:9092 --topic storm_test --from-beginning brocker-server is not a recognized option

./kafka-console-consumer.sh --bootstrap-server <kafka-broker>:<port> --topic <topic> 最后几条消息

spring.jpa.open-in-view

linux 查看kafka状态

如何启动ubuntu上的kafka

最新资源