Course Syllabus of ISM3113 Fall 2015

Transcription

1 Course Syllabus of ISM3113 Fall 2015 Professor Rob Totterdale, D.Sc., CITP General Information Course Number/CRN ISM 3113/CRN Course Title Systems Analysis and Design Semester/Year Fall 2015 Offering Lutgert College of Business (LCOB)/Information Systems and Operations Management (ISOM) College/Department Credit Hours 3 Meeting Room : LH 2209 Times/Location Start Date End Date Days Time Class Aug 20, 2015 Dec 3, 2015 T R 5:00pm 6:15pm Exam Dec 08, 2015 T 3:00pm 5:15pm Is this a DL Course? No, it is an on campus course. Method of Delivery Class meetings. Course URL (select ISM 3113 course and click Lessons ) Prerequisites ISM 3212 for level UG with min. grade of C and COP 3003 for level UG with min. grade of C or ISM 3232 for level UG with min. grade of C Instructor Information Instructor Rob Totterdale, D.Sc., CITP Office Location Lutgert Hall 3344 Phone Number E Mail Address rtotterdale@fgcu.edu Office Hours Mon 5:30 6:30pm Tues & Thurs 3pm 5pm or by appointment Important Note: As of this fall 2015, all faculty members are required to confirm a student's attendance for each course by the end of the first week of classes. Please complete the mandatory class survey in Canvas by Aug. 25. Course Information Description Systems concepts, structured methods, techniques, and computerized tools used in information systems analysis and design. Both procedural and object oriented analysis design approaches are covered. Students will work on a real life project to apply concepts and methods learned in class. (Fundamental computer programming knowledge required.) Teaching Philosophy /Approach OVEVIEW Upon completion of this course, the student will acquire a perspective of a business as an information system, knowledge of basic tools of systems analysis, and relevant experience in the application of these tools. Learning will be accomplished through both individual and group assignments. The major areas of focus in the course ( subject to modification) are as follows: 1. System development methods including waterfall and agile 2. Role of the business analyst 3. Requirements development (elicitation, understanding, documenting, validating) 4. Differences between package, custom, enhancement, outsourced, BPR, and agile projects 5. Design specifications, factors that influence design and best practices

2 6. Prototype development and presentation Students will learn about each of the above topics, and using tools such as SharePoint and Visio will gain experience learning how to gather, document, communicate, and share requirements. Having documented the functional and non functional requirements, students will develop a specification for a prototype that references broader system requirements. Using an iterative approach, students will be expected to refine the prototype and present their results at the end of the semester. Individually, students will complete a series of small assignments that will help to confirm their knowledge of the course content. Both a mid term and final exam will be given. GROUP PROJECT The group project will address the business needs of an actual small business. The class (groups) will have an opportunity to interact with the small business owner to identify business needs and will then develop specifications for a prototype to demonstrate the required business capabilities. SharePoint and Visio will be used to define the requirements for the business and to facilitate collaboration of team members. The business owner will be available periodically to answer questions and will participate in the evaluation of the final group projects. The best projects will receive the best grades! The small business that will participate needs a web presence to capture orders for products that they sell, an order cost estimator for one of the services they offer, background information on the various services and products they offer, links to social media, and exciting new offerings they plan to introduce that may require either venture capital and/or crowdsourcing. In addition to the web presence, other business functions will need to be addressed. (Small business participation is planned, but is subject to the availability of the owner. If the owner is unavailable, alternative steps for requirements gathering will be utilized). Key dates (tentative) see Canvas for assignments and class activities Aug. 20 First day of class Class and Group Project Overview Oct 8 Mid term exam Sept 7 Monday Holiday ( regular classes Sept 8 10) Sept 8 Group Project Outside participant ( tentative) Nov 30 Submission of group documentation and final prototype Dec 1 3 Group Presentations Dec 8 Final Exam Student Learning Outcomes Learning Objective Design an IT Solution Understand and apply systems analysis and design methods Utilize requirements elicitation techniques such as interviewing and benchmarking Define user classes, functional and non functional requirements Assessment Strategy Exams, class exercises, assignments

3 Utilize documentation and collaboration tools for communications Understand various design components including: data, process, dialog, interface, business rules, forms, report, and screens Create an IT Solution Develop specifications Develop and present a prototype for a business function Systems Thinking Understand the role of the business analyst Understand scope through an ecosystem map Understand interface and integration requirements Demonstrate production of scholarly work through: Prototype Group project Exam, Prototype Assignment writing skills critical thinking information literacy Classroom sessions will consist of lectures and open seminar type discussions. The student will be expected to incorporate the concepts of systems analysis in preparing project presentations and a prototype for a major business function(s). Students will demonstrate their knowledge through exams, class participation, homework assignments, and by creating and presenting a formal design of a business information system. ISM 4332 Project and QA and ISM 4154 System Integration Strategies will give students further practice designing, implementing, testing, and integrating such applications in cross functional systems. Required Materials Required textbook: Software Requirements, Third Edition, Wiegers and Beatty, Microsoft Press, ISBN 13: Software ( you do not need to buy access will be provided to you) Collaboration Software (Microsoft SharePoint) Access will be provided to a cloud based version of SharePoint (Office 365) for collaboration and management of system analysis and design content. Microsoft Visio (documentation tool) Cloud Services and Wordpress (tentative) Other Reference (optional available in library) Krug, S. (2005). Don't Make Me Think: A Common Sense Approach to Web Usability, 2nd Edition Other Reference and Reading Materials will be provided on Canvas

