Database development Process
Enterprise data modeling- which establishes the range and general contents of organizational
databases.
-Overall picture or explanation of organizational Data.
-Not the design for a particular database.
-Review the current system
System Development Life Cycle (SDLC)
-A complete set of steps that a team of information systems professionals, including database
designers and programmers, follow in an organization to specify, develop, maintain, and replace
information systems.
(1) Planning – Enterprise Modeling – Review of the enterprise modeling Components that
were developed during the information systems planning process.
-Review the information system, database, analyze the nature of business area that is the subject
of the development project, and describe, in very general terms, the data needed for each
information system under consideration for development.
(1.2) Planning -Conceptual Data modeling- The overall Data Requirement of the proposed
information system must be analyzed.
Planning Phase- the analyst develops a diagram, Documentation, outline the scope of data
involved in this particular development project without consideration of what databases already
exist.
(2) Analysis- Conceptual Data Modeling – Produces Detailed data model that identifies all the
organizational data that must be managed for this information system.
-Every Data attribute is defined.
- All categories of data are listed
- Every business relationship between data entities is represented
-Every rule that dictates the integrity of the data is specified
At this phase it checks the conceptual data model for consistency with other types of models
developed to explain other dimensions of the target information system.
-Steps
-rules in handling data
-timing of events
(3) Design- Logical Database Design - Logical database design approaches database
development from two perspectives.
-The conceptual schema must be transformed into a logical schema, which describes the data in
terms of the data management technology that will be used to implement the database.
-Application in the information system is designed, Including Input, output formats.
-The analyst performs a detailed review of the transactions, report displays, and inquiries
Supported by the database.
(3.1) Design- Physical Database Design and Definition -A physical schema is 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 system.
Physical Database- Requires knowledge of the specific DBMS that will be used to implement
the database.
-In physical database design and definition- an analyst decides on the organization of physical
records, the choice of file organizations, the use of indexes, and so on.
(4) Implementation – Database Implementation- A designer writes, tests, and installs the
programs/scripts that access, create, or modify the database.
-Can use standard programming language (Java, C# or visual basic. net)
-During Implementation- the Designer will finalize all database documentation, train users, and
put procedures into place for the on going support for information system (and database) users.
-The last step is to load data from existing information source.
(5) maintenance - Database management - The last step is to load data from existing
information source.
The Designer:
-Adds
-deletes
-Changes Characteristics of the structure of the database to meet the condition
-To correct errors in database Design
-To improve processing speed of data application
-Might also rebuild database if it becomes Contaminated or destroyed due to program or
computer system malfunction.