CIS and programs. Databases allow institutions to use and

 

 

 

 

 

CIS
111

 

Week
2 Assignment 1

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

 

Jerrell
L. Jackson

 

January
14, 2018

 

Strayer
University

 

Professor
Otto

 

 

 

Purpose of database

The purpose of the database is to track students,
the courses they take and the instructors teaching each of the classes. The
database will help manage students and instructor’s data including assignments,
grades, and historical data. Existing literature shows higher levels of student
engagement and learning when faculty uses active and collaborative learning
techniques (Umbach and Wawrzynski, n.d). The database will capture information
relevant for faculty to monitor student grades and to track instructors
teaching courses. The database will help ensure it monitors the grades of
students and instructors.

 

Business Rules and Data Models

Educational
institutions generate and consume a lot of operational information. These
institutions must track information about people including students,
instructors and other faculty members who play key functions in supporting
their services and programs. Databases allow institutions to use and manage
incredible a wide variety of information. This is an important aspect of
information management, the exploitation of data, information and knowledge
resources to support decision making via efficient access to relevant and
accurate information. The purpose of the current paper is to describe the
information that a college would want to track in a database. The focus is to
help develop a database to help faculty track students, courses, and
instructors.

 

 

Entities of the Database and Attributes of Each
Entity

Generally,
an entity refers to a thing or concept in which data is collected. Entities
comprises of various attributes, or the details or facts of a given entity. For
the course database, the entities are the ‘classes’, ‘class ID’ and ‘tasks’.
The attributes for the ‘classes’ entity are ‘class name’, department’,
‘instructor name’, ‘location’, ‘days/time’, ‘student’s name’, ‘major’,
‘assignment’, ‘class notes’, ‘cell phone number’, ‘grade’. The attributes for
the entity ‘class id’ are the ‘section’, ‘term’, ‘year’ and ‘units’. The
‘tasks’ entity has only four attributes: ‘create new classes, ‘view reports’
and ‘provide feedback’.

 

Business Rules that could Influence the
Structure of Database

Business
rules refers to statements that enforce constraints on specific database
aspects. Business rules define entities, relationships and attributes. Data in
the proposed database will be considered only after definition of business
rules. The following are the business rules:

Department ….offers ….course

Course….generates….class

Instructor….teaches…..class

Class….consists of….students

Student….undertakes….examinations

Examinations….produces….grades

Student…takes…maximum of 3 units

Information
for the Conceptual and Physical Data Models

Entity-relationship
(ER) modeling is central in relational database design because designers
conceptualize ER model and transform them to relations. Generally, data
modeling entails three levels: conceptual, logical and physical data models.
Conceptual data model is the initial step in data modeling and entails all
major entities and relationships but does not have detailed level of
information related to attributes. Therefore, the conceptual model for the
course database would feature entity names and entity relationships. The
physical data model describes the way data is stored or saved in a given media.
It stipulates the storage devices and the methods of accessing stored data.
Therefore, physical data model depends on both the hardware and the software.

 

 

 

 

 

 

 

 

 

 

References

 

Umbach,
P. & Wawrzynski, M. (n.d). Faculty do matter: the role of college faculty
in student learning and engagement, pp. 1-35. Accessed July 9, 2014 from http://nsse.iub.edu/pdf/research_papers/faculty_do_matter.pdf

 

Virnala,
S. Nehemiah, K. Bhuvaneswaran, R. & Saranya, G. (2013). Design methodology
for relational databases: issues related to tertiary relationships in
entity-relationship model and higher normal forms. International Journal of Database Management Systems, 5(3), pp.
15-37

 

 

x

Hi!
I'm Neil!

Would you like to get a custom essay? How about receiving a customized one?

Check it out