Design Patterns for Enterprise Development PROG1322 Course - Niagara College PDF

Course title :Design Patterns for Enterprise Development Code :PROG1322 niagaracollegetoronto.ca Wee Assessments and Topic Learning Objectives k...

Course title :Design Patterns for Enterprise Development Code :PROG1322 niagaracollegetoronto.ca Wee Assessments and Topic Learning Objectives k Activities ▪ Icebreaker Activity and Lecture and Introduction session - self-introduction Discussions overall objectives for ▪ Explore LMS(Canvas) (Group Activity): the course content and features, learn to Introduction to the implementation work communicate with software required instructors and peers and their functions REC through Canvas which will be used AP ▪ Familiarize with the TLP: in the throughout We Introduction to the learning courses -Hands-On ek 1 objectives and outcome, Lab Familiarize with the evaluation methods and weightage ▪Pre-requisite courses overview and Basic Riddhi Patel concepts related to the Wee Assessments and Topic Learning Objectives k Activities Database First: Lecture and 1. Design and Discussions Create Distributed  Creating the database In-Class individual Database schema first. Activity  Design SQL Server table (Discussion – Applications using proper database structures, set up finalize group objects to support AGE relationships between members and one tables, and define entity application (E.g. – enterprise NDA integrity constraints. development of School We Management multiple client ek System) for apply interfaces. 2 the different 1.1 Database First: function in the Design the SQL Server upcoming weeks table structures, [Based on relationships and selection of entity, domain and Riddhi Patel application and referential integrity Database Riddhi Patel Database A Database is an organized collection of Data. A database is a structured collection of data organized to allow efficient storage, retrieval, and manipulation. Database Components A database is comprised of the following primary parts. Schema A database contains at least one composition, which is essentially a gathering of at least one table of information. Table Each table contains various columns just like in a spreadsheet. A table can have as meager as two columns and upwards of one hundred or more columns, depending upon the kind of information being put in the table. Column Each column contains one of a few sorts of information, such as name, address, phone number, etc. Row Data in a table is recorded in rows. There are hundreds or thousands of rows in a table having any particular information. Riddhi Patel Application with Database Example: Bookstore Application Riddhi Patel Relation Data Model The relational model is a data model that represents data as a collection of tables, with each table consisting of rows and columns. It is the most widely used data model in DBMS and is the foundation of RDBMS (Relational Database Management System). Tables − In relational data model, relations are saved in the format of Tables. This format stores the relation among entities. A table has rows and columns, where rows represents records and columns represent the attributes. Tuple − A single row of a table, which contains a single record for that relation is called a tuple. Relation instance − A finite set of tuples in the relational database system represents relation instance. Relation instances do not have duplicate tuples. Relation schema − A relation schema describes the relation name (table name), attributes, and their names. Relation key − Each row has one or more attributes, known as relation key, which can identify the row in the relation (table) uniquely. Attribute domain − Every attribute has some pre-defined value scope, known as attribute domain. Constraints Example :Relation Data Model Riddhi Patel Relational Integrity Constraints Referential integrity is a property of a database that ensures the consistency and correctness of data in a table. It is typically enforced through the use of foreign keys, which are fields in a table that reference the primary key of another table. Every relation has some conditions that must hold for it to be a valid relation. These conditions are called Relational Integrity Constraints. There are three main integrity constraints − 1. Entity Integrity 2. Domain Integrity 3. User-Defined Integrity 4. Referential Integrity Riddhi Patel Riddhi Patel Connectivity: Riddhi Patel Creating the Database Schema first Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel  Design SQL Server table structures, set up relationships between tables, and define entity integrity constraints Riddhi Patel Outcome  Tables  Table data Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel  Assessments and Activities In-Class individual Activity Riddhi Patel  Week 2 Lab Exercise Database Design : 1. Download Microsoft Visual Studio Community 2022. 2. Choose a real-world Application Example. 3. Design the database schema. 4. Create minimum 3 tables and Establish relationships with them. 5. Understand and verify the integrity constraints in your example application. 6. Take a Screenshot of each for upcoming test as Report Submission. (For each of your work throughout entire course always take a screenshot for future submission ) Riddhi Patel  References https://www.tutorialspoint.com/dbms/dbms_data_schemas.htm https://databasetown.com https://learn.microsoft.com/en-us/visualstudio/data-tools/create-a-sql-database-by- using-a-designer?view=vs-2022 Riddhi Patel  Week Topics  Introduction of database concepts  Creating the database schema first.  Design SQL Server table structures, set up relationships between tables, and define entity integrity constraints. SU Assessments and Activities : MM Week  Lecture and Discussions ERY 2  In-Class individual Activity Discussion -Find and Choose one Learning Objectives :  1.1 Database First: Design the SQL Server table structures, relationships and entity, domain and referential integrity constraints required for a business application. Riddhi Patel Riddhi Patel Riddhi Patel Riddhi Patel Any Questions Riddhi Patel  Assessments and Week Topic Learning Objectives Activities Code First approach: Lecture and 1. Design and Create  Creating model classes Discussion Distributed Database representing business entities In-Class individual Applications using without worrying about the Activity. appropriate database NE database schema initially. objects to support  Use Entity Framework's enterprise development Database Migrations feature to of multiple client XT automatically create or update the SQL Server database based interfaces. 1.2. Code First: From an on the model classes. Object-Oriented paradigm, Discussing enterprise create model classes representing the entities Week 3 development models: involved in a business  Discussions about various application and use Database enterprise development models, such as 2-tier, 3-tier, n-tier Migrations to create a SQL systems, and internet Server database. applications. 1.3. Describe the various  The advantages and limitations models for enterprise of each model and learn to Riddhi Patel development including 2-tier, choose the most suitable model 3-tier and n-tier systems and