Running head: DATABASE INITIAL STUDY 1

Database initial study phase

Tanvi Parmar

Wilmington University

IST7000, Data Management

July 12, 2022

Database Initial Study Phase

DATABASE INITIAL STUDY 2

Definition of a database

A database is part of an information system that oversees the retrieval, storage, and collection of

data. Which is also used for data analysis. Software, Hardware, and Databases make up

information systems. Database design is the most important aspect of an information system. A

good database design should always provide fast access to data and a non-duplication database to

avoid anomalies and information gaps. The database should also serve and meet the requirements

of the information system. Before designing any database designers should have a clear

understanding of the system's requirements.

The problem the database is going to solve

The database I am going to create is a college management system database that will contain all

the information about the local high school. The information will include details about the

school, its teachers, students, and staff, as well as its history. The database will store teacher

information such as subject, salary, and role of teachers. Children were informed that the

database would store information such as form, date of birth, form, examination performance,

tuition fee, and balance. Once the database is created, the school will no longer have to rely on a

manual filing system that stores student, faculty, and staff information on paper. The database

will be available online and can be accessed from anywhere as long as the person who wishes to

access the database has an internet connection (Klochkov et al., 2016).

DATABASE INITIAL STUDY 3

Constraints associated with the database project

Constraints are fundamental features of any database, especially the relational database model. A

well-defined theory of constraints is supported by a relational database. Constraints will be

important because they will help me design specific database semantics. Constraints will then be

used to determine whether a given entity meets certain semantics (Gao et al., 2018).

The following restrictions will apply to my database project. The first will be entity integrity,

which will require each entity to have a primary key and no primary key to be null. I won't be

able to identify some rows if we allow null values in the primary. Another constraint is

referential integrity, which requires that every foreign key has a corresponding primary key.

Another constraint I will impose on the database is enterprise constraints, which are rules

designed and specified by users and can be applied to multiple farms (Klochkov et al., 2016).

Objectives of the database design

The primary goal of database treatment is to ensure that company data is not tampered with.

Another consideration is to ensure that all data can be retrieved from it.

Scope of your database design project

The goal of the database design is to collect all the work needed to complete the project. This

creates a clear picture of how to approach and execute project development work. The scope of

the project is updated during the project. Using quantifiable words in the scope of the project

makes the project easily measurable. The project manager writes down the intermediate and final

modules that the team creates during the development period. Deliverables include everything

the project team creates for the client during the development period, such as the budget, plan,
DATABASE INITIAL STUDY 4

schedule, and documents. Outputs are tangible outputs, measurable and precise items produced

to declare a project complete (Klochkov et al., 2016). The primary responsibility of the project

manager is to accurately document the deliverables of the project and then manage the work

around the project to produce the agreed-upon product. Outputs are advanced products that are

defined in a specific way.

Boundaries for database design project

Project boundaries define the scope of the project. The boundary command helps show all things

that are only applicable to the intended project, excluding areas that are out of scope. Adding

project boundaries will not only increase development costs but also introduce unnecessary

features into the system and reduce system performance. Certain limits are set and cannot be

exceeded. It is important for the project manager to understand the limits to avoid ambiguous

assumptions (Klochkov et al., 2016). The significance of the project boundary is provided by the

point of the curve that describes the increasing load on the resources and the decrease in

performance when the boundary is crossed. On the other hand, working around the boundaries is

not the best choice because better system performance is achieved over a wider spectrum. The

best working scope for the product provides testing and observation of system modules.
DATABASE INITIAL STUDY 5

References

Coronel, C., & Morris, S. (2016). Database systems: design, implementation, &

management. Cengage Learning.

Gao, Y., Liang, Z., Xing, Y., Zhang, H., Ma, J., Lu, H., ... & Moore, W. H. (2018, March). A

feasibility study of extracting tissue textures from a previous normal-dose CT database as

prior for Bayesian reconstruction of current ultra-low-dose CT images. In Medical

Imaging 2018: Physics of Medical Imaging(Vol. 10573, p. 105733C). International

Society for Optics and Photonics.