Data Management.doc
Upcoming SlideShare
Loading in...5
×
 

Data Management.doc

on

  • 623 views

 

Statistics

Views

Total Views
623
Views on SlideShare
623
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Data Management.doc Data Management.doc Document Transcript

    • KENNESAW STATE UNIVERSITY UNDERGRADUATE PROPOSAL New Course (NOT General Education) I. Proposed Information Course Prefix and Number: _____________IS 2080_______ Course Title: ___________ Data Management ___________________________ Credit Hours (format should be # - # - #): ____3-0-3_____ Prerequisites: ______________IS 2101 or Department Approval_______________ (Prerequisites are courses or requirements that non-negotiable and must be successfully completed by any student before enrolling in the course or program under consideration. Corequisites are courses that can be taken before or in the same semester as the course under consideration. Courses at the upper-division level will require lower-division competencies or prerequisites.) Course Description for the Catalog: This course introduces the student to the properties, logic, design, implementation, and access to business databases. Particular emphasis is placed on the relational approach to database management and processing, which focuses more on the logical nature of a database than its physical characteristics. Relational database programming assignments are drawn from the fields of business and government. II. Justification for Course A. Explain assessment findings which led to course development. Changes in the curriculum. B. Explain for Prerequisites: 1. What is the substance of content in each prerequisite that commands its inclusion as a prerequisite to the proposed course? IS 2101 relevant content areas include why and how information systems are used in real-world applications. This pre-requisite gives students the big picture to understand data management needs. 2. What is the desired sequence of prerequisites? IS 2101 à IS 2080 à IS 3540 à IS 4880 3. What is the rationale for requiring the above sequence of prerequisites? The sequence provides students the requisite skill to develop business applications. 4. How often are the required prerequisites offered?
    • The pre-requisites will be offered twice a year. C. Give any other justification for the course. III. Additional Information A. Where does this course fit sequentially and philosophically within the program of study. It fits in the lower major required courses. B. What efforts have been made to ensure that this course does not duplicate the content of other college courses with similar titles, purposes, or content? This course has unique database foundation using Microsoft Access and is integrated into other courses in the IS program. C. Where will the course be located in the program (elective, required in Area F, required or elective for the major)? Indicate and justify its placement in the curriculum. This course will be located as a major required course. D. How often will this course be offered? This course will be offered twice a year. E. All sections of the course will be taught with the understanding that the following apply: 1. Purpose of the Course The purpose of this course is to provide students with the fundamental knowledge and skills about managing data from databases and other data stores like spreadsheets. 2. Objectives of the Course To use data to stay competitive in a changing business environment and understand the role of databases including database modeling, design, development and implementation. The course teaches how to build, model and administer a database. In addition to that the course covers the main concepts of data warehousing, data integration, data mining, and data security and privacy. The relational approach to database management is emphasized. In-class assignments and related homework projects accentuate hands on development of the logical and physical data model. MS Access will be used as the primary pedagogical software in class. 3. Course Content The following content will be covered by this course: 1. Data modeling 2. Normalization
    • 3. Queries 4. Forms 5. Reports, macros, and switchboard 6. Data administration F. What instructional methodologies will be incorporated into the course to stimulate group process, writing skills, multiculturalism, and educational outcomes? Group project building, populating, and querying a database using teams with a real client. Lectures and labs: Lectures will focus on theoretical concepts illustrated by simple examples. The text, lecture notes and other lecture material will provide a knowledge base that students can use in assignments and course projects. Several class sessions will be held in Raley computer labs. Dates will be announced later. Examinations: There will be two knowledge-based classroom examinations, worth a total of 25% of your course grade. The exams are short answer and problems. They will include both conceptual questions and require the ability to program in query code, write input forms and output reports, normalize data tables, understand relational database and inferential integrity, for example. Students arriving late for exams will have less time to complete the exam. Multiple versions of each examination may be used within a class and between course sections. Because of the potential for cheating, all cell phones, pagers, PDAs, computers or any electronic devices must be turned off and put out of sight. No electronic dictionaries may be used during the exams (only pre-approved paper dictionaries are allowed). If you miss the mid-semester exam for a valid reason, you must take a comprehensive final examination. You can make-up the final exam only for the most serious emergencies. Exercises and in-class assignments: There will be three out of class team projects using Visual Analyst, MS Access, and SQL. Completion of each project will require you to spend a great deal of time on a computer. Please plan accordingly. All project deliverables are due at the time and date indicated in the schedule below. There are five in class assignments that will be announced at the beginning of the appropriate class session. The assignments will enable students and the instructor to ascertain how well a topic was understood, provide hands on experience on a topic and demonstrate individual preparedness for a class. There will be no opportunity to retake in class assignments except in cases discussed with the course instructor beforehand or other legitimate and documented reasons. Group Project: There will be one group project for a profit or non-profit organization in the local community or within 15 minutes from KSU. You will need to ascertain what the client needs to have done, develop the logical specifications (blueprints) for the new system with applications, get approvals from both the client and manager (professor), build the system and then show the database prototype to the client and get final signoff. There is no Internet component to this project. PROJECT DELIVERABLES
    • The group project will include a class demonstration of a running prototype to be demonstrated throughout the semester. The following deliverables need to be addressed by all of the database teams: 1. Project management template outlining details 2. Requirements analysis (in class led by professor) 3. Infrastructure plan for project 4. Database blue print: data model (conceptual) 5. Logical data models (ERD set) 6. Normalized database 7. Implemented database design (SQL) 8. Populated database Forms in Access 9. Reports in Access (SQL Joins) 10. Switchboard (macro groups) 11. User documentation for use of the database 12. Recommendations for future database functionality TEAMS All of the teams will work on the same project. All project teams will coordinate their efforts weekly via the team’s project manager. Each person in the class must sign up for three teams in preference order based solely upon expertise. The teams will have members in other classes. Selection of teams will be made in the first week based upon self-reported competencies. Members of the class will rank the teams they want to serve on; project managers will be selected by the manager (professor). Class members should be certain of their expertise in one of the four areas and therefore can accomplish what the team needs to. TEAM TYPES Each member of the class will work in one of six (6) project teams: • Data entity team – responsible for the conceptual and logical design of the data models, relationships, normalization, attributes. • Database team –responsible for building the database, populating the database, managing keys, implementing normalization • Forms team – responsible for writing all forms against the data base, writing input fields to related tables (minimum 10 forms per system). • Reports team – responsible for writing system reports for the project (minimum of 10 reports per system). • Switchboard/macros team – responsible for building the user interface for the client on their local system. • Infrastructure team – responsible for the hardware, operating system, managing files, implementing the local development project, writing the final documentation PROJECT MANAGEMENT Each team will have a project manager. All groups are responsible for their own project management and all groups for the strategy and success of the entire project. Every week, project managers are to turn in a Progress Report covering each week’s activities on Monday, no later than 12 noon. Time sheets and an updated project work plan are to be attached to the Progress Report. Each team will have a project manager that will report to the manager (professor) each
    • week the progress of the team. Project managers are required to meet weekly and work out all project details. GROUP MATERIALS TURN-IN POLICY All group (team) project materials for this class must be turned both in hard copy and on CD showing cumulative project-book, work-in-progress from the start of the semester until current. All CASE tool materials must be accompanied with a hard copy of the relevant updated repository objects. CLIENT MEETINGS / CLIENT CONTACT Every group will be able to meet a client onsite at least two time a semester. All contact to and from the client will be generated ONLY by project managers. Group Presentations: Each team should plan for between 10 – 20 minute presentations (depending upon the presentation) with each team member presenting, although not necessarily consecutively or sequentially. All teams must generate a series of classroom questions and comments to be successful. Each group and student will receive feedback on each oral presentation made in class. When you are presenting to the client, you are expected to be dressed in business formal attire. Inappropriate dress will lower the presentation grade. Teams will be assessed during their presentations on the following characteristics: • Ability to generate and capture audience interest • Smoothness and energy of presenters • Flow of presentation material throughout overall presentation • Relevance and comprehensiveness of concepts (content) • Creativity in the design of the presentation (video of relevant products and services that are similar in nature) Class Contribution: It is expected that students will attend every class that meets and every client meeting. If attendance is not possible, it is the student’s responsibility to let the professor, client, and/or team members know. You will not get a grade for attendance in class, but to contributing to class discussion. Contributing to class discussions includes asking questions, responding to questions posed by the professor or a fellow student, constructively evaluating and providing feedback on other teams' projects, and sharing knowledge or experiences related to the topic at hand. You have to earn each of the ten (10) points for your grade by TALKING in class. For example, if there are 30 classes and you contribute in only 6 classes (20%) you will get only 2 / 10 points or a drop of 2 letter grades. Likewise, it is expected that students will attend team meetings and get back to team members by email, cell phone, AIM, text messaging or other communication technique in the same day. Failure to participate in team meetings and class sessions will result in a grade reduction of one FULL letter grade (i.e. from B to C). G. Outline the plan for continuous course assessment. What are the department, school, college, or professional standards which will be used for the assessment? How will it be determined that the course is current, meeting the educational needs of students and responsive to
    • educational standards? How often will the course assessment be done by the department? Continuous course assessment will be done using student end of semester evaluation, regular evaluation by program curriculum committee, and annual Assurance of Learning evaluation. H. Enclose a course syllabus (optional format described at the end of this document) IV. Resources and Funding Required A. What resources will be redirected to accommodate this course? N/A B. Explain what items will cause additional cost to the department/school/college Personnel Computer Technology Library resources Equipment Space
    • IS 2080: Data Management Instructor: Solomon Negash Office Number: CL 3013 Office Hours: TBD Phone: 770-420-4312 Email snegash@kennesaw.edu Course Description: This course will provide students with the knowledge and skills needed to develop applications in a development environment. It covers .NET and .NET 2.0 technologies. This is the first course in the .NET development platform. Students will learn how to develop applications using Microsoft Visual Studio .NET development environment. Prerequisites: IS 2101 Textbooks: • Main text book: Frost, R., Day, J., van Slyke C., Database Design and Development: A visual Approach, Pearson Education, 2006. • Supplemental material and recommended books for self-study are to be announced in class. • Software: Microsoft Access is the primary program that will be used for designing and administrating database. VisibleAnalyst will be used for data modeling. XLminer will be used for the business intelligence part of the course. The 90-day trial version is available at the following website: http://www.resample.com/xlminer/download.shtml. Learning Objectives: To use data to stay competitive in a changing business environment and understand the role of databases including database modeling, design, development and implementation. The course teaches how to build, model and administer a database. In addition to that the course covers the main concepts of data warehousing, data integration, data mining, and data security and privacy. The relational approach to database management is emphasized. In-class assignments and related homework projects accentuate hands on development of the logical and physical data model. MS Access will be used as the primary pedagogical software in class and introduction to SQL Server will also be included.
    • Learning Outcomes: As a result of completing this course, students will be able to: • Describe and discuss the role of data and information in society • Learn the mechanism of data collection, storage and database administration and security • Analyze data needs for the systems-to-be and operational feasibility of it • Perform data modeling using Entity Relationship (ER) diagrams • Understand and use SQL and SQL syntax • Design and implement databases in Access using SQL • Understand the special needs of multi-user database processing and techniques for controlling the consequences of concurrent data access • Understand the nature of data warehouses • Perform simple knowledge discovery using data mining techniques Grading: The schedule and deliverables in this syllabus will change because we are working on a real project. A revised syllabus will be issued at the course midpoint. Activity Each % Examinations 25% Mid-semester examination 10% Final examination 15% Individual Assignments 25% Exercises Data modeling 5% Normalization 5% Access SQL 5% In-class assignments (5 @ 2% each) 10% Group Work * 40% Group Project Deliverables 30% Group Presentation 10% Class Contribution 10% Total 100% *This score is determined mostly by the manager (professor) with input from the project manager and the client. This score is an aggregate of the total project score at the end of the semester based upon all groups presenting.
    • Lectures and labs: Lectures will focus on theoretical concepts illustrated by simple examples. The text, lecture notes and other lecture material will provide a knowledge base that students can use in assignments and course projects. Examinations: There will be two knowledge-based classroom examinations, worth a total of 25% of your course grade. The exams are short answer and problems. They will include both conceptual questions and require the ability to program in query code, write input forms and output reports, normalize data tables, understand relational database and inferential integrity, for example. Students arriving late for exams will have less time to complete the exam. Multiple versions of each examination may be used within a class and between course sections. Because of the potential for cheating, all cell phones, pagers, PDAs, computers or any electronic devices must be turned off and put out of sight. No electronic dictionaries may be used during the exams (only pre-approved paper dictionaries are allowed). If you miss the mid-semester exam for a valid reason, you must take a comprehensive final examination. You can make-up the final exam only for the most serious emergencies. Exercises and in-class assignments: There will be three out of class team projects using Visual Analyst, MS Access, and SQL. Completion of each project will require you to spend a great deal of time on a computer. Please plan accordingly. All project deliverables are due at the time and date indicated in the schedule below. There are five in class assignments that will be announced at the beginning of the appropriate class session. The assignments will enable students and the instructor to ascertain how well a topic was understood, provide hands on experience on a topic and demonstrate individual preparedness for a class. There will be no opportunity to retake in class assignments except in cases discussed with the course instructor beforehand or other legitimate and documented reasons. Group Project: There will be one group project for a profit or non-profit organization in the local community or within 15 minutes from KSU. You will need to ascertain what the client needs to have done, develop the logical specifications (blueprints) for the new system with applications, get approvals from both the client and manager (professor), build the system and then show the database prototype to the client and get final signoff. There is no Internet component to this project. PROJECT DELIVERABLES The group project will include a class demonstration of a running prototype to be demonstrated throughout the semester. The following deliverables need to be addressed by all of the database teams: 1. Project management template outlining details 2. Requirements analysis (in class led by professor) 3. Infrastructure plan for project 4. Database blue print: data model (conceptual) 5. Logical data models (ERD set) 6. Normalized database
    • 7. Implemented database design (SQL) 8. Populated database Forms in Access 9. Reports in Access (SQL Joins) 10. Switchboard (macro groups) 11. User documentation for use of the database 12. Recommendations for future database functionality TEAMS All of the teams will work on the same project. All project teams will coordinate their efforts weekly via the team’s project manager. Each person in the class must sign up for three teams in preference order based solely upon expertise. The teams will have members in other classes. Selection of teams will be made in the first week based upon self-reported competencies. Members of the class will rank the teams they want to serve on; project managers will be selected by the manager (professor). Class members should be certain of their expertise in one of the four areas and therefore can accomplish what the team needs to. TEAM TYPES Each member of the class will work in one of six (6) project teams: • Data entity team – responsible for the conceptual and logical design of the data models, relationships, normalization, attributes. • Database team –responsible for building the database, populating the database, managing keys, implementing normalization • Forms team – responsible for writing all forms against the data base, writing input fields to related tables (minimum 10 forms per system). • Reports team – responsible for writing system reports for the project (minimum of 10 reports per system). • Switchboard/macros team – responsible for building the user interface for the client on their local system. • Infrastructure team – responsible for the hardware, operating system, managing files, implementing the local development project, writing the final documentation PROJECT MANAGEMENT Each team will have a project manager. All groups are responsible for their own project management and all groups for the strategy and success of the entire project. Every week, project managers are to turn in a Progress Report covering each week’s activities on Monday, no later than 12 noon. Time sheets and an updated project work plan are to be attached to the Progress Report. Each team will have a project manager that will report to the manager (professor) each week the progress of the team. Project managers are required to meet weekly and work out all project details. GROUP MATERIALS TURN-IN POLICY All group (team) project materials for this class must be turned both in hard copy and on CD showing cumulative project-book, work-in-progress from the start of the semester until current. All CASE tool materials must be accompanied with a hard copy of the relevant updated repository objects.
    • CLIENT MEETINGS / CLIENT CONTACT Every group will be able to meet a client onsite at least two time a semester. All contact to and from the client will be generated ONLY by project managers. Group Presentations: Each team should plan for between 10 – 20 minute presentations (depending upon the presentation) with each team member presenting, although not necessarily consecutively or sequentially. All teams must generate a series of classroom questions and comments to be successful. Each group and student will receive feedback on each oral presentation made in class. When you are presenting to the client, you are expected to be dressed in business formal attire. Inappropriate dress will lower the presentation grade. Teams will be assessed during their presentations on the following characteristics: • Ability to generate and capture audience interest • Smoothness and energy of presenters • Flow of presentation material throughout overall presentation • Relevance and comprehensiveness of concepts (content) • Creativity in the design of the presentation (video of relevant products and services that are similar in nature) Class Contribution: It is expected that students will attend every class that meets and every client meeting. If attendance is not possible, it is the student’s responsibility to let the professor, client, and/or team members know. You will not get a grade for attendance in class, but to contributing to class discussion. Contributing to class discussions includes asking questions, responding to questions posed by the professor or a fellow student, constructively evaluating and providing feedback on other teams' projects, and sharing knowledge or experiences related to the topic at hand. You have to earn each of the ten (10) points for your grade by TALKING in class. For example, if there are 30 classes and you contribute in only 6 classes (20%) you will get only 2 / 10 points or a drop of 2 letter grades. Likewise, it is expected that students will attend team meetings and get back to team members by email, cell phone, AIM, text messaging or other communication technique in the same day. Failure to participate in team meetings and class sessions will result in a grade reduction of one FULL letter grade (i.e. from B to C). Assessment and Grade Evaluation: Individual assignments 25% A 90% - 100% Group work 40% B 80% - 89% Class contribution 10 C 70% - 79% Examinations 25% D 60% - 69% Course Schedule (Tentative, subject to change): Project Other Date Topic due due INTRODUCTION
    • Course introduction and syllabus overview Data vs. Information. Database vocabulary, concepts and DBMSs. Different storage systems. Intro to Access SQL DATA MODELING Introduction to data modeling. Data modeling with data flows and Entity Relationship diagrams ERD in Visible Analyst (VA) Introduction of a Final Project and building a model in VA Overview of ER model for Final Project NORMALIZATION Transforming data models into database design: develop data dictionary and attribute list in Access Relational Model and Normalization Designing database for minimum cardinality in Access. Referential integrity actions Building a normalized database. Importing tables QUERIES SQL for database construction: DDL, DML and Joins SQL for database construction: using SQL in Access Database design: developing Access forms Database design: developing Access forms for Final Project. FORMS Populating database via SQL and Access forms. Populating database via forms. Midterm exam review. Midterm Exam REPORTS, MACROS, AND SWITCHBOARD Creating views and reports. Additional SQL statements/queries Database design: developing Access reports Macros in Access. Switchboard for Final Project Delivering a database to a client. Switchboard. Accessing Access database via Internet DATA ADMINISTRATION Database redesign: analyzing existing database, changing properties and cardinalities of the relationships Database administration and security in Access Final projects discussion. Prep for final exam Business Intelligence: data mining and reporting Final Examination Review Final Presentation and Final Report @ KSU with Client Final exam Academic honesty statement Every KSU student is responsible for upholding the provisions of the Student Code of Conduct, as published in the Undergraduate and Graduate Catalogs. Section II of the Student Code of Conduct addresses the University's policy on academic honesty, including provisions regarding plagiarism and cheating, unauthorized access to University materials, misrepresentation/falsification of University records or academic work, malicious removal,
    • retention, or destruction of library materials, malicious/intentional misuse of computer facilities and/or services, and misuse of student identification cards. Incidents of alleged academic misconduct will be handled through the established procedures of the University Judiciary Program, which includes either an "informal" resolution by a faculty member, resulting in a grade adjustment, or a formal hearing procedure, which may subject a student to the Code of Conduct's minimum one semester suspension requirement. Students are encouraged to study together and to work together on class assignments and lab exercises; however, the provisions of the STUDENT CONDUCT REGULATIONS, II. Academic Honesty, KSC Undergraduate Catalog will be strictly enforced in this class. Frequently students will be provided with “take-home” exams or exercises. It is the student’s responsibility to ensure they fully understand to what extent they may collaborate or discuss content with other students. No exam work may be performed with the assistance of others or outside material unless specifically instructed as permissible. If an exam or assignment is designated “no outside assistance” this includes, but is not limited to, peers, books, publications, the Internet and the WWW. If a student is instructed to provide citations for sources, proper use of citation support is expected. Additional information can be found at the American Psychology Association (APA) website: http://www.apa.org/journals/webref.html
    • Acknowledgment and Acceptance of Academic Integrity Statement: In any academic community, certain standards and ethical behavior are required to ensure the unhindered pursuit of knowledge and the free exchange of ideas. Academic honesty means that you respect the right of other individuals to express their views and opinions, and that you, as a student, not engage in plagiarism, cheating, illegal access, misuse or destruction of college property, or falsification of college records or academic work. As a member of the Kennesaw State University academic community you are expected to adhere to these ethical standards. You are expected to read, understand and follow the code of conduct as outlined in the KSU graduate and undergraduate catalogs. You need to be aware that if you are found guilty of violating these standards you will be subject to certain penalties as outlined in the college judiciary procedures. These penalties include permanent expulsion from KSU. Read the Academic Integrity Statement and then sign and date in the space below. You are required to abide by these ethical standards while you are a student at KSU. Your signature indicates that you understand the ethical standards expected of you in this academic community, and that you understand the consequences of violating these standards. ________________________________ ________________________________ Course Name Instructor Name Print Name Student ID Number Signature Date ________________________________ email
    • Attendance Policy Class attendance: Regular attendance is strongly recommended. If an emergency arises, contact professor prior to class time via email or phone. If you are absent for excusable emergency you have to bring proof to avoid academic penalty. For example, paper work indicating doctor’s visit. Make-up work*: Assignments; late assignments accrue 20% penalty for each late day. No late quizzes. No late project presentations. Exams; no make-up exams are given. If an emergency arises, and an absence is excused, then the student may take a cumulative final exam in its place. *Assignments, projects, and quizzes can be submitted anytime before the due date. Therefore, no emergency excuses are accepted. Reference/Bibliography N/A
    • V. COURSE MASTER FORM This form will be completed by the requesting department and will be sent to the Office of the Registrar once the course has been approved by the Office of the President. The form is required for all new courses. DISCIPLINE: _Information Systems_____________________ COURSE NUMBER: ___IS 2080______________________ COURSE TITLE FOR LABEL: __Data Management___________________ (Note: Limit 30 spaces) CLASS-LAB-CREDIT HOURS: __3-0-3__________ Approval, Effective Semester: __Summer 2008__________ Grades Allowed (Regular or S/U): __Regular___________ If course used to satisfy CPC, what areas? ___Major Required_____________________________ Learning Support Programs courses which are required as prerequisites: ______IS 2101 or Department Approval_____ APPROVED: _______________________________________________________________________ Vice President for Academic Affairs or Designee
    • KENNESAW STATE UNIVERSITY UNDERGRADUATE PROPOSAL New Course (NOT General Education) Course Prefix and Number: ___IS 2080__________________________ Responsible Department: ____Computer Science and Information Systems_______ Proposed Effective Date: ____Summer 2008________________________ Signature Page Submitted by: ___Solomon Negash___ Date: Name 12/03/2007 ___ Approved ___ Not Approved _____________________________ Department Curriculum Committee, Date ___ Approved ___ Not Approved _____________________________ General Education Council*, Date ___ Approved ___ Not Approved _____________________________ Professional Teacher Education Unit Program Area*, Date ___ Approved ___ Not Approved _____________________________ Department Chair, Date ___ Approved ___ Not Approved _____________________________ College/School Curriculum Committee AND/OR Teacher Education Council*, Date ___ Approved ___ Not Approved _____________________________ College/School Dean, Date ___ Approved ___ Not Approved _____________________________ Undergraduate Policies and Curriculum Committee, Date ___ Approved ___ Not Approved _____________________________ Dean of Undergraduate & University Studies, Date *For curriculum proposals involving General Education courses, there should be collaboration by the Department Curriculum Committee and the General Education Council. For Teacher Preparation proposals, there should be collaboration by the Department Curriculum Committee, the Professional Teacher Education Unit (PTEU) Program Area Committee, the Teacher Education Council, and the College/School Curriculum Committee. Form updated December 2, 2004.