Information Management [M1]

TRUE

In program data dependency, there is coordination and central control of data. True or false?

Metadata

data that describes the properties and context of user data

Information

data processed to increase knowledge in the person using the data

Unstructured

images, video, documents

Structured

numbers, text, dates

Data

stored representations of meaningful objects and events

Database

organized collection of logically related data

Program-Data Dependence

Disadvantages of File Processing. All programs maintain metadata for each file they use

Excessive Program Maintenance

Disadvantages of File Processing. 80% of information systems budget

Lengthy Development Times

Disadvantages of File Processing. Programmers must design their own file formats

Limited Data Sharing

Disadvantages of File Processing. No centralized control of data

Duplication of Data

Disadvantages of File Processing. Different systems/programs have separate copies of the same data

Database Approach

Solution to File Processing

Database Approach

Central repository of shared data

Database Approach

Data is managed by a controlling agent

Database Approach

Requires a Database Management System (DBMS)

Database Approach

Stored in a standardized, convenient form

Database Management System

A software system that is used to create, maintain, and provide controlled access to user databases

Program-data independence

Advantages of The Database Approach. Programs do not need to manage metadata

Planned data redundancy

Advantages of The Database Approach. Data is stored centrally to reduce duplication

Improved data consistency

Advantages of The Database Approach. Centralized data helps ensure consistent data

Improved data sharing

Advantages of The Database Approach. Centralized databases allow multiple applications to access the same data

Increased application development productivity

Advantages of The Database Approach. Databases reduce time spent on custom file formats

Enforcement of standards

Advantages of The Database Approach. Centralized systems make it easier to maintain organizational data standards

Improved data quality

Advantages of The Database Approach. Ensure that data is consistent and accurate

Improved data accessibility and responsiveness

Advantages of The Database Approach. Central databases enable quick and accurate responses

Reduced program maintenance

Advantages of The Database Approach. Centralized data management systems simplify program maintenance

Improved decision support

Advantages of The Database Approach. Data is more readily available and accurate for decision-making

New, specialized personnel

Costs and Risks of the Database Approach. New experts may be needed for database management.

Installation and management cost and complexity

Costs and Risks of the Database Approach. Database systems are complex to install and manage.

Conversion costs

Costs and Risks of the Database Approach. Converting data from legacy systems to modern databases can be costly.

Need for explicit backup and recovery

Costs and Risks of the Database Approach. Explicit backup and recovery plans are required.

Organizational conflict

Costs and Risks of the Database Approach. Changes in how data is managed can lead to resistance within organizations.

Elements of the Database Approach

Data models, Entities, Relationships, Relational Databases

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

Components of the Database Environment. Computer-aided software engineering

Repository

Components of the Database Environment. Centralized storehouse of metadata

Database Management System (DBMS)

Components of the Database Environment. Software for managing the database

Database

Components of the Database Environment. Storehouse of the data

Application Programs

Components of the Database Environment. Software using the data

User Interface

Components of the Database Environment. Text and graphical displays to users

Data/Database Administrators

Components of the Database Environment. Personnel responsible for maintaining the database

System Developers

Components of the Database Environment. Personnel responsible for designing databases and software

End Users

Components of the Database Environment. People who use the applications and databases

System Development Life Cycle

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

Planning

System Development Life Cycle (SDLC). Establish a preliminary understanding of the database needs and request for a study.

Analysis

System Development Life Cycle (SDLC). Conduct a detailed requirements analysis and develop an integrated conceptual model.

Logical Design

System Development Life Cycle (SDLC). Focus on structuring the database to meet information requirements, resulting in a detailed design specification.

Physical Design

System Development Life Cycle (SDLC). Specify the physical structure of the database, including data organization and system configuration.

Implementation

System Development Life Cycle (SDLC). Code the database, test it, and train users; includes creating documentation and conversion.

Maintenance

System Development Life Cycle (SDLC). Perform audits, analyze performance, and make necessary corrections or enhancements.

Prototyping Approach

Rapid Application Development (RAD): A faster method for developing databases by iterating on prototypes

Prototyping Approach

Involves cursory conceptual modeling and continuously refining the system through repeated implementations.

External Schema

Three-Schema Architecture. Different views of the database for various users (business-function/data entity matrices)

Conceptual Schema

Three-Schema Architecture. Entity-relationship (E-R) models describing the structure of the data.

Internal Schema

Three-Schema Architecture. Defines the logical and physical structure of the database.

Business Analysts

Roles in the Database Development Process. Focus on business requirements.

Systems Analysts

Roles in the Database Development Process. Bridge the business and technical sides.

Database Analysts

Roles in the Database Development Process. Design databases and create data models.

Data/Database Administrators

Roles in the Database Development Process. Oversee the operational integrity of the database.

Project Managers

Roles in the Database Development Process. Ensure that the database project meets objectives and timelines.

Users

Roles in the Database Development Process. Provide input on system requirements and interface needs.

Programmers

Roles in the Database Development Process. Develop database applications and integration.

Database Architects

Roles in the Database Development Process. Create the high-level structure of the database system.

Other Technical Experts

Roles in the Database Development Process. Handle specialized tasks such as security and performance tuning.