IS 495: Information Systems Practicum (AKA Information Systems Capstone Course) Syllabus Class Meeting Hours: One-on-one meetings with me are scheduled by each student Class Meeting Location: Kunsela Hall Room C120 Instructor: Christopher W. Urban How to Address Me (in both conversation and in writing): Mr. Urban, Professor Urban, Chris How Not to Address Me: Urban (using my last name only is considered unprofessional and rude) Office Location: Kunsela Hall Room C120 E-mail: urbanc@cs.sunyit.edu Telephone: 792-7229 Web Page: www.cs.sunyit.edu/~urbanc Office Hours: www.cs.sunyit.edu/~urbanc/oh.htm Required Textbooks: None Course Description: This is primarily a project-oriented course. IS 495 is designed to give senior-year students an opportunity to develop and manage an information systems project. Ideally, students shall draw upon their Computer Information Systems Program coursework to complete the project. Students should use their “personal network of contacts” to find a real-world project in the public or private sector; students shall complete these projects with little supervision from me. Project management by each student is an integral part of the course experience. A project proposal that includes scope, milestones, and deliverables is developed at the beginning of the course. Progress reports and a final oral and written presentation will complete the capstone course experience. Projects should focus on one aspect of Computer Information Systems such as systems analysis and design, data base management, telecommunications, electronic commerce, security, project management, expert systems, or management of information systems. Students are evaluated by their project deliverables. This course should be taken in the final semester of a student's program of study. Course Objectives: The goal of IS 495 is to have students demonstrate the integration and application of the major concepts of the SUNYIT Computer Information Systems Program. By accomplishing this goal, students demonstrate that they are ready for positions that use information technology to develop computer-based systems that support organizations. Learning Outcomes: Students completing IS 495 will be able to: coordinate interdependent tasks and resolve minor project and personnel difficulties. produce deliverables that are free from errors and convey complete and relevant information while successfully addressing project goals as defined in the statement of work. engage external stakeholders for information, knowledge, and support. translate broad goals and objectives into measurable tasks and deliverables. Time Requirements: Each student should spend 80 – 90 hours during the semester on IS 495. Log: Each student develop and maintain a log of the time spent on their IS 495 project. Meetings With Me: A timetable shall be established at the beginning of the course to meet with me to periodically (every two weeks) to discuss your project status and progress. Project Proposal: Each student shall submit project proposal that includes scope, milestones and deliverables. This proposal is due to me via e-mail no later than noon on Friday, February 5, 2016. I will reply (approve/disapprove) project proposals by 8 AM on Monday, February 8, 2016. Disapproved projects must be resubmitted by Friday, February 11, 2016. Project Proposal Format: Since the nature of the project will vary from one student to another, the following is provided as a generic guideline. If you have specific questions, discuss them with me. The project proposal must include the following components: 1. Project title. 2. Scope of project, the project purpose, problem at hand, project goals, project significance, anticipated outcomes, and any limitations. 3. Explain how the proposed project fits with the SUNY Poly Computer Information Systems Program. 4. Timeline with tentative deliverables (this table must be updated periodically as you progress with your work). Final IS 495 Project Submission Format: Each student shall write a paper that is approximately 13 - 15 pages in length; this paper is due no later than Friday, April 22, 2016. The Final IS 495 Project Submission Format shall include the items listed below. (Note 1: some projects may not require all the items listed below and some project may require other items. If source-code is part of the projects, that source code should be included as an Appendix. Note 2: a source-code appendix does not contribute to the 10 - 15 page length of the paper.) PRELIMINARIES Title Page Executive Summary / Abstract Table of Contents List of Figures, List of Tables, List of Notations CHAPTER I Project Context Purpose and Description Objective of the Project Scope and Limitations Introduction CHAPTER II Review of Related Literature CHAPTER III Project Plan Data Gathering Procedures Source of Data Software Model/ Paradigm Methodology CHAPTER IV Requirements Analysis Requirements Documentation Design of Software, Product, and Process Development and Testing Description of the Prototype Implementation Plan Implementation Results Results and Discussion CHAPTER V Summary Conclusions and Recommendations Summary, Conclusion and Recommendations APPENDICES (as appropriate) Only Relevant Source Code Evaluation Tool or Test Documents Sample input/output/reports User Guide Process/Data/Information Flow of the Project Poster (required for all projects) Final IS 495 Project Presentation: Each student shall develop and deliver a 10-minute presentation for his/her project; this presentation shall utilize PowerPoint slides. All presentations are tentatively scheduled for Friday, May 1, 2015. E-Mail Communication With Me: All e-mail communications with me for IS 495 shall use this subject line: IS 495 / Spring 2016 / XXXXXX YYYYYYY (replace the X’s at left with your first name and replace the Y’s with your last name). Evaluation and Grading: I will use the following criteria for grading. Grade of A: Work demonstrates a clear understanding of the material, but also a superior ability to utilize that material. All criteria are met. The student’s work goes beyond the task and contains additional, unexpected or outstanding features. Grade of B: Work demonstrates a good understanding of the material, and utilizes the material well. The student meets the assignment criteria, with few errors or omissions. Grade of C: Work has a few significant flaws or shortcomings or may not address criteria or may not accomplish what was stated in the proposal. Grade of D: Work has a many significant flaws or shortcomings or may not address criteria or may not accomplish what was stated in the proposal. Grade of F: Work that is incomplete, inappropriate and/or shows little or no comprehension of the project requirements. The course will be letter graded. A student’s final grade will depend on the quality of the project components. Initial Project proposal: 15% Periodic (fortnightly) updates: 25% Final Project Report Submission and Presentation: 60% END END END END