Search
MyUMUC
WebTychoUMUC European Division-Term IV/01-02
|
TENATIVE COURSE OUTLINE |
|
Class Times: 0900-1600
Class Location: London, UK
Lecturer: Joyce M. Rowe, Ph.D.
Office Hours: 1/2 hr. before/after class;
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. Additional
Readings from the Library on the web HANDOUTS:
Will be distributed from time-to-time; you will be responsible for this
material 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.
|
|
|
|
|
|
|
Database
Project [Users Manual]
|
20
points
|
|
Database
Project [Operation of DB]
|
25
points
|
|
Database
[Presentation]
|
5
points
|
|
Subject
research/presentation(15);class participation (5)
|
20
points
|
|
Final
|
30
points
|
|
|
GRADING SCALE: |
|
|
|
INSS
550 90-100 = A |
80
- 89 = B |
70
- 79 = C |
Below
70 = FA |
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 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.
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---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-7 page summary 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 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. 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 |
||
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:
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:
|
||
|
|
||
|
|
Topics
Discussed
|
Activities
|
|
Class
1
Mar
23 0900-1200 |
Chapter
1:File Systems and Databases; Chapter
2:Relational Databases
|
Read
Chapters 1-5 before class; In class problems and discussions; Select teams
|
|
Class
2
Mar
23 1300-1600 |
Chapter
3:SQL; Topic Research Assignment;
Teams selected
|
In-class
lecture and discussion; problems; Assignment:Read
Chapters 4-5; Review Project planning techniques; Gantt Chart
|
|
Class
3
Mar
24 0900-1200 |
Chapter
4:Entity-Relationship Diagrams;
Project assignments; Team meetings
|
In-class
lecture and discussion; problems; team meetings
|
|
Class
4
Mar
24 1300-1600 |
Review
Project planning; DFD; Class Diagrams; Use Case Diagrams; Team meetings;
Chapter 5:Normalization
|
In-class
lecture and problems; Assignment: Team DFD, ERD, and Class Diagrams;
Investigation activities; Read about Access Databases; Complete papers
|
|
Class
5
Apr
13 0900-1200 |
Presentation
of investigation, DFD, ERD, Class and Use Case Diagrams; Team meetings
|
In-class
lecture and problems
|
|
Class
6
Apr
13 1300-1600 |
Prototyping;
User’s Manuals; Interface specifications; Access Database tables
|
In-class
lecture and problems; Assignment:Team
assignments for User Manual, I/O interfaces, tables; Web search for writing
user manuals
|
|
Class
7
Apr
14 0900-1200 |
Normalization;
Discuss components of a good User Manual; good screen/interface design
|
Team
assignments reviewed and modified;
|
|
Class
8
Apr
14 1300-1600 |
Implementation
techniques; Techniques for Management presentations; Paper presentations
|
Team
assignments reviewed and modified; Assignment:Access
Forms and Reports; Chap. 9-10; begin to populate tables, develop queries
|
|
Class 9
Apr. 27 0900-1200 |
Chapter
9:Transaction Management and Currency
Control
|
Access
Queries; Discuss User’s Manual, transaction management
|
|
Class
10
Apr
27 1300-1600 |
Chapter
10:Distributed Database
|
Access
Database Population techniques; Macros; distributed database Assignment:Exam
|
|
Class
11
Apr
28 0900-1200 |
Design
and Testing Techniques; reports; Moving from test to production
|
In-class
lecture, problems; Database and User’s Manual
|
|
Class
12
Apr
28 1300-1600 |
EXAM |
Assignment:
Database and users manual; presentation; Chapters 11, 15;
|
|
Class
13
May
11 0900-1200 |
Modeling
for partitioning on the network; IFSM Reports
|
In-class
team work, discussion
|
|
Class
14
May
11 1300-1600 |
Chapter
15:Database Administration
|
In-class
lecture; Assignment:Complete
database and users manual
|
|
Class
15
May
12 0900-1200 |
Chapter
11:Database and Internet
|
In-class
discussion
|
|
Class 16
May 12 1300-1600 |
Team Project Presentations
with User's Manuals
|
Projects
presented
|
PRELIMINARY
LIST OF 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