| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Guidelines for Preparing the Final Manuscript for the Capstone Project The manuscript include the following information in the order listed:
Margins The first page of the Abstract, Acknowledgements, Table of Contents, List of Tables, List of Figures, Glossary and new chapters must have top margins of 2 inches; all other pages must have top margins of 1.5 inches. Bottom margins must be 1 inch except at the ends of chapters or other major sections where the page may not be full. Left-hand margins of all pages must be 1.5 inches. Left and right margins in the text must be fully justified (flush left and flush right). Page numbers The title page and the signature page must not contain any page numbers. Lower case Roman numerals must be used on all other pages preceding the main text, beginning with iii for the Abstract. Arabic numerals must be used for all subsequent sections, beginning with 1 for the Introduction, the first page of the main text. Page numbers must be placed at the bottom center of the page. Fonts and spacing To create the title page and the signature page, use the templates; do not change the fonts or spacing from these templates. The manuscript must be typed in Times New Roman font size 12, except where specified otherwise. For example, headings for the Abstract, Table of Contents, List of Tables, List of Figures, Glossary, chapters in the main text (beginning with the Introduction), and Appendices must be typed in bold Times New Roman font size 16; headings for these sections must be followed by three blank lines. All paragraphs must be indented 0.17 in (0.422 cm). All text must use line spacing of 1.5, i.e., 1.5 times that of single spacing. Punctuation at the ends of sentences must be consistent throughout the manuscript; a single space after punctuation is preferred. Chapters, sections and subsections Each chapter must start on a new page. Chapters must be sequentially numbered in Arabic numerals. The chapter headings must be in bold Times New Roman font size 16. Sections within a chapter must be numbered with the chapter number prefix (e.g., the sections in Chapter 4 would be numbered as 4.1, 4.2, and so on). A similar numbering scheme applies to subsections. Further levels of sectioning are discouraged. However, if you need to use them, use section headings with no numbers. Section headings must be typed in bold Times New Roman font size 14, and subsection headings must be typed in bold Times New Roman font size 12. There must be 1.5 blank lines before and after each section heading and subsection heading. Appendices must be numbered alphabetically. Each Appendix must have a header (with the same font and size as a chapter heading), e.g., Appendix A. The UML notations used in this manuscript Figures and tables Figures and tables must be centered on the page. They both must have appropriate captions and be numbered sequentially (in Arabic numerals) throughout the entire manuscript (e.g., Figure 1 in Chapter 2, Figure 2 in Chapter 5, Table 1 in Chapter 4 and so on). Captions (no bold face) for figures and tables must use the following format, and must be typed below the figure or table, centered with respect to the figure or table: Figure 1. <<caption>> Table 3. <<caption>> Bibliography/references The IEEE publication format must be used for references. The Bibliography section must list all books, journal articles, conference or workshop articles, technical reports, and theses. Bibliographical references must be listed alphabetically with respect to the last name of the first author and numbered consecutively. All listed references must be cited in the text by using the citation number of the reference in the Bibliography. The format described below must be used for references (Times New Roman font size 12). Books
Example: #. H.V. Vliet, Software Engineering: Principles and Practice (Second Edition), John Wiley and Sons, 2002. Journal articles
Example: #. J. Wing, “Writing Larch Interface Language Specifications”, ACM Transactions on Programming Languages and Systems, Vol. 9, No. 1, 1987, pp. 1-24. Conference or workshop articles
Example: #. K. Periyasamy and J. Chidambaram, “A Method for Structural Compatibility in Software Reuse Using Requirements Specification”, Proceedings of the IEEE Computer Software and Applications Conference (COMPSAC), Washington D.C., Aug 1997, pp. 426-433. Technical reports and thesis
Example: #. V.S. Alagar and K. Periyasamy, “Real-Time Object-Z: A Language for the Specification of Real-Time Reactive Systems”, Technical Report TR-12, Department of Computer Science, Concordia University, Montreal, Canada, June 1996.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
University of Wisconsin-La
Crosse 1725 State Street La Crosse, Wisconsin 54601 (608) 785-8000
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||