Thesis Proposal Final

Systems Technology Institute – Fairview
Integrated Database Management Application
A Thesis Proposal Presented to

Systems Technology Institute
STI-Fairview
In Partial Fulfillment
of the Requirements for the Degree of
Bachelor of Science in Computer Science
by:
Estrada, Wendell Wayne H.

Yubal, Marlon S.
Robert Kenry Palao

Thesis Adviser
September 2009
TECHNICAL ADVISER’S
RECOMMENDATION SHEET
This Thesis Proposal entitled
And submitted in partial fulfillment of the requirements of the

Bachelor of Science in Computer Science degree has been examined
and is recommended for acceptance and approval
_____________________
Robert Kenry Palao
Thesis Adviser
September 2009
Date
ENGLISH ADVISER’S
RECOMMENDATION SHEET
And submitted in partial fulfillment of the requirements of the

Bachelor of Science in Computer Science degree has been examined
and is recommended for acceptance and approval
_____________________
Jane Miraflor
English Adviser
_____________________
Fernando T. Dantes III
Dean
September 2009
Date
THESIS COORDINATOR AND DEAN’S

ACCEPTANCE SHEET
After having been recommended and approved is hereby accepted

by the Information Technology Department
of Systems Technology Institute – STI Fairview
_____________________
Robert Kenry Palao
Thesis Coordinator
_____________________
Fernando T. Dantes III
Dean
September 2009
Date
PANEL’S APPROVAL SHEET
developed by:
Estrada, Wendell Wayne H.

Yubal, Marlon S.
after having been presented is hereby approved

by the following members of the panel
_____________________ _____________________
Panelist Panelist
September 2009 September 2009
_____________________
Lead Panelist
September 2009
Table of Contents
1 INTRODUCTION...............................................................................................................1-5
1.1 Background of the Problem.........................................................................................1-5
1.2 Overview of the Current State of the Technology........................................................1-5
1.3 Project Rationale.........................................................................................................1-5
2 PROJECT DESCRIPTION.................................................................................................2-5
2.1 Problem Statement.......................................................................................................2-5
2.2 Proposed Research Project...........................................................................................2-5
2.2.1 General Objectives...............................................................................................2-5
2.2.2 Specific Objectives..............................................................................................2-5
2.2.3 Scope and Limitations.........................................................................................2-5
2.2.4 Methodology........................................................................................................2-5
3 PROJECT MANAGEMENT...............................................................................................3-5
3.1 Calendar of Activities..................................................................................................3-5
3.1.1 Description of Activities......................................................................................3-5
3.1.2 Gantt Chart of Activities......................................................................................3-5
3.2 Resources.....................................................................................................................3-5
3.2.1 Hardware.............................................................................................................3-5
3.2.2 Software...............................................................................................................3-5
4 APPENDICES.....................................................................................................................4-5
4.1 Appendix A. References.............................................................................................A-5
4.2 Appendix B. Resource Person/s..................................................................................B-5
4.3 Appendix C. Personal Technical Vitae........................................................................C-5
4.4 Appendix D. Object-Oriented Life Cycle...................................................................D-5
4.5 Appendix E. Gantt Chart of Activities.........................................................................E-5

1 INTRODUCTION
1.1 Background of the Problem
Data storage is an essential part of most software applications. A large
number of applications have the need to persist, or store, and retrieve data
efficiently. These applications need to search through data that have been stored
to retrieve specific information. This need to search for and retrieved data
means that an application must use a database.
The database is now the underlying framework of the information system,
and it has fundamentally changed the way many organizations operate.
Particularly, the developments of this technology over the last few years have
produced systems and applications becoming increasingly available to a wider
variety of users.
Different database technologies have been used to create a wide variety of
systems and applications. These technologies are becoming more powerful, but
are also becoming more complex. In this circumstance, the need for
applications that can manage databases is of great significance.
A database is a very complex piece of software. Writing programs to
communicate with a database through its native interface can be very
complicated and can result in limited and inflexible applications. However,
database client technologies simplify this process.
Database client technologies provide a uniform interface for
communicating with different database systems. With modern database client
interfaces, it is possible to write a single program that performs complex

