Your name(s)

Affiliation (department, school, university)

Email:

Date:

Class:

Instructor: Dr. Yujian Fu

Email: [email protected]

Abstract: (Required)

Abstract is required. It is a summary of your project. Your final project report is expected to be 10 pages, including the references and title. The font is Times New Roman, the font size is 12. You may use multiple line space of 1.15 or 1.25. Do not use single space or double space.

I. Introduction

Why do you want to do this work – goal and objectives. Background is to show the related work in this area. What are existing works in this area, what are current results? How do the current works solve the problem? Please put enough citation for current existing works in this area.

II. Problem Statement (Rationale)

What are the current existing research issues? What are the problems you will solve in this project? Give a detail description why this problem is important, i.e., what if the problem is not solved, why this work is significant.

III. Related Work (Background)

What are the current works that has been done? Please use correct reference form.

IV. Project Management

List all tasks of your project that you have implemented, the person that conducted and finished this task, time that started and finished this task. A sample chart is shown in the following.

V. Design Model of System

In this section, you need to present the model of the system. You need to use UML model (if you have no idea about any other design methodologies). In the UML model, the system design model must include static diagram – Class diagram and dynamic diagram – use case diagram and/or state diagram and/or sequence diagram and/or activity diagram. This is required for all projects.

Your system design model must use the correct notation.

VI. Tool Description

If you use any tools, platform, or new programming languages, plug-ins, please give a description what you use. You need to have introduction of the tool, syntax, semantics (if possible), examples, and why you need to use it.

VII. System Implementation and Results

All functions that you have implemented, new APIs (if you have), user defined classes, design patterns that you used, can be implementations. Make sure attach snapshots for your results. For each functions, show the key methods how this function is implemented, attach the code.

You need to pay attention to followings:

· The implementation has to be consistent with design model;

· The implementation has to be consistent with the tasks defined in your document.

VIII. Validation Methodology

Any system needs to be validated before release. The validation methodology can be software testing or formal verification. There are various types of testing technologies available now. A list of testing tool can be found in this link: http://wrestt.cis.fiu.edu/cen/. A good reference book should be Roger S Pressman, “Software Engineering: A Practitioner’s Approach,” 7th edition, McGraw-Hill Science, ISBN-13: 978-007337597-7. There are two unit testing techniques are recommended for this work: white box testing and black box testing. You are required to use one methodology, e.g., basis path testing.

· For Java applications, apps, you may use JUnit.

· For C or C-like program, you may use basis path testing. Testing is one of the biggest portion in the final report, please make sure you do it properly.

IX. Conclusion (Discussion and Future Works)

Conclusion includes the significance of this work and possible future extension that can be applied to this work.

References:

The template will number citations consecutively within brackets [1]. The sentence punctuation follows the bracket [2]. Refer simply to the reference number, as in [3]—do not use “Ref. [3]” or “reference [3]” except at the beginning of a sentence: “Reference [3] was the first . . .”

Number footnotes separately in superscripts. Place the actual footnote at the bottom of the column in which it was cited. Do not put footnotes in the reference list. Use letters for table footnotes.

Unless there are six authors or more give all authors’ names; do not use “et al.”. Papers that have not been published, even if they have been submitted for publication, should be cited as “unpublished” [4]. Papers that have been accepted for publication should be cited as “in press” [5]. Capitalize only the first word in a paper title, except for proper nouns and element symbols. For papers published in translation journals, please give the English citation first, followed by the original foreign-language citation [6].

G. Eason, B. Noble, and I. N. Sneddon, “On certain integrals of Lipschitz-Hankel type involving products of Bessel functions,” Phil. Trans. Roy. Soc. London, vol. A247, pp. 529–551, April 1955. (references)

J. Clerk Maxwell, A Treatise on Electricity and Magnetism, 3rd ed., vol. 2. Oxford: Clarendon, 1892, pp.68–73.

I. S. Jacobs and C. P. Bean, “Fine particles, thin films and exchange anisotropy,” in Magnetism, vol. III, G. T. Rado and H. Suhl, Eds. New York: Academic, 1963, pp. 271–350.

K. Elissa, “Title of paper if known,” unpublished.

R. Nicole, “Title of paper with only first word capitalized,” J. Name Stand. Abbrev., in press.

Y. Yorozu, M. Hirano, K. Oka, and Y. Tagawa, “Electron spectroscopy studies on magneto-optical media and plastic substrate interface,” IEEE Transl. J. Magn. Japan, vol. 2, pp. 740–741, August 1987 [Digests 9th Annual Conf. Magnetics Japan, p. 301, 1982].