
UMUC European Division-Term I/02-03
|
INSS 550 DATABASE MANAGEMENT & DECISION SYSTEMS |
||
|
Class Times: 24/08 - 20/10 Class Location: Aviano, Italy Lecturer: Joyce M. Rowe, Ph.D. Office
Hours: 1/2 hr. before/after class;
Database
Systems: Design Implementation
and Management by Rob and Colonel, 5th Edition, Course Technology,
2000. Additional Readings as assigned
COURSE DESCRIPTIONAn
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. |
||
|
GRADING
CRITERIA: |
|
|
Homework/Participation |
15
points |
|
Database
Project [Operation of DB] |
20
points |
|
Database
Project [Presentation and Users' Manual] |
15
points |
|
Subject
research |
20
points |
|
Final |
30
points |
|
|
GRADING SCALE: |
|
|
|
90-100 = A |
80 - 89 = B |
70 - 79 = C |
Below 70 = FA |
ASSIGNMENTS |
|
Homework/Participation--Each student will develop various models and
complete small assignments, often in class, sometimes out of class. These
cases are useful in applying the methodologies discussed in class.
Additionally, each student will be assigned a topic relating to a language, a
methodology, etc., to follow in the news over the eight weeks of classes and
to report/summarize at class meetings. Students will discuss 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.
Project--Students will be assigned a typical business
problem. This problem will be carried through the analysis and design phase,
with the appropriate DB and analysis models and brought into production with
the development of queries, input and output interfaces in Access; and
database population. Additionally, a complete Users' Manual will accompany
the database and an in-class presentation of the project. Students will work
in 3- to 4-member teams for this assignment, but each student will be
required to complete sections individually and will be graded accordingly.
Everyone on the team will be responsible for programming the database. Subject Research ---Students will select one topic from a list of current database topics (tentative list at bottom of syllabus). The student will produce a 5-7 page paper along with a page of resources used, (use the APA or MLA format, single spaced, for this bibliography, as provided on the UMd Library website), and provide each class member a 1-page summary to be posted on-line. Students will be graded on the quality of their work as well as the depth. 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. The test (worth 100 points) will be graded exactly like comprehensives; that is: 75% for content, 25% for English and organization |
||
COURSE POLICIES/EXPECTATIONS
|
||
|
The following policies apply to this class. These policies are generally reflected in the student catalog. * ATTENDANCE POLICY: Students should access the web site several times each week. This is a web-enhanced course, not a DE course. Therefore, the material will need to be covered in 8 weeks and will require more intense work and participation on a regular basis. * 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. Major tests to be missed must be taken before the date the test is to be given in class. * CLASS PREPARATION: Students are expected to access the web site several times each week. Also, students must be prepared; i.e., assignments should be read and completed before attempting to participate in class on-line discussions. |
||
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:
topologies
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:
|
||
|
TENTATIVE
SCHEDULE |
||
|
|
Topics Discussed |
Activities |
|
Class
1 Morning
Aug |
Chapter
1: File Systems and Databases;
Chapter 2: Relational Databases |
Read
Chapters 1-4 before class; In class problems and discussions; Assignment:
Homework assignments; Select teams |
|
Class
2 Afternoon
Aug
|
Chapter
3: SQL; Topic Research Assignment;
Teams selected |
In-class
lecture and discussion; problems; Chapter 4; Select paper topic and have
approved |
|
Class
3 Morning Aug |
Chapter
4: Entity-Relationship Diagrams;
Project assignments; Team meetings |
In-class
lecture and discussion; problems; team meetings; Review Project planning
techniques; Gantt Chart |
|
Class
4 Afternoon Aug |
Review
Project planning; Review DFD; Class Diagrams; Use Case Diagrams; Team
meetings |
In-class
lecture and problems; Assignment: Team DFD, ERD, and Class Diagrams;
Investigation activities; Chapter 5 and Access database |
|
Class
5 Morning
Sept
7 |
Chapter
5: Normalization; Presentation of investigation, DFD, ERD,
Class and Use Case Diagrams; Team meetings |
In-class
lecture and problems; I/O interfaces
|
|
Class
6 Afternoon
Sept |
Prototyping;
User’s Manuals; Interface specifications; Access Database tables |
In-class
lecture and problems; Team User Manual assignments; I/O interface assignments;
DB tables |
|
Class 7 Morning Sept
8 |
Access
Database |
Team
assignments reviewed and modified; Access Forms and Reports |
|
Class
8 Afternoon Sept |
Access
Database |
Team
assignments reviewed and modified; Assignment: Study for Midterm Exam – db theory;
Read Chapters 9 – 10; complete papers |
|
Class 9 Morning |
MidTerm
Exam; Team reviews |
Access Queries; Access database and
User’s Manual |
|
Class
10 Afternoon Sept |
Moving
the project from Logical to Physical; Design and Testing Techniques |
Access
Database Population techniques; Macros; Populating database and opening Macro |
|
Class
11 Morning Sept |
Normalization;
Implementation techniques; Techniques for presentations; Chapter 9: Transaction Management and Currency
Control |
In-class
lecture and problems; Presentations of papers |
|
Class
12 Afternoon Sept |
Chapter
10: Distributed Database; Modeling
for partitioning on the network |
In-class
lecture and problems; Assignment: Continue working on Database and
users manual; Read chapters 11 an 15 |
|
Class
13 Morning Oct |
IFSM
Reports |
In-class
lecture and problems; Present Database and User’s Manual |
|
Class
14 Afternoon Oct |
Chapter
15: Database Administration; INSS
Reports |
In-class
lecture; Discuss projects/problems |
|
Class
15 Morning
Oct |
Chapter
11: Database and Internet; Project
presentations |
Project
presentations; In-class lecture; Final Exam |
|
Class 16 Afternoon Oct |
Final Exam Chapters 9-11;
15; Access |
|
PRELIMINARY LIST
OF POSSIBLE RESEARCH TOPICS for INSS 550
- Security violations when implementing Scripting
with Database on the Internet
- Image Databases: Types, requirements, uses, advantages, disadvantages
- N-Tier database applications
- Security issues in a DB environment
- Web mining and its relationship to the
database and privacy issues
- Distributed databases: Partitioning constraints and
implementation
- Web to DB: Middleware needed
- Various methods for initializing a DB in client-server systems