7
operations using different types of databases. Some of the popular database
interfaces are: ODBC (Open Database Connectivity), DAO (Data Access
Objects), OLEDB (Object-Linking and Embedding Database), and ADO
(ActiveX Data Objects).
Database management systems (DBMS) are currently becoming more
popular and many sophisticated tools and applications have been developed
and improved just to provide the needs of many software developers, database
administrators, programmers and other technical staff. These software
applications provide sophisticated functions that allow users to manage their
databases.
Traditionally, companies used a single database management system
(DBMS). All database access was done either through the front end of that
system or through applications written to work exclusively with that system.
However, as the use computers grew and more computer hardware and
software became available, companies started to acquire different DBMS.
Acquiring different DBMS also requires different database management
tools or applications in accessing and managing data for each of these DBMS.
However, the majority of these applications, particularly the commercial
applications, are merely used for accessing and managing data from a single
DBMS. It would be a breakthrough when particular database management
tool/application has the ability to access and manage data from various DBMS.

8
1.2 Overview of the Current State of the Technology
In traditional database management, the creation and maintenance of
databases were very crucial that database administrators and programmers must
utilize useful and reliable database tools and applications. Early database
management tools were developed but were not much appealing to the users.
Traditionally, database tools were text-based and they do not provide a flexible
graphical user interface. Because tools were not very flexible enough to work
with, software developers continue to develop applications further until they came
up with the idea of making applications more reliable, flexible and easy to use.
Recently, many applications have been developed including database
applications. Most modern database management applications support SQL – the
standard for programming complex queries. Because SQL is available for many
different database management systems, programmers and sophisticated users
don’t need to learn new languages when they work with different hardware and
software systems. Users are usually insulated from the complexities of the query
language by graphical user interfaces that allow point-and-click queries. Because
of the power of the graphical user interfaces, users can now manipulate databases
easily, and some operations can be done in just a single click of a mouse button.
Some sophisticated database applications have the ability to handle complex
database operations such as information tracking, data access and storage, and
database security. However, most database management tools are developed just
for a single DBMS. For instance, the WebYog’s SQLYog Enterprise is intended to

9
work with MySQL Server and it cannot be used with other DBMS such as
Microsoft SQL Server and PostgreSQL.
1.3 Project Rationale
It would be beneficial if a database management tool/application can
support a variety of database management systems and provide cross-database
functionalities. Having this kind of application is advantageous because it can
eliminate the need for using multiple existing database tools/applications in
order to manipulate different types of databases. This study will be helpful to
the people who use single database management tools/applications but wanted
create connections to different DBMS. Specifically, the study will be beneficial
to database administrators, system administrators, programmers, and other
technical staff. The study will also be beneficial to the people who likewise
wanted to study on the same area of research.

10
2 PROJECT DESCRIPTION
2.1 Problem Statement
The study is an attempt to provide solutions on how to develop an
integrated database management application.
Specifically, the study sought answers for the following problems:
 How to develop a component that manages different connections
and monitors the database catalog?
Managing database connections is one of the pitfalls in
database management. The application should provide a
component that monitors and manages database connections to
avoid cluttering that takes place on the database catalog.
It is important that the application knows what objects are
available in the back-end database. The catalog provides a
convenient way for the user to quickly and efficiently glance at
the elements contained within the database. The database catalog
should display such information as: tables, views, fields, triggers,
stored procedures, and indexes. This component makes the
database catalog browsing handy for the user to work with. It is
the component’s task to categorize all the objects, along with its
contained objects, in the database catalog.

11
 How to develop an application that has the capability of
providing operations for maintaining and managing data from
different DBMS?
The main purpose of the study is to develop a database
application that can provide connections to various types of
DBMS. The ability of the application to manage and maintain
databases should not be limited to a single DBMS.
 How to develop an application that provides an efficient way of
performing common database operations?
One of the most important and the most common
operations in database management is the definition and
manipulation of databases. Therefore, these operations should be
present in the application and it includes the following:
 Creating and dropping databases
 Creating, dropping, altering, and truncating tables
 Creating and executing query statements
 Adding, deleting, and updating records from a table
 How to develop a module that should be able to retrieve and
