ISYS6198 – Data and Information

Management
COURSE EXPLANATION
 COURSE DESCRIPTION

• This course introduces the core concepts in data

and information management, started from
identifying organizational information
requirements until design physical database for
relational database based on Database System
Development Lifecycle
• This course also helps the students understand
the concepts and methodologies of database
design and gives student knowledge related to
database design
 GRADING
Database Design Project :
1. Make group of 4-5 persons
2. Select 1 Company to design database
3. Perform project presentation :
 Part 1 - Session 13-14 (Database System
Development Lifecycle, Database Analysis,
Conceptual Database Design, Logical Database
Design)
 Part 2- Session 25-26 (Revised Logical Database
Design, Physical Database Design, Application
Design)

Assignment (Project)
30%

Final Exam
35%

Mid Exam
35%
 PROJECT PRESENTATION FORMAT
Part 1

• Company Profile (Include Organization

Structure)
• Company Business Process
• Problem Statements
• Database Planning
• System Definition
• Requirement Collection and Analysis
• Database Design
– Conceptual ER Modeling
– Logical ER Modeling & Normalization
 PROJECT PRESENTATION FORMAT
Part 2

• Summary of Company Overview and Database

Planning
• Revised Database Design
– Logical ER Modeling
– Normalization
• Physical Database Design
• User Interface Design
 Database Foundations Certified Junior
Associate

• Special discount (25%), if you register as Oracle Academy

Member (Institutional Member under Universitas Bina
Nusantara)
• https://
academy.oracle.com/en/resources-junior-certifications.htm
l
• https://
education.oracle.com/oracle-database-foundations-novice-l
evel-exam/pexam_1Z0-006
Course : ISYS6198 – Data and Information
Management
Year : 2020

DATABASE SYSTEM
DEVELOPMENT LIFECYCLE
Session 1
 LEARNING OUTCOME

LO 1: Describe the concept of data and

information management as suitable with
Database System Development Life Cycle
and database design methodologies
 ACKNOWLEDGEMENT

These slides have been adapted

from:
- Thomas Connolly and Carolyn
Begg. 2015. Database Systems:
A Practical Approach To Design,
Implementation, and
Management. Pearson
Education. USA. ISBN:978-1-
292-06118-4, Chapter 10
- Oracle Academy, Database
Design, Section 1, 2, 10
 LEARNING OBJECTIVES

• List and describe the different stages of

Database System Development Life Cycle
(DBSDLC)
• List and describe the different stages of the
system development life cycle (SDLC)
• List and explain the three major steps in the
database development process
• Distinguish between Conceptual, logical, and
physical model

Bina Nusantara
DATABASE SYSTEM DEVELOPMENT
LIFECYCLE
 Database System
Development Lifecycle
• Database is fundamental component of IS, and
its development/usage should be viewed from
perspective of the wider requirements of the
organization.
• The Database System Development Lifecycle is
inherently associated with the lifecycle of the
information system
• It is important to recognize that the stages of
the database system development lifecycle are
not strictly sequential but involve some amount
of repetition of previous stage through
feedback loops.
Bina Nusantara
 Database
System
Developmen
t Lifecycle
Page 348, Connolly
Database Systems

Bina Nusantara
 1. Database Planning

In this step we define mission statement for database

system which is objectives for our database applications

Once mission statement is defined,

mission objectives are defined.

Each objective should identify a particular

task that the database must support.

Bina Nusantara
 1. Database Planning

• Database planning should also include

development of standards that govern:
– how data will be collected,
– how the format should be specified,
– what necessary documentation will be
needed,
– how design and implementation should
proceed.

2020projectmanagement.com
Bina Nusantara
 2. System Definition

• Describes scope and boundaries of database

system and the major user views.
• User view defines what is required of a
database system from perspective of:
– a particular job role (such as Manager or
Supervisor) or
– enterprise application area (such as
marketing, personnel, or stock control).

Bina Nusantara www.ticopa.com

 2. System Definition

• Database application may have one or more

user views.
• Identifying user views helps ensure that no
major users of the database are forgotten
when developing requirements for new
system.
• User views also help in development of
complex database system allowing
requirements to be broken down into
manageable pieces.

Bina Nusantara
 Representation of a Database
System with Multiple User
Views

Bina Nusantara
 3. Requirements Collection
and Analysis
• Process of collecting and analyzing information
about the part of organization to be supported
by the database system, and using this
information to identify users’ requirements of
new system.
• Information is gathered for each major user
view including:
– a description of data used or generated;
– details of how data is to be used/generated;
– any additional requirements for new
database system.

Bina Nusantara
 3. Requirements Collection
and Analysis
• Information is analyzed to identify
requirements to be included in new database
system. Described in the requirements
specification.
• Another important activity is deciding how to
manage the requirements for a database
system with multiple user views.
• Three main approaches:
– centralized approach;
– view integration approach;
– combination of both approaches.

