Overseas Chinese College

Undergraduate Thesis

Database Design, Implementation, and Management Gymnasium Database System

Students Name Zhu Wei Students ID 2005141389 College Overseas Chinese College Major Information and Management Instructor Joanne Zhang

March 30, 2009

ABSTRACT Database Design, Implementation, and Management Gymnasium Database System

Zhu Wei

As the world entering into a digital era, most of organizations use different kinds of database environment to achieve efficient management. A suitable database management system provides a set of tools for an organization to efficiently track and manage its data. The development of a database follows a database application lifecycle. It is a rather long process and requires a considerable amount of time, energy, and resources as well. A database administrator is obliged to strive for the perfection of the database to address the increasing amount of information to be dealt with. Apart from that, since new technology keeps emerging, suitable software application should be integrated into the database environment to support more advanced features and services. Following a well-structured database lifecycle will contribute to a reliable and satisfactory performance of the database system. Database system and its management is a quite broad principle. This dissertation focuses on the process of a database application lifecycle. The whole process would be applied to establish a gymnasium management database system. The first two parts introduce the basic concepts concerning database environment. The next four parts present the most important stages in a database lifecycle its requirement identification, design, implementation, and management by showing what shall be done, the process of doing so, as well as the techniques which could be taken advantage to attain the best results. The last part introduces a backup-and-restore strategy for this database system.

Key Words

database management system; database application lifecycle; database design; database backup-and-restore; gymnasium database system; Microsoft SQL Server 2005


21

Microsoft SQL Server 2005

II

Contents

ABSTRACT.................................................................................................................................I 1. Introduction...........................................................................................................................1 2. Database Management System...........................................................................................2 2.1 Database and Database Management System...............................................................................2 References................................................................................................................................4 Acknowledgement....................................................................................................................6 Appendix...................................................................................................................................7 Appendix A. Data Dictionary..............................................................................................................7

III

List of Figures

Figure 1. Database application lifecycle ... 8 Figure 2. Data collection for gymnasium management database system .... 12 Figure 3. Data flow diagram for gymnasiums membership management ...13 Figure 4. Example of ER diagram ....17 Figure 5. Microsoft SQL Server Management Studio ......24 Figure 6. Report generated using Report Services in SQL Server 2005 ...24 Figure 7. Example of creating database ....25 Figure 8. Example of creating table ..25 Figure 9. Example of creating trigger ...25 Figure 10. Example of creating procedure ........25 Figure 11. The process of Test First Development ...27 Figure 12. Full&Log backup strategy ..... 31

IV

List of Tables

Table 1. Example of entity types .15 Table 2. Example of relationship types ...15 Table 3. Example of attribute list 16 Table 4. Example of transaction list 18 Table 5. Example of physical data model 22

1. Introduction
For any organization the collection and storage of data have always been a primary concern. Large organizations nowadays use a database system to address this task. However, the earliest solution is a file-based system, and it is still in use in many small firms today. File-based system is a set of application programs that provides services for users to keep and process data. Each program is independent and can define and manage its own data. When users need to look up some information, they go to the filing system and search from the first entry until the desired result is found. Although the file-based system can be an effective approach sometime, it does suffer from two detrimental problems:

Isolation of data. When stored in a file-based system, data is kept within separate files in an isolated manner. It would be a rather difficult task when users want to access relevant information from two different files.

Duplication of data. Because a file-based system uses a decentralized approach to keep data, it will inevitably introduce the duplication of data into the system. The ensued data redundancy is a waste of resources, taking up additional storage space and increasing unnecessary costs. More importantly, it can give rise to the loss of data integrity. Unless the associated data stored in different files can be altered together when a change in one file occurs, these data will be eventually inconsistent and errors will occur.

Due to the problems of a file-based approach, a new technique emerged; that is database and Database Management System.

2. Database Management System

