CIS5200 - Database System Analysis and Design Report: PPP Kennel

This report presents a comprehensive analysis and design of a database system for Pampered Pets Palace (PPP), a boarding kennel in Brisbane, Australia. The report addresses the need for automating business processes to improve efficiency and solve booking-related issues. It includes a time management plan, a TO-BE process diagram illustrating the future state of business operations, and a comparison with the AS-IS process. The report also features an entity-relationship diagram (ERD) outlining the database structure, data normalization procedures to reduce redundancy and improve data integrity, and testing strategies to ensure system functionality. Furthermore, it covers employee training methods, system changeover considerations, and a user manual report for top management. The analysis aims to provide a robust and efficient database solution for PPP's operational needs.

DATABASE SYSTEM
Name of the Student
Name of the University
Author Note

Executive summary:
Mrs. Norris and Mr. Parlov established boarding kennel for the dogs and cats in Western suburbs of
Brisbane. This kernels’ operation is weekly. This kernel holds 100 single dog run, 25 dog dog run and
50 cat run. This kernel constructed 10 cats and 20 dogs comfortable kernels. From boarding the
animal, this kernel provides all other services like cleaning, fleas’ treatment and brushing. They do
running of business operations mostly. They need in automating the business process for solving
problem of business process and making the process effective and efficient. New technology should be
adopted by developing booking system of Pampered pet. This system should ensure every payment
process and booking process are implemented in the system and are also automated. The purpose of
this paper is to make a time management plan, an ER diagram for the system and TO BE process
diagram.

Table of Contents
Introduction and organisational background:...........................................................................................3
Time management plan:...........................................................................................................................3
TO-BE process:........................................................................................................................................4
Comparison of TO-BE process and AS-IS process:.................................................................................5
Entity relationship diagram:.....................................................................................................................6
Data normalization:..................................................................................................................................7
Testing:.....................................................................................................................................................8
Training:...................................................................................................................................................9
System changeover:..................................................................................................................................9
Report to top management:.....................................................................................................................10
References:.............................................................................................................................................11

Introduction and organisational background:
Mrs. Norris and Mr. Parlov established boarding kennel for the dogs and cats in Western
suburbs of Brisbane. The operation process of kennel runs for 7 days per week. Capacity of kennel is
as per following: 25 two-dog dog runs, 100 single-dog dog runs and 50 cats runs. The kennel also has
completed thirty luxury units recently and for providing board for the PPP, animals. They do running
of business operations mostly. They need in automating the business process for solving problem of
business process and making the process effective and efficient. New technology should be adopted by
developing booking system of Pampered pet. This system should ensure every payment process and
booking process are implemented in the system and are also automated. It also provides additional
services such as flea treatments, grooming etc (Sutrisna, Ramanayaka and Goulding, 2018). The
purpose of this paper is to create a Work Breakdown Structure for the pampered Pets team. There will
be a ERD diagram too for the PPP for showing all of the entities as well as their attributes, identifying
the key as well as for showing the relationships.
Time management plan:
ID Task
Mode
Task Name Duration Start Finish
0 Pet 45 days Mon 1/27/20 Sat 3/28/20
1 Requirement analysis 8 days Mon 1/27/20 Wed 2/5/20
2 Technical analysis 3 days Mon 1/27/20 Wed 1/29/20
3 Operational analysis 3 days Thu 1/30/20 Mon 2/3/20
4 Risk analysis 2 days Tue 2/4/20 Wed 2/5/20
5 System design 20 days Thu 2/6/20 Wed 3/4/20
6 Layout 3 days Thu 2/6/20 Mon 2/10/20
7 Design of database 3 days Tue 2/11/20 Thu 2/13/20
8 Design of system 7 days Wed 2/19/20 Thu 2/27/20
9 Future design 3 days Fri 2/28/20 Tue 3/3/20
10 Development 9 days Wed 3/4/20 Mon 3/16/20
11 Development of payment gateway 2 days Wed 3/4/20 Thu 3/5/20
12 Development of database 1 day Fri 3/6/20 Fri 3/6/20
13 Category and product listing 3 days Mon 3/9/20 Wed 3/11/20
14 Testing and Implement 11 days Mon 3/16/20 Sat 3/28/20
15 Purchase of domain name and hosting server2 days Mon 3/16/20 Tue 3/17/20
16 Deploy system 3 days Wed 3/18/20 Fri 3/20/20
17 Test system 3 days Mon 3/23/20 Wed 3/25/20
M T W T F S S M T W T
Jan 19, '20 Feb 9, '20 Mar 1, '20 Mar 22, '20

