(1)Information Management

5 keys to information management

1. Leadership

2. Operations

3. Processes

4. Data

5. Technology

SET THE VISION/STRATEGY, MAKE KEY DECISION

LEADERSHIP

PEOPLE, PROJECT MANAGEMENT, COMMUNICATIONS

OPERATIONS

DESIGN, DOCUMENT, EXECUTE

PROCESSES

COLLECT, ORGANIZE, MAINTAIN, USE

DATA

TECHNOLOGY ALIGNED TO THE FOUR PRIOR KEYS

TECHNOLOGY

AN ORGANIZED COLLECTION OF LOGICALLY RELATED DATA

DATABASE

Two types of Data

1. STRUCTURED DATA

2. UNSTRUCTURED DATA

- FACTS THAT INCLUDES CUSTOMER NAME, ADDRESS AND MOBILE NUMBER.

✓ NUMERIC, CHARACTER AND DATES

- THIS KIND OF DATA ARE STORED IN TABULAR FORM

STRUCTURED DATA

- MULTIMEDIA DATA

✓ PHOTO IMAGE, SOUND RECORDING OR VIDEO CLIP ❖THE TRADITION DEFINITION OF DATA ARE EXPANDED.

UNSTRUCTURED DATA

Referred to facts concerning objects and events that could be recorded and stored on computer media.

Data

A stored representation of objects and events that have meaning and importance in the user's environment.

EXPANDED DATA

as data that have been processed in a way that the knowledge of the person who uses the data is increase.

Information

It is described as properties or characteristics of end-user data and the context of that data.(data of data)

Meta Data

A person, a place, an object, an event, or a concept in the user environment about which the organization wishes to maintain data.

Entities

A database that represents data as a collection of tables in which all data relationships are represented by common values in related tables.

Relational Databases

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

Database management system

Components of The database environment

1. DATA MODELING AND DESIGN TOOLS

2. REPOSITORY

3. DATABASE MANAGEMENT SYSTEMS

4. Database

5. Application Program

6. User Interface

7. Data and database administrator

8. System developers

9.End users

Software tools that provide automated support for creating data models.

DATA MODELING AND DESIGN TOOLS

A centralized knowledge base of all data definitions, data relationships, screen and report formats, and other system components.

REPOSITORY

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

DATABASE MANAGEMENT SYSTEMS

DATABASE

➢ Is an organized collection of logically related data, usually designed to meet the information needs of multiple users in an organization.

Computer-based application programs are used to create and maintain the database and provide information to users

APPLICATION PROGRAM

➢ It includes languages, menus, and other facilities by which users interact with various system components

USER INTERFACE

Are persons who are responsible for the overall management of data resources in an organization.

DATA AND DATABASE ADMINISTRATOR

➢ are persons such as systems analysts and programmers who design new application programs.

SYSTEM DEVELOPERS

Are persons throughout the organization who add, delete, and modify data in the database and who request or receive information from it

End user

What are the database development process?

1. Enterprise Data modeling - Scope and general contents of database are specified- interview in top down approach

2. Planning- Enterprise Modeling - analysts review current databases and information systems

3. Planning - conceptual data modeling: overall data requirements is analyzed 3.1 develop a diagram 3.2 systems development life cycle

4. Analysis - conceptual data modeling: produce am odel for all organizational data that must be managed

5. design -logical database design: conceptual schema transform into logical. 2nd is combine and reconcile

6. Design Physical database design and definition:one physical schema for each logical schema

7. Implementation- Database implementation: finalize all database documentation, train users and put procedure unto place.(load data from legacy application)

8.

s a detailed technologyindependent specification of the overall structure of organizational data.

Conceptual schema

a set of specifications that describe how data from a logical schema are stored in a computer's secondary memory by a specific database management systems.

Physical Schema

Steps in Systems development life cycle

1. Planning

2. Analysis

3. Design

4. Implementation

5. Maintenance

6. Planning

The traditional methodology used to develop, maintain, and replace information systems.

Systems Development Life Cycle (SLDC)

An iterative process of rapidly repeating analysis, design, and implementation steps until they converge on the system the user wants.

Rapid Application Development (RAD) methods

An iterative process of systems development in which requirements are converted to a working system that is continually revised through close work between analysts and users

