School of Information and Library Science
University of North Carolina at Chapel Hill

INLS 162, Systems Analysis
Fall 2003

SAMPLE OUTLINE FOR TEAM PROJECT DOCUMENTATION

1. TITLE PAGE.
   • Project name, author(s), date.
      
2. TABLE OF CONTENTS.
   • A list of report sections.
      
3. EXECUTIVE SUMMARY.
   • A summary of the entire report, not to exceed 3 pages, single-spaced.
     

     Includes:
     Brief description of old system.
     Problem definition.
     Recommendations; description of new system, in terms of the changes it introduces.
     Summary of cost/benefit analysis.

4. DESCRIPTION OF CURRENT SYSTEM.
   • Brief narrative description.
   • Models of the current system, using/integrating one or more of the models discussed in class. (Should be summarized as much as possible, to provide a very brief overview).
      
5. RECOMMENDATIONS FOR NEW SYSTEM.
   • Summary of changes introduced in new system (narrative; 1-2 pages).
   • Models of the proposed system, using/integrating two or more of the models discussed in class. (Should provide a complete and specific description of the proposed system).
      
6. COST/BENEFIT ANALYSIS FOR NEW SYSTEM.
   • Summary of physical aspects of new system (hardware, software, staffing resources needed).
   • Costs of implementing and operating the new system (tangible and intangible).
   • Benefits of new system (tangible and intangible).
      
7. IMPLEMENTATION SCHEDULE FOR NEW SYSTEM.
   • Activities needed for implementing the new system, and a schedule for performing those activities (Gantt chart, time table or PERT chart).
      
8. APPENDIX (not for client report).
   • Team's reflections on the experience and lessons learned.
      

Syllabus / Schedule / Assignments / Discussion Forum (password-protected) / Email to Class / Class Roster