L545 Systems Analysis & Design Week 10: November 4, 2008.

Slides:



Advertisements
Similar presentations
Database Design The process of finding user requirement
Advertisements

Entity-Relationship (ER) Modeling
BUSINESS DRIVEN TECHNOLOGY Plug-In T4 Designing Database Applications.
Chapter 10 Analyzing Systems Using Data Dictionaries
System Analysis and Design
Analyzing Systems Using Data Dictionaries Systems Analysis and Design, 7e Kendall & Kendall 8 © 2008 Pearson Prentice Hall.
Data Dictionary What does “Backordered item” mean? What does “New Customer info.” contain? How does the “account receivable report” look like?
3/5/2009Computer systems1 Analyzing System Using Data Dictionaries Computer System: 1. Data Dictionary 2. Data Dictionary Categories 3. Creating Data Dictionary.
Data Dictionary A Data Dictionary is a repository for all the primitive level data structures and data elements within a system. It is a list of everything.
SYSTEM ANALYSIS & DESIGN (DCT 2013)
 To provide you with an overview of the aspects that make up a relational database.  This includes: › Tables › Records › Fields › Data types › Keys.
Analyzing Systems Using Data Dictionaries
The Relational Database Model:
WELL-DESIGNED DATABASES Process faster Easy to develop and maintain Easy to read and write code.
Database Design Chapter 2. Goal of all Information Systems  To add value –Reduce costs –Increase sales or revenue –Provide a competitive advantage.
Chapter 8 Analyzing Systems Using Data Dictionaries
Database Design Concepts Info1408
SE 555 Software Requirements & Specification Requirements Analysis.
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
Information systems and databases Database information systems Read the textbook: Chapter 2: Information systems and databases FOR MORE INFO...
APPENDIX C DESIGNING DATABASES
Oracle Data Definition Language (DDL)
Entity Relationship Modeling
Data Modeling Using the Entity-Relationship Model
IT 244 Database Management System Data Modeling 1 Ref: A First Course in Database System Jeffrey D Ullman & Jennifer Widom.
Databases From A to Boyce Codd. What is a database? It depends on your point of view. For Manovich, a database is a means of structuring information in.
Entities and Attributes
System Analysis and Design
IS 320 Notes for Chapter 8. ClassX Problems: Low-Tech Fix Use last year's videos on ClassX  Select "Semesters" tab  Select IS 320  Select the week/lecture.
The Structured Specification. Why a Structured Specification? System analyst communicates the user requirements to the designer with a document called.
CSCI 3140 Module 2 – Conceptual Database Design Theodore Chiasson Dalhousie University.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
Concepts and Terminology Introduction to Database.
CHAPTER 8: MANAGING DATA RESOURCES. File Organization Terms Field: group of characters that represent something Record: group of related fields File:
UML Diagrams: Class Diagrams The Static Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Databases From A to Boyce Codd. What is a database? It depends on your point of view. For Manovich, a database is a means of structuring information in.
Oracle Data Definition Language (DDL) Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2008.
Relational Databases (MS Access)
Fundamentals of Relational Database Operations
Chapter 7 Database Design and The E–R Model. 2 Goals n Facilitate DB design and represent the overall logical structure of the DB. n Definition Entities.
Information Systems & Databases 2.2) Organisation methods.
1.  An introduction to data modelling  The purpose of data modelling  Modelling data relationships 2.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 Domain Classes.
Database Terminology Database Terminology. DATA: Data is a collection of raw facts and figures and is represented in alphabets, digits and special characters.
Chapter 8 Analyzing Systems Using Data Dictionaries Systems Analysis and Design Kendall & Kendall Sixth Edition.
Copyright © 2011 Pearson Education Analyzing Systems Using Data Dictionaries Systems Analysis and Design, 8e Kendall & Kendall Global Edition 8.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Analyzing Systems Using Data Dictionaries Systems Analysis and Design, 8e Kendall.
Data modeling using the entity-relationship model Chapter 3 Objectives How entities, tuples, attributes and relationships among entities are represented.
+ Information Systems and Databases 2.2 Organisation.
Analyzing Systems Using Data Dictionaries Systems Analysis and Design, 8e Kendall & Kendall 8.
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
Tutorial 2 Data Modelling. 3 Terminology & Notation(1) An entity is an object about which the system needs to hold information –Customer, Student, Course.
DBMS ER model-2 Week 6-7.
Entity Relationship Diagram (ERD). Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship.
COP Introduction to Database Structures
CS 325 Spring ‘09 Chapter 1 Goals:
Chapter 8 Analyzing Systems Using Data Dictionaries
Tools Of Structured Analysis
UML Diagrams: Class Diagrams The Static Analysis Model
© The McGraw-Hill Companies, All Rights Reserved APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
Information Systems Today: Managing in the Digital World
Software Specification Tools
Entity-Relationship Model
Chapter 8 Analyzing Systems Using Data Dictionaries
بسم الله الرحمن الرحيم.
Session 2 Welcome: The seventh learning sequence
MIS2502: Data Analytics Relational Data Modeling
MIS2502: Data Analytics Relational Data Modeling
Chapter 10 Analyzing Systems Using Data Dictionaries
Presentation transcript:

L545 Systems Analysis & Design Week 10: November 4, 2008

