Book Image

Hands-On Object-Oriented Programming with C#

By : Raihan Taher
Book Image

Hands-On Object-Oriented Programming with C#

By: Raihan Taher

Overview of this book

Object-oriented programming (OOP) is a programming paradigm organized around objects rather than actions, and data rather than logic. With the latest release of C#, you can look forward to new additions that improve object-oriented programming. This book will get you up to speed with OOP in C# in an engaging and interactive way. The book starts off by introducing you to C# language essentials and explaining OOP concepts through simple programs. You will then go on to learn how to use classes, interfacesm and properties to write pure OOP code in your applications. You will broaden your understanding of OOP further as you delve into some of the advanced features of the language, such as using events, delegates, and generics. Next, you will learn the secrets of writing good code by following design patterns and design principles. You'll also understand problem statements with their solutions and learn how to work with databases with the help of ADO.NET. Further on, you'll discover a chapter dedicated to the Git version control system. As you approach the conclusion, you'll be able to work through OOP-specific interview questions and understand how to tackle them. By the end of this book, you will have a good understanding of OOP with C# and be able to take your skills to the next level.
Table of Contents (16 chapters)

Use case diagrams

A use case diagram is a behavioral diagram that is very commonly used in software development. The main purpose of this diagram is to illustrate the functional usage of a piece of software. It holds the use cases of a system and can be used to provide a high-level view of the functionality or even a very specific low-level module of a software. Normally for a system, there are multiple use case diagrams that focus on the different levels of the system. Use case diagrams shouldn't be used to display the implementation details of a system; they were developed to show only the functional requirements of a system. Use case diagrams are very good diagrams for business people to convey what they need from a system.

There are four main parts of a use case diagram, as shown in the following list:

  • The actor
  • The use case
  • The communication link
  • The system boundaries...