John Sullivan: Developed in 1996
Background
I have been teaching at the college level for almost 20 years and have become overwhelmed by the amount of work I do. I teach 4 to 5 classes per semester plus overloads (Overtime) or extra classes. Since, I began teaching I have taught over 25 different courses. In addition, I teach two overload classes each summer. I also teach about five different courses per academic year. The number of students I have is usually about 120 a semester. In addition, there has also been some downsizing going on at the college, and the secretarial help is now very limited. This has lead to a number of problems. Therefore, I am trying to automate everything I possible can.
One: When students come for a recommendation I have my grade books stored serially by academic year and in no course order. Plus, I have to reprogram my calculator every semester for every course because of different grading criteria.
Another problem I have is I read a lot and have stacks of Journals, Magazines, Books, Newspapers and etc. all over my office and home. Inevitably I can not remember where what is, and after a period of time throw it away. I would like to not only keep track of these reading but be able to add them to my lecture notes or research papers.
Problem three is I cannot keep track of what tests I have given when in a course. For instance, for some courses I have over 10 versions of the same test. As hard as I have tried I cannot keep track of this process.
Last, I never have course descriptions and pertinent information handy.
Project goals
The purpose of my project is to develop a database that every professor would love to have on their PC. This project will be developed using the phased implementation method. It will be phased in over the next year. The first phase was developed in a course on Database Development & Design at Nova Southeastern University. However, I envision more tables being implemented over time. For instance, an Administrative table to keep track of materials for self evaluations, and promotions. Eventually, I would like to keep track of notes and lectures as well.
In the first phase that will be developed for this course I will develop a number of tables. First, a student grading table will be implemented to keep track of all tests, projects, and extra credit. A form will be created to input the data for each student. In addition, a report will be developed (from a query) that will determined the course grade for each student by that course's grading criteria. Second, I would like to not only keep my readings organized, but keep my lectures organized and up to date with clippings. In addition, I would like to keep the clippings in an A.P.A. format for future reference for my research activities. Third, I would like to keep track my course descriptions, course syllabus, and other course material better. Last, I would like to keep track of when I give certain tests. This is to make sure I do not give the same test the following semester. Due to the number of tables I already have I may add the administrative table at a latter date.
The one thing I am looking at is a file of clippings. Most large organizations have a clipping service that cuts out all articles pertaining to that business or organization. I would like to do the same for my courses.
Major Functions
Keep track of my courses: To keep track of course numbers, descriptions, requirements, etc.
Be able to keep track of my new readings (Like a clipping service): To be able to recall and update old readings. The output would be in an APA format. The form would be developed the same way.
Enable a student grading database: To record, keep track, calculate final grades, To reference for future recommendation
General Outputs
Student List:
Course
Section
Student Name
Clippings: (A.P.A. style)
Author
Date
Title
Source
Location
Pages
Student Grades:
Course Name
Section
Student Name
Student Soc. Sec. Number
Grades
Tests Inventory:
Test Name
Test Topic
Date Given
General Information - Inputs Required
Each faculty member will be responsible for their own input. There will be a lot of initial input but after that it will be updated as input is generated. This database is voluntary, and maintained as needed. Each semester a new class will be entered which is the way I do it now.
Performance
This database will have to be accessible in a timely manner. In other words, if I have ten minutes before class to retrieve my notes it is capable of doing so.
Growth
Over the years this database will grow with the years of experience of the teacher. As I said I now have close to 2000 files and the rate of growth is increasing as I use the computer for more and more house keeping. The only problem in the past has been the size of the hard drive.
Operation & Environment
Each faculty member has the necessary hardware. They can request this software if they desire to do so. It will be each faculty members responsibility to maintain their own database. Timely input is highly recommended. It is expected that Microsoft's Access will be the database of choice. I will develop it in the newest version and make it backward compatible when needed. This due to the fact that not all faculty are working in a Windows 95 environment.
Compatibility, Interfaces
There are no compatibility requirements for the CIS department where this will be piloted since there is no present system. Some of the reports generated will need to replicate existing forms which should help faculty readily adjust to this new system. Familiar forms will be developed to help the faculty make a transition. One area under testing is, do I want to start students grades in Excel and ship them over to Access or start them in Access? Another area of concern is putting the actual Word for Windows files right in Access and therefore doubling my storage requirements. Last, will this work with Ingres?
Reliability, Availability
The system is expected to be reliable and then made generally available after an initial pilot testing. Then it will be distributed on an per request basis.
Human Interface
The user will need to be familiar with the Windows 95 operating system and Microsoft's Access.
Documentation and Training
Since the new system is replacing a paper system and all inputs and outputs are familiar to faculty members little documentation is needed. Faculty that are not familiar with Windows 95 or Microsoft's Access will need training.
Data Dictionary
e-mail:jsulliva@raritanval.edu
Back to John Sullivan's Home Page
Copyright @ 1997 John Sullivan, Revised January 2000