view table data and schema definitions?
The application should allow the user to display the data
contained in a particular database table and it should also allow
the user to view a particular database schema. The schema shows
how a particular database is structured.

12
 How to develop a module that allows the user to export table
data, database schemata, and query results to different file
formats?
The user may want to save or export table data, database
schemata, and query results to different file formats such as
HTML, XML, or CSV. The application should handle this kind
of situation.
 How to develop a module that allows the user to search table
data from a particular database?
The application should provide a search engine that
would help the user find instances of a string in a database.
 How to develop a backup and restore utilities?
The application should provide backup and restore
services that offers the flexibility of backing up and restoring
on type of database.
2.2 Proposed Research Project
General Objectives
The main objective of the study is:
 To develop an integrated database management application that
can access data from various database management systems
(DBMS) and provides a graphical user interface in managing

13
various databases which makes the application more intuitive
to use.
Specific Objectives
 To develop a component that manages different connections
and monitors the database catalog.
 To develop an application that has the capability of providing
operations for maintaining and managing data from different
DBMS.
 To develop an application that provides an efficient way of
performing common database operations.

 To develop a module that should be able to retrieve and view
table data and schema definitions.

 To develop a module that allows the user to export table data,
database schemata, and query results to different file formats.

 To develop a module that allows the user to search table data
from a particular database.

 To develop a backup and restore utilities.
Scope and Limitations
The study is focuses on the development of an integrated
database management application that allows database
users/programmers to access data from various database management
systems (DBMS). The proposed application will have the capability of
performing database management operations such as creating, dropping,

14
and altering databases and tables. The application will be able to display
table data and it will allow the user to export this data into different file
formats such as XML, HTML, and CSV. The application will also
provide operations which allow the user to create and manipulate stored
procedures, triggers, functions, and views. It will also have the capacity
to perform query statements.
The proposed application will not be able to provide functions
for performing database administrative tasks due to the developers’
expectations that the development of the software application may
become very large in expanse, as a matter of fact, almost all database
connections will be done in a database vendor-specific manner.
The backup and restore utilities is limited to backing up only
certain objects in the database, such as tables, views, stored procedures,
and triggers. Other database-specific objects, such as user logins, user
defined data types, and sequences are not eligible for backup and restore.
In addition, the proposed application might not be able to
support all types of DBMS due to limited resources available and the
software programming/development experience and skills the developers
have.
Methodology
Building large and complex software applications are
notoriously difficult. The developers need methodologies backed by

15
languages that would feature characteristics addressing the particular
needs of such applications.
To increase the productivity and quality, the software
developers had to adopt methods of building the application out of
reusable components, and at the same time to raise the level of
abstraction of the designed artifacts. Utilizing reusable components will
reduce the development time, automate repetitive design and
implementation; and raising the level of abstraction leaves the developers
with less semantic richness and fewer venues for extensibility.
Because of the dilemmas involving project planning, project
management, and activity workflow pervade the world of software
development. Object-Oriented Methodology (OOM) provides an elegant
language for framing such problems, and powerful tools for resolving
them. [HKSA2005]
The following benefits can be achieved by adopting OOM:
 Improved productivity
Application development is facilitated by the reuse
of existing components which can greatly improve the
productivity and facilitate rapid delivery.
 Deliver high quality system
The quality of the system can be improved as the
system is build up in a component manner with the use of

16
existing components which are well-tested and well-
proven.
 Lower maintenance cost
The associated property of traceability of OOM can
help to ensure the impact of change is localized and the
problem area can be easily traced. As a result, the
maintenance cost can be reduced.
 Manage complexity
The use of OOM eases the process in managing
complexity. By the breaking down of a complex solution
into different components and with each component
encapsulated (e.g. treated as a black box) from others,
complex development can be better managed.
Object-Oriented Life Cycle
 Object-Oriented Analysis
 Object-Oriented Design
 Object-Oriented Implementation
 Object-Oriented Testing

