Scribd
Upload
111 views

CAT400 Report Outline

This document outlines the required sections and content for an undergraduate major project report at the School of Computer Sciences, USM. The report should include an abstract, table of contents, introduction, background and related work, system requirements analysis, system design and implementation, system testing and evaluation, conclusion and future work, references, and appendices. Each section provides detailed guidelines on what information and analyses should be included to comprehensively document the project.

Uploaded by

Evo Lution
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
111 views

CAT400 Report Outline

This document outlines the required sections and content for an undergraduate major project report at the School of Computer Sciences, USM. The report should include an abstract, table of contents, introduction, background and related work, system requirements analysis, system design and implementation, system testing and evaluation, conclusion and future work, references, and appendices. Each section provides detailed guidelines on what information and analyses should be included to comprehensively document the project.

Uploaded by

Evo Lution
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

CAT

400 Undergraduate Major Project

(c) 2012 School of Computer Sciences, USM

CAT 400 Undergraduate Major Project Report Outline


Abstract
The whole project in miniature, and stand on its own. Should include:
- Problem statement
- Key Requirements
- State main objectives What did you investigate and why?
- Describe methods What did you do?
- Summarize important results What did you find out?
- State main conclusions what do your results mean?
- All in one paragraph
(1 page)
Acknowledgement

Table of Contents

List of Tables and Figures

Chapter 1: Introduction

Background general background of the environment.


Problem statement state the problems within the environment
Motivation (reason why the study was carries out)
System objectives
Proposed solution
Benefit or impact of the proposed solution
Uniqueness of proposed solution ( innovation or novelty)
Organization of the report - A brief overview of the rest of the chapters in the
report (a guide to the reader of the overall structure of the report)


Chapter 2: Background and Related Work

Identify
status
of
project
development
(new
or
continuation/enhancement/review relevant past project)
Summarize relevant project to provide context, key terms, and concept so the
reader can understand the study.
List details of existing algorithms/theories/models
Criticize strength and weaknesses of existing system/work
Provide brief introduction of the proposed work

ver. 1.0, 20121130

CAT 400 Undergraduate Major Project

(c) 2012 School of Computer Sciences, USM

Chapter 3: System Requirements/ Analysis


Identify project scope, system capabilities and system limitation
Project management :
o work breakdown structure- WBS
o work schedule- Gantt chart and milestone timeline
o SWOT analysis
Development Methodology according to cluster
Detail requirements of new system (information gathering- e.g. survey,
questionnaire etc)
Analysis of the new system using appropriate diagrams
o IS/SE/Multimedia: using UML modeling which include i) use case
diagram, ii) use case descriptions, iii) class diagram, iv) system
sequence diagram and iv) state chart diagrams
o Network/Parallel, Distributed, Grid/Security: Flow Chart, Pseudo code
o AI/Vision and Image/NLP: Flow Chart, Pseudo code
Technology deployed ( the chosen technology) Justify
o Hardware
o Software
- Tools
- OS (development PC + server)
- Programming languages involved.
- Algorithms (if relevant)


Chapter 4: System Design and Implementation

Design System/Application Architecture - discuss/describe each component


in detail
Design modeling
o IS/SE/Multimedia:
i) Design Class Diagram,
ii) Detailed Sequence Diagrams,
iii) Detailed Statecharts Diagram and
iv) Package Diagrams.
(The detailed diagrams should appear in the appendix)
o Network/Parallel, Distributed, Grid/Security: Protocol, Message
Passing Diagram, Algorithm
o AI/Vision and Image/NLP: Algorithms
Design Database (if applicable)
Design user Interface (Sample screen shots should appear in the appendix)
Design system interface (if relevant)
Implementation Strategy (e.g. bottom-up, top-down)


Note: Give a good overview so that the design is clear and focus on the
interesting design decisions (what were the alternatives, why select one
particular solution).

ver. 1.0, 20121130

CAT 400 Undergraduate Major Project

(c) 2012 School of Computer Sciences, USM

Chapter 5: System Testing and Evaluation


Discuss testing strategy (unit, integration, system, acceptance, and how they
are carried out).
Discuss how test cases/scenarios were selected.
A summary of the test results and what coverage was achieved. (The detailed
test reports should appear in the appendix)
Evidence that the application meets the requirements and works.
Provide a critical evaluation of your work (advantages, disadvantages,
strengths and limitations of your work) by comparing your work with others
(existing system)
Summary of important findings.

Chapter 6: Conclusion and Future Work

Summary of results and how requirements have been met.


A critical evaluation of the results of the project (e.g., how well were the goals
met, is the application fit for purpose, has good design and implementation
practice been followed, was the right implementation technology chosen and
so on)
Outline the success of your project when compared to the objectives that
were set.
Suggest further work for your project.


Note: Make explanations complete. Avoid speculation that cannot be tested in
the foreseeable future. Discuss possible reasons for expected or unexpected
findings.
References
List down all the references from books, journals, proceedings, websites,
manual etc.
Reference Style: APA OR Harvard OR IEEE.

Appendices

Any other relevant information that does not fit in Sections 1 6, for example
detail of use-case specifications, detail sequence diagrams, screen shots,
detail test results, pseudo code etc.

ver. 1.0, 20121130

You might also like