INSS 550 DATABASE MANAGEMENT & DECISION SYSTEMS and

IFSM 410 DATABASE CONCEPTS 
COURSE OUTLINE

Class Times: 6:30 - 9:30 26/03 - 16/05                         Class Location: Geilenkirchen, DE
Lecturer: Joyce M. Rowe, Ph.D.                                    Office Hours:  1/2 hr. after class;
Phone: TBA                                                                               by appointment 
e-mail: jrowe@faculty.ed.umuc.edu                              Course Credit: 3 semester hours

Pre-requisite: All pre-requisite classes as listed in catalog or permission of the lecturer

TEXTBOOK: Database Systems:  Design Implementation and Management by Rob and Colonel, 4th Edition, Course Technology, 2000.  

                       INSS 550 will have additional Readings from the Library on the web

HANDOUTS: Will be distributed from time-to-time; you will be responsible for this material

COURSE DESCRIPTION

An introduction to the design and management of database systems in a business environment.  Topics include the role of databases in organizations, the management of information as a critical business resource; types and functions of database management systems; conceptual data modeling, entity-relationship and semantic data models, and the fundamental principles of relational and object-oriented database design.  The implementation and maintenance of database management systems are discussed as is the role of the database administrator. 

<o:p</o:p

GRADING SCALE:

<o:p</o:p

<o:p</o:p

<o:p</o:p

INSS 550       90-100 = A

80 - 89   = B

70 - 79  = C

Below 70 = FA

IFSM 410      90-100 = A

80 – 89 =  B

70 – 79 = D

60 – 69 = FA       <60 = F

ASSIGNMENTS

Individual cases/assignments--Each student will develop various models and complete small case studies and assignments in Access, often in class, sometimes out of class.  These cases are useful in applying the methodologies discussed in class.  Additionally, each graduate student will be assigned a topic relating to a language, a methodology, etc., to follow in the news over the eight weeks of classes. Information relating to that subject will be introduced and discussed every two weeks. Quizzes may be given without notice. 

Project--Students will be divided into small teams and will analyze a typical business problem. This problem will be carried through the analysis and design phase, with the appropriate models required, and brought into production. This requires a project team with a project leader, design and development models, database design and development with query, input and output interfaces in Access; and database population. Additionally, a quality User’s Manual describing the use of the system will be produced. In the last week of classes each team will make a management-level presentation of their system.

Subject Research and Class Participation---Graduate students will select one topic from a list of current database topics (tentative list at bottom of syllabus). The student  will make a 10- to 15-minute class presentation,  turn in a 5-page summary along with a page of resources used,  (use the APA format for this bibliography, as provided on the UofM Library website), and   provide each class member a 1-page handout.  Students will be graded on the quality of their presentations and summations along with their classroom discussion.  By the end of the class every student should have an elementary understanding of these topics; this material will be eligible for testing on exams.  Students also are expected to be able to discuss the concepts in the book and demonstrate their applications through discussion of real-world problems.  This part of the course will familiarize students with the concepts in modern databases and the respected researchers in the field. Undergraduate students will select a database language or company, research the background and future prospects, produce a 2-3 page report on the findings, and make a class report.

Midterm/Final--Graduate midterm and final exams will consist of essay questions related to the goals listed at the beginning of each chapter and the outside readings and a comprehensive exam question. This portion of the tests (worth 100 points) will be graded exactly like comprehensives; that is: 75% for content, 25% for English and organization. Undergraduate midterm and final exams will contain 25 -50% objective questions and the remainder short answer discussion and/or programming-related questions.

COURSE POLICIES/EXPECTATIONS

The following policies apply to this class. These policies are generally reflected in the student catalog.

*   ATTENDANCE POLICY: Regular class attendance is expected, both mornings and afternoons of weekend classes. If you should miss a meeting, it is your responsibility to obtain information concerning the material covered and upcoming assignments. If there is a quiz or other assignment due on that class period, previous arrangements should be made with the instructor whenever possible. Please note that those students receiving tuition assistance from the Federal Government must not miss three consecutive class meetings without prior approval, or the education Services Officer (ESO) must be notified by the instructor.

*  ACADEMIC HONESTY: Students are expected to do their own work. Cheating on tests, plagiarism on written assignments, or any other form of academic dishonesty will result in a "0" for the assignment. Note that a D or an F usually results in at least 60 or 50 points, where violation of academic honesty results in none. See the European Division Catalog for the UMUC policy on academic dishonesty and plagiarism.

*  ASSIGNMENT/TEST SCHEDULES: Students are expected to hand in all assignments and complete all tests on the days they are due. If a student fails to complete any assignment or test, the resulting grade will be a "0," rather than an "F." Any other assignments will be marked down half a letter grade for each half week the assignment is late. Quizzes cannot be made-up unless the student had an excused absence. Major tests to be missed must be taken before the date the test is to be given in class. On the date of research presentations or project presentations, each person must be in attendance for the first presentation. Otherwise, the presentation will be deemed late and a 10% reduction will be made for all presentations given that the student missed.

