Skip to main content

COMP 495/496 Project Manual

Part 3: Analysis and Design or Implementation

When the focus of the project is on the implementation of an applied information system, the deliverables for the third part of the project will be computer programs and data that implement the applied information system, as well as necessary documentation such as a user’s guide. The implementation will be evaluated on the basis of the functionalities implemented, quality of coding, design and implementation of the user interface, and sufficiency of supporting documentation.

When a project has little or no programming, such as an analysis of case studies in IT/IS management, the deliverables for the third part of the project will be a well-written document in an acceptable format (.rtf, .doc, .docx, or .pdf) that provides your analysis of the cases and design of an information/computer system or solution to the problems presented by the cases. The document should be about 5000 to 7000 words long. The evaluation of the document will be based on your demonstrated grasp of the material, your analysis of the IT cases, the quality of the proposed solution or system, and the presentation of the above.

Guidelines for Marking Part 3

TOP

The grade will be based on the following criteria:

Technical merit (40 points)

  • documentation
  • solution (algorithm, data structures, classes, database optimization, etc.)
  • coding standards
  • project-specific criteria

User satisfaction (40 points)

  • interface look and feel, ease of use
  • performance (speed, validity, reliability)
  • project-specific criteria

Project process (20 points)  

  • project control and feedback to the project supervisor
  • group assessment, to be negotiated where applicable.

These are general guidelines for project marking. The nature of the project may require that they be modified. That will be negotiated prior to submission of the proposal.

Group Assessment

TOP

  • Once in each contract period, every group will make a formal presentation about its project to other students and guests from the host site.
  • Project methodologies, reporting structures, and contents will be agreed upon in consultation with the individual sites. These factors will vary from site to site, reflecting the different projects and site practices.
  • Teams will retain a record of activities and progress, detailed to include meetings, agreements, time spent, etc. Individual team members will also log their time, showing the activities they have been doing. This record will provide input to the biweekly progress reports.