MIS 34068-002 Spring 2013 Polites
MIS 34068: Systems Analysis and Design
Spring Semester 2013
Section 002 – CRN 15531
Tuesday / Thursday – 12:30 to 1:45 PM
Classroom: BSA 210
Instructor
Greta L. Polites
Assistant Professor
Department of Management & Information Systems
College of Business Administration
Email: gpolites@kent.edu (include “MIS 34068-002” in the subject line)
Phone: (330) 672-1166 (office)
Office: BSA A406
Office Hours: Tues/Thurs 10 AM – 12:30 PM, and by appointment
Course Web Site: BlackBoard
Course Description
This course introduces students to the methods, tools, and techniques used to analyze and develop information systems in organizations today. It can thus be viewed as the cornerstone upon which all subsequent IS activities are based. If you intend to pursue a career in IS, the skills you learn in this class are designed to have immediate applicability. If you intend to pursue a career in another discipline, the knowledge you obtain in this class will help you better appreciate the role of the IS department in your organization, and better understand how to manage and support IS-related projects.
Prerequisites
MIS 24053 (Introduction to Computer Applications) or equivalent
MIS 24065 (Web Programming) or equivalent
Minimum grade of C; may not be taken concurrently.
Beginning with the 2012/2013 catalog year, this course is required if you are completing a CIS major within the College of Business Administration. As such, it will be taught under the assumption that most enrolled students are in fact business students pursuing a CIS major, who know basic business concepts and already have some exposure to object-oriented programming concepts.
If you have not completed the prerequisites listed above, you should not be in this class, and may be deregistered. If you remain, you may find that you have tremendous difficulty in understanding and keeping up with the course content. Please be warned that if you have been waived into this course with less than the expected level of knowledge of business and IS concepts, I will not slow the course down for you!
Course Objectives
Upon completion of this course, you should be able to:
· describe the basic concepts and principles associated with the systems development life cycle (SDLC), which includes systems planning, analysis, design, implementation, and support.
· explain the roles and responsibilities of systems analysts in organizations today.
- use a simple CASE tool to create UML diagrams that accurately model system requirements.
- design and prototype forms, reports, screens, and user-computer dialogs which convey the look and feel of a new system to end users.
- apply what you have learned in a practical manner, by identifying a need for a new or improved IS in a specific local organization, documenting and modeling the business requirements for that system, creating and maintaining a project plan, performing a cost-benefit analysis of the proposed system, and presenting your final proposal before a group of your peers.
Some sections of this course (particularly the UML portion) will require you to work hard and devote a fair amount of time outside of class to developing the necessary skills. There will be a number of individual and group assignments in this unit designed to help you with this process. Where UML is concerned, “practice makes perfect” is a fitting axiom.
Textbook and Course Material
Systems Analysis and Design with UML (4th Edition, 2012) by Dennis, Wixom, and Tegarden
Wiley Publishers, ISBN 978-1118037423
Visual Paradigm Community Edition (free download; used for UML portion of class & group project)
Grading Information
Points for the course will be distributed as follows.
Components of the Final Course Grade |
|
Conversion for Final Course Grades |
|||||
Attendance |
5% |
|
93% - 100% |
A |
|
77% - 79% |
C+ |
Partic. assignmts / quizzes |
12% |
|
90% - 92% |
A- |
|
73% - 76% |
C |
Homework assignments |
13% |
|
87% - 89% |
B+ |
|
70% - 72% |
C- |
Group project |
30% |
|
83% - 86% |
B |
|
60% - 69% |
D |
Two exams (20% each) |
40% |
|
80% - 82% |
B- |
|
Below 60% |
F |
Total |
100% |
|
|
|
|
|
|
Under no circumstances will "extra credit assignments" or "makeup points" be offered to individual students as a result of poor individual performance on an exam, quiz, homework assignment, or the course as a whole. This is not fair to other students in the class. All grades in this course are final and non-negotiable. I do not curve (up or down).
Note: The group project grade will not be counted if all other individual grades are not at least at the C level.
Extra Credit Opportunities
Regardless of your major, class standing, and expected graduation date, interacting with IT industry professionals will help you to practically apply the concepts that we are learning in class throughout the semester.
One opportunity for doing so is to attend the weekly Management Information Systems Association (MISA) meetings, where you can listen to presentations from recruiters and recent KSU grads who hold IT jobs in the Kent / Akron / Cleveland area, and network with them afterwards. Another is to attend local IT career-related events, such as the 2013 IT/IS Career Expo in March.
Thus, I will offer the opportunity for class members to earn extra credit through either one of the following channels:
- Attend at least three MISA meetings by no later than April 15th (attendance will be verified), and write a short (one paragraph) reflection statement within a week of each meeting on what you have learned.
- Write three short papers (3 pages each, double-spaced) on companies that you are interested in working for, either through internships or after graduation. These papers should discuss who / what the company is, what specific IT job opportunities it offers, why you are interested in working there, and how you can prepare during your time at KSU (including in this course) to have the best possible chance of obtaining a position there. All papers must be turned in no later than April 15th.
More details on the requirements for each of these extra credit opportunities will be provided to you at the start of the semester. Each MISA meeting attended, or paper written, will be worth 10 points (0.5% of your overall course grade), up to a maximum of 30 points (1.5% of your overall course grade).
Course Policies
Due Dates
All assignments are due at the beginning of class on their due dates. Since we go over the answers to all participation assignments in class, I will not accept for a grade any handwritten work that is turned in to me after we have already discussed the answers, nor will I accept for a grade any electronic work that is emailed to me after I have already collected everyone else’s papers. I will check the timestamp on all emailed assignments to determine whether they were submitted by class time. Homework assignments that are not turned in when I ask for them in class will likewise be considered late and will be penalized (a minimum of one letter grade) or rejected altogether.
Individual Work
Participation and homework assignments are to be completed individually. This means that you are not to solve problems together, compare answers prior to turning in the work, or otherwise use other people’s answers or previous work. This includes the work of students enrolled in other sections of the course. Collaborative efforts on individual work are considered violations of academic honesty, and will be penalized accordingly.
Group Work
Assignments in this category are to be completed as members of a team. Team members should be available to help each other. If a team member must miss class, the other members of the team should make sure that he/she receives any notes and handouts from that class and is informed of any assignments or activities discussed during class. All team members are expected to participate in all team activities. Your team must be self-managing, and you will have the opportunity to evaluate your team members on their contributions at the end of the semester. Please note that all group work must be original work, created by the members of that group specifically for this class. Use of work by people outside of the group, or work previously done by members of the group, is not allowed and is considered a violation of academic honesty.
Group Project
The purpose of the group project is to provide you with the opportunity to apply the tools and techniques you have learned in class to a real world problem, within a project team environment. Your individual project grade will be calculated as a function of the team grade and your peer evaluations. Restrictions on group project work are the same as those in “Group Work” above. More detailed information concerning the group project will be provided in class and posted in BlackBoard.
Note on Group Project Grading: Group project grades will not be counted if other (individual) grades are not at least at the C level. If you do not have acceptable performance on the analysis and modeling techniques tested in class, your project work will not help you. You must learn these techniques!
Attendance
This course relies heavily on participation, and you cannot participate if you are not in class. The UML section of the course is particularly difficult if you do not attend class regularly. More than 3 absences without a note from the Dean will result in a 0 for your attendance grade. Leaving early for a vacation or holiday trip is not an acceptable excuse, so please plan your travel accordingly. Hangovers, incarceration, job interviews, and exams in other classes are also not acceptable excuses. Note that being in attendance means being in class when I take roll.
Attendance at presentations (both your own and those by other groups) is very important. Students who miss a presentation will receive an automatic 50-point (2.5%) deduction to their overall course grade, unless they have received an excused absence from me. Grades for participation assignments and the group project may also be affected by excessive absences, so it is in your best interests to attend class regularly.
You alone are responsible for obtaining information from missed classes from other students and/or BlackBoard (this includes handouts and changes to course requirements, due dates, and the course schedule). It is not my responsibility to fill you in on what you missed. Please inform both me (by email) and your group ahead of time of an expected absence.
When you enter the workforce, you will be expected to arrive at work on time every day. Therefore, please show respect to me and your classmates by arriving to class on time. At the end of any class in which you arrive after roll is called, please see me and explain why you were late. Attendance credit might or might not be given depending on the reason for being late, the amount of class time missed, and whether or not you have a pattern of being late.
Electronic Devices
Electronic devices (e.g., laptops, cell phones, smart phones, iPads, iPods) are a distraction to you, me, and your classmates. As such, the use of all types of electronic devices is explicitly forbidden during class time, except during class periods when we are using CASE tools for UML modeling exercises. I will notify you in advance when it is acceptable to use a laptop in class for this purpose.
Exams
Two in-class exams will be given. Exams may contain objective questions, applied problems, and/or short answer/essay questions. In the case of documented illness, emergency, or a University-approved event causing a student to miss an exam, a special makeup exam might be given or other arrangements might be made. However, in fairness to all students, I must have documentation as justification for missing an exam – no exceptions! This means that, for example, if you are sick with the flu on exam day, you need to go to University Health Services or another doctor because you will need a note from him/her to justify your absence. Please note that I will not excuse anyone from taking an exam on the scheduled day/time simply because they have an exam in another class on the same day.
All exams must be returned to me for safekeeping after we go over them in class. If you leave the classroom with a copy of your exam (or if I catch you taking photos of an exam on your cell phone or other electronic device), you will receive a 0 on the exam and be referred to the Office of Student Conduct.
Quizzes
Quizzes are intended to test whether students are keeping up with the reading. They are intended to be easy if you have done the reading, and difficult if you have not. A pop quiz is possible on any day that reading is assigned. Pop quizzes might or might not be given during the semester depending on whether I feel that incentive is necessary to ensure that students are doing the assigned reading prior to class. I may also choose to save class time by administering quizzes on BlackBoard rather than in class. Each quiz will count as one of the percentage points out of the 12% participation portion of your course grade (see “Grading Information” above).
Participation Assignments
Each participation assignment, which is like a short homework, counts as one of the percentage points out of the 12% participation portion of your course grade (see “Grading Information” above). Participation assignments are graded on an “effort” basis, i.e., you get full credit if it appears that you made a strong effort at completing the assignment and turned it in on time. There is no makeup for a participation assignment, and you must actually attend class and turn in the assignment on time in order to get credit. If you have an excused absence from class on the day that a participation assignment is due – defined as an absence of such a nature that you were also prevented from completing the assignment and submitting it to me by email prior to the start of the missed class – that assignment will not be factored into your course grade. Please make a copy of each participation assignment submission and bring both the original copy and the copy to class on the day it is due. I will collect the original from you, and you will keep the copy so that the assignment can be discussed in class.
Homework Assignments
There will be three homework assignments, which together will equal the 13% homework portion of your course grade (see “Grading Information” above). The first two assignments will cover UML concepts and will each be worth 5% of your overall course grade. The final assignment will cover user interface design principles and will be worth 3% of your overall course grade. Unlike participation assignments, homework assignments are graded for accuracy and completeness. Professionalism also counts, so homework assignment submissions should be neat, readable, spellchecked and grammar-checked. Please make a copy of each homework submission and bring both copies to class on the day it is due. I will collect one copy from you, and you will keep the other copy so that the assignment can be discussed in class.
University Policies
The following policies apply to all students in this course:
- Students attending the course who do not have the proper prerequisite risk being deregistered from the class.
- Students have responsibility to ensure they are properly enrolled in classes. You are advised to review your official class schedule (using Student Tools on FlashLine) during the first two weeks of the semester to ensure you are properly enrolled in this class and section. Should you find an error in your class schedule, you have until Sunday, January 27, 2013 to correct the error. If registration errors are not corrected by this date and you continue to attend and participate in classes for which you are not officially enrolled, you are advised now that you will not receive a grade at the conclusion of the semester for any class in which you are not properly registered.
- For Spring 2013, the course withdrawal deadline is Sunday, March 24, 2013.
- Academic honesty: Per KSU policy, “cheating” means to misrepresent the source, nature, or other conditions of your academic work (e.g., tests, papers, projects, assignments) so as to get undeserved credit. In addition, it is considered to be cheating when one cooperates with someone else in any such misrepresentation. The use of the intellectual property of others without giving them appropriate credit is a serious academic offense. It is the University's policy that cheating or plagiarism result in receiving a failing grade for the work or course. Repeat offenses result in dismissal from the University.
- Students with disabilities: University policy 3342-3-01.3 requires that students with disabilities be provided reasonable accommodations to ensure their equal access to course content. If you have a documented disability and require accommodations, please contact the instructor at the beginning of the semester to make arrangements for necessary classroom adjustments. Please note, you must first verify your eligibility for these through Student Accessibility Services (contact 330-672-3391 or visit http://www.registrars.kent.edu/sas for more information on registration procedures).
- If you are eligible to graduate, it is your responsibility to apply for graduation before the set deadline (May Graduation: Apply before September 15th. August Graduation: Apply before December 15th. December Graduation: Apply before March 15th.) If you apply after the deadline you will be assessed a $200 late fee. Please see your academic advisor as soon as possible if you are uncertain as to your progress toward graduation. To apply for graduation complete the following steps: Log onto your Flashline account 1. Click on the Student Tools tab, 2. Look in the Graduation Planning Tool Box, 3. Click on Application for Graduation. If an error message appears, you must contact your advisor.
Tentative Schedule of Classes
This schedule contains a general layout of the course; however, changes will be necessary. It is therefore important to attend class, monitor your email, check BlackBoard, and obtain notes from classmates when you are absent so that you remain informed. Topics, assignments, and due dates are all subject to change.
Please note that for some topics, we will not cover all of the material in the associated textbook chapter. I will assign the exact pages to be read at the appropriate time in the course. Some topics will also be supplemented with readings from outside the textbook.
Week |
Date |
Topics |
Preparation |
Major Due Dates |
1 |
Jan 15 |
Course intro |
|
|
Jan 17 |
Group project intro |
Group Project Manual |
|
|
2 |
Jan 22 |
IN-CLASS GROUP WORK DAY (since the Mon/Wed section had yesterday off for MLK Day) |
||
Jan 24 |
Introduction to Systems Analysis, SDLC |
Chapter 1 (pp.1-22,28-30) + addt’l assigned readings |
|
|
3 |
Jan 29 |
Project Initiation |
Chapter 2 (pp. 48-69) |
Project Deliverable 1 |
Jan 31 |
Feasibility Analysis |
Handouts |
|
|
4 |
Feb 5 |
Project Management |
TBA |
Project Deliverable 2 |
Feb 7 |
Requirements Determination |
Chapter 3 |
|
|
5 |
Feb 12 |
Case study / catch-up / review |
|
|
Feb 15 |
EXAM #1 IN CLASS |
|||
6 |
Feb 19 |
Overview of UML |
Chapter 1 (pp. 23-28) |
|
Feb 21 |
Group Deliv 3 Presentations |
|
Project Deliverable 3 |
|
7 |
Feb 26 |
Functional Modeling (use cases) |
Chapter 4 (portions) + handouts / TBA |
FUNCTIONAL MODELING: There will be at least two participation assignments and one homework assignment for this section of the course. |
Feb 28 |
||||
8 |
Mar 5 |
Functional Modeling (use case descriptions) |
||
|
Mar 7 |
|||
9 |
Mar 12 |
Structural Modeling (data modeling and class diagrams) |
Chapter 5 (portions) + handouts / TBA |
STRUCTURAL & BEHAVIORAL MODELING: There will be at least two participation assignments and one homework assignment for this section of the course. |
Mar 14 |
||||
10 |
Mar 19 |
Behavioral Modeling (activity diagrams) |
Chapters 4, 6 (portions) + handouts / TBA |
|
Mar 21 |
||||
11 |
Mar 26/28 |
NO CLASS – SPRING BREAK |
||
12 |
Apr 2 |
Design Strategies |
Chapter 7 (portions) |
|
Apr 4 |
Group Deliv 4 Presentations (continued on April 9th, if necessary) |
|
Project Deliverable 4 |
|
13 |
Apr 9 |
User Interface Design and Evaluation |
Chapter 10 |
|
Apr 11 |
User Interface Homework |
|||
14 |
Apr 16 |
User Interface Validation, Architecture Design |
Chapters 10, 11 |
|
Apr 18 |
Architecture Design, cont’d |
Chapter 11 |
|
|
15 |
Apr 23 |
Construction |
Chapter 12 |
|
Apr 25 |
Installation and Operations |
Chapter 13 |
|
|
16 |
Apr 30 |
FINAL PRESENTATIONS, DAY 1 (if needed) |
|
|
May 2 |
FINAL PRESENTATIONS, DAY 2 |
|
Project Deliverable 5 |
|
17 |
May 9 |
EXAM #2 (during scheduled final exam period, Thursday, May 9th, 12:45 to 3:00 PM) |