Click to edit Master title style

Database Development
Life Cycle
Web Programming---1.4

1
Click to edit Master title style

What Is System Development Life Cycle

• Process used in the development, creation, and maintenance of an
information system.
• Field of software engineering, .
• Process of developing and maintaining software
• Focuses on one aspect of the development.
• Can serve as a useful tool for anyone trying to undertake a large
database project.
• Rich discipline with many different methods
2 2
Click to edit Master title style

A general model
of system
development:
Waterfall
model

3
3
Click to
Steps of edit
DDLC Master title style

• Establishing requirements
• Analysis
• Design
• Implementation
• Testing
• Maintenance

4 4
Click to edit
Purposes Master
of data title style
modeling

5 5
Click to edit
Purposes Master
of data title style
modelling

• Building a data model requires answering questions about entities,

relationships, and attributes.
• Data models can be used to convey the designer’s understanding of the
information requirements of the enterprise.
• The most popular high-level data model used in database design is based on the
concepts of the er model.
• Database design is an iterative process that has a starting point and an almost
endless procession of refinements.
• They should be viewed as learning processes.
• Information gained may well necessitate changes to other parts of the design.
6 6
Click to edit Master title style

• Conceptual database design

• The process of constructing a model of the data used in an enterprise, independent of all
physical considerations such as the target DBMS software, application programs,
programming languages, hardware platform, or any other physical considerations.
• Logical database design
• The process of constructing a model of the data used in an enterprise based on a specific
data model, but independent of a particular DBMS and other physical considerations.
• Physical database design
• The process of producing a description of the implementation of the database on
secondary storage; it describes the base relations, file organizations, and indexes used to
achieve efficient access to the data, and any associated integrity constraints and security
measures.
7 7
Click to edit Master title style

Model of
database
development

8 8
1Click
— Database Development
to edit Master title style Life Cycle:

Requirements gathering
/Planning
• Crucial stage of the SDLC process • Define the problem and scope of existing
system.
• Identifying and defining the project
scope • Overview the new system and determine its
objectives.
• Comprehensive action plan for the
project • Confirm project feasibility and produce the
project Schedule.
• Outlines what will happen throughout
the entire life cycle • During this phase, threats, constraints,
integration and security of system are also
• Success of the entire project
considered.
• A feasibility report for the entire project is
created at the end of this phase.

9 9
Click to edit Master title style

During this phase, the group that is responsible for creating the system
must first determine what the system needs to do for the organization
(requirements gathering). Often this means asking questions such as..
•What do we need this system for ?
•What will the system do for the organization ?
•How are we going to make this system ?
During this initial phase, resources (both human and technology
resources) are put together and a project plan is devised by the project
manager.

1010
Click to edit Master title style
Each course which is available for study is given a course
code, a title and a value for credit points – either a 30-point
course or a 60-point course. A course
may have a quota – the maximum number of students that
can be enrolled on the course in any one year; each quota
is reviewed regularly and the last dat
e of review is recorded with the quota. A course need not
(yet) have any students enrolled on it. Students may not enrol
for more than 180 points’ worth of courses at any one time.
You should note that the above says nothing about how the
data are processed, but it does state what the data items are,
what attributes they have, wha
t constraints apply and the relationships that hold between
the data items. 1111
 Click to edit Master title style
2 — Database Development Life Cycle:
Analysis

• Data requirements • Gather, analyze, and validate the information.

• Conceptual data model • Define the requirements and prototypes for
new system.
• Expectations of the target audience.
• Evaluate the alternatives and prioritize the
• Expectations are then finalized
requirements.
• System makes sense from financial,
• Examine the information needs of end-user
technological, and organizational
and enhances the system goal.
standpoints.
• A Software Requirement Specification (SRS)
• Detailed description of the data that will
document, which specifies the software,
suit user requirements
hardware, functional, and network
requirements of the system is prepared at the
end of this phase.

1212
Click to edit
Conceptual Master
data modeltitle style

• Provides a shared, formal representation of

what is being communicated between
clients and developers
• Irrespective of the eventual use of that
data in user processes or implementation
• Meaning and structure of data
• Not with the details affecting how they are
implemented.

1313
Click to edit Master title style

The Analysis Phase the second phase of the SDLC and is when
the group that has been placed in charge of the project must
decide if the project should go ahead with the resources
available. This also includes looking at any existing system to
see what it is doing for the organization and how well that
system is doing its job. The feasibility of the project is also
considered, and the group has to ask questions such as...
•Can this system be created with the resources (and budget)
we have available?
•Will this system significantly improve the organisation?
•Does the old system even need to be replaced?

1414
 Click to edit Master title style

One of the hardest issues facing an analyst is to perform the analysis without
prejudging decisions about implementation. The analysis is purely focused on the
data requirements and not about how those requirements are to be met, or the
limitations that might be enforced by the DBMS chosen to host the database.
Compromises and enforced limitations resulting from a particular DBMS or
computer system should be dealt with during the implementation phase. The
requirements gathering and analysis tasks should be performed as if the
implementation environment will do everything that needs to be done to satisfy the
requirements being specified. Any compromises made at the analysis stage will
affect the usefulness of the database and may lead to it failing to meet the user
requirements.

