Updated for Spring 2007

IS207: Analysis of Information Systems

The Final Report

There is no single approach that works for all projects, but the following Table of Contents both gives you an idea of what we expect and is a useful "default." In almost every case, your project report is expected to include the following:

• Executive Summary
• Statement of the problem
• Background information on both the system and the organization, including (if relevant):
• methodology for gathering information and findings (place research design details in appendix if necessary)
• business model of the organization
• value proposition of your innovation
• Mission, goals, objectives
• Description of existing system
• Requirements for the proposed system
• Alternative(s)
• Evaluation of alternatives (general discussion, effectiveness measures, etc.)
• Economic Feasibility Analysis (or Cost Comparison, if appropriate; can be separate or part of the evaluation of alternatives)
• Recommendations
• Implementation (include analysis of organizational barriers or issues and diffusion of innovation strategy)
• Plan for evaluation (Any new or revised system should be evaluated after it is up and running. Include a brief section on how and when this evaluation should be done.)

The topic of the report is subject to evaluation on its significance and appropriateness. The report as a whole is evaluated on its clarity, logic (does it hang together?), thoroughness, and persuasive writing style.

The final report for your project is to be written as a report (not a PPT presentation) in standard business English, portrait mode. Each section of the paper will be evaluated on whether it is missing, not needed (rare), or whether the quality is excellent, good, fair, or poor. Put supporting information in appendices so that the project report is easy to follow and looks professional.

General guidance on what we expect: think of yourself or your group as a consultant and that this is work for hire. Write it as professionally as possible -- business writing, professional graphics and layout -- this is the last practice before reality starts.

Additional notes:

The items listed above are a good starting point for your Table of Contents. You may organize this to meet your specific needs, but each of these topic areas should be covered.

Presentations of progress reports for each project will be scheduled for March 6^th & 8th. Structure your presentation so each member of your group gets to speak. You may use PowerPoint or a browser. Do not read your report to the class. (Hint: practice your presentations with your classmates or other willing victims.) The oral presentations are required but will not be graded.

To save time, we ask you to put all necessary files or in-class presentation materials in a common folder in the class directory. This will reduce the time between presentations when the next group needs to search for its files. Use the "To Be Determined" directory. If you want to access your files with a browser, use the sub-directory Then they can be accessed online at http:// / "Groups" is mapped to drive ?: on most computers on the SIMS LAN.