Syllabus+Spring+2012



=**IST 704 – Database Management**= = Spring 2012 =


 * Instructor ** : Neal J. Hannon
 * Office ** : Summerfield Hall, Room 318
 * Phone ** : 660-888-8526
 * Email: ** hannon@ku.edu
 * Skype: ** nealhannon


 * Office Hours ** :Tuesday 12 noon to 12:45 PM or by appointment; Skype available


 * Classes ** : Tuesday 1:00 PM to 2:15.00 PM T-TH SUM 507 352 & H 364


 * Texts ** : **//Modern Database Management //**//** (10th Edition) **//by Jeffery A. Hoffer, V. Ramesh, and Heikki Topi Prentice Hall

Course Description
IST 704 familiarizes the student with a range of topics related to databases and database management. Topics include the nature of databases, process modeling and database development, structured query language, and specialize database applications. Upon completion of the course, the student should understand the importance of databases and database performance in a variety of business applications. Moreover, the student should be able to apply generally accepted conventions to accurately and effectively model business processes. While students will create a functioning database system (using Microsoft Access), the primary focus of IST 704 is on concepts rather than technical implementation. Course Communication I intend to make extensive use of wikispaces, blackboard and email to communicate with you. You'll need to check frequently. I anticipate a lively, dynamic class; we'll work to keep it that way. Again, please check http://IST704.wikispaces.com regularly. It is a primary communication medium for the course serving as a portal for all most course materials. For this reason, it will change regularly as we progress through the semester. Class Format The course will consist of lectures, general discussion of pertinent topics, an individual case study discussion, and a team based software product research and presentation. Teams will be formed that will act as the catalyst for learning. I will provide greater detail on specific course elements at appropriate times in the semester. **Class Attendance and Participation****. **Each student brings to the group a unique blend of experience, insight, and personal background. Your active participation will contribute more than you realize to the success of this course. I appreciate that you'll have many demands on your time. I'll do my best to accommodate an occasional absence for valid reasons. I'd like each of you to do your best to attend every class meeting possible. Be prepared and ready to actively participate in each session. Your team will depend on you. As you’ll note below, I consider attendance, team contributions and postings to the course wiki in determining the grade you earn in this course. Online collaboration outside of class is highly encouraged. ** Database Product Research, Selection and Presentation ****. ** We'll ask teams of two or three students to research select and present a database project to the class. To successfully complete this project, teams will apply their knowledge about databases to map put the features and functionality of your proposed solution while identifying user needs. The purpose of the project is to develop your team’s understanding of how database management systems function in “real” environments. In addition to modeling your solution, your team is expected to become familiar with the software alternatives that are available (much like you would if you were working for a company) and then select one to work with. You will find vendors’ websites to be valuable sources of information in making your selection decision. A major consideration in selecting a software product is the availability of a version of the software that can be used in a hands-on class session with the class. You may want software that the class can actually play with (e.g., follow a case study to do an OLAP analysis) rather than simply view a “canned” demo. On many of the vendors’ websites, you will find downloadable, trial or evaluation copies of their software. You will normally need to register to use the software (a very simple process). The software that you download will typically be “crippled” in some way. For example, it may expire in 30 days or the amount of data that can be stored is limited. This should not pose a problem for your team. After you have modeled your data and selected the software that your team wants to work with, discuss the selection with your instructor to gain final approval. Then install and learn the software. Your objective should be to learn the capabilities and functionality of the software and to design a hands-on session for the class to use the software. Your team will have a full class session to make a presentation and to have the class use the software. Your team will essentially teach a class, covering the kind of software that you are working with, and leading them in a hands-on session. Try to make the class presentation interactive and incorporate hands-on activities whenever possible. In this way, every one in the class will experience working with the software. I reserve the right to review your choice of software to cut down the learning curve. The final design of the class session will be up to your team, but it is likely to include: After you have designed “your class,” discuss the design with your instructor for final approval for what you plan to do. **Database Topical Case study Research & Presentation.** Students, in teams of a size to be determined by class enrollment, will be assigned a case study to research in a database-related topic, then develop and guide a discussion of the case in class. These cases have been selected and aligned with certain topics in class. I'll provide detailed information early in the semester. You may also visit the course wiki for an extensive library of white papers. **Evaluation**. Graduate level studies are and should be demanding. You will be graded on your ability to successfully integrate and demonstrate knowledge of the material presented and assigned. Your ability to understand and apply concepts creatively and synergistically, as well as your ability to clarify ambiguous situations, are important considerations in the graduate grading process__. As a general rule, work meeting basic graduate requirements results in a grade of B. Performance that clearly exceeds requirements merits a grade of A__. Should work fail to meet graduate standards, lesser grades will be appropriate and recorded. The components of your final grade are shown in the table below. The examinations and individual project, because they focus directly on the key learning objectives, constitute the major portion of the cumulative grade. 
 * 1)  An overview of the data design including all data flow diagrams.
 * 2)  A short demo and justification for the software that your team has selected
 * 3)  Vendors and software products that are available in this space
 * 4)  Hands-on use of the software – if possible
 * 5)  Discussion of the database design and software chosen with the class (e.g., likes and dislikes)
 * Project #1 || In Class Presentation 1  || In Class Presentation 2  || Project #2  || Participation  ||
 * ||  ||   ||   || In class 5  ||
 * 25 || 15  || <span style="font-family: Cambria,serif;">15  || <span style="font-family: Cambria,serif;">25  || <span style="font-family: Cambria,serif;">Wiki 15  ||