17
3 PROJECT MANAGEMENT
3.1 Calendar of Activities
Description of Activities
3.1.1 Initial Planning and Establishing Project Requirements
Before the actual project can begin, the project manager
must establish the project requirements with the project
stakeholders. The stakeholders must specify their requirements
for the project, constraints on the project, time and cost
objectives for the project, so that the project manager will be able
to gather the requirements to start building the project plan and
create the deliverables. Once the project is defined, the project
manager can then state the start and end date of the project. The
project manager must monitor the progress throughout the entire
development of the project.
3.1.2 Object-Oriented Analysis
In this phase, the project requirements should be identified
including both functional and non-functional requirements based
on the problem statement. Once the requirements have been
identified, the analyst will have to prepare a model of the desired

18
application. The model is based on what the application is
required to do. At this stage, the implementation details are not
taken care of. Only the model of the application is prepared
based on the idea that the application is made up of a set of
interacting objects.
3.1.3 Object-Oriented Design
In this phase, the overall architecture of the application is
decided. The application is organized as a set of subsystems
interacting with each other. The application architecture will be
designed using the n-tier architecture or multi-tier architecture
wherein the application is divided into separate layers. The
separation of the functionality of the application helps to
decrease or manage complexity especially when the application
is large or complex. Once the architectural design of the
application is defined, then the objects can be identified and
modeled and the interrelationships between these objects can be
defined.
3.1.4 Object-Oriented Implementation
During this phase, the objects and their interrelationships
are translated and actually coded using the programming
language that the developers have decided to use.

19
3.1.5 Object-Oriented Testing
The application testing will be performed using different
types of testing tools and testing methods in order for the
developers to make sure that the project requirements are met.
Gantt Chart of Activities
The Gantt chart shows the detailed activities that the developers
will undergo from the start up to the end of the project. (See Appendix E)
3.2 Resources
Hardware
- Pentium 4 CPU 1.80 GHz

- 1 Gb RAM
- Mouse
- Keyboard
- Printer
Software
- Microsoft Office (Word, PowerPoint, Project, Access, Excel, Visio)

- Microsoft Windows XP Service Pack 2
- Microsoft .NET Framework 3.5 (for .NET 2.0 & 3.5 versions)
- Microsoft Visual Studio Team System 2008
- Sparx Systems Enterprise Architect Corporate Edition 7.0
- MySQL Server 5.0
- PostgreSQL 8.2
- Microsoft SQL Server 2000/2005
4 APPENDICES
4.1 Appendix A. References
Books:

20
[MAHA2009] Mahajan, R. (2009). UML in 7 Days.
[PODE2005] Podeswa, H. (2005). Business Analyst: A Practical
Guide to Object-Oriented Requirements Gathering.
Canada: Thomson Course Technology PTR.
[HKSA2005] Government of the Hong Kong Special
Administrative Region, the (2005). An Introduction
to Object Oriented Methodology (OOM).
[SAMS1999] Robinson, L. (1999). Sams Teach Yourself Database
Programming with Visual C++6 in 21 Days.
Indianapolis, USA: Macmillan Computer
Publishing.
[LHOT2006b] Lhotka, R. (2006). Expert C# 2005 Business
Objects, Second Edition. Berkeley, CA, USA:
Apress.
[PHIL2004b] Philips, J. (2004). IT Project Management: On
Track From Start to Finish, Second Edition.
California, USA: McGraw-Hill/Osborne

21
[CHAR2003] Charvat, J. (2003). Project Management
Methodologies: Selecting, Implementing, and
Supporting Methodologies and Processes for
Projects. John Wiley and Sons.
World Wide Web:
[CHAR2003] Lakewhitney, Jason . (2006). ‘The Code Project’.
http://www.codeproject.com/KB/HelpDBLib.htm

22
4.2 Appendix B. Resource Person/s
Mr. Rubinato Lubian III
Faculty
Information Technology Department
Mr. Jayson Nardo
Faculty
Information Technology Department

