Information Management - Module 1: Database Environment & Development Process PDF

Document Details

FEU Alabang, FEU Diliman, FEU Institute of Technology

2018

Tags

database management systems database development information management database design

Summary

This document is a module on information management, specifically focusing on database environment and development. It covers the fundamentals of databases, data models, and related elements. The module is clearly a part of an introductory database course.

Full Transcript

INFORMATION MANAGEMENT Module 1: Database Environment and Development Process MODULE 1 SUBTOPIC 1 THE DATABASE ENVIRONMENT At the end of the chapter, the learner should be able to: Define Terms. Name limitations of conventional file processing E...

INFORMATION MANAGEMENT Module 1: Database Environment and Development Process MODULE 1 SUBTOPIC 1 THE DATABASE ENVIRONMENT At the end of the chapter, the learner should be able to: Define Terms. Name limitations of conventional file processing Explain advantages of databases Identify costs and risks of databases List components of database environment Identify categories of database applications Database: organized collection of logically related data Data: stored representations of meaningful objects and events Structured: numbers, text, dates Unstructured: images, video, documents Information: data processed to increase knowledge in the person using the data Metadata: data that describes the properties and context of user data Context helps users understand data Graphical displays turn data into useful information that managers can use for decision making and interpretation Descriptions of the properties or characteristics of the data, including data types, field sizes, allowable values, and data context Database Systems 1 Program-Data Dependence All programs maintain metadata for each file they use Database Systems 1 Duplication of Data Different systems/programs have separate copies of the same data Database Systems 1 Limited Data Sharing No centralized control of data Database Systems 1 Lengthy Development Times Programmers must design their own file formats Database Systems 1 Excessive Program Maintenance 80% of information systems budget Database Systems 1 Central repository of shared data Data is managed by a controlling agent Stored in a standardized, convenient form Requires a Database Management System (DBMS) Database Systems 1 A software system that is used to create, maintain, and provide controlled access to user databases Order Filing System Invoicing Central database DBMS System Contains employee, order, inventory, Payroll pricing, and System customer data Database Systems 1 1. Program-data independence 2. Planned data redundancy 3. Improved data consistency 4. Improved data sharing 5. Increased application development productivity Database Systems 1 6. Enforcement of standards 7. Improved data quality 8. Improved data accessibility and responsiveness 9. Reduced program maintenance 10.Improved decision support Database Systems 1 1. New, specialized personnel 2. Installation and management cost and complexity 3. Conversion costs 4. Need for explicit backup and recovery 5. Organizational conflict Data models – Graphical system capturing nature and relationship of data – Enterprise Data Model–high-level entities and relationships for the organization – Project Data Model–more detailed view, matching data structure in database or data warehouse Entities – Noun form describing a person, place, object, event, or concept – Composed of attributes Relationships – Between entities – Usually one-to-many (1:M) or many-to-many (M:N) Relational Databases – Database technology involving tables (relations) representing entities and primary/foreign keys representing relationships 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/Database 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 Application Programs–software using the data User Interface–text and graphical displays to users Data/Database 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 END OF MODULE 1 SUBTOPIC 1 MODULE 1 SUBTOPIC 2 DATABASE DEVELOPMENT PROCESS At the end of the chapter, the learner should be able to: Describe database system development life cycle Explain prototyping and agile development approaches Explain roles of individuals Explain the three-schema architecture for databases 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 Database Systems 1 Planning Analysis Logical Design Physical Design Implementation Maintenance Database Systems 1 Planning Planning Purpose–preliminary understanding Deliverable–request for study Analysis Logical Design Physical Design Database activity– Implementation enterprise modeling and early conceptual Maintenance data modeling Database Systems 1 Purpose–thorough requirements analysis Planning and structuring Deliverable–functional system specifications Analysis Analysis Logical Design Physical Design Database activity–thorough Implementation and integrated conceptual data modeling Maintenance Database Systems 1 Purpose–information requirements elicitation Planning and structure Deliverable–detailed design specifications Analysis Logical Design Logical Design Physical Design Database activity– Implementation logical database design (transactions, forms, Maintenance displays, views, data integrity and security) Database Systems 1 Purpose–develop technology and Planning organizational specifications Analysis Deliverable–program/data structures, technology purchases, organization redesigns Logical Design Physical Design Physical Design Database activity– Implementation physical database design (define database to DBMS, Maintenance physical data organization, database processing programs) Database Systems 1 Purpose–programming, testing, Planning training, installation, documenting Analysis Deliverable–operational programs, documentation, training materials Logical Design Physical Design Database activity– Implementation Implementation database implementation, including coded programs, documentation, Maintenance installation and conversion Database Systems 1 Planning Purpose–monitor, repair, enhance Analysis Deliverable–periodic audits Logical Design Physical Design Database activity– Implementation database maintenance, performance analysis and tuning, error Maintenance Maintenance corrections Database Systems 1 External Schema User Views Subsets of Conceptual Schema Can be determined from business-function/data entity matrices DBA determines schema for different users Conceptual Schema E-R models Internal Schema Logical structures Physical structures Database Systems 1 Different people have different views of the database…these are the external schema The internal schema is the underlying design and implementation Database Systems 1 Project–a planned undertaking of related activities to reach an objective that has a beginning and an end Initiated and planned in planning stage of SDLC Executed during analysis, design, and implementation Closed at the end of implementation Database Systems 1 Business analysts Systems analysts Database analysts and data modelers Data/Database administrators Project managers Users Programmers Database architects Other technical experts Database Systems 1 Driven by four main objectives: Need for program-data independence ➔ reduced maintenance Desire to manage more complex data types and structures Ease of data access for less technical personnel Need for more powerful decision support platforms Database Systems 1 Database Systems 1 Database Systems 1 Database Systems 1 Database Systems 1 Database Systems 1 Database Systems 1 Database Systems 1 Database Systems 1 Personal databases Multitier client/server databases Enterprise applications Enterprise resource planning (ERP) systems Data warehousing implementations Database Systems 1 Database Systems 1 Database Systems 1 Taylor, A. G. (2019). SQL for dummies (9th ed.). Hoboken, NJ: For Dummies. Harrington, J. (2016). Relational Database Design and Implementation (4th Edition). Morgan Kaufmann Juric, N., Vrbsky, S., Nestorov, S. (2016). Database Systems: Introduction to Databases and Data Warehouses. Prospect Press Kroenke, D. M., & Auer, D. J. (2016). Database Concepts. Pearson. Sullivan, D. (2015). NoSQL for Mere Mortals (1st ed.). Boston: Addison- Wesley. Hoffer, J., Ramesh, V., Topi, H. (2016). Modern Database Management 12th Edition, Prentice Hall. END OF SUBTOPIC 2 END OF MODULE 1

Use Quizgecko on...
Browser
Browser