2.1 Database and Database Management System A database (DB) is a structured collection of logically related data that is stored in a computer system. The organization of data follows a particular database model so that computer programs can select desired data quickly. A database model is not only an approach of structuring data; it also defines a set of operations that can be performed on raw data to achieve data manipulation. Relational model is a most commonly used database model today. It was introduced in the 1970s as a way to make database management systems more independent of any particular application[1]. A relational database has three key terms: relations, attributes, and domains. A relation is a table with columns and rows. A named column of a relation is an attribute of the relation, and the domain of an attribute is the set of values this attribute is allowed to take. Along with a database, a user needs a database management system to access information from the database. A Database Management System (DBMS) is a set of software programs that controls the organization, storage, management, and retrieval of data in a database. The DBMS accepts requests for data from the application program and instructs the operating system to transfer the appropriate data. As a most important advantage of DBMS environment, whenever requirements of the system alter, it can be changed much easily. New categories of data can be added into the database without interference or disruption to the existing system.

References

1. Best Practices for Backup and Recovery in SQL Server 2005 (n.d.). Retrieved February 20, 2009 from http://www.dell.com/downloads/global/solutions/public/white_papers/sql2005_backup_ wp.pdf, p.1 2. Best Practices for Backup and Recovery in SQL Server 2005 (n.d.). Retrieved February 20, 2009 from http://www.dell.com/downloads/global/solutions/public/white_papers/sql2005_backup_ wp.pdf, p.3 3. Best Practices for Backup and Recovery in SQL Server 2005 (n.d.). Retrieved February 20, 2009 from http://www.dell.com/downloads/global/solutions/public/white_papers/sql2005_backup_ wp.pdf, p.4 4. Best Practices for Backup and Recovery in SQL Server 2005 (n.d.). Retrieved February 20, 2009 from http://www.dell.com/downloads/global/solutions/public/white_papers/sql2005_backup_ wp.pdf, p.4 5. Codd, E.F. The Relational Model for Database Management: Version 2. AddisonWesley (1990), p. 271 6. Database Assessment and Planning (n.d). Retrieved February 23, 2009 from http://www.progressivetech.org/Resources/PDF/Database%20assessment%20and %20planning.pdf 7. Database Design (n.d.). Retrieved March 19, 2009 from http://www.dcs.vein.hu/CIR/cikkek/conceptual_ design.pdf 8. Database Planning (n.d.). Retrieved February 15, 2009, from galleryimage.com: http://www.galleryimage.com.au/database-planning.htm 9. Database Planning Workbook (n.d.). Retrieved February 15, 2009, from techsoup.com: http://www.techsoup.org/binaries/files/DatabasePlanningWorkbook.pdf 10. Database Testing: How to Regression Test a Relational Database (n.d.), retrieved February 17,2009, from http://www.agiledata.org/essays/databaseTesting.html 11. David Avison & Hanifa Shah, 1997, Information Systems Series - The Information Systems Development Life Cycle: A First Course in Information Systems, London; McGraw-Hill 12. Davor Gornik, Entity Relationship Modeling with UML (November 3, 2006). Retrieved March 15, 2009 from ibm.com:
4

