Week 02 (4).pptx

df s ff s f

1. niagaracollegetoronto.ca Course title :Design Patterns for Enterprise Development Code :PROG1322 Instructor's name : Session Number : Date : Spring 2024 

2. Week Topic Assessments and Activities Learning Objectives Week 1 ▪ Icebreaker Activity and self-introduction ▪ Explore LMS(Canvas) features, learn to communicate with instructors and peers through Canvas ▪ Familiarize with the TLP: Introduction to the learning objectives and outcome, Familiarize with the evaluation methods and weightage ▪Pre-requisite courses overview and Basic concepts related to the subject. Lecture and Discussions (Group Activity): Introduction to the software required and their functions which will be used in the throughout courses -Hands-On Lab Introduction session -overall objectives for the course content and implementation work RECAP Riddhi Patel

3. Week Topic Assessments and Activities Learning Objectives Week 2 Database First : Creating the database schema first. Design SQL Server table structures, set up relationships between tables, and define entity integrity constraints. Lecture and Discussions In-Class individual Activity (Discussion –finalize group members and one application (E.g. – School Management System) for apply the different function in the upcoming weeks [Based on selection of application and group, will submit the database project] 1. Design and Create Distributed Database Applications using proper database objects to support enterprise development of multiple client interfaces. 1.1 Database First: Design the SQL Server table structures, relationships and entity, domain and referential integrity constraints required for a business application. AGENDA Riddhi Patel

4. Database Riddhi Patel

5. 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

6. Application with Database Example: Bookstore Application Riddhi Patel

7. 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

8. 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 − Entity Integrity Domain Integrity User-Defined Integrity Referential Integrity Riddhi Patel

9. Riddhi Patel

10. Connectivity: Riddhi Patel

11. Creating the Database Schema first Riddhi Patel

12. Riddhi Patel

13. Riddhi Patel

14. Riddhi Patel

15. Riddhi Patel

16. Riddhi Patel

17. Riddhi Patel

18. Riddhi Patel

19. Riddhi Patel

20. Riddhi Patel

21. Riddhi Patel

22. Riddhi Patel

23. Riddhi Patel

24. Riddhi Patel

25. Design SQL Server table structures, set up relationships between tables, and define entity integrity constraints Riddhi Patel

26. Outcome  Ta bles  Table data Riddhi Patel

27. Riddhi Patel

28. Riddhi Patel

29. Riddhi Patel

30. Riddhi Patel

31. Riddhi Patel

32. Riddhi Patel

33. Assessments and Activities In-Class individual Activity Riddhi Patel

34. Week 2 Lab Exercise Database Design : Download Microsoft Visual Studio Community 2022. Choose a real-world Application Example. Design the database schema. Create minimum 3 tables and E stablish relationships with them. Understand and verify the integrity constraints in your example application.  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

35. 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 References Riddhi Patel

36. Week Topics Week 2 Introduction of database concepts Creating the database schema first. Design SQL Server table structures, set up relationships between tables, and define entity integrity constraints. Assessments and Activities : Lecture and Discussions 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. SUMMERY Riddhi Patel

37. Riddhi Patel

38. Riddhi Patel

39. Riddhi Patel

40. Any Questions Riddhi Patel

41. Week Topic Assessments and Activities Learning Objectives Week 3 Code First approach: Creating model classes representing business entities without worrying about the database schema initially. Use Entity Framework's Database Migrations feature to automatically create or update the SQL Server database based on the model classes. Discussing enterprise development models : Discussions about various enterprise development models, such as 2-tier, 3-tier, n-tier systems, and internet applications. The advantages and limitations of each model and learn to choose the most suitable model for specific business environments and project requirements. Lecture and Discussion In-Class individual Activity. 1. Design and Create Distributed Database Applications using appropriate database objects to support enterprise development of multiple client interfaces. 1.2. Code First: From an Object-Oriented paradigm, create model classes representing the entities involved in a business application and use Database Migrations to create a SQL Server database. 1.3. Describe the various models for enterprise development including 2-tier, 3-tier and n-tier systems and internet applications and decide which system would be right in each business environment. NEXT Riddhi Patel