Bina Nusantara
 Centralized Approach to
Managing Multiple User

Bina Nusantara
 View Integration Approach

• Data model representing single user view (or

a subset of all user views) is called a local
data model.
• Each model includes diagrams and
documentation describing requirements for
one or more but not all user views of
database.
• Local data models are then merged at a later
stage during database design to produce a
global data model, which represents all user
views for the database.

Bina Nusantara
 View Integration Approach to
Managing Multiple User View

Bina Nusantara
 4. Database Design

• Process of creating a design for a database

that will support the enterprise’s mission
statement and mission objectives for the
required database system.
• Main approaches include:
– Top-down
– Bottom-up
– Inside-out
– Mixed : uses both bottom-up and top-
down

Bina Nusantara
 4. Database Design

• Building data model requires answering

questions about entities, relationships, and
attributes.
• A data model ensures we understand:
- each user’s perspective of the data;
- nature of the data itself, independent of its
physical representations;
- use of data across user views.

Bina Nusantara
www.compbuilding.com
 Criteria to Produce an
Optimal Data Model

Bina Nusantara
 Three phases of database
design

Conceptual
database
design

Physical Logical
database database
design. design

Bina Nusantara
 4.1 Conceptual Database
Design
• Process of constructing a model of the data
used in an enterprise, independent of all
physical considerations.

• Data model is built using the information in

users’ requirements specification.

• Conceptual data model is source of

information for logical design phase.

Bina Nusantara
 4.2 Logical Database Design

• Process of constructing a model of the data

used in an enterprise based on a specific data
model (e.g. relational), but independent of a
particular DBMS and other physical
considerations.

• Conceptual data model is refined and

mapped on to a logical data model.

Bina Nusantara
 4.3 Physical Database Design

• Process of producing a description of the

database implementation on secondary
storage.

• Describes base relations, file organizations,

and indexes used to achieve efficient access
to data. Also describes any associated
integrity constraints and security measures.

• Tailored to a specific DBMS system.

Bina Nusantara
 Three-Level ANSI-SPARC
Architecture and Phases of
Database Design

Bina Nusantara
 5. DBMS Selection

• Selection of an appropriate DBMS to support

the database system.
• Undertaken at any time prior to logical design
provided sufficient information is available
regarding system requirements.
• Main steps to selecting a DBMS:
– define Terms of Reference of study;
– shortlist two or three products;
– evaluate products;
– recommend selection and produce report.

Bina Nusantara
 6. Application Design

• Design of user interface and application

programs that use and process the database.
• Database design and application design are
parallel activities.
• Includes two important activities:
– transaction design;
– user interface design.

Bina Nusantara
 7. Prototyping

• Building working model of a database system.

• Purpose
– to identify features of a system that work
well, or are inadequate;
– to suggest improvements or even new
features;
– to clarify the users’ requirements;
– to evaluate feasibility of a particular
system design.

Bina Nusantara
 8. Implementation

• Physical realization of the database and

application designs.
– Use DDL to create database schemas and
empty database files.
– Use DDL to create any specified user views.
– Use 3GL or 4GL to create the application
programs. This will include the database
transactions implemented using the DML,
possibly embedded in a host programming
language.

Bina Nusantara
 9. Data Conversion and Loading

• Transferring any existing data into new

database and converting any existing
applications to run on new database.
• Only required when new database system is
replacing an old system.
– DBMS normally has utility that loads
existing files into new database.
• May be possible to convert and use
application programs from old system for use
by new system.

Bina Nusantara
 10. Testing

• Process of running the database system with

intent of finding errors.
• Demonstrates that database and application
programs appear to be working according to
requirements.
• Evaluation conducted against a usability
specification. Examples of criteria include:
– Learnability;
– Performance;
– Robustness;
– Recoverability;
– Adaptability.
Bina Nusantara
 11. Operational Maintenance

• Process of monitoring and maintaining

database system following installation.
• Monitoring performance of system.
– if performance falls, may require tuning or
reorganization of the database.
• Maintaining and upgrading database
application (when required).
• Incorporating new requirements into database
application.

Bina Nusantara http://orbex.co.in

 CASE Tools
Support provided by CASE tools include :

Data dictionary
to store Design tools to
information support data
about database analysis
system’s data

Tools to permit
development of Tools to
corporate data
enable
model, and
conceptual and prototyping of
logical data applications.
models

Bina Nusantara
 CASE Tools

• Provide following benefits:

– Standards;
– Integration;
– Support for standard methods
– Consistency;
– Automation .

edlivetoday.com
Bina Nusantara
 CASE Tools and Database System
Development Lifecycle

Bina Nusantara
System Development Life Cycle
 System Development Life