http://www.ibm.com/developerworks/rational/library/content/03July/2500/2785/2785_u ml.pdf 13. Gilmore, An Introduction to Database Normalization (November 27, 2000). Retrieved February 15, 2009, from http://www.devshed.com/c/a/MySQL/An-Introduction-toDatabase-Normalization 14. John Archibald, Our Approach to Database Design and Development -- A road map to better information management. Retrieved February 23, 2009 from Sigmer.com:http://www.sigmer.com/products_services/database_solutions_lifecyle.php 15. Microsoft SQL Server, Retrieved February 13, 2009, from Wikipedia: http://en.wikipedia.org/wiki/SQL_Server_2005 16. Primary Key (n.d.). Retrieved March 15 from TechTarget: http://searchsqlserver.techtarget.com/sDefinition/0,,sid87_gci902812,00.html 17. Relational Model (n.d.). Retrieved February 13, 2009, from Wikipedia: http://en.wikipedia.org/wiki/Relational_model 18. Thomas Connolly & Carolyn Begg, Database Systems A Practical Approach to Design, Implementation, and Management (Third Edition), Beijing: Publishing House of Electronics Industry, p.253 19. Thomas Connolly & Carolyn Begg, Database Systems A Practical Approach to Design, Implementation, and Management (Third Edition), Beijing: Publishing House of Electronics Industry, p.333 20. Thomas Connolly & Carolyn Begg, Database Systems A Practical Approach to Design, Implementation, and Management (Third Edition), Beijing: Publishing House of Electronics Industry, p.342 21. Thomas Connolly & Carolyn Begg, Database Systems A Practical Approach to Design, Implementation, and Management (Third Edition), Beijing: Publishing House of Electronics Industry, p.353 22. Thomas Connolly & Carolyn Begg, Database Systems A Practical Approach to Design, Implementation, and Management (Third Edition), Beijing: Publishing House of Electronics Industry, p.370 23. Unified Modeling Language (n.d.). Retrieved February 13, 2009, from Wikipedia: http://en.wikipedia.org/wiki/Unified_Modeling_Language

Acknowledgement
Upon completing the writing of my undergraduate dissertation, I would like to give my sincere gratefulness to many people. First of all, I would like to thank my instructor, Ms. Joanne Zhang for giving me guidance and instructions when I was writing this thesis. Secondly, I would like to thank all authors of the articles from which I got inspirations or direct help. Besides, I would like to thank all staff working in KangBei Gymnasium for kindly providing me with not only detailed information but also encouragement needed for my dissertation. Finally, I would like to thank my friends in college and workmates in North China Power Equipment and Material Central Corp where I worked as intern for offering me possible solutions and support when I met problems.

Zhu Wei

Appendix

Appendix A. Data Dictionary 1. Entity Types

Entity Staff Description All staff Occurrence - Each staff belongs to a department. - Some staff manage departments. - Each staff has salary. - Some staff are trainers. - Some staff are instructors. - Some staff receive members. - Some staff contact supplier. - A department is managed by a staff. - Department has staff working for. - A trainer is a staff. - A trainer trains at least one member. - An instructor is a staff. - Instructor teaches at least one class. - Each salary belongs to one staff - A member is received by a staff. - A member has at least one card. - A member issues registration for a class. - A member has at least one physical test. - A member have a trainer. - A member can purchase commodity. - One card is held by one member. - A physical test is for one member. - Supplier provides equipments. - Supplier provides commodity. - Supplier is contacted by staff. - Equipment is supplied by suppliers. - Commodity can be purchased. - Commodity is supplied by supplier. - Class can registered by members. - Class takes room. - Class is taught by one instructor. - Each room is for at least one class. - A member can have a purchase. - Each purchase is for one commodity. - Registration is issued by a member. - Each registration is for one class.

Department Trainer Instructor Salary Member

All department Trainer Instructor Salary information Person who registers membership

Card PhysicalTest Supplier

The card a member had/has. Tests for members physical condition. Suppliers for the facilities The equipments The commodity for purchase All class

Equipment Commodity Class

Room Purchase Registration

The room for class The commodity a member purchased. The registration of a member for a class.

2. Relationship Types
Entity name Staff Staff Staff Trainer Instructor Staff Member Member Trainer Class Instructor Supplier Supplier Staff Member Registration Member Purchase Multiplicity 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 1..1 Entity Manages Belongs to Has Is a Is a Receives Has Has Trains Takes Teaches Provides Provides Contacts Makes Registers Issues Contains Multiplicity 0..1 1..1 1..* 1..1 1..1 0..* 1..* 1..* 1..* 1..1 1..* 1..* 1..* 0..* 0..* 1..1 0..* 1.1 Entity Name Department Department Salary Staff Staff Member Card PhysicalTest Member Room Class Equipment Commodity Supplier Registration Class Purchase Commodity