Business Data Management

Assignment 1
By: Abhishek Singh
MB17GBA173

Database Development Life Cycle

A DDLC is a subset of SDLC [Software development life cycle] and is used to design, plan,
develop, deploy, maintain a database. A DDLC pens down the life of a database that could be from
a simple drawing on your board to actual deployment and maintenance at client live-side. The
different phases of SDLC’s are as follows:
1) Database Initial Study:
The first baby step of database development lifecycle is to gather answers for “what and
why” a database is needed and designed for. Following are the guidelines that could be
helpful to an analyst are –

 Clearly identify the data needs and requirements a user has regarding performance,
security, and accessibility and data volume.
 Categorize the problems, constraints that you foresee or experience in the current/old
database. Getting feedback from the users at this point may be worthwhile.
 Delineate the design objectives of the proposed database. Make sure to address issues
like data security, data integrity, performance, concurrency,
 Define and document the design guidelines and standards such as – the naming
conventions, the diagramming standards, nomenclatures to be adopted.

2) Database Design:
This phase focuses on the design of the database model that will support company
operations and objectives. This is arguably the most critical phase: making sure that the
final product meets user and system requirements. Following points must be remembered
while examining the procedures required to complete the design phase in the DBLC:
 The process of database design is loosely related to the analysis and design of a larger
system. The data component is only one element of a larger information system.
 The systems analysts or systems programmers are in charge of designing the other
system components. Their activities create the procedures that will help transform the
data within the database into useful information.
Following pointers to assist with the conceptual design are as follows:
 Analyze the data regarding its characteristics, what type of output is expected, how and
who would be the audience using the data and data output.
 Create a data model with entities and relationship using ER or UML or the tool of your
choice.
 Validate each data and ER with the requirements
 Get it verified with the clients/users.

3) Implementation and Loading:

The output of the database design phase is a series of instructions detailing the creation of
tables, attributes, domains, views, indexes, security constraints, and storage and
performance guidelines. In this phase, all these design specifications are implemented.
 Install the DBMS:
This step is required only when a new dedicated instance of the DBMS is necessary
for the system. The DBMS may be installed on a new server or it may be installed
on existing servers. One current trend is called virtualization. Virtualization is a
technique that creates logical representations of computing resources that are
independent of the underlying physical computing resources.
  Create the Database(s):
In most modern relational DBMSs a new database implementation requires the
creation of special storage-related constructs to house the end-user tables. The
constructs usually include the storage group (or file groups), the table spaces, and
the tables.

 Load or Convert the Data:

After the database has been created, the data must be loaded into the database tables.
Typically, the data will have to be migrated from the prior version of the system.
Often, data to be included in the system must be aggregated from multiple sources.
Data may have to be imported from other relational databases, non-relational
databases, flat files, legacy systems, or even manual paper-and-pencil systems.

4) Testing and Evaluation:

In the design phase, decisions were made to ensure integrity, security, performance, and
recoverability of the database. During implementation and loading, these plans were put
into place. In testing and evaluation, the DBA tests and fine-tunes the database to ensure
that it performs as expected. This phase occurs in conjunction with applications
programming.

 Test the Database:

During this step, the DBA tests the database to ensure that it maintains the integrity
and security of the data. Data integrity is enforced by the DBMS through the proper
use of primary and foreign key rules. In database testing one must check Physical
security allows, Password security, Access rights, Data encryption etc.
 Fine-Tune the Database:
Although database performance can be difficult to evaluate because there are no
standards for database performance measures, it is typically one of the most
important factors in database implementation. Different systems will place different
performance requirements on the database. Many factors can impact the database’s
performance on various tasks. Environmental factors, such as the hardware and
software environment in which the database exists, can have a significant impact
on database performance.

 Evaluate the Database and Its Application Programs:

As the database and application programs are created and tested, the system must
also be evaluated from a more holistic approach. Testing and evaluation of the
individual components should culminate in a variety of broader system tests to
ensure that all of the components interact properly to meet the needs of the users.
 To ensure that the data contained in the database are protected against loss, backup
and recovery plans are tested.

5) Operation
Once the database has passed the evaluation stage, it is considered to be operational. At
that point, the database, its management, its users, and its application programs constitute
a complete information system. The beginning of the operational phase invariably starts
the process of system evolution.

6) Maintenance and Evaluation

The tricky part is the evaluation of tools and picking the one that suits your project, budget,
performance needs and ease of use. Apart from the factors just described also consider
following factors while exploring the tool –

 Do the features inbuilt in the tool matches the expectation set by your project and
