Info Sys 422/722; ISyE 722 Computer Based Data Management Fall, 2010 1. Instructor: Rafael Lazimy Office: 4269 Grainger Phone #: 262-3950 E-mail: rlazimy@ bus.wisc.edu Office Hours: M, W 11:00-12:00 or by appointment 2. Class Schedule: 1:00-2:15 M, W, 1190 Grainger TA/Grader: Sean Ma Office Hours: 12-1 PM, M, W E-mail: ma29@wisc.edu 3. Texts: Required text: a. A reading package, available for purchase at the Business School Copy Center, 1220 Grainger. Books for reference: I. Database Design and Management Books: Hoffer, Prescott, and Topi, Modern Database management, Pearson/Prentice Hall, 2009 (9th edition). II. SQL Server 2005 Books: Petkovic, Microsoft SQL Server 2005: A Beginner s Guide, McGraw Hill/Osborne, 2006. Morrison, Morrison, Creating SQL Server 2005 Applications with Visual Studio, Pearson/Prentice Hall, 2007. 4. Objectives of the course: Databases are essential components of modern computer-based information systems. The general objective of Info-Sys 422/722/ISyE 722 is to help the student understand how to design and build databases for information systems applications, how to manipulate data in an information system environment, and how to build database applications. Specifically, the course focuses on three major parts: Data modeling and database analysis and design: Identifying the data and information requirements for information system applications, and creating a conceptual data model for these applications. Relational database design, including mapping a conceptual database model into a relational database design and normalization. Practical database technologies, including Structured Query Language (SQL), Oracle and SQL-Server 2005 database technologies, stored procedures, triggers, SQL Views, database administration with SQL. Students develop (in teams) comprehensive 1
database-driven applications for real-world companies in which they implement all the concepts and technologies they learn in the class, therefore obtain hands-on-experience. As such, this course will provide you with practical and valuable skills to build state-ofthe-art relational databases, work with them, and build information systems based on database technologies. Specific Topics/Learning Objectives: I. The context of database management: The database environment Levels of data representation, and the database design life cycle II. Conceptual data modeling: Elementary data modeling constructs Data modeling with the Entity-Relationship (E-R) model III. The database design process: Requirement definition: User views modeling Conceptual database design Relational database design IV. The relational database model: Relational database design Normalization V. Structured Query Language (SQL): Oracle SQL: SQL*Plus Creating, dropping, and altering tables Single-table queries Multiple-table queries VI. VII. VIII. Microsoft SQL Server 2005: Transact-SQL Using SQL in Applications: Oracle triggers, cursors, stored procedures, exceptions T-SQL Programming (SQL Extensions), Stored Procedures, User-Defined Functions, and Triggers in SQL Server 2005 SQL views Database administration with SQL: o Indexes o Database security o Data dictionary The Internet and database technologies: Client-server architectures Web-enabled client/server database applications 5. Grading and Assignments: The final grade will be based on the following: Midterm 1 (in mid semester): 20% Midterm 2 (during Finals week) 15% 2
Projects: 45% Homework: 20% DONE IN TEAMS MUST BE DONE INDIVIDUALLY! The purpose of the homework is to practice theory and concepts covered in the class and prepare you for the project work and the exams. Midterm 2 is not cumulative (it covers material not covered in Midterm 1). The schedule for the tests, projects, and homework assignments appear in the attached course schedule. 6. Project and Team Work: Teams of 3 students will be formed in the beginning of the course. Each team will work on two projects: A. Data Modeling and Database Design for Pine Valley Furniture. Pine Valley Furniture is a medium-size furniture manufacturing company. This case (included in the reading package) provides you with an opportunity to develop a comprehensive conceptual and a relational database system for a manufacturing company, including many business processes/operations. Based on the case description, your team is required to identify the database requirements of users (user view modeling), develop a conceptual database model, and map it into a relational database design. Detailed description of the assignments for this project is included in the reading B. Client-Server Database Application for a Real-World Company/Organization: This will be a semester-long project that will dominate your activities during this course. Each team will select a real-world company/organization, identify certain application areas, and perform business analysis, database design, and develop a database application for this business/organization. This project will provide you with the opportunity to apply all the concepts, methodologies, and information technologies you learn in this class in the context of a real-world business/organization. As such, the value of the project should be apparent. The project work will be divided into milestones. The milestones are as follows (the due date for each milestone report appears in the class schedule): 1. Project Proposal. After you submit a written project proposal, I will meet with each team and review the proposal. Project selection should be finalized within the first 2-3 weeks of the semester. 2. Milestone 1: Business Analysis and Systems Study. The purpose of this milestone is to gain a thorough understanding of your business application/organization and its information requirements, analyze problems and opportunities and their relationships to information requirements, and develop an information system plan for your application. Class presentation of Milestone 1: Each team will make a short presentation of its project to class. (Around week # 4.) 3. Milestone 2: Database Design. In this milestone you will develop a conceptual database model for your project (using E-R diagrams) and a relational database design. 3
I will meet with each team in my office and review your database design. In this meeting I will also review the scope of the proposed implementation of your project (Milestone 3). 4. Milestone 3: Implementation Design. In this milestone you will outline the scope of the implementation for your project. 5. Milestone 4: Prototype Database Application. In this final milestone of the project, you will implement a prototype of your system. (See below details about the technology you will use to create this application.) Class presentation of the final project: Each team will make a presentation of its final project to the class, including the implementation. (Last week of the semester.) The technology for creating the database application (Milestone 4). Your team will be required to develop a tiered, client/server implementation. You will use the following technologies in this project:.net Framework, Visual Studio 2008. Your system, therefore, should be form-based (i.e., the user-interface is form-based). You may use the Integrated Development Environment (IDE) in Visual Studio to design and create your system. Programming Language: you are free to use Visual Basic (VB), C# (C Sharp), or Java to write the code for implementing the user interface, business rules (business functionality), and database connectivity. Database Connectivity: The database will reside on a SQL Server 2005 database server that will execute database transactions, while your user interface and most of the business functionality will be executed on the client machine. (Information about the database server will be provided to you later in the semester.) You will use ADO.NET to create database connectivity and work with the remote database server. Server-Side Code: You will be required to implement several triggers and stored procedures that reside with your SQL Server database server. These triggers and stored procedures will execute certain business functionality on the database server rather than on the client machine. 7. Course Web Site: The Learn@UW-Madison course web site includes (among other things) the following information and services: On the Content page: o The course syllabus and schedule o The homework assignments o The project milestone requirements o The schedule for the Access tutorial, the Access database files, and the weekly Access assignments 4
o Past projects: Milestone reports of projects done in this course in previous semesters are included on this page; they should help you in doing your project work. DropBox: You are required to submit homework assignments and milestone reports electronically using the DropBox. Grades: Grades (for homework assignments, milestone reports, exams, etc) will be posted on the web site. 8. Class attendance It is mandatory to attend all classes. Not attending two or more classes will result in a penalty: If you otherwise deserve, say, a grade of AB but missed two classes, your grade will drop to B. Penalties will increase if you miss more than two classes. Of course, if you have special justification for not attending a class (for example, illness, family/personal emergencies) there will be no penalty. It is your responsibility to notify me of these circumstances. 9. Code of conduct Students are expected to adhere to the University and the School of Business student codes of conduct. 9. Miscellaneous: The amount of work involved in this class is above average. Managing your time properly and good team work is important for your success. The course will be a combination of lectures, class discussion, and computer work (possibly in the computer classroom). The projects will require a significant amount of work and time so it is suggested that you get started on them as soon as possible. Late submission of homework and project work is allowed only with a severe penalty. For each day that an assignment is late, you lose 20% of the points. Hence, after 5 days, your homework/project is worth nothing. Note that all homework, projects, and tests must be completed before you will be awarded a passing grade. Students should also understand fully that all assigned work is to be done individually, unless otherwise explicitly stated. Finally, students may be called on in class discussions to answer questions or present solution/analysis on the board. 10. Peer Evaluation: The prospect of working with teams carries with it the possibility that not all team members will pull their fair share of the load. For this reason, there will be anonymous peer evaluations at the end of the semester after the project is completed. Individual evaluations are the property of the instructor and will not be divulged to other team members - your confidentiality is assured! The average of the peer evaluation scores 5
given to each team member will be used as a weight in determining the member s grade on the project work. 11. The use of lap tops during the lectures is not encouraged. 6