Cycle

• A database also can be

developed from concept
through production, by using the
system development life cycle
(SDLC) for software
development.

• Applying this top-down,

systematic approach to
database development
transforms business-information
requirements into an
operational database.
 Strategy and Analysis

• Study and analyze the business requirements.

• Interview users and managers to identify the information
requirements.
• Incorporate the enterprise and application mission
statements as well as any future system specifications.
• Build conceptual models of the system.
• Transfer the business narrative into a graphical
representation of business-information needs and rules.
• Confirm and refine the model with the analysts and experts.
 Design

• Transform the model developed in the strategy and analysis

phase.
• Map entities to tables, attributes to columns, relationships
to foreign keys, and business rules to constraints.
 Build

• Write and execute the commands to create the tables and

supporting objects for the database.
• Populate the tables with data.
• Develop user documentation, help text, and operations
manuals to support the use and operation of the system.
 Transition

• Conduct user-acceptance testing.

This type of testing is where monitored users determine
whether a system meets all their requirements, and will
support the business for which it was designed.
• Convert existing data
• Parallel operations.
Both systems (old and new) are running at the same time.
This is done to give users time to train and switch over to
the new system and to check that the new system is
producing the same results as the old system
• Make any modifications required.
 Production

• Production phase tasks:

– Roll out the system to the users.
– Operate the production system.
– Monitor its performance and enhance and refine the
system.
• The various phases of the system development life cycle can
be carried out iteratively.
Database Development Process
 Database Development Process

• Data modeling is the first

step in the database
development process.
• It involves collecting and
analyzing the data that a
business needs to track,
and then diagramming
the organization of that
data in an Entity
Relationship Diagram.
• Data modeling begins by
researching the
information requirements
of a business.
 Database Development Process

• An entity relationship
diagram should
completely capture and
accurately model the
organization’s information
needs and support the
functions of the business.
• The database design
phase of the development
process, translates the
information modeled on
the entity relationship
diagram to a table
instance chart.
 Database Development Process
The table instance chart lists the design
specifications of the information and has
the following components
• Table name
• Column names
• Keys: a primary key (PK) is the unique
identifier for each row of data; a
foreign key (FK) links data in one table
to the data in a second table by
referring to the PK column in the
second table
• Nulls: indicates if a column must
contain a value (mandatory)
• Unique: indicates if the value contained
in a column is unique within the table
• Data type: identifies the definition and
format of the data stored in each
column
 Database Development Process

• Structured Query
Language (SQL)
commands are used to
build the physical
structure of the
database.
• SQL is also used to
populate, access, and
manipulate the data
within the relational
database.
Conceptual, Logical, Physical
Model
 Conceptual, Logical, Physical Model

• It is the art of planning, developing, and communicating

that allows a group of people to work together to achieve a
desired outcome.
• Data modeling is the process of capturing the important
concepts and rules that shape a business and depicting
them visually on a diagram.
• This diagram becomes the blueprint for designing the
physical thing.
• The client’s dream (conceptual model) will become a
physical reality (physical model).
 A conceptual model
• Identifies :
– important entities (objects that become tables in
database)
– relationships among entities
• Does not specify :
– attributes (objects that become columns or fields in
database)
– unique identifiers (attribute that becomes primary key in
database).
 A conceptual model
• Captures the functional and informational needs of a
business
• Is based on current needs but it may reflect future needs
• Addresses the needs of a business (what is conceptually
ideal), but does not address its implementation (what is
physically possible)
• Is the result of completing the Data Modeling process
 A conceptual model
• Identifies :
– important entities (objects that become tables in
database)
– relationships among entities
• Does not specify :
– attributes (objects that become columns or fields in
database)
– unique identifiers (attribute that becomes primary key in
database).
 A conceptual model
• A conceptual model is important to a business because it:
– Describes exactly the information needs of the business
– Facilitates discussion
– Prevents mistakes and misunderstandings
– Forms important “ideal system” documentation
– Forms a sound basis for physical database design
– Documents the processes (also known as the “business
rules”) of the business
– Takes into account regulations and laws governing this
industry
 A logical model
• Includes all entities and relationships among them.
• Is called an entity relationship model (ERM).
• Is illustrated in an ERD.
• Specifies all attributes and UIDs for each entity.
• Determines attribute optionality.
• Determines relationship optionality and cardinality.
 A physical model
• Is an extension to a logical data model.
• Defines table definitions, data types, and precision.
• Identifies views, indexes, and other database objects.
• Describes how the objects should be implemented in specific
database.
• Shows all table structures, including columns, primary keys,
and foreign keys.
SCHOOL OF INFORMATION SYSTEMS
http://sis.binus.ac.id
/
http ://www.facebook.com/schoolisbinus

SIS Binus