There are different types of assignments.

Due Dates: Due dates are listed for each item. In each case, the assignment is due at the end of the class period on the due date. Late assignments will receive a 4 points per (calendar) day (or fraction thereof) late penalty.

Format: All assignments must be typed (or word-processed) and must be double-spaced; use page numbers. Margins must be at least one inch (1") on all sides. Staple assignments in upper left corner; do not provide folders with your work.

Medium: Some assignments will be turned in during class. Other assignments will be posted to students' blogs or wikis. Still others will be turned in through Canvas. Never email assignments to me unless I explicitly as for it to be so sent. Students must turn in their assignments in the specified way to get credit for them.

Length: Where page estimates are specified, they are gauged at a font size of 11; students using a larger font should assume their texts can be about one-third longer I will quit reading at the end of the page restriction. Hence, if your main point occurs after the maximum number of pages for the assignment, it will be lost.

Content: Not only will I grade on the basis of the content of the material, but also the presentation of the material. I expect the writing to be of the caliber of college graduates; I expect good grammar and accurate spelling. Note the writing rubric is available. Failure to meet this expectation may result in a reduction of your grade.

Class Participation: I believe in an interactive class and so we have a variety of ways in which students need to be involved. One of these is the individual rating sheet for cooperative learning groups that is to be completed each week after groups are formed. In addition, from time to time, we will have activities in class (generally these are not scheduled far in advance). The most major of these is the group forming exercise early in the semester. Generally these activities are graded similarly to the homework; the exception to this is the group forming exercise.

The Blog: As part of your class participation grade, you will be blogging about your project and how it relates to service learning. In our semester project, you will be learning about how to do systems analysis and the issues that can arise in a real application. At the same time, you will be helping our community partner (i.e., your client) understand how to use technology to meet the goals of its organization more effectively. Without you, your client might not be able to improve its technology use! The Blog assignment is intended to get you to think about your project in terms its contribution to your community, and what it means to you. Specific issues will be assigned each week that must be addressed. However, other issues may be addressed as you deem appropriate.

Quizzes: There will be quizzes throughout the semester to ensure that you are keeping up with your reading. These will generally be announced on the Announcements page on Canvas.

Regular Homework: In addition to the various projects and major assignments, students will be assigned regular homework that must be completed and turned in. These will be listed on Canvas under announcements. It is the student's responsibility to learn of the assignments. Your grade for individual homework assignments is either a check or check minus. The grade that is used in the final grade computation is the percentage of assignments completed. So, for example, if there are 10 assignments and you have turned in 5, your homework grade would be 50.

"Networking" Activities: Learning to network, and learning to learn about new topics is an important part of any IS Professional's life. Therefore, you are going to practice that activity this semester by attending at least three external events. These might include the IS Mentoring Program, the IS Programming Club, the Career Services Activities (note the Job Fair and interviews do not count), the Executive Leadership Institute Events, the Distinguished Lecture program, Student Night Seminars sponsored by the Institute of Internal Auditors and the Information Systems Audit and Control Associations, the local Web Developers Chapter, Saint Louis Visual Basic Users Group, the XPSTL Group, the Wireless SIG or any other IS-related seminar by a campus based or local professional organization (if it is not in this list, be sure to get permission before you go). The base grade will be the percentage of the expected events (3) you attend. So, if you have attended one event, this grade is 33.3, two events, the grade is 66.7, etc. You may get extra credit for one additional event.

To get credit for attendance, you must complete the required form (there is also a Word version of the form) and have it signed by some official of the organization or the event.

Project Assignments: The group (project) assignments, include regular Progress Reports and Final Paper/Presentation. All of these assignments will be completed as the group defined by the instructor (to be announced approximately February 27). All of these assignments will be completed as the group defined by the instructor (to be announced approximately February 27). While the entire group generally will receive the same grade, I reserve the right to differentially assign grades to reflect substantially different levels of work being completed by members of the group. At the date when the final project is due, each individual group member must evaluate the amount of work done by others in the group using the Team Evaluation Form.

Progress Reports: In addition to the paper, the analysis group must provide the instructor with regular reports on group activity. These reports are due from the group on each Wednesday at the beginning of class. These reports must include: (a) brief minutes of the discussion and decisions considered during any group meetings during the week; (b) action items for the next week; (c) task assignments; (d) problems and/or opportunities faced by the group that week. Additional, specific sections (such as those noted below) may be required from time to time, and will be announced in class, and stated on the "current page." These assignments can be as long or as brief as is relevant for the activities of the group. However, all progress reports will be provided on the Group Wiki on my Google Drive.

Your progress reports grade will be an average of six scores: the five assignments below (on a 100 point scale) and the percentage of all progress reports completed. So, a group that received an 85 on each of the five specific assignments, but turned in none of the progress report would receive a grade of 70.8 for their progress reports. The groups should think of these assignments as input into their final project since most of the components will be included in the final report.

Background Exercise: All systems analysts must "do their homework" to be in a position to understand enough about the system and organization to be able to ask the right questions. To ensure that all groups are ready to meet the client for the first time, each group must provide a list of appropriate and relevant questions to pose to the client. These questions must be justified in your summary, which should address how the information will help you in completing the analysis, and why the information is not available prior to the meeting with the client.

Due Date: March 10 by 11:59 pm Content: A summary of what you know about the organization or similar types of organizations, the environment and technologies that would be appropriate. In addition, you will provide a set of questions for client (the questions should be sent via email in addition to appearing in your wiki) that will help you to understand the organization better. The first Team Evaluation Forms are due on March 13.

System Description: Once you have collected information about and interviewed your client, it is time to refine your "current system" definition. This statement is your starting point for your analysis, and as such is a critical component to understanding how to approach the analysis. Each group must describe the system (including subsystems, the environment, and interfaces), the problem, the stakeholders and other information pertinent to understanding the system under consideration. One important question that must be answered is how you will know when you are successful in solving your client's problem. In addition, you must provide appropriate diagrams describing the system.

Due Date: April 10 Content: This assignment should include appropriate diagrams.

Questionnaire:One of the tools systems analysts use to determine and refine user requirements is a questionnaire. The approach taken to the length, type of questions and usage depend on the situation and already available information. You must develop an instrument that could be used for collecting data for your project. You must turn in a copy of your questionnaire to the instructor. In addition, you must be prepared to role play with other members of the class to test your instrument. You must use this (or a refined version of it) to query a number of users about the system needs for the final project report.

Due Date: April 19 Content: You must provide the set of questions for your questionnaire. In addition, you must provide a justification for the questions. This justification should explain how the answers to the questions will help you evaluate alternatives better or solve the client's problems more effectively.

Prototype: One of the tools systems analysts use to determine and refine user requirements is the prototype. Prototypes vary substantially; they might be an electronic "toy" version of the system, electronic versions of possible screens, paper versions of possible screens or "post-its" on paper representing the screen. Regardless of the format, the goal is to provide the user something tangible to which to react in order to clarify his or her specifications.

Due Date: April 24 Content: You must provide a copy of your prototype. In addition, you must provide a justification for your prototype. In particular, you must explain how the use of the prototype will help you evaluate alternatives better or solve the client's problems more effectively. The second Team Evaluation Forms are due on April 24.

Cost-Benefit Study: It is important to show the benefits of the project are significant, i.e., that the benefits outweigh the costs of completing the project. We will discuss more about what is included in a feasibility analysis in class, or you can check the website.

Due Date: May 1

 

The Final Paper and Presentation: The purpose of the Analysis Project is to give students the opportunity to practice all of the skills taught in this class, and to meld the results of those activities into a coherent and professional report that describes the recommendations for systems change as well as a set of specifications for systems design. The specific project to be completed this semester will be discussed in class. Detail about the requirements of this assignment and specifications for the final report are available on the Web, and will be discussed throughout the semester. Please note that it is intended that the materials created for the progress reports will be included in the final paper.

Presentations: May 15, 5:30-7:30 Paper Due Date: May 10 at 5 pm The Final Team Evaluation Forms are due by May 12 Format: Write the paper from the perspective of an outside consultant.              Provide two “hard” copies plus and electronic copy. As you consider written materials you might provide this semester, please check the writing rubric that is available. This is a sample project paper and the associated presentation from Fall 2009 for your reference.