4 Grading Policy Graded Learning Activities/Assignments in this course: Participation, attitude, and attendance 5% Assignments 40% Project 25% Exams 30% Grading Scale % A 80 89% B 70 79% C 60 69% D 0 59% F Attendance Policy + and grades may be given to borderline students at the discretion of the instructor Students are expected to attend every class session. It is the student's responsibility to get course notes from fellow students should they have to miss a class. Since this is a three credit course you should expect to spend between 6 and 9 hours outside of class each week on readings, projects, and homework. Policy regarding missed exams and assignment completion deadlines Per policy, no make ups for missed exams are administered (except for authorized and excused absences specified in the university catalog). A student who seeks an authorized or excused absence must submit documentation (such as a physician s note) to the instructor in a timely manner. See the university catalog for more information. No late assignments will be accepted for any reasons except the authorized and excused absences specified in the university catalog. A student who seeks an authorized or excused absence must submit documentation (such as a physician s note) to the instructor in a timely manner. See the university catalog for more information. Unfortunately, "dropped by the University for not paying the full tuition" is not an authorized and excused absence as specified in the university catalog. An emergency situation such as unavailability of or inaccessibility to CANVAS due to network problems will be considered by the instructor on a case by case basis. Students must submit documentation (such as a screenshot of error messages) to the instructor in a timely manner. Policies regarding inclass use of cell phones, PDAs, laptops, and other personal electronic devices Statement on e mail usage in Eagle mail and/or Canvas Last Day to withdrawal Disclaimer Cell phones must be turned off before coming to class. Bringing food or drink to class or office hours is strictly prohibited. Canvas will be used to submit assignments, and to post course notes. Eagle mail will be used for correspondence. (SharePoint will also be used for collaboration, sharing and storing of project content.) Nov 03 is the last day to withdrawal without academic penalty. Assignments, schedules & due dates, instructions, and other course information presented in CANVAS are integral components of the course material and are hereby incorporated as part of this syllabus. The instructor reserves the right to change the schedule and due dates. Any changes will be reflected as necessary in Canvas. The availability and structure of certain assignments are subject to technology availability.

5 University Statements Academic Behavior Standards and Academic Dishonesty All students are expected to demonstrate honesty in their academic pursuits. The university policies regarding issues of honesty can be found in the FGCU Student Guidebook under the Student Code of Conduct and Policies and Procedures sections. All students are expected to study this document which outlines their responsibilities and consequences for violations of the policy. The FGCU Student Guidebook is available online at Sanctions for academic dishonesty may include receiving a F in this course FGCU may impose additional penalties. Any incidents of academic dishonesty may be referred to the FGCU Office of Judicial Affairs. Please look up the definition of plagiarism it includes copying something off the Internet & submitting it as your own work. Some examples of what is NOT OK to do: Working with another student & turning in the same work (e.g. spreadsheet, database, etc). ing or posting your work to let someone else just see how you did it. Copying someone s assignment or copying something from a book or the Internet. Giving or receiving help from someone (in person, on line or on the phone) during an online test. Telling someone else what is on a test. Examples of what is OK: Discussing how to approach an assignment with another student. Showing someone where they might have made a mistake on an assignment. Asking the professor for help. Disability Accommodations Services Florida Gulf Coast University, in accordance with the Americans with Disabilities Act and the university s guiding principles, will provide classroom and academic accommodations to students with documented disabilities. If you need to request an accommodation in this class due to a disability, or you suspect that your academic performance is affected by a disability, please see me or contact the Office of Adaptive Services. The Office of Adaptive Services is located in the Wellness Building. The phone number is or Video Phone (VP) Student Observance of Religious Holidays All students at Florida Gulf Coast University have a right to expect that the University will reasonably accommodate their religious observances, practices, and beliefs. Students, upon prior notification to their instructors, shall be excused from class or other scheduled academic activity to observe a religious holy day of their faith. Students shall be permitted a reasonable amount of time to make up the material or activities covered in their absence. Students shall not be penalized due to absence from class or other scheduled academic activity because of religious observances. Where practicable, major examinations, major assignments, and University ceremonies will not be scheduled on a major religious holy day. A student who is to be excused from class for a religious observance is not required to provide a second party certification of the reason for the absence. How To Log Into the Course in Canvas o Activate your FGCU Eagl Account (if you have not done this yet). Your FGCU Eagl account MUST be activated to log in to Canvas. If you are a first time student, you will need your PIN and Eagle ID, both of which are assigned at registration. o If you don t know your PIN, you will need to go to the Registrar's office to retrieve it. o To activate your account, visit o Log in to Canvas at You need to use FGCU Eagl account and password to log in. o Click ISM3113 Systems Analysis and Design CRN 80681