An iterative process of systems development in which requirements are converted to a working system that is continually revised through close work between analysts and users

Three-Schema Architecture for Database Development

1. External Schema 2. Conceptual Schema 3. Internal Schema

This is the view (or views) of managers and other employees who are the database users.

External Schema

This schema combines the different external views into a single, coherent, and comprehensive definition of the enterprise's data

External Schema

Consisted of 2 separate schemas: logical and physical schema

This schema combines the different external views into a single, coherent, and comprehensive definition of the enterprise's data

This schema combines the different external views into a single, coherent, and comprehensive definition of the enterprise's data

This schema combines the different external views into a single, coherent, and comprehensive definition of the enterprise's data

describes how data are to be represented are stored in secondary storage using DBMS.

Physical Schema

These individuals concentrate on determining the requirements and design for the database component of the information system.

Database analysts and data modelers

it provides assessments of their information needs and monitor that the developed system meets their needs.

Users

These individuals establish standards for data in business units, striving to attain optimum data location, currency, and quality.

These individuals establish standards for data in business units, striving to attain optimum data location, currency, and quality.

These individuals have responsibility for existing and future databases and ensure consistency and integrity across databases, and as experts on database technology, they provide consulting and training to other project team members.

Data administrators

Project managers oversee assigned projects, including team composition, analysis, design, implementation, and support of projects.

Project Managers

Other individuals are needed in areas such as networking, operating systems, testing, data warehousing, and documentation

Other technical experts

People involved in database development

1. Business analysts

2. Systems analysts

3.Database analysts and data modelers T

4. Users

5. Programmers

6. Database architects

7. Data administrators

8.Project managers

These individuals design and write computer programs that have commands to maintain and access data in the database embedded in them.

Programmers

is a data modeling technique used in software engineering to produce a conceptual data model of an information system.

ERD

Entity → table Attribute → column Relationship → line

"...anything (people, places, objects, events, etc.) about which we store information (e.g. supplier, machine tool, employee, utility pole, airline seat, etc.).”

Entity

are data objects that either identify or describe entities

Attribute

are associations between entities. Typically, a relationship is indicated by a verb connecting two or more entities

Relationship

is the number of occurrences in one entity which are associated to the number of occurrences in another.

Cardinality

What are the three basic cardinalities

one to one, one to many and many to many

uses a standard set of symbols and notations to represent entity types, relationships, attributes, subtypes

CROW’S FOOT NOTATION Known as Industrial Engineering notation

means, you must have at least one and only one instance.

One – Mandatory

means that you must have at least one, but you can have several instances.

Many – Mandatory

means that you don’t have to have an instance, but if you do, you can only have one.

One – Optional

means that you don’t have to have an instance, but if you do, there will be no limit on how many instances you can have.

Many-Optional

The main purpose of a conceptual data model is to understand the main groups of data and their relationships; therefore, descriptive names are important.

CRYPTIC ENTITY NAMES

An entity is a category of similar things or concepts and thus must be singular. Every instance of an entity is one thing that belongs to the category.

PLURAL ENTITY NAMES

The entity name should reflect the essence of the object it represents. Avoid additional superfluous nouns such as entity, object, record, information, or data.

TOO MANY WORDS IN ENTITY NAMES

Data models should be as simple as it is reasonable. Key business entities often have a life cycle with distinct states.

CONFUSING ENTITIES AND CATEGORIES

Most entities require an identifier, a name, or both. This is how we will distinguish the data about each instance of the same entity when storing business data.

MISSING IDENTIFYING ATTRIBUTES

When modelling entities that represent events or transactions, the time attributes must be present.

MISSING TIME ATTRIBUTES

CONFUSING ATTRIBUTES WITH VALUES

When creating data models, learn to focus on the characteristics you need to track, not the values of these characteristics.

A parent and child relationship (one-tomany association) requires that we link the parent and child entity, and there is only one correct way to do it: the child has an attribute linking it to the parent.

INCORRECT PLACEMENT OF ATTRIBUTES LINKING PARENT AND CHILD

A one-to-many relationship exists between two entities. Instead, it is a mistake to try and “squeeze” the information about “many” into “one” as in the example below.

MISSING ONE-TO-MANY RELATIONSHIP