C# Software Architecture, ADO.NET, Windows Forms, and Version Control

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/46

flashcard set

Earn XP

Description and Tags

Vocabulary practice flashcards covering multilayered architecture, FileHandler patterns, ADO.NET object models, stored procedures, software design patterns, Git/GitHub version control, and Windows Forms controls.

47 Terms

1
New cards

Layers

The logical division and grouping of software components and functionality within an application or service.

2
New cards

Tiers

The physical distribution of software components and functionality across separate physical machines, servers, or hardware environments.

3
New cards

Presentation Layer

The topmost layer in an application that manages user interaction and presents content to the end user through a Graphical User Interface (GUI).

4
New cards

Business Logic Layer (BLL)

The middle tier of layered architecture that implements the core functionality and encapsulates the business rules laid down by an organization.

5
New cards

Data Layer (DAL)

The lowest tier of layered architecture, responsible for the storage and retrieval of application data from databases or file servers and exposing it through an API.

6
New cards

FileHandler

A dedicated class created to house file input/output methods (such as reading and writing text files), preventing code clutter in the Main() method and promoting loose coupling.

7
New cards

ADO.NET

An object-oriented set of classes organized in the System.Data namespace of the Microsoft .NET Framework that enables applications to interact with data sources like databases and XML files.

8
New cards

Scalability

The ability of an application to handle an increasing number of simultaneous clients without a noticeable degradation of performance.

9
New cards

Disconnected Data Architecture

A data architecture model where applications connect to the database only while retrieving or updating data, caching it locally in memory and immediately closing the connection to conserve server resources.

10
New cards
<p>Data Provider</p>

Data Provider

A library set of specialized ADO.NET components—including Connection, Command, DataReader, and DataAdapter—tailored for interacting with a specific type of data source.

11
New cards

System.Data.SqlClient

The .NET namespace that contains the specialized SQL Server provider classes used to connect to and interact with Microsoft SQL Server databases.

12
New cards

SqlConnection

An ADO.NET object that manages a connection and unique session to a SQL Server database using a connection string.

13
New cards

Security Support Provider Interface (SSPI)

A Windows security package mechanism used in connection strings (Integrated Security = SSPI) to enable secure authentication using Windows single sign-on credentials.

14
New cards

SqlCommand

An ADO.NET object that specifies the Transact-SQL statement or stored procedure to be executed against a data source.

15
New cards

SqlDataReader

An ADO.NET object that provides a fast, read-only, forward-only stream of data rows fetched directly from a database.

16
New cards

ExecuteReader()

A method of the SqlCommand object used to execute SELECT queries and return a SqlDataReader object.

17
New cards

ExecuteNonQuery()

A method of the SqlCommand object used for executing catalog operations or INSERT, UPDATE, and DELETE statements, returning the number of rows affected.

18
New cards

ExecuteScalar()

A method of the SqlCommand object used to execute queries that return a single aggregate value (such as a COUNT, SUM, or AVG) as an object type.

19
New cards

DataTable

An in-memory representation of a single relational database table consisting of DataColumn, DataRow, and Constraint objects.

20
New cards

DataSet

An in-memory data cache that can hold multiple DataTable and DataRelation objects along with relational integrity constraints, functioning independently of any active database connection.

21
New cards
<p>System.Data Namespace</p>

System.Data Namespace

The fundamental .NET namespace providing access to disconnected data classes, including DataSet, DataTable, DataColumn, DataRow, Constraint, ForeignKeyConstraint, UniqueConstraint, and DataRelation.

22
New cards

SqlDataAdapter

An ADO.NET class that acts as a bridge between a DataSet or DataTable and the database, managing connections to automatically open, execute Fill or Update operations, and close connections.

23
New cards

Fill() Method

A SqlDataAdapter method that automatically opens the database connection, populates a specified DataSet or DataTable with query results, and promptly closes the connection.

24
New cards

Stored Procedure

A precompiled group of Transact-SQL statements stored within the database server that can take parameters, execute business logic, and return data while optimizing performance and security.

25
New cards

CommandType.StoredProcedure

An ADO.NET property setting on a SqlCommand object that instructs the provider to interpret the CommandText as the name of a stored procedure rather than an inline SQL string.

26
New cards
<p>Design Pattern</p>

Design Pattern

A general, repeatable, and proven solution or template to a commonly occurring problem in software design within a specified context.

27
New cards

Gang of Four (GoF)

The group of four authors—Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides—who cataloged 23 classic software design patterns in their 1995 book.

28
New cards

Creational Design Patterns

Design patterns that deal with object creation mechanisms to instantiate objects in the best possible way for specific situations (e.g., Factory, Abstract Factory, Singleton, Prototype, Builder).

29
New cards

Structural Design Patterns

Design patterns that provide ways to organize class and object structures, using inheritance and composition to create large objects from smaller objects (e.g., Adapter, Facade, Decorator).

30
New cards

Behavioral Design Patterns

Design patterns that provide solutions for better interaction and communication between objects, offering loose coupling and flexible extensibility (e.g., Observer, Strategy, Command).

31
New cards

Singleton Pattern

A creational design pattern that restricts the instantiation of a class to exactly one single instance, typically implemented using a private constructor.

32
New cards

Factory Pattern

A creational design pattern that provides an interface for creating objects without exposing the instantiation logic to the client, referring to created objects via a common interface.

33
New cards

Version Control System (VCS)

Software that manages and records changes to documents, programs, or project files over time, enabling developers to recall specific versions and collaborate efficiently.

34
New cards

Distributed Version Control System (DVCS)

A peer-to-peer version control architecture where every developer has a complete local clone of the entire repository history, avoiding a single point of failure.

35
New cards
<p>Git</p>

Git

A free and open-source distributed version control system developed by Linus Torvalds in 2005 to track changes in source code and support non-linear development.

36
New cards

GitHub

A cloud-hosted platform for Git repositories that enables developers to store, manage, track, and collaborate on code projects remotely.

37
New cards

Commit (Git)

A Git command and record that permanently saves a snapshot of staged changes into the local repository history accompanied by a descriptive message.

38
New cards

Staging Area (Git)

An intermediate area in Git that holds changed or newly tracked files prepared to be included in the next commit.

39
New cards

Branching (Git)

The mechanism that allows developers to create isolated lines of development off the main branch to work on features or fixes without affecting the production code.

40
New cards

Team Explorer

A tool window in Visual Studio used to manage Git repository connections, synchronization, commits, branches, and remote publishing.

41
New cards

InitializeComponent()

A method automatically created and maintained by the Windows Forms designer inside form.designer.cs that defines and initializes all form controls and layout properties.

42
New cards

Program.cs (Windows Forms)

The entry point file of a Windows Forms application containing the static Main() method and the Application.Run(new Form1()) statement.

43
New cards

Form1.cs

The code-behind file of a Windows Form where programmers write the event-handling logic, user methods, and interactions for the form.

44
New cards
<p>Properties Window</p>

Properties Window

An IDE window in Visual Studio that displays and allows configuration of properties and events for selected controls or components on a form.

45
New cards

DataGridView

A flexible, customizable Windows Forms control designed to display tabular data in grid format from various data sources like DataTables, DataSets, or object lists.

46
New cards

ListView

A Windows Forms control that displays items in different views (such as Details), requiring column headers and ListViewItems with SubItems for tabular data display.

47
New cards

BindingSource

An intermediate component in Windows Forms that encapsulates data source management and currency/positioning when binding data to controls like DataGridView.