MIS
120 Term Project Specifications
6
September 2007
PROJECT DESCRIPTION
In this project, you will investigate and evaluate usage of Microsoft® Excel and/or Access within an organization. You will apply the material and thought processes learned in class to the assessment of such usage. As part of a three- or four-person team, you will also practice teamwork and allocation of work within project planning. Additionally, you will provide some of your own motivation for studying these software tools by examining, critically, their ability, or lack thereof, to support managerial objectives of a business enterprise.
Each team will select an organization, obtain its co-operation, interview one or more employees within the organization to learn about its usage of one or both of these software tools, and write a paper describing its investigation and assessment. Each team member will complete a peer evaluation of the others.
Each paper will differ depending on the organization and usage investigated, but all must include:
PROJECT STEPS
DELIVERABLES
PAPER FORMAT
Papers are to be typed (use a word processor, Times New Roman with font size
10 or 12) and single-spaced with double spacing between headings and
paragraphs. The paper should run 5 to 6
pages, exclusive of title page, bibliography, and such. The first portion of your paper (after a
title page listing the authors and specifying the organization and
interviewee(s)) should be an executive summary which provides highlights from
the paper and summarizes the topics to be discussed in the paper. It is well for the paper to provide a
bibliography. An appendix page (last)
will specify the date(s) and location(s) of the interview(s) and list all
people present at the interview(s).
Avoid relying overmuch on web sites for definitive references (as opposed to
guidance to sources of reliable, vetted information). If you doubt the need for this caveat, visit http://www.lhup.edu/~dsimanek/fe-scidi.htm. The Sheridan Libraries of The Johns Hopkins University
provide an excellent site
providing guidance in the evaluation of a web site's intellectual and academic
reliability and validity.
Avoid even more (indeed, eschew) transcribing paragraphs from an organization's web site into your term paper (in Fall 2001 semester, this intellectual cancer metastasized alarmingly). Indeed, plagiarism, like exposure to bubonic plague or stepping on stonefish, is best avoided. The following sites will help you avoid it:
"How Not to Plagiarize" by Margaret Procter, Coordinator, Writing Support, University of Toronto
"Using
Sources" by Lisa Trivedi and Sharon Williams
of
"Avoiding
Plagiarism" from the
Professor Zachary M. Schrag, a historian and scholar of Columbia University, has courteously permitted linkage to his excellent guide The Anatomy of a Ten-Page Term Paper (scroll down a bit to read it). Additionally, our own School of Management has explicit and valuable writing guidelines on-line.
PROJECT EVALUATION
The best papers will synthesize material from the interview(s), the text, the lectures, other classes, and other experiences of the team members. A paper which only reports on the interview, without including your assessment of the usage of Microsoft® Excel and/or Access and your defense of that assessment, is deficient and its grade will be at most a "C".
As I read and grade a paper, I will assess:
Content:
Presentation:
All team members will receive the same grade on the project unless a document (i.e., the peer review(s)) signed by all team members advises me otherwise.
INTERVIEWING SUGGESTIONS
As you plan the interview, decide on its major themes. Some possible themes are:
Remember: this list is indicative, not exhaustive. Not all themes will be appropriate for all systems, nor for all interviewee(s).
Consider obtaining background information about the organization before the interview(s).
There is a place for three types of questions within the interview:
Arrange your questions in logical sequence.
Take notes during the interview(s). Even if you tape the interview (doing so requires explicit permission of the interviewee(s)), your notes will help you remember important items. Taping may inhibit the discussion, and tapes have a way of being unintelligible at just the wrong places.
Stay flexible – if your interviewee brings up an interesting subject that the team didn't anticipate, follow up on it.
Ask your interviewee(s) if you may call or send email if follow-up questions arise.
Professor Lending's advice (originally pertinent to MIS 310) to assign a project of this type, and her permission to adapt her materials, are gratefully acknowledged. This project requires a term paper of less than one-half the length, and more straightforward analytically, than does the MIS 310 project, in view of the fact that this is a 100-level (versus 300-level) course.