database team?
 What’s the SLA provided by the third party [the tool provider] in the case of any
technical issues?
 What type of “data model” you are looking at? Most of the DBMS tools have an
underlying data model like – Network, Hierarchical, Object-Relational, and
Relational.
 Is the tool compatible enough across different platforms and languages?

After evaluating the tool we move towards maintaining it, this is not just about maintaining
the live site database but as and when the new requirements are being added, it is essential
to ensure that database functions smoothly. Few of the tasks undertaken in this phase are –
 Performance tuning
 Database backup and recovery
 Database designs modifications
 Database audits (access audits, usage audits, security audits, etc.)
 Database access management
 Hardware maintenance
 Usage monitoring
 DBMS Software up gradation
Systems Development Life Cycle

The system-development life cycle enables users to transform a newly-developed project into an
operational one. The System Development Life Cycle, "SDLC" for short, is a multistep, iterative
process, structured in a methodical way. This process is used to model or provide a framework for
technical and non-technical activities to deliver a quality system which meets or exceeds a
business’s expectations or manage decision-making progression.

Similar to a project life cycle (PLC), the SDLC uses a systems approach to describe a process. It
is often used and followed when there is an IT or IS project under development.

The SDLC highlights different stages (phrases or steps) of the development process. The life cycle
approach is used so users can see and understand what activities are involved within a given step.
It is also used to let them know that at any time, steps can be repeated or a previous step can be
reworked when needing to modify or improve the system.
1) Planning:
This is the first phase in the systems development process. It identifies whether or not there
is the need for a new system to achieve a business’s strategic objectives. This is a
preliminary plan (or a feasibility study) for a company’s business initiative to acquire the
resources to build on an infrastructure to modify or improve a service. The company might
be trying to meet or exceed expectations for their employees, customers and stakeholders
too. The purpose of this step is to find out the scope of the problem and determine solutions.
Resources, costs, time, benefits and other items should be considered at this stage.
This phase requires the user to define what the problem is. Following five activities must
exist within planning.
 Define the problem
 Produce the project schedule
 Confirm project feasibility
 Staff the project
 Launch the project

2) Analysis:
Second phase involves gathering requirements for the system. In this phase, business needs
are studied with the intention of making business processes more efficient. In the analysis
phase, a significant amount of time is spent talking with stakeholders and reviewing the
stakeholder’s input.
Once stakeholders have been recognized, the gathering and analysis of the requirements
can begin. Requirement gathering must be related to business needs or opportunities.
Requirement analysis involves capturing requirements and analyzing requirements.
Capturing requirements is communicating with stakeholders to agree on what the
requirements are. Following activities must exist in this phase:
 Gather Information
 Define the new system's requirements
 Build prototypes for the new system
 Prioritize requirements
 Evaluate alternatives
 Meet with management to discuss new options
3) Design:
The third phase is concerned with the physical construction of the system. Included are the
design or configuration of the network (hardware, operating system, programming, etc.),
design of user interfaces (forms, reports, etc.), design of system interfaces (for
communication with other systems), and security issues. The main objective of this phase
is to transform the previously defined requirements into a complete and detailed set of
specifications which will be used during the next phase. Some of the activities that need to
take place during the design phase are:
 Design the application
 Design and integrate the network
 Design and integrate the database
 Create a contingency plan
 Start a Maintenance, Training and Operations plan
 Review the design
 Articulate the business processes and procedures
 Establish a transition strategy
 Deliver the System Design Document
 Review final design

4) Implementation:
The fourth phase is when the majority of the code for the program is written. Additionally,
this phase involves the actual installation of the newly-developed system. This step puts
the project into production by moving the data and components from the old system and
placing them in the new system via a direct cutover. While this can be a risky (and
complicated) move, the cutover typically happens during off-peak hours, thus minimizing
the risk. Both system analysts and end-users should now see the realization of the project
that has implemented changes. Following five activities must be performed during the
implementation phase:
 Construct software components
 Verify and test
 Convert Data
 Training end users and document the system
 Install the system
5) Maintenance/Support:
The final phase involves maintenance and regular required updates. This step is when end
users can fine-tune the system, if they wish, to boost performance, add new capabilities or
meet additional user requirements.
 Include all the activities such as phone support or physical on-site support for users
that is 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.
 It also includes handling the residual errors and resolve any issues that may exist in
the system even after the testing phase.
 Maintenance and support may be needed for a longer time for large systems and for
a short time for smaller systems.