* CLASS PREPARATION: Students are expected to come to class prepared. This means they should have read the materials assigned for class for that session and have prepared any pertinent assignments. Quizzes may be given.

COURSE OBJECTIVES

The objectives for this course are listed in each chapter. Questions on the midterm and final will be directly related to these goals, even though the topic may not be covered in class.  Students completing class should:

• Develop database planning models
• Identify types of databases utilized within business structures 
• Identify, describe and model different database topologies 
• Discuss the advantages and disadvantages of databases over flat files; of different types of database

        topologies 

• Develop SQL queries
• Develop logical and physical database designs
• Produce 1NF, 2NF, and 3NF structures
• Explain centralized, decentralized, and distributed database systems  Discuss Security systems appropriate for databases
• Develop Specification Requirements for on-line databases
• Describe the process for developing applications, including development of Program Specification Requirements

The activities and assignments for this course are designed to help the student know, comprehend, and apply the basic concepts of systems analysis and design.  In addition to the academic objectives, students are expected to improve their skills in the following areas:

1. Critical Thinking: Students should improve their ability to analyze computer user situations and make appropriate suggestions for resolving business problems through computer systems.  The  projects in this class encourage students to think critically about real-world situations.
2. Writing Skills: Students should improve writing skills through development of the Feasibility Study and formal report on the major project and on the mid-term and final.
3. Oral Presentation Skills: Students should improve their presentation skills through their oral reports on the major project, class discussions, and group presentations.
4. Computer Skills: Students are expected to improve their computer skills by using word processing and project management software.  The use of  Internet and e-mail are also encouraged.

TENTATIVE SCHEDULE

Topics Discussed

Activities

Class 1

Mar 26

Chapter 1:  File Systems and Databases; Chapter 2:  Relational Databases

Read Chapters 1 and 2 before class; In class problems and discussions; Assignment: Homework assignments; Select teams; Chapter 3

Class 2

Mar.28

Chapter 3:  SQL; Topic Research Assignment; Teams selected

In-class lecture and discussion; problems; Assignment:  Homework; Chapter 4

Class 3 

Apr. 2

Chapter 4:  Entity-Relationship Diagrams; Project assignments; Team meetings

In-class lecture and discussion; problems; team meetings:  Assignment:  Homework; Review Project planning techniques; Gantt Chart

Class 4

Apr. 4

Review Project planning; DFD; Class Diagrams; Use Case Diagrams; Team meetings

In-class lecture and problems; Assignment: Team DFD, ERD, and Class Diagrams; Investigation activities; Chapter 5

Class 5 

Apr. 9
 

Chapter 5:  Normalization;  Presentation of investigation, DFD, ERD, Class and Use Case Diagrams; Team meetings

In-class lecture and problems; Assignment: Team Design activities with Program Specs; I/O interfaces 

Class 6

Apr 11

Prototyping; User’s Manuals; Interface specifications; Access Database tables

In-class lecture and problems; Assignment:  Team User Manual assignments; I/O interface assignments; Database tables

Class 7

Apr. 16 
 

Access Database

Team assignments reviewed and modified; Assignment:  Access Forms and Reports;

Class 8

Apr. 18

Access Database

Team assignments reviewed and modified; Assignment:  Study for Midterm Exam

Class 9
Apr. 23
 

MidTerm Exam; Team reviews

 Access Queries; Assignment: Access database and User’s Manual

Class 10 

Apr. 25  

Moving the project from Logical to Physical; Design and Testing Techniques

Access Database Population techniques; Macros; Assignment:  Populate database and opening Macro

Class 11 

Apr. 30

Normalization; Implementation techniques; Techniques for Management presentations

Assignment:  In-class lecture and problems; Continue working on Database and User’s Manual; Chapter 9

Class 12

May 2

Chapter 9:  Transaction Management and Currency Control

Assignment: In-class lecture and problems;  Continue working on Database and users manual; Chapter 10

Class 13

 May 7

Chapter 10:  Distributed Database; Modeling for partitioning on the network; IFSM Reports

Assignment:  In-class lecture and problems; Continue working on Database and User’s Manual; Chapter 15 Database Administration

Class 14

May 9 

Chapter 15:  Database Administration; INSS Reports

In-class lecture; Reports; Assignment:  Chapter 11

Class 15

May 14 

Chapter 11:  Database and Internet; Project presentations

Project presentations; In-class lecture; Assignment:   Final Exam

Class 16
May 16

Final Exam Chapters 1-11; 15