TO-BE process:
At the time of designing new process, the main focus needs to be ensured that the process
provides the organisation exactly what the company hopes to accomplish with it. For achieving the
result, different methodologies need to be used such as brainstorming, studies about the scenarios as
well as real time model. Process of TO-BE defines business process’s future state for this organization.
Analysis goal for putting together state process in future in for clarifying the procedure of business
process in future, after some time in future. The changes are changes of business process and
technology change. TO-BE process includes every section of typical method of business process.
Process of TO-BE is completed as a part of project. TO-BE process impacts the process of business
(Turner, Abrahams and Harris 2017). While designing TO-BE, focus is for ensuring that this offers the
organization exactly as it is expected to deliver. Key for such stage is be totally simple, idealizing
easily explained and understood activities. This is good way for checking descriptions of activities that
are objective and efficient. The activities must be linked orderly, the activities should be defined
without clinging agents of process, defining objectively the process to be done and create parallels
among activities. TO-BE process must be better and different than current process. This is necessary
for making comparison among results that are obtained currently with the required results. The TO-BE
process diagram for the system is as follows:

Comparison of TO-BE process and AS-IS process:
The effective technique that can be used to transform the visions in to results is for developing
as well as for populating as TO-BE and AS-IS process. AS-IS diagram can describe the current state
of culture, process and capabilities of the organisation (Van et al., 2018). On the other side, the TO-BE
process can describe the future states that means how culture, process and capabilities of the
organisation would appear in future. Process of AS-IS is “now” state whereas process of TO-BE is
future state. Both process state of TO-BE and process state of AS-IS should be known for getting in
process management. Process of AS-IS allows to get appropriate view of the working procedure of the
process. This part is crucial to understand how any kind of improvements could be made. After
analysing the process, specific improvements could be proposed (Araújo et. al. 2017). Process of AS-
IS describes the process’s present state, capabilities and culture of the organization. Future state of the
organization is described in process of TO-BE. Main purpose for process of AS-IS needs in working
out where the improvements are required and knowing starting point of change. On the other hand,
process of TO-BE needs the business analysts as creative for solving the problems and for designing
the processes for achieving the outcomes of the business, often based only in the imperfect
information for what should be accomplished by the organization.
Entity relationship diagram:
The entity relationship diagram is describing the structure of the database for the system with
the help of a diagram (Turner, Abrahams and Harris, 2017). The entity relationship model is basically
a blueprint or design of the database which could be implemented as database later. The primary
components of the ER model are, relationship set and entity set. ERD shows the relationships of the
entity sets that are stored within database. Entity in such context is the object, which is component of
the data. Entity set is similar entities’ collection. Such entities could have attributes which define the
properties. By defining entities, the attributes and also showing relationships among them, ERD
illustrates databases’ logical structure (Frantiska 2018). ERD are used for sketching out design of

database. ERD is conceptual high level data model. ERD is dependent on notion of entities of real
world and relationship among them. ERD helps in analysing requirements of data systematically for
producing data that is well designed. Hence, this is considered best practice for completing ERD
before implementing the database. ERD displays relationship of set of entity stored in database. ERD
helps in explaining databases’ logical structures. ERD looks quite similar with flowchart. ERD
consists of several specialised symbols for making the model unique. ERD allows in drawing design
of database. It is easy in using graphical tool to model data and is used widely in design of database. It
is GUI representation of database’s logical structure. It helps in identifying entities that exist within
the system and relationship among those entities. ERD is used for defining the terms which are related
with the entity relationship modelling (da Paixão and Pereira 2018). It provides preview of
connections of all the tables and location of fields within every table. It helps in describing entities,
relationships and attributes. ERD are translatable to the relational tables that allows in building
databases quickly. ERD could be used by the designers of database as blueprint to implement data into
certain software applications. Information’s better understanding is gained by database designers that
is to be stored in database by using ERD. ERD allows in communicating with logical structure of
database for the users. The Entity relationship model for the system is as given below:

Data normalization:
The data normalization is basically a process that is used for structuring a relational database
according to a series of normal forms for reducing the data redundancy as well as for improving data
integrity (Newman et al., 2017). Tables and columns of database are organised by using data
normalization for ensuing that dependencies are enforced properly by the integrity constraints of the
database. This is accomplished through applying formal rules such as by synthesis process or by
decomposition. Decomposition is improving design of existing database. Synthesis process is creating
new design of a new database. Data normalization is technique of design of database that organises the
tables in such manner which reduces redundancy and dependency of data. This divides the larger
tables into smaller tables and connects them by using the relationships. Key is used in the tables of the
database which is value used for identifying record within table uniquely. A key might be single
column or could be combination of several columns (Zhang, Sugano and Bulling 2018). Designing

