Personal tools
You are here: Home Academics Syllabi Spring 2008 Syllabi BAD 84082 Spring 2008 Brandyberry
Navigation
 

BAD 84082 Spring 2008 Brandyberry

B AD 84082 - Database Management Systems
Graduate School of Management
SYLLABUS
Spring 2008
COURSE INFORMATION:
Name of Course:
Database Management Systems - B AD 84082 - Section 001
Term:
Spring 2008
Room:
A404 BSA
Meeting Time:
1:00-3:30 pm Monday
Course Web Site:
Prerequisites:
PhD Status
Catalog Description:
In-depth investigation of intelligent database management systems in support of business decision making. An understanding of relational databases is assumed. Object-oriented and semantic databases will be explored. Prerequisite: doctoral standing and permission of instructor.
 
INSTRUCTOR INFORMATION:  
Name of Instructor:
Dr. Alan Brandyberry
Office Address:
BSA A425
Telephone:
(330)672-1146
Office Hours:
3:30-6:15 PM Mon. (and by appointment)
E-mail:
abrandyb@kent.edu
Instructor Web Site:
Under Construction
 
COURSE MATERIALS:
Required Materials:
Journal and other readings to be assigned.
  
COURSE INFORMATION:  
Detailed Prerequisites:
A solid understanding of relational databases and their management is assumed.
 
 
Course Objectives:
Preparation of students to teach and do research in the data management area.  Teaching: Ensure students are prepared to teach database concepts at the undergraduate and master's levels.  Research: Acquaint students with the variety of active data management research topics and develop an in-depth understanding of a few.
 
 
Course Format:
Teaching: We will spend the first several weeks reviewing database concepts to ensure proficiency in the context of ensuring the ability to teach in the area (approximately two-four weeks). 
Research: Following this portion of the course we will alternate weeks between students to lead discussions on more advanced data management topics.  Each student will select a data management related topic (get oral approval for topic from instructor), create a short bibliography (10 minimum, 20 maximum) of what appears to be the most important scholarly papers on this topic, and select four of these papers as readings to be discussed in class.  Students should pass out their bibliography with the selected readings designated the week prior to the discussion. 
The student should plan on leading the discussion on the topic and the other student(s) (along with the instructor) should be prepared to participate in the discussion.  As the discussion leader you may want to present certain aspects of the paper but this should always be done with the assumption that the rest of the class have carefully read these papers.  You should also have discussion points prepared to help guide the discussion.  You may decide to bring in material not in scholarly journals (e.g. text book, web page, etc.) to add to the discussion.  If it is necessary to have the other members look at this prior to the discussion please distribute it early.  Each topic will be presented over two weeks (two papers and any support material per week).  Two topics will always be prepared for each week.  If discussion on the first topic is sufficiently interesting the second topic may be pushed to the following week or started and finished the next week.  We will confirm who will need to be prepared for the next week at the end of each session.  I will attempt to make sure that everyone presents the same number.  This may require teaming up on topics toward the end of semester.
Finally, concurrently with above, each student will select one topic for further research.  This may be one of the topics you presented, one of the topics a colleague has presented (students have first rights to the topics they presented - make sure the student who presented it will not be using it themselves), or a data management topic not presented (obtain approval).  Each student will describe one empirical and one conceptual research topic related to their described topic.  A moderately thorough, generic,  literature review will be written that could support either research idea.  The literature review should be approximately 3000-4000 words, not including bibliography.  The balance of class time will be spent on individual and class discussion and consultation on these topics.
 
 
Attendance:
Attendance at each class meeting is required.  Unexcused absences will adversely affect overall grade.  Non-emergency absences should be cleared with instructor prior to the absence.  Emergencies will be dealt with on an individual basis.
 
GRADES: Grades will be based on the following:
Attendance & Participation
33%
Topic Presentations
33%
Final Project.
34%
 
The following scale indicates the minimum course percentage required for each letter grade:
Letter-grade determinations will be made on the following percentage basis:  A>90%; B>80%; C>70%; D>60%; F<60%. 
 
NOTES:

Data management

From Wikipedia, the free encyclopedia [instructor note: Wikipedia is not an authoritative source without independent verification - however, it is often a useful starting point]

Data management comprises all the disciplines related to managing data as a valuable resource. The official definition provided by DAMA is that "Data Resource Management is the development and execution of architectures, policies, practices and procedures that properly manage the full data lifecycle needs of an enterprise." This definition is fairly broad and encompasses a number of professions which may not have direct technical contact with lower-level aspects of data management, such as relational database management.
Topics in Data Management include:
[This is certainly not exhaustive.  I would include data transport, data querying, open data models (probably a subset of architecture), 'other than database' data storage (eg XML), and certainly others.  Basically if it concerns the management of data in any organizational context it is pertinent to this course topic.]
The Following Policies Apply to All Students in this Course
 
A.     Students attending the course who do not have the proper prerequisite risk being deregistered from the class.
 
B.    Students have responsibility to ensure they are properly enrolled in classes.  You are advised to review your official class schedule (using Student Tools/Flashfast) during the first two weeks of the semester to ensure you are properly enrolled in this class and section.  Should you find an error in your class schedule, you have until Friday, January 25, 2008 to correct the error with your advising office.  If registration errors are not corrected by this date and you continue to attend and participate in classes for which you are not officially enrolled, you are advised now that you will not receive a grade at the conclusion of the semester for any class in which you are not properly registered.
 
C.    Academic Honesty:  Cheating means to misrepresent the source, nature, or other conditions of your academic work (e.g., tests, papers, projects, assignments) so as to get undeserved credit.  The use of the intellectual property of others without giving them appropriate credit is a serious academic offense.  It is the University's policy that cheating or plagiarism result in receiving a failing grade for the work or course.  Repeat offenses result in dismissal from the University.
 
D.    For Spring 2008, the course withdrawal deadline is Sunday, March 30, 2008.   Withdrawal before the deadline results in a "W" on the official transcript; after the deadline a grade must be calculated and reported.
 
E.     Students with disabilities:  University policy 3342-3-18 requires that students with disabilities be provided reasonable accommodations to ensure their equal access equal access course content.  If you have documented disability and require accommodations, please contact the instructor at the beginning of the semester to make arrangements for necessary classroom adjustments.  Please note, you must first verify your eligibility for these through the Student Accessibility Services (contact 330-672-3391 or visit www.kent.edu/sas for more information on registration procedures).
 
Document Actions