UniversityofZimbabwe

ComputerScienceDepartment
CT260/CT360ProjectGuidelines
PreparedbyZanamweN
CHAPTERONE
1.Introduction
1.1Background
Here you develop the theoretical and conceptual framework upon which the project is based. It is
appropriate to describe relevant data representations and algorithms. The developer must initiate
reader into the project. The developer must begin with a general overview and then narrow down
tospecificfocus.Thebackgroundpaveswayforthestatementofproblem.
1.2StatementofProblemorNatureoftheResearchProblem
The first stage of a project is to realize a problem and the problem has to be chronic. A problem
statement is a clear concise statement that spells out the problem to be solved and it also
PreparedbyZanamweN@20131
articulatesthevalueaddedifproblemissolved.Thestatementmustbebriefandnontechnical.
1.3PreviousandCurrentWork,MethodsandProcedures
This is an historical or conceptual survey of relevant work done in the area by previous
investigators. Each contribution must be accompanied by appropriate references to be listed in
the reference section. The developer must identify existing systems that were developed to
addressthecurrentproblemandhowtheyareinadequateorwhataretheirweaknesses.
1.4ProjectDescription/NovelCharacteristicsoftheResearch
This section presents a brief overview of new, extended or different functions, structure or
operation of the system. The developer must clearly show the novelty or newness of system to
bedeveloped.
1.5ResearchPurpose/ResearchObjectives/Aims
Developers are urged to focus on the statement to generate research objectives. Objectives are
evidenceoffocus/direction
1.6JustificationofProject/Rationale/Significanceofproject
Theoretical,practical,oreducationalimpactsonhardware,software,orusers
Rationaleaddressesamongotherissuesthefollowing:
Whytheresearchisnecessary
Whyitisimportanti.e.itsbenefitstotheusersandthecommunityatlarge
Expressingvalueofprojectoutputtotargetusers
1.7Organisationoftheproject/Summary/PresentationofResearch
This section gives an overview of the whole project that is what is going to be covered in each of
theforegoingchapters.
CHAPTERTWO
2. SystemSpecification
2.1.Introduction
Giveabriefintroductionaboutwhatthischaptercovers.
2.2.SystemFunctionalSpecificationorProblemDefinition
This is a detailed specification of functions performed by the proposed system, from an external
or user perspective, not from an internal or programmer viewpoint. Thus, the system is regarded
as a black box with various inputs and outputs related by the functions performed by the system.
Thedescriptionshouldbesufficientforanotherprogrammertoimplementthesystem.
PreparedbyZanamweN@20132
2.1.1FunctionalRequirements
List and briefly describe each of the functions which the system will be designed to perform for
its user: What the system will do. The requirements must be complete and should not be
ambiguous.
2.1.2NonFunctionalRequirements
List and describe each of the internal (self) and external (environment) limitations and/or
restrictions on the range of system functions: What will the system not do. DO NOT
INSULT/OFFENDTHEREADERBYINCLUDINGITEMSTHATWOULDNOTBEASURPRISE.
2.1.3SystemEvolution
The developer must outline assumptions on which the system is based, anticipated changes
duetohardwareandsoftwareevolutionandchangesinuserrequirements.
2.1.4SystemScope
This stage involves establishing the system boundary. A system boundary depicts the parts of
the original requirements that are to be computerised. The developer must realise that that the
boundary may or not may enclose all requirements. When setting up a system boundary the
developer must consider among other things, the available resources, user requirements and
other limitations in implementing the system. Further this section must give a description of
systemcomponentsandthesystemenvironment
2.1.5Prototyping
Developers may use this technique if they want to validate the requirements. Prototyping
involves developing a quick and dirty but still convincing model of the final system. The developer
must articulate the goals of prototyping, functions prototyped and results of the prototyping
process.
2.1.6UserInterfaceDesign
Give a detailed description of the system user interface including diagrams of all the ``work''
windows (or screens or panes), a table of operations for each work window, and precise
descriptions of each operation that the user would regard as unfamiliar. A work window is one
that contains data the user is editing, browsing or viewing. This section is required for all
programsthatengagetheuserinteractively.
2.1.7OtherUserInputs
Give a precise description of the other inputs to the system including source (human or storage)
syntax (format) and semantics (meaning). Give examples. This section is required for all
programsthatobtaininputfromtheirenvironmentnoninteractively.
2.1.8OtherUserOutputs
Give a precise description of the other outputs of the system including syntax and semantics.
PreparedbyZanamweN@20133
Correlate the outputs with the inputs and the functions performed. Give examples. This section
isrequiredforallprogramsthatobtaininputfromtheirenvironmentnoninteractively.
2.1.9SystemDataFiles
Give a precise description of the data files created or maintained by the system. Thus, for
example, you would include files in a database and you would exclude executable files and text
files.
2.1.10UserInterfaceSpecification
InterfaceMetaphorModel
UserScreens/Dialog
ReportFormats/SampleData
OnlineHelpMaterial
ErrorConditionsandSystemMessages
ControlFunctions
2.3.FeasibilityStudy
A feasibility study decides whether or not the proposed system is worthwhile. The goal of
feasibility study is to identify the existing system and note any problems associated with it,
establish if any practical solutions exist and determine whether it is worthwhile to implement
thesystem.Afeasibilitystudychecksthefollowing:
Ifthesystemcontributestoorganisationalobjectives
Ifthesystemcanbeengineeredusingcurrenttechnologyandwithinbudget
Ifthesystemcanbeintegratedwithothersystemsthatareused.
Thedevelopermustthereforeconductthefollowingfeasibilitystudies
2.3.1Economicfeasibility
Involves establishing whether it is possible to implement the system using the existing monetary
resources (hardware and human resources). Economic feasibility study also involves carrying
outacostbenefitanalysisforeachofthealternativesolution.
2.3.2TechnicalFeasibility
To a larger extent this involves assessing the knowledge and skills that the system developer
has and establishing whether it is possible to develop the system using the existing level of skills
andknowledge.
2.3.3.OperationalFeasibility
An operational feasibility study tries to figure out whether upon completion the system is going to
beusableintheintendedenvironment.
2.4.SystemPerformanceRequirements
PreparedbyZanamweN@20134
2.4.1Efficiency(speed,size,peripheraldeviceusage)
2.4.2Reliability
DescriptionofReliabilityMeasures(accuracy,precision,consistency,reproducibility,etc.)
Error/Failure Detection and Recovery (failure modes, failure consequences, error logging
andreporting,manualandautomaticrecoveryprocedures)
Allowable/AcceptableError/FailureRate
2.4.3Security
HardwareSecurity
SoftwareSecurity
DataSecurity
ExecutionSecurity(uservalidation)
2.4.4Maintainability
2.4.5.Modifiability
2.4.6.Portability
2.5 Conclusion
Giveachapterconclusion
CHAPTERTHREE
3.ProjectplanningandLiteratureReview
3.1.Introduction
Giveachapterintroduction
3.2.Projectplanningandscheduling
The project developer must clearly articulate the deliverables and milestones. Students can also
using project planning tools such as bar charts, project network charts, Gantt charts etc. Project
planningsoftwaremayalsobeused.
3.3.LiteratureReview
This is a historical or conceptual survey of relevant work done in the area by previous system
developers. Each contribution must be accompanied by appropriate references to be listed in the
reference section. The developer must identify existing systems that were developed to address
the current problem and how they are inadequate or what are their weaknesses. Further the
developer must identify process models that that will be used and a justification must be given
as to why certain process models have been chosen. The user might choose process models
such waterfall, spiral, incremental etc. Be sure to choose a process model that suits your
project.
PreparedbyZanamweN@20135
3.4.Conclusion
Giveachapterconclusion
CHAPTERFOUR
4. SystemAnalysisandDesign
This is a top level preliminary or provisional indication of the proposed system architecture and
flow. You should correlate system functions with system structure and interface specifications.
Further the developer should analyse both the existing and new system with the aim of obtaining
a fuller understanding of the system. The developer can use questionnaires or interviews or both
when investigating about the system. The developer must not use technical tools in the analysis.
At this stage, the developer can make use of the following tools: dataflow diagrams, decision
tables and trees, ERDs, sequence diagrams, use case diagrams, class diagrams, data
dictionary,petrinets,statetransitiondiagrams.
4.1.Introduction
Chapterintroduction
4.2.SystemArchitecture
4.2.1.DataFlowDiagrams(level1and2DFDs)
This is a hierarchical (or levelled) set of diagrams showing the flow of data elements into and out
of the functional units of the program, data stores and environmental sources and sinks.
Labelled arrows denote data flows. This diagram is complementary to the structure chart
describednext.
4.2.2.EntityRelationshipDiagram
This is a conceptual model of a system showing the entities and their attributes as well as the
relationshipsbetweenoramongentities.
4.2.3.SystemStructureChart(s)
This is a (set of) chart(s) showing the functional units of the system hierarchically organized to
show which units call, use or contain other units. Each interface between two units (a call) is
annotatedwithsmallarrowsanddataitemlabelstoshowthedataexchangedbetweentheunits.
4.2.4.SystemDataDictionary
This is a comprehensive dictionary of all the data items that appear in the system data flow
diagrams and the structure charts. At a minimum it contains, for each data item, its identifier,
any abbreviation used instead of the identifier, the name of the type of the data, and a definition of
the data item in the form of either a symbolic expression or a precise description. The most
PreparedbyZanamweN@20136
appropriate way is to come up with data dictionary for each and every technique that the
developerwouldhaveused.Thedatadictionaryshouldbepartofeveryproject.
4.2.5.EquipmentConfiguration
Describetheequipmentyouwillusetosupporttheoperationanddevelopmentofyoursystem.
4.3.SystemDataStructureSpecifications
4.3.1.OtherUserInputSpecification
4.3.1.1.IdentificationofInputData
4.3.1.2.SourceofInputData(NOTinputdevice)
4.3.1.3.InputMediumand/orDevice
4.3.1.4.DataFormat/Syntax
4.3.1.5.LegalValueSpecification
4.3.2.OtherUserOutputSpecification
4.3.2.1. IdentificationofOutputData
4.3.2.2. DestinationofOutputData(NOToutputdevice)
4.3.2.3 OutputMediumand/orDevice
4.3.2.4 OutputFormat/Syntax
4.3.2.5 OutputInterpretation(meaningofoutput)
4.3.3.SystemDatabase/FileStructureSpecification
4.3.3.1IdentificationofDatabase/Files
4.3.3.2(Sub)systemsaccessingtheDataBase(creating,updating,usingfrequency)
4.3.3.3LogicalFileStructure(recordformats,fileorganization,accessmethods,rationale,examples)
4.3.3.4PhysicalFileStructure(storagedevice,blocking,organization,access,etc.)
4.3.3.5DataBaseManagementSubsystemsUsed(internalorexternal)
4.3.3.6DataBaseCreationandUpdateProcedure(ifNOTbysystem)
4.3.4SystemInternalDataStructureSpecification
4.3.4.1.IdentificationofDataStructures
4.3.4.2.ModulesAccessingStructures(creating,updating,using)
4.3.4.3.LogicalStructureofData(format,organization,access,rationale,examples)
4.4.ModuleDesignspecifications
4.4.1.ModuleFunctionalspecification
4.4.1.1FunctionsPerformed
4.4.1.2ModuleInterfaceSpecifications(input/outputarguments/globalvariables/files)
4.4.1.3ModuleLimitationsandRestrictions
4.4..2ModuleoperationalSpecification
4.4.2.1LocallyDeclaredDataSpecifications(variabledictionary)
4.4.2.2AlgorithmSpecification(flowchart,pseudocode,decisiontable,etc)
4.4.2.3DescriptionofModuleOperation
PreparedbyZanamweN@20137
4.5.Conclusion
Chapterconclusion
CHAPTERFIVE
5ImplementationandTesting
5.1. Introduction
Chapterintroduction
5.1. Choosingthelanguage
List the programming languages or scripting languages you have used for the implementation of
yourprojectandgivereasonsforchoosingeachlanguage.
5.2.Choiceofenvironment
Indicate where applicable the databases that were used and justify why you chose for instance
Oracle instead of MySQL or vice versa. Indicate the operating system used and web servers and
otherwebauthoringtoolsusedanddonotforgettojustifywhyyouchosethosetools.
5.3.Languagespecificalgorithm
5.4.Efficiency
5.5.Correctness
5.6.Documentationofcode
5.7.Variables
5.8.Systemverification/testing
5.8.1.Items/FunctionstobeTested
5.8.2.DescriptionofTestCases
5.8.3.JustificationofTestCases
5.8.4.TestRunProceduresandResults
5.8.5.DiscussionofTestResults
5.8.6.EvaluationofUserSystem
5.8.6.1.ProtocolStudy
5.8.6.2.UserSurvey
5.8.6.3.RealTimeMonitoring
5.8.6.4.Interviews
5.9.Conclusion
Chapterconclusion
PreparedbyZanamweN@20138
CHAPTERSIX
6.Conclusions
6.1.Summary
6.2.ProblemsEncounteredandSolved
6.3.SuggestionsforBetterApproachestoProblem/Project
6.4.SuggestionsforFutureExtensionstoProject
REFERENCES
APPENDICES
Anyotherattachments
ProgramListing
Usermanual
CDs or DVDs containing the System and Documentation where necessary, provide
passwordsandusernamesforloggingintothesystem.
StyleandPolicyManualforSoftwareProjects
DearStudent
The aim of doing a project is to solve a real world problem using computer science skills at your
disposal. A software project is the outcome of a substantial effort. Its content and style will reflect
PreparedbyZanamweN@20139
on you, your supervisors and on the Computer Science Department. By adhering to the
standards set forth in the following pages you will be presenting your work in a professional
manner,tothecreditofallwhohavecontributedtoit.
Statementonplagiarism
The Computer Science Department takes plagiarism very seriously and will never ever tolerate
it. To the uninitiated, Plagiarism refers to the use of other peoples intellectual property (words,
ideas, diagrams, code etc) without appropriately acknowledging the sources of these materials.
This constitutes plagiarism whether it is intentional or unintentional and whether it is the work of
another or of you. Students are therefore strongly warned against downloading software projects
from the internet or getting them from other universities across the world and posing as if they
are the original developers of those projects. Supervisors must make an effort to ensure that
students submit plagiarism free projects by using the antiplagiarism software. It is also the
responsibilityofthestudenttomakesurethattheirworkisfreefromanyformofplagiarism.
RequirementsforProjects
Pleasenotethefollowing:
1)Thereportshouldbeprintedononesideofthepage,
2)Numbereachsheetconsecutivelyatthebottomofthepage.
3) Headings: Chapter titles start on a new page. Chapter numerals should be Arabic, not
Roman numerals. Type the chapter number and title in upper and lower case, flush left, at the
top of the report page leave an extra space and then begin the text. Since you will have several
levels of subheadings, distinguish one level from another in a consistent way, such as (1, 1.1,
1.2,2,2.1,2.1.1,2.1.2,2.2).Avoidhavingmorethanthreelevelsofsubheadings.
1.Textformatting
The font size must be 12. Subscripts or superscripts must not be smaller than 9 point.
Students must note that projects using oversized or small font sizes will not be accepted.
These requirements apply only to body text implying that students can use font sizes greater
than 12 for chapter headings. The same typeface and size must be used throughout the text.
Students are recommended to use a standard, clearly legible font for example Times New
Roman or Arial. Exotic fonts will not be accepted. Bold, italics, and underlines are acceptable,
but only if they remain in the same character size as the rest of the text. If you have any
questionsregardingaparticularfont,pleasebringanoriginalexampletothecoordinators.
Thetextoftheprojectmustbepresentedwithfulljustificationontheprescribedmargins.
Linespacingmustbe1.5
ChangelanguagetoZimbabweanEnglish
Donotuseabbreviatedwordssuchascant,dont,&,ie,etc
PreparedbyZanamweN@201310
Nooneortwosentenceparagraphs
Students must place caption below Figures and above Tables, their numbering must
showchapterforexampleatableinchapter2canbegivenacaptionTable2.1
Margins: margin refers to the blank space surrounding printed text. The mechanics of
binding require that projects have at least a 1.5inch margin on the binding side of the page and a
1inch margin on the remaining three sides. No margin may be greater than 1.5 inches. Please
note that the page number is included in the text area and must not violate the margins. The
margin above the page number must be at least 1 inch. Insufficient margins seriously affect the
readability and appearance of the project. Students must note that projects that do not meet
these requirements will not be accepted. Margin requirements apply to all materials to be bound
withintheproject,includingappendices.
Be consistent in style, that is, do not use more than one font type in the same document or
emboldenotherheadingswhileothersarenot.
Do not use bullets when numbering sections and subsections and when numbering
subsections, your numbering must reveal the chapter for example, 4.3.2 means the second
subsectioninthethirdsectionofchapter4
Donottostartasentencewithanumber
Thefinalcopiesmustbeneatlyexecutedandcorrectinspelling,punctuation,andformat.
The print must be of the same intensity throughout. Corrections on the submitted copies
(i.e.,whiteout,correctiontape,interlineations,etc.)willnotbeaccepted.
2.Pagination
Studentsmustnotethattwoseparatenumberingsystemsareusedinformattingprojects:
2.1 PreliminaryPages
The Title Page is page one but is not numbered so the page two is numbered ii. Small roman
numerals ( ii, iii, iv, etc.) are used for all other preliminary pages, including subsequent pages of
the Abstract, Table of Contents, List of Figures, List of Tables, Acknowledgments, Dedication,
etc. The numbers must appear in the upper righthand corner of the page at least 1 inch from the
edge of the paper to allow for the standard margin. A Preface is optional but if it is included, it
mustbelistedintheTableofContents.
2.2 Text
The text is numbered with Arabic numerals, without embellishment or punctuation (i.e., initials,
hyphens, running heads or footers, lines across the page, etc.,). Page numbers must be centred
at the top of the page or placed in the upper righthand corner so that they are at least 1 inch
from the top and right edges of the paper. Only whole numerals are acceptable and must be in
the same typeface and location throughout. Pages numbered 56a, 56b, etc., will not be
accepted. Every page must have a page number. However, the number will not appear on the
followingpages:
a.Thefirstpageoftext.(Thesecondpageispage2.)
b.ThefirstpageofeachChapter,thefirstpageoftheBibliographyorReferencesCited,
c.ThefirstpageofeachAppendix.
PreparedbyZanamweN@201311
d. Minor sections within chapters are not considered title pages and must carry a page
number.
3. Illustrations
Illustrations refer to informational material that illustrates and enhances the text. Figures and
tables are all examples of illustrations and are either inserted throughout the text, appearing as
soon as possible after the references to them have been made, or grouped at the end of each
chapter. Whichever method you choose, you must use it consistently for all the figures, tables,
or other illustrations included. Students are discouraged from including illustrations which are not
referredto,implyingthatyoumustrefertoeachandeveryillustration
All illustrations must conform to the margin requirements. Please consult a project coordinator
for help with an oversize illustration. If an illustration continues for more than one page,
subsequent pages are numbered consecutively with the rest of the text. The illustration number
followed by the word continued appears placed appropriately. (EXAMPLE: Fig 4.3 (continued)).
All illustrations, including those appearing in appendices, must be numbered, titled, and listed in
the appropriate preliminary pages. They may be numbered consecutively throughout the text or
within each chapter or appendix. If you choose to number them within each chapter or section,
they must be identified with the chapter or section number. For example: Figure 2.2_(Title),
Table III.3_(Title). Illustrations in previously published material which you are presenting as
appendicesmayretaintheoriginalidentificationandshouldnotbelistedinthepreliminarypages.
4. CaptionsandLegends
A caption consists of the illustration number (e.g., Table 2:) and its title. Captions may be single
spaced and must all be in the same typeface. If illustrations are reduced, the caption and page
number must remain the same size as the text. If illustrations appear horizontally (i.e., landscape
format) in the text, the top must be on the left margin, and the caption, must also appear
horizontally. The page number remains vertical (i.e., portrait format), consistent with the rest of
thetext.
Tables
Tables contain information placed in a columnar arrangement and are the only illustrations
numberedandcaptionedabove.
Figures
Figures may include DFDs, ERDS, photographs (original or photocopied), charts, diagrams,
graphs, and drawings. They must all be listed in the preliminary pages in a List of Figures. Figure
titles in the List of Figures may be abbreviated, if necessary. Figure numbers and captions
appearbelowthefigure.
5. Listofreferences
A List of References is a comprehensive list of all sources used by the project developer and is
required at the end of each project, appearing immediately after the text. The Department of
PreparedbyZanamweN@201312
Computer Science will accept any recognized format but it must be used consistently
throughout. Full citation must appear in alphabetical order at the end of text. Note that all sources
must appear in the text and in references. No source must be included in the reference list that
hasnotbeendirectlyreferredtointhebodyoftheproject.
ThenextsectionspresenttheHarvardreferencingformat.
Students should not confuse referencing and a reference list which are two different but related
concepts. Referencing refers to citing sources inside the body of the project and the standard is
tojustincludethesurnameoftheauthorandthedateofpublicationasfollows:
If authors surname forms part of sentence, the year follows in parentheses as given
below:
As illustrated by Sipser (1996), theory of computation deals with complexity theory and
computabilitytheory.
If authors name is not part of sentence, both the author and year are shown in
parentheses:
Theoryofcomputationdealswithcomplexitytheoryandcomputabilitytheory(Sipser,1996)
Whenreferringtoaparticularpage,thisisgiveninparenthesesaftertheyear:
Theoryofcomputationdealswithcomplexitytheoryandcomputabilitytheory(Sipser,1996:56)
Direct quoting a full paragraph: here you have to indent paragraph and use difference
format,thereisnoneedforquotationmarks.Theauthor,yearandpagemustbeprovided
If author has more than one publications in different years, use chronological order in
reference list but if publications are in the same year, use letters a, b after the year to
distinguish(Cohen,2006a),(Cohen,2006b)
Whennoauthorisgiven,appropriatebodyorinstitutionshouldbeused:
(UniversityofZimbabwe,2006)or(WorldBank,2007)
Whenthereferenceisnottheoriginalsource:
Date(2005)citedinNavatheandElmasri(2006),
Citingmorethanoneauthor:
Iftherearetwoauthors,bothshouldbegiven:
NavatheandElmasri(2003)averthat
If there are more than two authors, all should appear the first time, thereafter, author et al. (year).
Notethattheorderofauthorsmustbestrictlyadheredto
Referencingabbreviations(inthebodyoftheproject)
oAuthornotgiven(Anon)
oDatenotgiven(n.d.)
oNoplace,sineloco(s.l.)
oNopublisher,sinenomine(s.n.)
Reference list: a reference list on the other hand is an elaborate list of sources that you referred
toanditmustincludethetitlesofbooksorarticlesandpublishers
1. Author(s)oreditorsofarticles
2. Dateofpublication(inbrackets)
3. Titleofarticle(insinglequotes)
PreparedbyZanamweN@201313
4. Titleofjournal(underlined)
oVolume,partnumber(whereavailable)
oPagenumbersofarticles
5.Titleofbook(underlined)
oPlaceofpublication
oPublisher(s)
6.Bookwithoneortwoauthors:
oNavathe,Elmasri(2001).DatabaseSystems.London:MacMillan
7.Author,I.(year)Title.[Website](datewhenthewebwasviewedordownloaded)
8.Surnameofjournalist,Initial.(year)titleofarticle.NameofNewspaper.Date,page
9. Author, Initial. (Year) Title of paper. Paper presented at name of conference, place of
conference,monthofconference
6.Appendices
Appendices may consist of material that is related to, but not appropriate for, inclusion in the
main body of the project. This includes user manuals, code listing, CDs or DVDs etc. They
appear after the List of References and must be titled. They are listed, along with their titles, in
the Table of Contents, not on a separate list of appendices. Pagination is continuous with the
project, and the first page of each appendix is treated like the first page of a chapter in the text
(i.e.,counted,butnotnumbered).
Appendix material need not be retyped unless it does not meet the above requirements for
margins and readability. Material may be reduced as long as it remains legible. However,
appendix titles and page numbers must remain fullsize it is recommended that they be added
to the page after reduction. Any illustrations appearing in the appendices which are not from
previouslypublishedmaterialmustbecaptionedandplacedintheappropriatelist.
7. Arrangementofpages
All projects submitted to the Computer Science Department must include the following in the
orderlisted:
1.Titlepage
The Title Page must include the correct project title, the correct degree title, the correct year, and
the students first and last names conforming exactly to University records. The title page must
also include the name of the supervisor and the year the project was done. Further, the title page
must include the name of the university and department. See sample below. All text appearing
ontheTitlePagemustbecentredonthemargins.
2. Dedication(optional)
3. Declaration(Mandatoryseesamplebelow)
PreparedbyZanamweN@201314
4. Abstract
An abstract is a single paragraph in which you summarize the essence of your project: why the
software was developed, what problem was solved, how the problem was approached, what
major results were found, what major conclusion were drawn. It would be unusual for an
abstracttobelongerthantwopages.
5. TableofContents.
Each project must have only one Table of Contents listing all of the chapters or main sections
and their appropriate page numbers. The listing of subsections within chapters is optional. Only
major sections, whether called chapters or not, will start on a new page sections within
chapters must be contiguous with the previous text. The numbering and wording of titles and
headings in the Table of Contents must be consistent with the text. All preliminary pages must
be included in the Table of Contents except the Title Page and Declaration Page. Each appendix
must be identified separately, including a title, and must be listed in the Table of Contents, NOT
on a separate List of Appendices. Appendices are paginated consecutively with the text. Pocket
materials must also be included in the inside back cover and must be listed after the
appendices.StudentsmustincludeaCDorDVDwiththeexecutablesystem.
6. ListofFigures
If your project includes any figures you must identify them in a List of Figures, in the preliminary
pages.
7. ListofTables
If your project includes any tables you must identify them in a List of Tables in the preliminary
pages. Each List of Figures, List of Tables, or List of Illustrations included in the preliminary
pages must appear on a separate page and must be numbered in small Roman numerals
centred at the bottom of the page, at least one inch from the edge of the paper, in the order in
which they are to be bound. All illustrations must be numbered and titled. Captions must appear
on the appropriate list in the preliminary pages. These may be abbreviated titles if the full title is
toolongforinclusion.
8. Glossary(optional)
9. ListofAbbreviations(optional)
10.Preface(optional)
11.Acknowledgments.
Acknowledgments recognize the people to whom you are indebted for guidance and assistance
and those to whom you are grateful for any special or nonroutine aid. Acknowledgments should
be expressed simply and tactfully. They should be oneandonehalf or doublespaced and
conform to margin requirements. Acknowledgments are numbered consecutively with the other
preliminary pages with small Roman numerals centred at the bottom of the page. Please note:
Acknowledgmentsand/orDedicationarenotlistedintheTableofContents.
12.Dedication(optional).
13.Mainbodyoftheproject.
PreparedbyZanamweN@201315
14.BibliographyorListofReferences.
15.Appendices(listyourcodehereandtheusermanual).
16. Pocket Materials (CDs containing the software, remember to provide logon details
andinstructionsonhowthesystemoperates)
DeclarationSample
I, Ngonidzashe Zanamwe, do hereby declare that this project is the result of own investigation
and research, except to the extent indicated in the Acknowledgements and References and by
acknowledged sources in the body of the report, and that it has not been submitted in part or full
foranyotherdegreetoanyotherUniversityorCollege.
Signature............................................................................Date.........................................
TitlePageSample:
DevelopmentofaMembershipManagement
InformationSystemforusebyChurchOrganizations
By
NgonidzasheZanamwe
Aprojectsubmittedinpartialfulfillmentofthe
requirementsforthedegreeofBachelorofBusiness
StudiesandComputingScience
2002
PreparedbyZanamweN@201316
ComputerScienceDepartment
UniversityofZimbabwe
Supervisor:Dr.Hapanyengwi
PreparedbyZanamweN@201317