database is crucial for database management system’s successful implementation which meets
requirements of data of the system of the organization. Data normalization helps in producing the
systems of database which are cost-efficient and have much better models of security. The functional
dependencies within the database system are very crucial component of normalise process of data.
Data normalization is performed on maximum database systems up to third normal form (Heyne, Papo
and Shifman 2020). Primary key of a table within the database are uniquely identified and could not
null value. Foreign key within the database is used for connecting the tables and references primary
key always.
Testing:
To test the system, there are some steps that are needed to be followed. The steps are given
below:
 Test environment setup: The environment of the system should be tested for making sure every
component of the system is working properly.
 Creating test case: The test case needs to be created for testing the system. Test case for testing
every component should be created to make sure the system is performing properly.
 Create test data: Test data should be created for performing the test of the system. These test
data would be used for testing the test cases of the system (Rogstad and Briand 2016).
 Executing the test case: Test case should be executed for making sure that the system is
working properly. The test data created for the test case should be executed to check every
component of the system.
 Defect reporting: The defects detected while testing the system should be identified and
described within the defect report. Defect report’s purpose is stating the issue clearly so that
the developers could replicate easily the defect and could fix it.

 Regression testing: The testing should be done for making sure that recent code or program has
not affected adversely the existing features (Shen et. al. 2016).
 Log defects: Defect logging should be done to find the defects within the system under product
or test by recording feedback of customers or by testing and thus making the system’s new
system which fix defects.
 Retesting: Retesting should be done for running the previously test cases that failed again on
new system for verifying defects that are posted earlier.
For this system, performance testing needs to be performed. The performance testing is basically a
software testing which is carried out for testing the scalability, speed, reliability and stability of the
software application and product.
Training:
The best ways for training employees are as follows:
 Blending in-person training as well as in online training: Training should be provided to the
employees in person or by online.
 Explain and demonstrate the operations: The operations should be explained and demonstrated
properly.
 Prepare the trainer: The trainer should be prepared properly.
 Prepare the trainee: The trainee should be prepared properly.
 Follow up and take feedback from them: Feedback should be taken from the employees.
For this system the staffs and the manager need proper training to manage the system.
System changeover:
For managing the system more efficiently, the staffs need to handle the system gently. The
system need to be updated with the latest components. The Operating system need to be also kept up

to date. As the future is developing with new technologies the system also need to be upgraded with
that.
Report to top management:
For top management a user manual for the employees need to be developed. They need to
handle the system properly. The developer needs to check and update the system on a daily basis.

References:
Araújo, C.S., De Toledo, L.B., Mendes, L.A.G. and Cunha, S.G.T., 2017. Modeling the “AS-IS”
product development process: lessons learned from a practical experience in the aerospace industry.
Product: Management & Development, 1(1), pp.69-78.
da Paixão, R.S.S. and Pereira, C.P., 2018. Web Application for Model, Share and Conversion of
Entity-relationship Diagrams for Person Visually Impaired. In CSEDU (1) (pp. 405-411).
Frantiska, J., 2018. Entity-relationship diagrams. In Visualization Tools for Learning Environment
Development (pp. 21-30). Springer, Cham.
Heyne, M., Papo, N. and Shifman, J.M., 2020. Generating quantitative binding landscapes through
fractional binding selections combined with deep sequencing and data normalization. Nature
Communications, 11(1), pp.1-7.
Imam, A.A., Basri, S., Ahmad, R. and González-Aparicio, M.T., 2019, April. Literature Review on
Database Design Testing Techniques. In Computer Science On-line Conference (pp. 1-13). Springer,
Cham.
Newman, A.M., Gentles, A.J., Liu, C.L., Diehn, M. and Alizadeh, A.A., 2017. Data normalization
considerations for digital tumor dissection. Genome biology, 18(1), p.128.
Pořízka, P., Klus, J., Hrdlička, A., Vrábel, J., Škarková, P., Prochazka, D., Novotný, J., Novotný, K.
and Kaiser, J., 2017. Impact of laser-induced breakdown spectroscopy data normalization on
multivariate classification accuracy. Journal of Analytical Atomic Spectrometry, 32(2), pp.277-288.
Rogstad, E. and Briand, L., 2016. Cost-effective strategies for the regression testing of database
applications: Case study and lessons learned. Journal of Systems and Software, 113, pp.257-274.