Description
IS 675 is the graduate course component of IS 475. To register for IS 675, you must be enrolled as a graduate student at the University of Nevada, Reno. The objectives for IS 675 are fundamentally the same as those given in the course syllabus for IS 475. As stated in the syllabus, the course explains "how" to perform database design and implementation tasks. The difference for the graduate component is that a graduate student is expected to explore course topics in more depth so that you understand "why" the activities performed during design and implementation are done.
Requirements
Graduate students are expected to complete all required coursework
as stated in the IS 475/675 syllabus.
In addition to the required coursework, you will also complete
an individual paper or a practical design/implementation project
of your own definition and creation. If you are not able to define
a special project or paper, then I recommend you drop IS675 and
sign up for IS475; as a graduate student you must be able to independently
identify a special area that is of interest to you and is related
to the course.
Possible topics for a paper include (but are not limited to): Data mining techniques, issues in data warehousing, the limitations of current data modeling methodologies, security methods for web-based databases, performance issues in web-based databases, evolving XML standard, quality assurance for database design, database integrity issues or issues in database administration. This is a business information systems class, so I expect your paper topic will be related in some way to business databases. It will not be acceptable to submit a paper that exclusively discusses DBMS algorithms or database issues relevant only to computer science such as an evaluation of query optimizer algorithms.
If you elect to complete a practical project, the project must go beyond the scope of the design and implementation tasks completed for the undergraduate projects. We will be designing and implementing a transaction processing database in this class. Your project would have to expand on these tasks by incorporating a web-based database, creating a decision support database or changing the architecture of the database. You might consider creating a database by integrating the contents of publicly available databases, such as data from the census or other governmental agencies. Another possibility would be to take the SQL project from class and expand it by adding production-level triggers and stored procedures. It is not sufficient, however, to simply design or implement a database similar to one we have done in class.
The time line for the graduate project deliverables is as follows:
09-22-09 First draft of project or paper explanatory statement. The explanatory statement should describe in detail the objective of the project and the deliverables from the project. If it is a practical project, then you should describe the platform you intend for implementation. If it is a paper, then you should identify your topic and define a few questions you intend to answer in your paper. The explanatory statement should be 1/2 to 1 page in length.
You MUST meet with me before submitting the statement. You are responsible for setting up a meeting day and time with me prior to this date to discuss your project/paper.
10-01-09 Finalized draft of project or paper explanatory statement. If your first statement was marked "acceptable," "OK," or "good," then you do not have to complete a finalized draft. 11-03-09 Bibliography of paper or complete design specifications of project. I expect a complete bibliography of all intended resources (paper and web-based) if you are doing a paper. Be sure to include at least 6 references and at least 3 of those references must be journals rather than trade publications. If you do not know the difference between a journal and trade publication, please see me for assistance. If you are doing a project, then the design specifications include database design, user interface design, and processing design. 12-03-09 Final version of paper or project.