1515
Click to edit Master title style
Sample

For each of the following statements decide which processes –

requirements gathering or data analysis – would generate the
statement as part of the documented output.
1.A customer record will allow for the storage of a name, UK
address, evening and daytime phone numbers, one mobile phone
number and as many email addresses as the customer wants to
include.
2.We need to relate customer orders to their credit card details. If
the credit card is invalid we need to know before any orders are
accepted.
3.An order must have the opportunity to include a delivery address
that is different from the customer's credit card billing address.
1616
 Click to edit Master title style
3 — Database Development Life Cycle:
Design

• Starts with a conceptual data model. • Includes the design of application, network,
• Produces a specification of a logical schema. databases, user interfaces, and system
interfaces.
• Determine the specific type of database system.
• Transform the SRS document into logical
• We can use a relational representation of the structure, which contains detailed and
conceptual data model as input to the design complete set of specifications that can be
process. implemented in a programming language.
• Logical schema. • Create a contingency, training, maintenance,
• Choices are made. and operation plan.
• Completeness, integrity, flexibility, efficiency • Review the proposed design. Ensure that the
and usability. final design must meet the requirements stated
• Satisfies the completeness and integrity in SRS document.
requirements, • Finally, prepare a design document which will
be used during next phases.
1717
 Click relational
Using to edit Master
theorytitle
for a style
formal design

There will be occasions when it is necessary to prove

formally that a database satisfies given requirements.
Using relational theory can allow a relational
representation of a conceptual data model to be
analysed rigorously. This stage, which is usually
omitted in all but the most exacting development
environments (such as safety-critical systems),
involves using the formal properties of the relational
theory to mathematically prove properties of the
conceptual data model that would then be realised in
the database design.

1818
Click to edit Master title style

The Design stage is the third stage of the System development life cycle
and it involves the actual creation and design of a system. This is where
they put together the different pieces that will create the system. In a
database approach, this would include...
Layout is made.
•The server hosting the database
•The software that will form the database (Access, Oracle, mySQL, etc)
•Other needed DBMS (Database Management System) software

1919
 Click to edit Master title style
4 — Database Development Life Cycle:
Implementation

• Construction of a database according to the specification of a logical

schema.
• Specification of an appropriate storage schema,
• Heavily influenced by the choice of available DBMS
• Matching the design requirements with the best available implementing
tools
•

2020
Click to edit Master title style

• The Implementation Phase is the final phase of the SDLC and it involves the
actual construction and installation of a system. This phase also includes the
maintenance of the system and any future updates or expansion of the system.
With the database project example, the following activities would be common:
• Physical installation of the server hosting the database
• Installation of the database onto the system
• Installation of the Database Management System
• Initialization and continuous operation of the database and DBMS
• Maintaining the hardware and software hosting the database
• Updating the hardware (physical hard drives, etc) and software (DBMS) as
needed
• Any future expansion of the database.
2121
 Click to edit Master title style
5 — Database Development Life Cycle:
Testing And Integration

• testing and integration of the system • testing of subsystems, security testing, user
testing& unit testing
• procedures to assess
• help all stakeholders determine flaws in the
• expected and fully delivers on the
system prior to deployment
requirements.
• tests small portions of code
• quality assurance (QA) team
• details on how implementation should take
place are imperative to address.

2222
 Click to edit Master title style
6 — Database Development Life Cycle:
Maintenance
• It also includes handling the residual errors
• Checked for bugs and updated with and resolve any issues that may exist in the
features system even after the testing phase.
• Product may perform well upon release • Maintenance and support may be needed for a
• Include all the activities such as phone support longer time for large systems and for a short
or physical on-site support for users that is time for smaller systems.
required once the system is installing.
• Implement the changes that software might
undergo over a period of time, or implement
any new requirements after the software is
deployed at the customer location.

2323
Click to editcan
Maintenance Master title main
take three styleforms:

• Operational maintenance, where the performance of the database is

monitored.
• Porting and implementation maintenance, in which the DBMS, the user
processes, the underlying computer system or some other aspect
undergoes changes that require the database implementation to be
revised.
• Requirements change, where the original requirement specification
changes, usually because databases are frequently used for purposes for
which they were not originally designed. This involves restructuring and
typically involves a ‘mini life cycle’ related to the development of changes
to meet the new requirements.
2424
Click to edit Master title style

The database administrator must be prepared to perform routine maintenance

activities within the database. Some of the required periodic maintenance
activities include:
• Preventive maintenance (backup). Corrective maintenance (recovery).
• Adaptive maintenance (enhancing performance, adding entities and attributes,
and so on).
• Assignment of access permissions and their maintenance for new and old users.
• Generation of database access statistics to improve the efficiency and usefulness
of system audits and to monitor system performance.
• Periodic security audits based on the system-generated statistics.
• Periodic (monthly, quarterly, or yearly) system-usage summaries for internal
billing or budgeting purposes.
2525