|
MASTER SYLLABUS |
|||||||||
|
CST 2510 |
|||||||||
| Class Hours: 3.0 | Credit Hours: 4.0 | ||||||||
| Laboratory Hours: 3.0 | Date Revised: Spring 01 | ||||||||
| Catalog Course Description: | |||||||||
| A study of database management systems. Topics include classic database models, knowledge-based and object-oriented models, conceptual design, data structures, storage techniques, data administration, and distributed systems. Special emphasis will be put on relational systems and application of query languages using relational operations. Practical application of specific query languages or techniques may include SQL, xBase, and QBE. | |||||||||
| Entry Level Standards: | |||||||||
| The entering student should have a familiarity with the MS-DOS and the Windows environment. The student is expected to have moderate programming abilities in a high-level language. Problem solving skills will be essential. The student should be able to keyboard at least 23 words per minute. | |||||||||
| Prerequisites: | |||||||||
| CST 1410 and CST 1540 | |||||||||
| Textbook(s) and Other Reference Materials Basic to the Course: | |||||||||
| Database Processing Fundamentals, Design,and Implementation; Kroenke, David (7th. Edition); Prentice-Hall, 2000. | |||||||||
| I. Week/Unit/Topic Basis: | |||||||||
| Week | Topic | ||||||||
| 1 | Introduction, Database Concepts, Processing and Development | ||||||||
| 2 | Database Development, Database Models | ||||||||
| 3 | The Entity-Relationship Model | ||||||||
| 4 | The Entity-Relationship Model | ||||||||
| 5 | Design Using the Entity-Relational Model | ||||||||
| 6 | The Relational Model and Normalization, Exam I | ||||||||
| 7 | The Relational Model and Normalization | ||||||||
| 8 | Normalization, Relational Implementation with Relational Algebra | ||||||||
| 9 | Relational Algebra and Calculus, QBE, SQL | ||||||||
| 10 | Application Design, Physical Design and Implementation | ||||||||
| 11 | Physical Design and Data Structures, Exam II | ||||||||
| 12 | Managing Multi-user Databases, Transactions and Concurrency Control, Security | ||||||||
| 13 | Sharing Enterprise Data, OLAP, Data Warehouses and Marts, Drill-down, Data Cubes | ||||||||
| 14 | Database Access and the Internet, ODBC | ||||||||
| 15 | Object-Oriented Database Processing | ||||||||
| 16 | Final Exam | ||||||||
| II. Course Objectives*: | |||||||||
| A. | Understand the advantages and disadvantages of using a database management system rather than conventional filing methods. II III IV VII IX XI XII | ||||||||
| B. | Recognize the language of data definition and data manipulation and its importance. III IV VII XI | ||||||||
| C. | Recognize the components of the various database models and appreciate how implementations as systems may vary from the model. III IV VII IX XI XII | ||||||||
| D. | Understand the factors involved in the transformation of a conceptual design into a logical data base design and to a physical database design. III IV VII IX XI XII | ||||||||
| E. | Appreciate the database administration function. I II III IV V IX XI XII | ||||||||
| F. | Use a database management package including use of a query language. III IV VI VIII IX | ||||||||
| G. | Recognize classic data structuring techniques. I II III IV V IV IX XI XII | ||||||||
| *Roman numerals after course objectives reference goals of the Computer Science Technology program. | |||||||||
| III. Instructional Processes*: | |||||||||
| Students will: | |||||||||
| 1. | Use professional tools to produce software components and documentation. Technological Literacy Outcome, Transitional Strategy, Personal Development Outcome | ||||||||
| 2. | Learn to analyze and solve problems using structured analytical techniques. Technological Literacy Outcome, Information Literacy Outcome, Numerical Literacy Outcome, Active Learning Strategy, Problem Solving and Decision Making Strategy | ||||||||
| 3. | Use professionally accepted methods and materials in completion of applications. Technological Literacy Outcome, Transitional Strategy, Active Learning Strategy, Personal Development Outcome | ||||||||
| 4. | Practice elements of the work ethic such as punctuality, professionalism, dependability, cooperation, and contribution. Personal Development Outcome | ||||||||
| *Strategies and outcomes listed after instructional processes reference Pellissippi State’s goals for strengthening general education knowledge and skills, connecting coursework to experiences beyond the classroom, and encouraging students to take active and responsible roles in the educational process. | |||||||||
| IV. Expectations for Student Performance*: | |||||||||
| Upon successful completion of this course, the student should be able to: | |||||||||
| 1. | Explain the similarities and differences of hierarchical, network, and relational data models. C D E | ||||||||
| 2. | Perform database normalization. D E | ||||||||
| 3. | Develop Entity-Relationship Models. D E | ||||||||
| 4. | Create a data dictionary. D E | ||||||||
| 5. | Describe the functions of data base administration. E | ||||||||
| 6. | Write programs using query languages. F | ||||||||
| 7. | Explain and schematically draw data structures represented as tree structures or networks. A C E G | ||||||||
| 8. | Define schema and subschema and explain the generic terminology associated with them. B C D E | ||||||||
| 9. | Describe the organization and problems associated with distributed database systems. A C E | ||||||||
| 10. | Read a program specification block and construct the corresponding application program view of the data. E | ||||||||
| 11. | Represent data using the object-oriented model. C E G | ||||||||
| 12. | Describe the concept of binary trees, B-trees, linked lists, and hash tables. A C D E F G | ||||||||
| 13. | Represent data from the hierarchial and network models using the relational model. A C E | ||||||||
| 14. | Explain file organizations and access methods. A C G | ||||||||
| 15.
16. 17. 18. |
Explain
the concept of inverted files. A C G
Design forms and reports using Visual dBase. B E F Design forms and reports using Access. B E F Use SQL to create and access a table on an Oracle server. B F |
||||||||
| *Letters after performance expectations reference the course objectives listed above. | |||||||||
| V. Evaluation: | |||||||||
| A. Testing Procedures: | |||||||||
| Three comprehensive exams will be given during the course of the semester. Dates will be announced in class and each test will account for 200 points of your final grade -- 600 points total. During summer semester, two 300 point exams will be given. | |||||||||
| B. Laboratory Expectations: | |||||||||
| Lab Schedule:
Week Topics 1-2 File Manager Program 3 E-R Design Documentation 4-7 xBASE/QBE Application Development 9 Access Application Development 10-15 SQL Tutorial, Oracle Client/Server Access Several lab assignments will be made during the course of the semester. A late penalty may be imposed on any overdue assignment. Individual and/or group projects may be as-signed to emphasize practical solutions to database problems. Failure to satisfactorily complete any assigned projects may result in a grade of F for the course. Lab projects will account for 300 points of your final grade. |
|||||||||
| C. Field Work: | |||||||||
| Unannounced quizzes and homework assignments will be given. These will account for 100 points of your final grade. | |||||||||
| D. Other Evaluation Methods: | |||||||||
| This information, if applicable, will be provided by the instructor in full detail during the first week of class via syllabus supplement. | |||||||||
| E. Grading: | |||||||||
| Grade
Breakdown:
First Exam 200 (20%) Second Exam 200 (20%) Final Exam 200 (20%) Lab Assignments 300 (30%) Quiz/Homework 100 (10%) Total 1000 Points Grading Scale:
|
|||||||||
| VI. Policies: | |||||||||
| A. Attendance Policy: | |||||||||
| Class attendance may affect your grade. Pellissippi State Technical Community College expects students to attend all scheduled instructional activities. As a minimum, students in all courses must be present for at least 75 percent of their scheduled class and laboratory meetings in order to receive credit for the course. | |||||||||
| B. Academic Dishonesty: | |||||||||
| Plagiarism, cheating, software piracy, non-educational use of computer systems and other forms of academic dishonesty are strictly prohibited. A student caught cheating or infracting specific rules will be given a grade of "F" for the course. | |||||||||
| C. Other Policies: | |||||||||
| Make-up
exams: All exams are required, and make-ups will be allowed only
in the rarest of cases. In the event of an emergency, notification of the
instructor must be made in advance.
It is the student's responsibility to request help from the instructor prior to an assignment's due date. |
|||||||||