Final Report Plan
| Version 1.0 | Monday 9th March 1998. |
Part III Computer Science Project
Department of Electronics & Computer Science
University of Southampton
|
| Name: | Alex Walker |
| Title of Project: | JavaScript Parser and Error-Reporter |
| First Project Supervisor: | Ed Zaluska |
| Second Project Supervisor: | Gwil Edmonds |
Introduction:
This document gives the intended outline of the final report, due to be completed by 7th May 1998.
The aim of this is to give a clear structure to the document from a very early stage, and to allow for comment and discussion before any major work begins on the content.
Structure:
The intended structure of the final report is as follows:
- Introduction
- Preliminary Work
- Functional Specification
- Design Specification
- System Implementation
- Testing & Verification
- Conclusions
- Acknowledgements
Section 1 - Introduction:
Section 1 will introduce the project, how it came into being, and its purpose. Also, the JavaScript programming language, its standardisation to ECMAScript, and its use on the World Wide Web.
Section 2 - Preliminary Work:
Section 2 will outline the first few weeks of the project and the initial design work. Also, the reading done and choice of programming language and compiler tools.
Section 3 - Functional Specification:
Describes in detail the functionality of the system as a whole. To include some sample JavaScript errors which should be picked up by the system.
Section 4 - Design Specification:
Comments on the use of Lex and Yacc and how these tools work. Describes on the individual modules chosen and why.
Section 5 - System Implementation:
Describes in detail the data structures and modules of the system, and how they all pieced together.
Section 6 - Testing and Verification:
Talk about how to test a compiler, and the techniques used. The results and details will be given in an appendix.
Section 7 - Conclusions:
A summary, including any significant problems encountered and possible future enhancements.
Section 8 - Acknowledgements:
Thanks and References
Appendices:
These may cover the following:
- Details of the testing, and the test plan.
- Diagrams, including the object diagram, and any tables of data.
- User Manual
- Screenshots of the system in use.