Chapter 1: The Database Environment
|
|
- Shanon Owen
- 5 years ago
- Views:
Transcription
1 Chapter 1: The Database Environment Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden Prentice Hall,
2 Definitions Data: Meaningful facts, text, graphics, images, sound, video segments Database: An organized collection of logically related data Information: Data processed to be useful in decision making Metadata: Data that describes data Chapter 1 2 Prentice Hall, 2002
3 Figure 1-1a Data in Context Large volume of facts which are difficult to interpret Chapter 1 3 Prentice Hall, 2002
4 Figure 1-1b Summarized data Useful information that managers can use for decision making and interpretation Chapter 1 4 Prentice Hall, 2002
5 Table 1-1 Metadata Descriptions of the properties or characteristics of the data, including data types, field sizes, allowable values, and documentation Chapter 1 5 Prentice Hall, 2002
6 Databases vs. File Processing Data is stored in two electronic forms: Databases A central data-store that can be read from different sources Program Files Distributed data-stores that can usually only be read from a single source Common Examples: Word, Excel, PowerPoint Chapter 1 6 Prentice Hall, 2002
7 Disadvantages of File Processing Program-Data Dependence All programs maintain metadata for each file they use Data Redundancy (Duplication of data) Different systems/programs have separate copies of the same data Limited Data Sharing No centralized control of data Lengthy Development Times Programmers must design their own file formats Chapter 1 7 Prentice Hall, 2002
8 Figure 1-2 Three file processing systems at Pine Valley Furniture Duplicate Data Chapter 1 8 Prentice Hall, 2002
9 Problems with Data Dependency Each application programmer must maintain their own data Each application program needs to include code for the metadata of each file Each application program must have its own processing routines for reading, inserting, updating and deleting data Lack of coordination and central control Non-standard file formats Chapter 1 9 Prentice Hall, 2002
10 Problems with Data Duplication Waste of space to have duplicate data Causes more maintenance headaches The biggest Problem: When data changes in one file, could cause inconsistencies Compromises data integrity Chapter 1 10 Prentice Hall, 2002
11 SOLUTION: The DATABASE Approach Central repository of shared data Data is managed by a controlling agent Stored in a standardized, convenient form Requires a Database Management System (DBMS) Chapter 1 11 Prentice Hall, 2002
12 Database Management System A DBMS is a data storage and retrieval system which permits data to be stored nonredundantly while making it appear to the user as if the data is well-integrated. Chapter 1 12 Prentice Hall, 2002
13 Database Management System Application #1 Application #2 DBMS Database containing centralized shared data Application #3 DBMS manages data resources like an operating system manages hardware resources Chapter 1 13 Prentice Hall, 2002
14 Advantages of Database Approach Program-Data Independence Metadata stored in DBMS, so applications don t need to worry about data formats Data queries/updates managed by DBMS so programs don t need to process data access routines Results in: increased application development and maintenance productivity Minimal Data Redundancy Leads to increased data integrity/consistency Chapter 1 14 Prentice Hall, 2002
15 Advantages of Database Approach Improved Data Sharing Different users get different views of the data Enforcement of Standards All data access is done in the same way Improved Data Quality Constraints, data validation rules Better Data Accessibility/ Responsiveness Use of standard data query language (SQL) Security, Backup/Recovery, Concurrency Disaster recovery is easier Chapter 1 15 Prentice Hall, 2002
16 Costs and Risks of the Database Approach Up-front costs: Installation Management Cost and Complexity Conversion Costs Ongoing Costs Requires New, Specialized Personnel Need for Explicit Backup and Recovery Organizational Conflict Old habits die hard Chapter 1 16 Prentice Hall, 2002
17 The Enterprise Data Model A graphical model that shows the high-level entities for the organization and the relationships among those entities Chapter 1 17 Prentice Hall, 2002
18 Figure 1-3 Segment from enterprise data model Figure 3 Chapter 1 18 Prentice Hall, 2002
19 Figure 1-3 Segment from enterprise data model Figure 3 Business Rule: One customer may place many orders, but each order is placed by a single customer One-to-many relationship Chapter 1 19 Prentice Hall, 2002
20 Figure 1-3 Segment from enterprise data model Figure 3 Business Rule: One order has many order lines; each order line is associated with a single order One-to-many relationship Chapter 1 20 Prentice Hall, 2002
21 Figure 1-3 Segment from enterprise data model Figure 3 Business Rule: One product can be in many order lines, each order line refers to a single product One-to-many relationship Chapter 1 21 Prentice Hall, 2002
22 Figure 1-3 Segment from enterprise data model Figure 3 Therefore, one order involves many products and one product is involved in many orders Many-to-many relationship Chapter 1 22 Prentice Hall, 2002
23 Implementing Relational Databases How Many Records Are Involved: More records require a more powerful system Example: >500K Records shouldn t use Access How Many People Will Use the RDMS More DB connections require more power Example: >25 People shouldn t use Access What Structure Currently Exists Using existing systems can keep costs down Chapter 1 23 Prentice Hall, 2002
24 Figure 1-4 Pine Valley Furniture Company Access DB Order, Order_Line, Customer, and Product tables Relationships established in special columns that provide links between tables Chapter 1 24 Prentice Hall, 2002
25 Figure 1-5 Client/server system for Pine Valley Furniture Company Is having the database server and database enough? Chapter 1 25 Prentice Hall, 2002
26 The Database Application Create: Add new data to the database Read: Read current database data Update: Modify current database data Delete: Remove current data from the database Chapter 1 26 Prentice Hall, 2002
27 Figure 1-6 Customer invoice (Pine Valley Furniture Company) Application program functions: inserting new data, updating existing data, deleting existing data, reading data for display Chapter 1 27 Prentice Hall, 2002
28 The Range of Database Applications Personal Database standalone desktop database Workgroup Database local area network (<25 users) Department Database local area network ( users) Enterprise Database wide-area network (hundreds or thousands of users) Chapter 1 28 Prentice Hall, 2002
29 Figure 1-7 Typical data from a personal computer database Chapter 1 29 Prentice Hall, 2002
30 Figure 1-8 Workgroup database with local area network Chapter 1 30 Prentice Hall, 2002
31 Figure 1-9 An enterprise data warehouse Chapter 1 31 Prentice Hall, 2002
32 Components of the Database Environment CASE Tools computer-aided software engineering Repository centralized storehouse of metadata Database Management System (DBMS) software for managing the database Database storehouse of the data Application Programs software using the data User Interface text and graphical displays to users Data Administrators personnel responsible for maintaining the database System Developers personnel responsible for designing databases and software End Users people who use the applications and databases Chapter 1 32 Prentice Hall, 2002
33 Evolution of DB Systems Flat files s s Hierarchical 1970s s Network 1970s s Relational 1980s - present Object-oriented 1990s - present Object-relational 1990s - present Data warehousing 1980s - present Web-enabled 1990s - present Chapter 1 33 Prentice Hall, 2002
34 Questions \ Discussion Why might a firm choose to implement a database system? What is the Enterprise Data Model (no it is not a small plastic starship)? What are two benefits of the Relational Database Approach? Chapter 1 34 Prentice Hall, 2002
35 Chapter 2: The Database Development Process Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden 35
36 Information Systems Architecture (ISA) Overall blueprint for organization s information systems Consists of: Data (Enterprise Data Model simplified ER Diagram) Processes data flow diagrams, process decomposition, etc. Data Network topology diagram (like fig 1.8) People people management using project management tools (Gantt charts, etc.) Events and Points in Time (when processes are performed) Reasons for events and rules (e.g. decision tables) Chapter
37 Information Engineering A data-oriented methodology to create and maintain information systems Top-down planning approach. Four steps: Planning Results in an Information Systems Architecture Analysis Results in functional specifications i.e. what we want Design Results in design specifications i.e. how we ll do it Implementation Results in final operational system Chapter
38 Information Systems Planning Strategy development IT Planning to meet Corporate strategy Three steps: 1. Identify strategic planning factors 2. Identify corporate planning objects 3. Develop enterprise model Chapter
39 Identify Strategic Planning Factors (table 2.1) Organization goals what we hope to accomplish Critical success factors what MUST work in order for us to survive Problem areas weaknesses we now have Chapter
40 Identify Corporate Planning Objects (table 2.3) Organizational units Organizational locations Business functions these might become the users Entity types the things we are trying to model Information (application) systems Chapter
41 Develop Enterprise Model Decomposition of business functions See figure 2.2 Enterprise data model See figure 2.1 Planning matrixes See figure 2.3 Chapter
42 Enterprise Data Model First step in database development Specifies scope and general content Overall picture of organizational data, not specific design Entity-relationship diagram Descriptions of entity types Relationships between entities Business rules Chapter
43 Figure 2-1 Segment from enterprise data model (Pine Valley Furniture Company) [simplified E-R diagram, repeat of figure 1.3] Enterprise data model describes the entities in an organization and the relationship between these entities Chapter
44 Figure Example of process decomposition of an order fulfillment function (Pine Valley Furniture) Decomposition -- breaking large tasks into smaller tasks in a hierarchical structure chart Chapter
45 Planning Matrixes Function-to-data entity Location-to-function Unit-to-function IS-to-data entity Supporting function-to-data entity which data are captured, used, updated, deleted within each function IS-to-business objective Chapter
46 Customer Product Raw Material Order Work Center Work Order Invoice Equipment Employee Example business function-todata entity matrix (fig. 2.3) Data Entity Types Business Function (users) Business Planning X X X X Product Development X X X X Materials Management X X X X X X Order Fulfillment X X X X X X X X X Order Shipment X X X X X X Sales Summarization X X X X X Production Operations X X X X X X X Finance and Accounting X X X X X X X X Chapter
47 Alternative Approaches to Database and IS Development SDLC System Development Life cycle Detailed, well-planned development process Time-consuming, but comprehensive Long development cycle Prototyping Rapid application development (RAD) Cursory attempt at conceptual data modeling. Define database during development of initial prototype. Repeat implementation and maintenance activities with new prototype versions. Chapter
48 Systems Development Life Cycle (figures 2.4, 2.5) Project Identification and Selection Project Initiation and Planning Analysis Logical Design Physical Design Implementation Maintenance Chapter
49 Systems Development Life Cycle (figures 2.4, 2.5) Project Identification and Selection Project Initiation and Planning Purpose --preliminary understanding Deliverable request for project Analysis Logical Design Physical Design Database activity enterprise modeling Implementation Maintenance Chapter
50 Systems Development Life Cycle (figures 2.4, 2.5) Project Identification and Selection Project Initiation and Planning Purpose state business situation and solution Deliverable request for analysis Analysis Logical Design Physical Design Database activity conceptual data modeling Implementation Maintenance Chapter
51 Systems Development Life Cycle (figures 2.4, 2.5) Project Identification and Selection Project Initiation and Planning Purpose thorough analysis Deliverable functional system specifications Analysis Logical Design Physical Design Database activity conceptual data modeling Implementation Maintenance Chapter
52 Systems Development Life Cycle (figures 2.4, 2.5) Project Identification and Selection Project Initiation and Planning Purpose information requirements structure Deliverable detailed design specifications Analysis Logical Design Physical Design Database activity logical database design Implementation Maintenance Chapter
53 Systems Development Life Cycle (figures 2.4, 2.5) Project Identification and Selection Project Initiation and Planning Purpose develop technology specs Deliverable program/data structures, technology purchases, organization redesigns Analysis Logical Design Physical Design Database activity physical database design Implementation Maintenance Chapter
54 Systems Development Life Cycle (figures 2.4, 2.5) Project Identification and Selection Project Initiation and Planning Purpose programming, testing, training, installation, documenting Deliverable operational programs, documentation, training materials Analysis Logical Design Physical Design Database activity database implementation Implementation Maintenance Chapter
55 Systems Development Life Cycle (figures 2.4, 2.5) Project Identification and Selection Project Initiation and Planning Purpose monitor, repair, enhance Deliverable periodic audits Analysis Logical Design Physical Design Database activity database maintenance Implementation Maintenance Chapter
56 Figure 2-6 The prototyping methodology and database development process Chapter
57 Figure 2-6 The prototyping methodology and database development process Chapter
58 Figure 2-6 The prototyping methodology and database development process Chapter
59 Figure 2-6 The prototyping methodology and database development process Chapter
60 Figure 2-6 The prototyping methodology and database development process Chapter
61 Managing Projects: People Involved Systems analysts Database analysts Users Programmers Database/data administrators Systems programmers, network administrators, testers, technical writers Chapter
62 Figure 2-7a Gantt Chart Shows time estimates of tasks Chapter
63 Figure 2-7b PERT chart Shows dependencies between tasks Chapter
64 Database Schema Physical Schema Physical structures covered in chapters 5 and 6 Conceptual Schema ER models covered in chapters 3 and 4 External Schema User Views Subsets of Conceptual Schema Can be determined from business-function/data entity matrices DBA determines schema for different users This is part of people-management in databases Chapter
65 Figure 2-8 Three-schema database architecture External schema Different people have different views of the database these are the external schema Internal schema Chapter
66 Figure 2-10 Three-tiered client/server database architecture Chapter
67 Pine Valley Furniture Preliminary data model (figure 2-11) Chapter
68 Chapter 3: Modeling Data in the Organization Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden Prentice Hall,
69 SDLC Revisited Data Modeling is an Analysis Activity (figures 2.4, 2.5) Project Identification and Selection Project Initiation and Planning Purpose thorough analysis Deliverable functional system specifications Analysis Logical Design Physical Design Database activity conceptual data modeling Implementation Maintenance Chapter 1 Prentice Hall,
70 Business Rules Statements that define or constrain some aspect of the business Assert business structure Control/influence business behavior Expressed in terms familiar to end users Automated through DBMS software Chapter 1 Prentice Hall,
71 A Good Business Rule is: Declarative what, not how Precise clear, agreed-upon meaning Atomic one statement Consistent internally and externally Expressible structured, natural language Distinct non-redundant Business-oriented understood by business people Chapter 1 Prentice Hall,
72 E-R Model Constructs Entity instance - person, place, object, event, concept (often corresponds to a row in a table) Entity Type collection of entities (often corresponds to a table) Attribute - property or characteristic of an entity type (often corresponds to a field in a table) Relationship instance link between entities (corresponds to primary key-foreign key equivalencies in related tables) Relationship type category of relationship link between entity types Chapter 1 Prentice Hall,
73 Sample E-R Diagram (figure 3-1) Chapter 1 Prentice Hall,
74 Figure Basic E-R Notation Entity symbols A special entity that is also a relationship Relationship symbols Attribute symbols Chapter 1 Prentice Hall,
75 What Should an Entity Be? SHOULD BE: An object that will have many instances in the database An object that will be composed of multiple attributes An object that we are trying to model SHOULD NOT BE: A user of the database system An output of the database system (e.g. a report) Chapter 1 Prentice Hall,
76 Figure 3-4 Inappropriate entities System user System output Appropriate entities Chapter 1 Prentice Hall,
77 Attributes Attribute - property or characteristic of an entity type Classifications of attributes: Simple versus Composite Attribute Single-Valued versus Multivalued Attribute Stored versus Derived Attributes Identifier Attributes Chapter 1 Prentice Hall,
78 Identifiers (Keys) Identifier (Key) - An attribute (or combination of attributes) that uniquely identifies individual instances of an entity type Simple Key versus Composite Key Candidate Key an attribute that could be a key satisfies the requirements for being a key Chapter 1 Prentice Hall,
79 Characteristics of Identifiers Will not change in value Will not be null No intelligent identifiers (e.g. containing locations or people that might change) Substitute new, simple keys for long, composite keys Chapter 1 Prentice Hall,
80 Figure A composite attribute An attribute broken into component parts Chapter 1 Prentice Hall,
81 Figure 3-9a Simple key attribute The key is underlined Chapter 1 Prentice Hall,
82 Figure 3-9b -- Composite key attribute The key is composed of two subparts Chapter 1 Prentice Hall,
83 Figure Entity with a multivalued attribute (Skill) and derived attribute (Years_Employed) What s wrong with this? Derived from date employed and current date Multivalued: an employee can have more than one skill Chapter 1 Prentice Hall,
84 Figure 3-19 an attribute that is both multivalued and composite This is an example of time-stamping Chapter 1 Prentice Hall,
85 More on Relationships Relationship Types vs. Relationship Instances The relationship type is modeled as the diamond and lines between entity types the instance is between specific entity instances Relationships can have attributes These describe features pertaining to the association between the entities in the relationship Two entities can have more than one type of relationship between them (multiple relationships) Associative Entity = combination of relationship and entity More on this later Chapter 1 Prentice Hall,
86 Degree of Relationships Degree of a Relationship is the number of entity types that participate in it Unary Relationship Binary Relationship Ternary Relationship Chapter 1 Prentice Hall,
87 Degree of relationships from figure 3-2 One entity related to another of the same entity type Entities of two different types related to each other Entities of three different types related to each other Chapter 1 Prentice Hall,
88 Cardinality of Relationships One to One Each entity in the relationship will have exactly one related entity One to Many An entity on one side of the relationship can have many related entities, but an entity on the other side will have a maximum of one related entity Many to Many Entities on both sides of the relationship can have many related entities on the other side Chapter 1 Prentice Hall,
89 Cardinality Constraints Cardinality Constraints - the number of instances of one entity that can or must be associated with each instance of another entity. Minimum Cardinality If zero, then optional If one or more, then mandatory Maximum Cardinality The maximum number Chapter 1 Prentice Hall,
90 Cardinality figure 3-2 Chapter 1 Prentice Hall,
91 Unary relationships -- figure 3-12a Chapter 1 Prentice Hall,
92 Binary relationships figure 3-12b Chapter 1 Prentice Hall,
93 Ternary relationships figure 3-12c Note: a relationship can have attributes of its own Chapter 1 Prentice Hall,
94 Basic relationship with only maximum cardinalities showing figure 3-16a Mandatory minimum cardinalities figure 3-17a Chapter 1 Prentice Hall,
95 Figure 3-17c Optional cardinalities with unary degree, one-to-one relationship Chapter 1 Prentice Hall,
96 Figure 3-10a Relationship type 3-10b Entity and Relationship instances Chapter 1 Prentice Hall,
97 Figure 3-11a A binary relationship with an attribute Here, the date completed attribute pertains specifically to the employee s completion of a course it is an attribute of the relationship Chapter 1 Prentice Hall,
98 Figure 3-12c -- A ternary relationship with attributes Chapter 1 Prentice Hall,
99 Figure 3-13a A unary relationship with an attribute. This has a many-to-many relationship Representing a bill-of -materials structure Chapter 1 Prentice Hall,
100 Examples of multiple relationships entities can be related to one another in more than one way Figure 3-21a Employees and departments Chapter 1 Prentice Hall,
101 Figure 3-21b -- Professors and courses (fixed upon constraint) Here,max cardinality constraint is 4 Chapter 1 Prentice Hall,
102 Figure 3-15: Multivalued attribute vs. relationship. Alternative approaches Chapter 1 Prentice Hall,
103 Strong vs. Weak Entities, and Identifying Relationships Strong entities exist independently of other types of entities has its own unique identifier represented with single-line rectangle Weak entity dependent on a strong entity cannot exist on its own Does not have a unique identifier represented with double-line rectangle Identifying relationship links strong entities to weak entities represented with double line diamond Chapter 1 Prentice Hall,
104 Figure 3-5: Strong and weak entities Strong entity Identifying relationship Weak entity Chapter 1 Prentice Hall,
105 Associative Entities It s an entity it has attributes AND it s a relationship it links entities together When should a relationship with attributes instead be an associative entity? All relationships for the associative entity should be many The associative entity could have meaning independent of the other entities The associative entity preferably has a unique identifier, and should also have other attributes The associative may be participating in other relationships other than the entities of the associated relationship Ternary relationships should be converted to associative entities (p102) Chapter 1 Prentice Hall,
106 Figure 3-11b: An associative entity (CERTIFICATE) Associative entity involves a rectangle with a diamond inside. Note that the many-to-many cardinality symbols face toward the associative entity and not toward the other entities Chapter 1 Prentice Hall,
107 Figure 3-13c -- an associative entity bill of materials structure This could just be a relationship with attributes it s a judgment call Chapter 1 Prentice Hall,
108 Figure Ternary relationship as an associative entity Chapter 1 Prentice Hall,
109 Figure 3-22 E-R diagram for Pine Valley Furniture Chapter 1 Prentice Hall,
110 Chapter 4: The Enhanced E-R Model and Business Rules Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden Prentice Hall,
111 Supertypes and Subtypes Subtype: A subgrouping of the entities in an entity type which has attributes that are distinct from those in other subgroupings Supertype: An generic entity type that has a relationship with one or more subtypes Inheritance: Subtype entities inherit values of all attributes of the supertype An instance of a subtype is also an instance of the supertype Chapter Prentice Hall, 2002
112 Figure 4-1 Basic notation for supertype/subtype relationships Chapter Prentice Hall, 2002
113 Figure Employee supertype with three subtypes All employee subtypes will have emp nbr, name, address, and date-hired Each employee subtype will also have its own attributes Chapter Prentice Hall, 2002
114 Relationships and Subtypes Relationships at the supertype level indicate that all subtypes will participate in the relationship The instances of a subtype may participate in a relationship unique to that subtype. In this situation, the relationship is shown at the subtype level Chapter Prentice Hall, 2002
115 Figure Supertype/subtype relationships in a hospital Both outpatients and resident patients are cared for by a responsible physician Only resident patients are assigned to a bed Chapter Prentice Hall, 2002
116 Generalization and Specialization Generalization: The process of defining a more general entity type from a set of more specialized entity types. BOTTOM-UP Specialization: The process of defining one or more subtypes of the supertype, and forming supertype/subtype relationships. TOP-DOWN Chapter Prentice Hall, 2002
117 Figure 4-4 Example of generalization (a) Three entity types: CAR, TRUCK, and MOTORCYCLE All these types of vehicles have common attributes Chapter Prentice Hall, 2002
118 Figure 4-4(b) Generalization to VEHICLE supertype Note: no subtype for motorcycle, since it has no unique attributes Chapter Prentice Hall, 2002
119 Figure 4-5 Example of specialization (a) Entity type PART Applies only to purchased parts Only applies to manufactured parts Chapter Prentice Hall, 2002
120 Figure 4-5(b) Specialization to MANUFACTURED PART and PURCHASED PART Created 2 subtypes Note: multivalued attribute was replaced by a relationship to another entity Chapter Prentice Hall, 2002
121 Constraints in Supertype/ Completeness Constraint Completeness Constraints: Whether an instance of a supertype must also be a member of at least one subtype Total Specialization Rule: Yes (double line) Partial Specialization Rule: No (single line) Chapter Prentice Hall, 2002
122 Figure 4-6 Examples of completeness constraints (a) Total specialization rule A patient must be either an outpatient or a resident patient Chapter Prentice Hall, 2002
123 Figure 4-6(b) Partial specialization rule A vehicle could be a car, a truck, or neither Chapter Prentice Hall, 2002
Chapter 2: The Database Development Process
: The Database Development Process Modern Database Management 7 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden 1 Objectives Definition of terms Describe system development life cycle
More informationOBJECTIVES DEFINITIONS CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS. Figure 1-1a Data in context
OBJECTIVES CHAPTER 1: THE DATABASE ENVIRONMENT AND DEVELOPMENT PROCESS Modern Database Management 11 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi! Define terms! Name limitations of conventional
More informationObjectives Definition iti of terms Importance of data modeling Write good names and definitions for entities, relationships, and attributes Distinguis
Chapter 3: Modeling Data in the Organization Modern Database Management 9 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Heikki Topi 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Objectives
More informationFigure 1-1a Data in context. Context helps users understand data
Chapter 1: The Database Environment Modern Database Management 9 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Heikki Topi 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Definition of terms
More informationQM Chapter 1 Database Fundamentals Version 10 th Ed. Prepared by Dr Kamel Rouibah / Dept QM & IS
QM 433 - Chapter 1 Database Fundamentals Version 10 th Ed Prepared by Dr Kamel Rouibah / Dept QM & IS www.cba.edu.kw/krouibah Dr K. Rouibah / dept QM & IS Chapter 1 (433) Database fundamentals 1 Objectives
More informationDatabase Environment. Pearson Education 2009
Chapter 2 Database Environment 1 Chapter 2 - Objectives Purpose of three-level database architecture. Contents of external, conceptual, and internal levels. Purpose of external/conceptual and conceptual/internal
More informationUnit 2 - Data Modeling. Pratian Technologies (India) Pvt. Ltd.
Unit 2 - Data Modeling Pratian Technologies (India) Pvt. Ltd. Topics Information Engineering Approaches to IS Developments SDLC Prototyping ER Modeling Why Data Modeling? Definition Information Engineering
More informationObjectives Definition iti of terms List five properties of relations State two properties of candidate keys Define first, second, and third normal for
Chapter 5: Logical Database Design and the Relational Model Modern Database Management 9 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Heikki Topi 2009 Pearson Education, Inc. Publishing as Prentice
More informationChapter 2 Conceptual Modeling. Objectives
Chapter 2 Conceptual Modeling Basic Entity Relationship Diagrams 1 Objectives Definition of terms Importance of data modeling Write good names and definitions for entities, relationships, and attributes
More informationAgenda: Understanding Relationship Types Degree and Cardinality with Examples
Data Processing AAOC C311 I Semester 2012 2013 CLASS 4 Agenda: Understanding Relationship Types Degree and Cardinality with Examples Prentice Hall, 2002 1 More on Relationships (A set of meaningful associations
More informationModern Systems Analysis and Design Seventh Edition
Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Structuring System Data Requirements Learning Objectives ü Concisely define each of the following
More informationEssentials of Database Management
Essentials of Database Management Jeffrey A. Hoffer University of Dayton Heikki Topi Bentley University V. Ramesh Indiana University PEARSON Boston Columbus Indianapolis New York San Francisco Upper Saddle
More informationChapter 3 The Enhanced E-R Model
Chapter 3 The Enhanced E-R Model 1 Objectives Define terms Understand duse of supertype/subtype relationships Understand use of specialization and generalization techniques Specify completeness and disjointness
More informationInformation Technology Audit & Cyber Security
Information Technology Audit & Cyber Security Structured Data Requirements Systems & Infrastructure Lifecycle Management with E-R LEARNING OBJECTIVES Explain the role of conceptual data modeling in the
More informationFull file at
Modern Database Management, 10e (Hoffer/Ramesh/Topi) Chapter 2 Modeling Data in the Organization 1) Data modeling may be the most important part of the systems development process because: A) data characteristics
More informationRepresent entities and relations with diagrams
LEARNING OBJECTIVES Define data modeling terms Describe E-R Model Identify entities and relations Represent entities and relations with diagrams WHAT IS DATA MODELING? A data model is a collection of concepts
More informationConceptual Database Design (ER modeling) Chapter Three
Conceptual Database Design (ER modeling) Chapter Three 1 Agenda (Chapter Three) Overview-database design Conceptual Design (E-R Modeling) Structural Constraints EER- Generalization and Specialization Reducing
More informationRelated download: Instructor Manual for Modern Database Management 12th Edition by Hoffer Venkataraman Topi (Case studies included)
Modern Database Management Test Bank, 12e (Hoffer) Completed download: https://testbankarea.com/download/modern-database-management-12thedition-test-bank-hoffer-venkataraman-topi/ Related download: Instructor
More informationNon-overlappingoverlapping. Final outcome of the worked example On pages R&C pages R&C page 157 Fig 3.52
Objectives Computer Science 202 Database Systems: Entity Relation Modelling To learn what a conceptual model is and what its purpose is. To learn the difference between internal models and external models.
More informationThe DBMS accepts requests for data from the application program and instructs the operating system to transfer the appropriate data.
Managing Data Data storage tool must provide the following features: Data definition (data structuring) Data entry (to add new data) Data editing (to change existing data) Querying (a means of extracting
More informationDistributed Database Systems By Syed Bakhtawar Shah Abid Lecturer in Computer Science
Distributed Database Systems By Syed Bakhtawar Shah Abid Lecturer in Computer Science 1 Distributed Database Systems Basic concepts and Definitions Data Collection of facts and figures concerning an object
More informationThe Entity-Relationship Model. The Entity-Relationship model. The ER model. The Entity-Relationship model. E-R Model Constructs. E-R Model Constructs
The Entity-Relationship Model Conceptual Data Modeling The Entity-Relationship model The E-R model is a detailed, logical representation of the data for an organisation or business area It should be understandable
More informationDatabase Systems: Design, Implementation, and Management Tenth Edition. Chapter 9 Database Design
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 9 Database Design Objectives In this chapter, you will learn: That successful database design must reflect the information
More informationEssentials of Database Management (Hoffer et al.) Chapter 2 Modeling Data in the Organization
Essentials of Database Management (Hoffer et al.) Chapter 2 Modeling Data in the Organization 1) The logical representation of an organization's data is called a(n): A) database model. B) entity-relationship
More informationModern Systems Analysis and Design
Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Designing Databases Learning Objectives Concisely define each of the following key database design terms:
More informationData Analysis 1. Chapter 2.1 V3.1. Napier University Dr Gordon Russell
Data Analysis 1 Chapter 2.1 V3.1 Copyright @ Napier University Dr Gordon Russell Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is
More information0. Database Systems 1.1 Introduction to DBMS Information is one of the most valuable resources in this information age! How do we effectively and efficiently manage this information? - How does Wal-Mart
More informationRelational Model (cont d) & Entity Relational Model. Lecture 2
Relational Model (cont d) & Entity Relational Model Lecture 2 Relational Database Operators Relational algebra Defines theoretical way of manipulating table contents using relational operators: SELECT
More informationMODERN DATABASE MANAGEMENT
Global Twelfth Edition Edition MODERN DATABASE MANAGEMENT Jeffrey A. Hoffer University of Dayton V. Ramesh Indiana University Heikki Topi Bentley University PEARSON Boston Columbus Indianapolis New York
More informationIntroduction to Database. Dr Simon Jones Thanks to Mariam Mohaideen
Introduction to Database Dr Simon Jones simon.jones@nyumc.org Thanks to Mariam Mohaideen Today database theory Key learning outcome - is to understand data normalization Thursday, 19 November Introduction
More informationDatabase Systems. Overview - important points. Lecture 5. Some introductory information ERD diagrams Normalization Other stuff 08/03/2015
Lecture 5 Database Systems Instructor: M.Imran Khalil Imrankhalil3@gmail.com Resource:Imrankhalil3.wordpress.com University of Sargodha Canal Campus Lahore Overview - important points Some introductory
More informationChapter 4 Entity Relationship Modeling In this chapter, you will learn:
Chapter Entity Relationship Modeling In this chapter, you will learn: What a conceptual model is and what its purpose is The difference between internal and external models How internal and external models
More informationEntity Relationship Modelling
Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is a relationship? Entities, attributes, and relationships in a system The degree of
More informationCourse Design Document: IS202 Data Management. Version 4.5
Course Design Document: IS202 Data Management Version 4.5 Friday, October 1, 2010 Table of Content 1. Versions History... 4 2. Overview of the Data Management... 5 3. Output and Assessment Summary... 6
More informationChapter 3 Database Modeling and Design II. Database Modeling
Chapter 3 Database Modeling and Design II. Database Modeling Dr. Eng. Shady Aly 1 Data modeling تمثيل مجرد A data model is abstract representation of the data on which the IS application is to be based
More informationInputs. Decisions. Leads to
Chapter 6: Physical Database Design and Performance Modern Database Management 9 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Heikki Topi 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Objectives
More informationObjectives of logical design... Transforming the ERD diagram into relations. Relational database components. Mapping a composite attribute
Logical database design and the relational model Objectives of logical design... Translate the conceptual design into a logical database design that can be implemented on a chosen DBMS Input: conceptual
More informationCHAPTER 6 DATABASE MANAGEMENT SYSTEMS
CHAPTER 6 DATABASE MANAGEMENT SYSTEMS Management Information Systems, 10 th edition, By Raymond McLeod, Jr. and George P. Schell 2007, Prentice Hall, Inc. 1 Learning Objectives Understand the hierarchy
More informationDatabase Systems: Design, Implementation, and Management Tenth Edition. Chapter 1 Database Systems
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 1 Database Systems Objectives In this chapter, you will learn: The difference between data and information What a database
More informationThe Entity Relationship Model
The Entity Relationship Model CPS352: Database Systems Simon Miner Gordon College Last Revised: 2/4/15 Agenda Check-in Introduction to Course Database Environment (db2) SQL Group Exercises The Entity Relationship
More informationA l Ain University Of Science and Technology
A l Ain University Of Science and Technology 4 Handout(4) Database Management Principles and Applications The Entity Relationship (ER) Model http://alainauh.webs.com/ 1 In this chapter, you will learn:
More informationA l Ain University Of Science and Technology
A l Ain University Of Science and Technology 4 Handout(4) Database Management Principles and Applications The Entity Relationship (ER) Model http://alainauh.webs.com/ http://www.comp.nus.edu.sg/~lingt
More informationCOMP Instructor: Dimitris Papadias WWW page:
COMP 5311 Instructor: Dimitris Papadias WWW page: http://www.cse.ust.hk/~dimitris/5311/5311.html Textbook Database System Concepts, A. Silberschatz, H. Korth, and S. Sudarshan. Reference Database Management
More informationChapter 8. Database Design. Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel
Chapter 8 Database Design Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel 1 In this chapter, you will learn: That successful database design must reflect the information
More informationIT 3203 Introduction to Web Development
IT 3203 Introduction to Web Development Databases and SQL April 7 Notice: This session is being recorded. Copyright 2007 by Bob Brown Disadvantages of File Processing Program-Data Dependence All programs
More informationStrategic Information Systems Systems Development Life Cycle. From Turban et al. (2004), Information Technology for Management.
Strategic Information Systems Systems Development Life Cycle Strategic Information System Any information system that changes the goals, processes, products, or environmental relationships to help an organization
More informationMultiple Choice Questions
Chapter 9 Structuring System Data Requirements 193 Chapter 9 Structuring System Data Requirements Multiple Choice Questions 1. Some systems developers believe that a data model is the most important part
More informationData about data is database Select correct option: True False Partially True None of the Above
Within a table, each primary key value. is a minimal super key is always the first field in each table must be numeric must be unique Foreign Key is A field in a table that matches a key field in another
More informationSystems Analysis and Design Methods Chapter 7: Data Modeling and Analysis
Systems Analysis and Design Methods Chapter 7: Data Modeling and Analysis Multiple Choice Questions 1. Which of the following sentence is NOT correct about a logical model: A. is implementation dependent
More informationDatabase Principles: Fundamentals of Design, Implementation, and Management Tenth Edition. Chapter 8 Data Modeling Advanced Concepts
Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition Chapter 8 Data Modeling Advanced Concepts Objectives In this chapter, students will learn: About the extended entity
More informationCMP-3440 Database Systems
CMP-3440 Database Systems Database Architecture Lecture 02 zain 1 Database Design Process Application 1 Conceptual requirements Application 1 External Model Application 2 Application 3 Application 4 External
More informationDatabase Systems: Design, Implementation, and Management Tenth Edition. Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 4 Entity Relationship (ER) Modeling Objectives In this chapter, students will learn: The main characteristics of entity relationship
More informationCS403- Database Management Systems Solved MCQS From Midterm Papers. CS403- Database Management Systems MIDTERM EXAMINATION - Spring 2010
CS403- Database Management Systems Solved MCQS From Midterm Papers April 29,2012 MC100401285 Moaaz.pk@gmail.com Mc100401285@gmail.com PSMD01 CS403- Database Management Systems MIDTERM EXAMINATION - Spring
More informationCS102B: Introduction to Information Systems. Minerva A. Lagarde
CS102B: Introduction to Information Systems Minerva A. Lagarde Module 1: Fundamental Database Concepts Introduction Objectives In this module, the student will learn: 1) Difference between data and information;
More informationChapter 1 Chapter-1
Chapter 1 Chapter-1 Data: Data are the raw facts that can be obtained after some experiments or observations. Raw data is of no use until and unless we process it to find some useful information form it.
More informationChapter 4. In this chapter, you will learn:
Chapter Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel 1 In this chapter, you will learn: The main characteristics of entity
More informationMTAT Introduction to Databases
MTAT.03.105 Introduction to Databases Lecture #4 Entity-Relationship Modelling Ljubov Jaanuska (ljubov.jaanuska@ut.ee) Lecture 3. Summary So far we have been dealing with a relational database (PCA.db)
More informationU1. Data Base Management System (DBMS) Unit -1. MCA 203, Data Base Management System
Data Base Management System (DBMS) Unit -1 New Delhi-63,By Vaibhav Singhal, Asst. Professor U2.1 1 Data Base Management System Data: Data is the basic raw,fact and figures Ex: a name, a digit, a picture
More informationFundamentals of Database Systems (INSY2061)
Fundamentals of Database Systems (INSY2061) 1 What the course is about? These days, organizations are considering data as one important resource like finance, human resource and time. The management of
More informationRelational Database Systems Part 01. Karine Reis Ferreira
Relational Database Systems Part 01 Karine Reis Ferreira karine@dpi.inpe.br Aula da disciplina Computação Aplicada I (CAP 241) 2016 Database System Database: is a collection of related data. represents
More informationReview for Exam 1 CS474 (Norton)
Review for Exam 1 CS474 (Norton) What is a Database? Properties of a database Stores data to derive information Data in a database is, in general: Integrated Shared Persistent Uses of Databases The Integrated
More informationIntro to DB CHAPTER 6
Intro to DB CHAPTER 6 DATABASE DESIGN &THEER E-R MODEL Chapter 6. Entity Relationship Model Design Process Modeling Constraints E-R Diagram Design Issues Weak Entity Sets Extended E-R Features Design of
More informationA database can be modeled as: + a collection of entities, + a set of relationships among entities.
The Relational Model Lecture 2 The Entity-Relationship Model and its Translation to the Relational Model Entity-Relationship (ER) Model + Entity Sets + Relationship Sets + Database Design Issues + Mapping
More informationDatabase Principles: Fundamentals of Design, Implementation, and Management Tenth Edition. Chapter 7 Data Modeling with Entity Relationship Diagrams
Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition Chapter 7 Data Modeling with Entity Relationship Diagrams Objectives In this chapter, students will learn: The
More informationB.H.GARDI COLLEGE OF MASTER OF COMPUTER APPLICATION. Ch. 1 :- Introduction Database Management System - 1
Basic Concepts :- 1. What is Data? Data is a collection of facts from which conclusion may be drawn. In computer science, data is anything in a form suitable for use with a computer. Data is often distinguished
More informationTHE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E)
THE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E) 2 CHAPTER 7 OUTLINE Using High-Level, Conceptual Data Models for Database Design Entity-Relationship (ER) model Popular high-level conceptual
More informationHandout 4. Logical Database Modeling, Part 1: Relational Data Model. Transforming EER model to Relational.
Handout 4 CS-605 Database Management and Modeling -Spring 18 Page 1 of 9 Handout 4 Logical Database Modeling, Part 1: Relational Data Model. Transforming EER model to Relational. Logical Database Design
More informationChapter 6: Entity-Relationship Model. The Next Step: Designing DB Schema. Identifying Entities and their Attributes. The E-R Model.
Chapter 6: Entity-Relationship Model The Next Step: Designing DB Schema Our Story So Far: Relational Tables Databases are structured collections of organized data The Relational model is the most common
More informationMIS Database Systems Entity-Relationship Model.
MIS 335 - Database Systems Entity-Relationship Model http://www.mis.boun.edu.tr/durahim/ Ahmet Onur Durahim Learning Objectives Database Design Main concepts in the ER model? ER Diagrams Database Design
More informationOVERVIEW OF DATABASE DEVELOPMENT
DATABASE SYSTEMS I WEEK 2: THE ENTITY-RELATIONSHIP MODEL OVERVIEW OF DATABASE DEVELOPMENT Requirements Analysis / Ideas High-Level Database Design Conceptual Database Design / Relational Database Schema
More informationE-R Model. Hi! Here in this lecture we are going to discuss about the E-R Model.
E-R Model Hi! Here in this lecture we are going to discuss about the E-R Model. What is Entity-Relationship Model? The entity-relationship model is useful because, as we will soon see, it facilitates communication
More informationFile Processing Approaches
Relational Database Basics Review Overview Database approach Database system Relational model File Processing Approaches Based on file systems Data are recorded in various types of files organized in folders
More informationThe Next Step: Designing DB Schema. Chapter 6: Entity-Relationship Model. The E-R Model. Identifying Entities and their Attributes.
Chapter 6: Entity-Relationship Model Our Story So Far: Relational Tables Databases are structured collections of organized data The Relational model is the most common data organization model The Relational
More informationDatabase Management System CS403 Lecture No 1 Database definitions: 1 A shared collection of logically related data, designed to meet the information
Database Management System CS403 Lecture No 1 Database definitions: 1 A shared collection of logically related data, designed to meet the information needs of multiple users in an organization. 2 A Computerized
More informationIntroduction to Databases
Introduction to Databases 1 Objectives Most common types of digital information processing enter file-based systems Why database systems came around DBMS environment: components / roles Is it all worth
More informationAdvance Database Management System
Advance Database Management System Conceptual Design Lecture- A simplified database design process Database Requirements UoD Requirements Collection and Analysis Functional Requirements A simplified database
More informationEntity-Relationship Model &
Entity-Relationship Model & IST 210 Diagram Todd S. Bacastow IST 210: Organization of data 2/1/2004 1 Design Principles Setting client has (possibly vague) idea of what he/she wants. YOUR task must design
More informationCS403- Database Management Systems Solved Objective Midterm Papers For Preparation of Midterm Exam
CS403- Database Management Systems Solved Objective Midterm Papers For Preparation of Midterm Exam Question No: 1 ( Marks: 1 ) - Please choose one Which of the following is NOT a feature of Context DFD?
More informationDavid M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Chapter Five: Data Modeling with the Entity-Relationship Model Chapter Objectives To understand the two-phase
More information4. Entity Relationship Model
4. Entity Relationship Model a) ER-Model: Used to construct conceptual data model, representing the structure and constraints of a database, which is not dependent on a software (like DBMS) or any data
More informationTechno India Batanagar Computer Science and Engineering. Model Questions. Subject Name: Database Management System Subject Code: CS 601
Techno India Batanagar Computer Science and Engineering Model Questions Subject Name: Database Management System Subject Code: CS 601 Multiple Choice Type Questions 1. Data structure or the data stored
More informationElements of the E-R Model
Chapter 3: The Entity Relationship Model Agenda Basic Concepts of the E-R model (Entities, Attributes, Relationships) Basic Notations of the E-R model ER Model 1 Elements of the E-R Model E-R model was
More informationIMS1002/CSE1205 Lectures 1
IMS1002/CSE1205 Systems Analysis and Design Lecture 2 & 3 Introduction to Data Modelling Entity Relationship Modelling Data Modelling Focus on the information aspects of the organisation In a database
More informationChapter 2: Entity-Relationship Model
Chapter 2: Entity-Relationship Model! Entity Sets! Relationship Sets! Design Issues! Mapping Constraints! Keys! E-R Diagram! Extended E-R Features! Design of an E-R Database Schema! Reduction of an E-R
More informationConceptual Data Modeling
Conceptual Data odeling A data model is a way to describe the structure of the data. In models that are implemented it includes a set of operations that manipulate the data. A Data odel is a combination
More informationFundamentals, Design, and Implementation, 9/e Copyright 2004 Database Processing: Fundamentals, Design, and Implementation, 9/e by David M.
Chapter 5 Database Design Elements of Database Design Fundamentals, Design, and Implementation, 9/e Chapter 5/2 The Database Design Process Create tables and columns from entities and attributes Select
More informationUNIT I. Introduction
UNIT I Introduction Objective To know the need for database system. To study about various data models. To understand the architecture of database system. To introduce Relational database system. Introduction
More informationManaging Data Resources
Chapter 7 Managing Data Resources 7.1 2006 by Prentice Hall OBJECTIVES Describe basic file organization concepts and the problems of managing data resources in a traditional file environment Describe how
More information1. Considering functional dependency, one in which removal from some attributes must affect dependency is called
Q.1 Short Questions Marks 1. Considering functional dependency, one in which removal from some attributes must affect dependency is called 01 A. full functional dependency B. partial dependency C. prime
More informationChapter 2: Entity-Relationship Model. Entity Sets. Entity Sets customer and loan. Attributes. Relationship Sets. A database can be modeled as:
Chapter 2: Entity-Relationship Model Entity Sets Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E-R Diagram Extended E-R Features Design of an E-R Database Schema Reduction of an
More informationBusiness Intelligence and Decision Support Systems
Business Intelligence and Decision Support Systems (9 th Ed., Prentice Hall) Chapter 8: Data Warehousing Learning Objectives Understand the basic definitions and concepts of data warehouses Learn different
More informationnamib I A U n IVERS I TY
namib I A U n IVERS I TY OF SCIEnCE AnD TECH n 0 LOGY FACULTY OF COMPUTING AND INFORMATICS DEPARTMENT OF COMPUTER SCIENCE QUALIFICATION: BACHELOR OF COMPUTER SCIENCE QUALIFICATION CODE: 07BACS LEVEL: 5
More informationUsing High-Level Conceptual Data Models for Database Design A Sample Database Application Entity Types, Entity Sets, Attributes, and Keys
Chapter 7: Data Modeling Using the Entity- Relationship (ER) Model Using High-Level Conceptual Data Models for Database Design A Sample Database Application Entity Types, Entity Sets, Attributes, and Keys
More informationER DIAGRAM ER) diagram, a graphical representation of entities and their relationships to each other, typically used in computing in regard to the
ER DIAGRAM ER) diagram, a graphical representation of entities and their relationships to each other, typically used in computing in regard to the organization of data within databases or information systems.
More informationManagement Information Systems Review Questions. Chapter 6 Foundations of Business Intelligence: Databases and Information Management
Management Information Systems Review Questions Chapter 6 Foundations of Business Intelligence: Databases and Information Management 1) The traditional file environment does not typically have a problem
More informationIS 263 Database Concepts
IS 263 Database Concepts Lecture 1: Database Design Instructor: Henry Kalisti 1 Department of Computer Science and Engineering The Entity-Relationship Model? 2 Introduction to Data Modeling Semantic data
More informationMIT Database Management Systems Lesson 01: Introduction
MIT 22033 Database Management Systems Lesson 01: Introduction By S. Sabraz Nawaz Senior Lecturer in MIT, FMC, SEUSL Learning Outcomes At the end of the module the student will be able to: Describe the
More informationManaging Data Resources
Chapter 7 OBJECTIVES Describe basic file organization concepts and the problems of managing data resources in a traditional file environment Managing Data Resources Describe how a database management system
More informationEntity-Relationship Models: Good Design and Constraints
Entity-Relationship Models: Good Design and T. M. Murali September 29, 2010 T. M. Murali September 29, 2010 CS 4604: E/R Design and Guidelines Be faithful to the specification of the application. Avoid
More informationSOFTWARE ENGINEERING Prof.N.L.Sarda Computer Science & Engineering IIT Bombay. Lecture #10 Process Modelling DFD, Function Decomp (Part 2)
SOFTWARE ENGINEERING Prof.N.L.Sarda Computer Science & Engineering IIT Bombay Lecture #10 Process Modelling DFD, Function Decomp (Part 2) Let us continue with the data modeling topic. So far we have seen
More information