- Standard manual instructing users how to use the system
- Must have a section on "System Installation"
that specifies the environment and installation procedures
necessary to install the system. For example, given the client-server
architecture of many of your project systems,
this entails specifying the required server hardware and software,
ditto for a client machine, the files that must be uploaded
to the server (include a disk containing the files), and any
installation procedures that must be followed. In other words, a client
given this information should be able to install your system in another
(presumably the customer's) environment that has the specified equipment.
(A graduate assistant, QA team, or your instructor will likely test your installation procedures
by trying to install your system either on another server or in a different folder on the development server.)
- Include screen shots for a Web interface
Technical Paper for Possible Publication
- Typical sections include:
- Introduction (some can come from course website project description)
- Relevance in the context of other work (search and document similar work)
- Methodology (e.g., condense material from design document)
- Results - usefulness, etc. (document any results, describe utility of system, etc.)
- Conclusions, Implications, Recommendations, and Summary (make projections)
- The paper must be in IEEE format
(see IEEE template)
and the number of pages limited to 8.
The main IEEE requirements are:
- Type-style and Fonts. Times font is preferred, Times Roman may also be used.
- The Main Title should be centered in Times 14-point, boldface type.
Initially capitalize nouns, pronouns, verbs, adjectives, and adverbs;
do not capitalize articles, coordinate conjunctions, or prepositions (unless the title begins with such a word).
Leave two 12-point blank lines after the title.
- Author's Name(s) and Affiliation(s) are to be centered beneath the title and printed in Times 12-point,
non-boldface type. This information is to be followed by two 12-point blank lines.
- The Abstract is to be in fully-justified italicized text, below the author and affiliation information.
Use the word "Abstract" as the title, in 12-point Times, boldface type, initially capitalized.
The abstract is to be in 10-point, single-spaced type, and limited to 150 words.
- Main Text. Type main text in 10-point Times, single-spaced. Do NOT use double-spacing.
- First Order Headings should be Times 12-point boldface, initially capitalized,
flush left, with one blank line before, and one blank line after.
Use a period (".") after the heading number, not a colon.
- Second Order Headings should be Times 11-point boldface, initially capitalized, flush left,
with one blank line before, and one after.
- References. Number and list the references alphabetically by the last name of the first author.
Use 9-point Times, single-spaced, at the end of your paper.
When citing references in the text, enclose the citation number in square brackets, for example .
Project Website and Directory
Each team will be provided with a directory on the Utopia CSIS server.
Using Secure FTP each team will create a simple website
to post the project information and a list of the project's team members.
It will also serve as the repository of all projects deliverables and other project information (programs, data, etc.).
For a continuation project, we usually continue to use the same directory used by the previous team,
which you will need to update with your project information and
move the material from the earlier project into a subdirectory so it doesn't get lost.
For a new project, you will need to create a website and associated information from scratch.
FTP access information (Host, Username, Password) will be emailed to each team separately.
A free download from Core FTP is easy-to-use FTP software,
but you must check the box for SSH/SFTP (see screenshot).
Note that the project ID on the Projects page of the course website
is a link to the project directory and associated website on the Utopia server.
Although it must be completed, this is not a major deliverable and your team should not spend excessive effort on it.