S556-Fall Data Dictionary A data dictionary subsystem keeps track of:  the definitions of all the data items in the database  Relationships that exist between various data structures  Screen and report format definitions that may be used by various application programs

S556-Fall Data Dictionaries: Purpose To provide unambiguous definitions of all system data Communicate/validate definitions to all participants in the analysis process:  Analyst  Users  System designers

S556-Fall Level of Data Dictionary Data Elements Data Structure Data flows and Data Stores

S556-Fall Level of Data Dictionary Data Elements  Data elements are pieces of data, which need not be broken further.  Data elements can describe files, data flows, or processes.  Often a data element is self-defining, e.g., Student name, enrolment no.

S556-Fall Level of Data Dictionary Data Structure  Data structure is defined as collection of data elements  For example, let us consider the following "Student Information Record"

S556-Fall Level of Data Dictionary Data Structure  E.g., "Student Information Record“  Student Information Enrolment Number Student name  First name  Last name  Middle name  STUDENT INFORMATION" is a data structure, made up of data elements: student name and enrolment number

S556-Fall Level of Data Dictionary Data flow and data stores  Data flows are paths along which data travels  Data stores are places where data is stored until needed  Data flows are Data structures in motion  Data stores are Data structures at rest

S556-Fall Sample Entry: Attribute A library reserves processing system ITEM Item_status Item_title Item_id Item_author

S556-Fall Sample Entry: Attribute A library reserves processing system ITEM Item_title Item_id Item_author Item_status

S556-Fall Sample Entry: Attribute A library reserves processing system Item Status Alias: Book status, Article status Meaning: The current status of the reserve item being processed Data type: 1 character Possible values: L = lost T = traced R =recalled from current borrower W =in library workroom S = on reserve shelf (processing complete)

S556-Fall Sample Entry: Attribute Name is entry name (e.g., item status) Alias = a synonym for a previously-defined data item Meaning = the semantic aspect of the attribute (i.e., definition) Data type:  at least length and encoding means  Specify the possible values

S556-Fall Examples of Data Formats in PC Systems (Kendall & Kendall, p. 254 Data TypeMeaning Char, textAny alphanumeric character DatetimeAlphanumeric data, several formats Decimal, numericNumeric data that are accurate to the least significant digit CurrencyMonetary numbers accurate to four decimal places AutonumberA number that is always incremented by one when a record is added to a database table

S556-Fall Sample entry: Complex attribute Catalog ordering system Customer address Alias: Client address Meaning: the full mailing address of the person ordering the materials; the address to which the materials are to be delivered Composition: Street address + (Apt. number) + City + State + Zip code Note: No P.O. numbers allowed; U.S. addresses only optional

S556-Fall Sample entry: Complex attribute Define the composition of the entry  Partition/decompose the data into its components  Components = the data elements which make up the complex attribute

S556-Fall Notation for Composition +and; includes all the components listed [ ]or; select one of the alternatives given separate components with | { }repetition of the component enclosed, 0-n ( )enclosed component is optional

S556-Fall Implementing a Data Dictionary Accompanies E-R diagram  Provide additional detail about entities and attributes  Also provide: Meanings of entities/relationships Notes on entities/relationship Ordering of entities  By entity/relationship  Alphabetical, within entity/relationship

S556-Fall Implementing a Data Dictionary Minimize redundancy to ease maintenance  Do not represent anything that is represented elsewhere Use simple conventions for writing definitions

S556-Fall What Does DD Look Like? First, compile a list of fields that appear on existing forms and reports (see Davis p ) For typical data dictionary entries, see Davis p. 84

S556-Fall Example STUDENT PID Name Phone

S556-Fall Example: Data dictionary STUDENT: An individual person who takes a seminar and work PID Meaning: An identification number assigned to uniquely identify each student Data type: numeric/symbolic Possible values: Name Meaning: The name of the student Data type: alphanumeric, up to 30 characters including punctuation Phone Composition: area code + number Phone area code Meaning: area code of the student phone number Data type: alphanumeric, 3 characters Phone number Meaning: local number of the student phone number Data type: alphanumeric, 7 characters

S556-Fall Mapping Specialization & Generalization Relationships ACADEMIC PERSON STUDENTFACULTY d PID Major Appointment

S556-Fall Mapping Specialization & Generalization Relationships ACADEMIC_PERSON PIDNameAddress STUDENT PID Major FACULTY PID Appointment

S556-Fall Example: Data dictionary ACADEMIC_PERSON: An individual person who belongs to a university PID Meaning: An identification number assigned to uniquely identify each academic person Data type: numeric/symbolic Possible values: STUDENT: An individual academic person who is taking courses PID Inherited from ACADEMIC_PERSON.PID Major Meaning: The major that the student is pursuing Data type: alphanumeric, up to 30 characters including punctuation

S556-Fall Example: Data dictionary FACULTY: An individual academic person who is teaching courses PID Inherited from ACADEMIC_PERSON.PID Appointment Meaning: The school of college that the faculty member has an appointment Data type: 4 characters Possible values:  ANTH = Anthropology  BIOL = Biology  HIST = History  JOUR = Journalism  PHYS = Physics  ……  SLIS = School of Library & Information Science

S556-Fall Example ATTEND Passed?

S556-Fall Example: Data dictionary ATTEND: the seminar attended by students Passed Meaning: whether the student attended the session Data type: 1 character Possible values:  Y = Yes  N = No