B-23
4.3 Appendix C. Personal Technical Vitae
Name: Wendell Wayne H. Estrada
Address: Francisco HMS II, City of San Jose Del Monte, Bulacan
E-mail: whizkid_wwe12@yahoo.com
Contact No.: 09164900068
Name: Marlon S. Yubal
Address: 43 Jonah St., Freedom Park 6, Batasan Hills, Quezon City
E-mail: marlon_yubal @yahoo.com
Contact No.: 09186643994

C-24
4.4 Appendix D. Object-Oriented Life Cycle
Initial Planning
Requirements Gathering
Iterative Development Incremental Development
Problem Analysis
Adap
t
t
User Interface Application Reusable
en
Design Design Component
m
s
e
ag Harvest
an Implementation
M
ect
oj
Testing
Pr
The diagram above provides a pictorial overview of the development phases and their
relationships with each other and with key repositories. It is intended to show that:
 Requirements Gathering and Testing are pre and post-iterative phases.

 Analysis, Design and Implementation occur in an Iterative and
Incremental process.
 Analysis needs to be performed before Design.
 User Interface and Application Design can be done concurrently.
 Design precedes Implement.
 Project Management is an on-going activity.

D-25
4.5 Appendix E. Gantt Chart of Activities

E-26

Thesis Proposal Final

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Thesis Proposal Final

Загружено:

Авторское право:

Доступные форматы

Systems Technology Institute – Fairview

Integrated Database Management Application

A Thesis Proposal Presented to

Estrada, Wendell Wayne H.

Robert Kenry Palao

This Thesis Proposal entitled

Integrated Database Management Application

And submitted in partial fulfillment of the requirements of the

This Thesis Proposal entitled

Integrated Database Management Application

And submitted in partial fulfillment of the requirements of the

THESIS COORDINATOR AND DEAN’S

This Thesis Proposal entitled

Integrated Database Management Application

After having been recommended and approved is hereby accepted

PANEL’S APPROVAL SHEET

This Thesis Proposal entitled

Integrated Database Management Application

Estrada, Wendell Wayne H.

after having been presented is hereby approved

1.1 Background of the Problem.........................................................................................1-5

1.2 Overview of the Current State of the Technology........................................................1-5

1.3 Project Rationale.........................................................................................................1-5

2.1 Problem Statement.......................................................................................................2-5

2.2 Proposed Research Project...........................................................................................2-5

2.2.1 General Objectives...............................................................................................2-5

2.2.2 Specific Objectives..............................................................................................2-5

2.2.3 Scope and Limitations.........................................................................................2-5

3.1 Calendar of Activities..................................................................................................3-5

3.1.1 Description of Activities......................................................................................3-5

3.1.2 Gantt Chart of Activities......................................................................................3-5

4.1 Appendix A. References.............................................................................................A-5

4.2 Appendix B. Resource Person/s..................................................................................B-5

4.3 Appendix C. Personal Technical Vitae........................................................................C-5

4.4 Appendix D. Object-Oriented Life Cycle...................................................................D-5

4.5 Appendix E. Gantt Chart of Activities.........................................................................E-5

1.1 Background of the Problem

Data storage is an essential part of most software applications. A large

means that an application must use a database.

The database is now the underlying framework of the information system,

and it has fundamentally changed the way many organizations operate.

produced systems and applications becoming increasingly available to a wider

Different database technologies have been used to create a wide variety of

applications that can manage databases is of great significance.

A database is a very complex piece of software. Writing programs to

communicate with a database through its native interface can be very

complicated and can result in limited and inflexible applications. However,

database client technologies simplify this process.

Database client technologies provide a uniform interface for

communicating with different database systems. With modern database client

interfaces, it is possible to write a single program that performs complex

Integrated Database Management Application

interfaces are: ODBC (Open Database Connectivity), DAO (Data Access

Objects), OLEDB (Object-Linking and Embedding Database), and ADO

(ActiveX Data Objects).

Database management systems (DBMS) are currently becoming more

administrators, programmers and other technical staff. These software

applications provide sophisticated functions that allow users to manage their

Traditionally, companies used a single database management system

system or through applications written to work exclusively with that system.

software became available, companies started to acquire different DBMS.

Acquiring different DBMS also requires different database management

However, the majority of these applications, particularly the commercial