The title of your work by Your Name Submitted in partial fulfilment of the requirements for the award of the degree of Your Degree of the University of Portsmouth April 2007
The title of your work
by
Your Name
Submitted in partial fulfilment of the requirements for the award of the degree of Your Degree of the University of Portsmouth
April 2007
i
CopyrightCopyright © 2010 Your Name. All rights reserved.
The copyright of this thesis rests with the Author. Copies (by any means) either in full, or of extracts, may not be made without prior written consent from the Author.
iv
Table of ContentsCopyright iPreface iiiTable of Contents ivList of Tables viList of Figures viiNomenclature viiiAbstract ix
Chapter 1 Introduction 10
1.1 A Major Section 101.1.1 A Major Subsection 102.1 Another Major Section 113.1 Report Outline 11
Chapter 2 A Review of your subject area and topics12
4.1 Blah blah blah 125.1 Bleh bleh bleh 126.1 Chapter Summary 12
Chapter 3 Artefact Design 14
7.1 Introduction 148.1 Design Methodology 149.1 Requirements 1410.1 Proposed Solution 1411.1 Summary 15
Chapter 4 System Implementation 16
12.1 Introduction 1613.1 Blah Blah 1614.1 Interesting Problems 1615.1 Summary 1716.1 Testing and Evaluation 1817.1 Introduction 182.1.1 Testing Summary 1818.1 Evaluation 183.1.1 Requirements Review 194.1.1 Artefact Review 1919.1 Testing and Evaluation Summary 19
Chapter 5 Conclusion 20
20.1 Introduction 20
v
21.1 Summary 2022.1 Conclusions 215.1.1 Key Points 21
Chapter 6 References 22
Appendices 23
Something interesting 24Something Else 25
viii
NomenclatureA number of key terms are used throughout this document and are defined here:
A Nomenclature Section can be a useful eay of defining common terms without having to include a lot of bracketed terms in your document. If you prefer to introduice terms when they are first used remove this section.
ix
AbstractThis abstract should be the last thing you write, it is a summary of the introduction that is only a few sentences long. At most it should be a couple of paragraphs. It must be very succinct.
10
Chapter 1 Introduction
This chapter introduces the overarching themes of this report and places the motivation for the work into context. Thereafter, the rationale and goals defined for the investigation of the project are discussed, followed by a summary of the overall project. Finally, an overview of the dissertation is given on a per-chapter basis.
Your words begin here at the high level, then dive into detail in sections and subsections...
1.1 A Major Section
Your words go here...
1.1.1 A Major Subsection
Your words go here...
1.1.1.1 A Minor Subsection
Your words go here...
Chapter 1 - Introduction 11
a b
c
d
y
x
Figure 1: An example diagram that shows four connected things
1.2 Another Major Section
This section shows you how the numbering works.
1.3 Report Outline
The rest of this report is organised as follows:
Chapter 2 reviews the state-of-the-art in blah blah...
Chapter 3 describes the design of blah blah...
Chapter 4 describes the implementation of blah blah...
Chapter 5 demonstrates how blah blah performed in testing...
Chapter 6 closes the report, reviewing the work undertaken and draws conclusions about key parts of the work that was undertaken. Finally, future work is discussed with particular focus on blah blah...
12
Chapter 2 A Review of …
This chapter discusses the state-of-the-art of blah and blah and any blah considered during the analysis and design phase of this project. The investigation served n purposes: firstly, we wished to identify blah blah blah (section Error: Reference source not found); and secondly we wished to establish bleh bleh bleh (section 2.2). Finally, section 2.3 summarises the chapter.
2.1 Blah blah blah
blah
2.2 Bleh bleh bleh
bleh
2.3 Chapter Summary
In Chapter 1 we proposed blah blah blah.
Chapter 2 - A Review of 13
In this chapter the state-of-the-art was categorised into blah (section x) and blah (section y). Observations were made on the systems reviewed (section z), and the relevance of the state-of-the-art to blah blah was summarised (section w).
The next chapter presents the design of blah blah, which is a system intended to blah blah.
14
Chapter 3 Artefact Design
3.1 Introduction
In Chapter 2 we identified that blah blah...
This chapter describes the design of blah blah, a system that blah blah. First, the chapter describes the project’s design methodology (section 3.2), and system requirements (section 3.3). A proposed solution is then discussed (section 3.4), followed by a blah blah....
3.2 Design Methodology
The design and development of blah blah
3.3 Requirements
The main purpose of blah blah
Chapter 3 - Artefact Design 15
3.4 Proposed Solution
Blah blah blah at a high level, then create subsections that go into detail
3.5 Summary
This chapter described the high-level requirements and design of a system that blah blah blah. The chapter started by describing blah. The proposed solution was then discussed in section blah followed by blah in section blah, etc.
Blah blah is covered in further detail in Chapter 4 which describes the implementation of blah blah.
16
Chapter 4 System Implementation
4.1 Introduction
Chapter 3 presented the design of blah blah. This chapter builds on that design by detailing the key aspects of the blah blah implementation.
The chapter is organised as follows. Section x provides an overview of blah blah, etc. Finally, in Section y, a summary of the chapter is given.
4.2 Blah Blah
Write like the wind.
Chapter 4 - System Implementation 17
4.3 Interesting Problems
During the project implementation several issues were identified that merit discussion. This section addresses those topics, which are blah, blah and blah.
4.4 Summary
This chapter described the implementation of blah blah, which was based on the design described in Chapter 3. The implementation was introduced in section x and blah blah blah. Once the general implementation details had been introduced, several interesting implementation problems were addressed in section q, including the detailed coverage of blah blah.
18
4.5 Testing and Evaluation
4.6 Introduction
Chapters 3 and 4 described the design and implementation of blah blah, a system that blah blah blah. In this chapter, we present a testing method and its results that show blah blah blah. The chapter is organised as follows: Section x introduces blah and describes blah. Next, section y presents blah, etc.
The results of the tests are summarised in section z, before the solution is evaluated in section qqq.
Write what you did, why you did it and how you did it here.
4.6.1 Testing Summary
In total over n tests were executed. Each test was blah blah blah, and this data was then used to blah. The tests illustrate that blah blah. In the next section, this is evaluated and the extent to which it supports the thesis is discussed.
4.7 Evaluation
Chapter 1 highlighted the problem of blah blah blah. Chapter 2 reviewed the state-of-the-art in blah and blah. Chapter 3 identified
4.5 -Testing and Evaluation 19
a set of technical requirements underpinning the development of blah, and the implementation of a blah blah was described in Chapter 4.
The testing described in section x demonstrates that blah blah blah. In this section therefore, we evaluate the implementation and discuss issues in the underlying technologies that the implementation has highlighted.
4.7.1 Requirements Review
This section reviews the implemented platform, referring back to the requirements to identify the extent to which each has been fulfilled, and reflecting on their relevance for future work. Each of the requirements is reintroduced and discussed in turn.
Refer back to each specified requirement and discuss...
4.7.2 Artefact Review
In this section, we evaluate the implementation of blah blah and review the prevailing issues that were highlighted by the implementation, which were blah, blah and blah
4.5 -Testing and Evaluation 20
4.8 Testing and Evaluation Summary
This chapter introduced blah and blah. In section x a series of tests were described which demonstrated blah blah.
An evaluation of blah blah was then presented in section y. Section z revisited the requirements described in Chapter 3 and identified that blah blah blah. Finally in section q the aspects of blah blah were discussed.
21
Chapter 5 Conclusion
5.1 Introduction
In this Chapter, we first summarise the work described in this report (section x). Then we draw a number of conclusions about key parts of the work undertaken in section y, and finally in section z we discuss future work and how we see Semantic Web technologies helping support projects such as this one.
5.2 Summary
This is a summary of each chapter intro and summary
Chapter 1 introduced blah.
Chapter 2 reviewed the state-of-the-art in blah and blah. Blah was introduced and blah described. The potential for blah blah was highlighted.
Chapter 3 describes the design of blah blah. The separate functions of blah blah that support the requirements were then described in more detail, including blah and blah.
Chapter 4 described the implementation blah blah.
Chapter 5 - Conclusion 22
Chapter 5 presented a series of tests that demonstrate blah blah.
5.3 Conclusions
The aim of this project was to blah blah. We chose to focus on blah blah.
We then designed and implemented a system that could:
blah
blah
blah
blah
These combined capabilities blah blah blah.
In Chapter 1 we state the general hypothesis that blah blah blah. We have tested this thesis by blah blah.
5.3.1 Key Points
Discuss future work as you go.
5.3.1.1 Your key Point
Blah point one discussed.
5.3.1.2 Your key Point
Blah point two discussed.
Appendices 26
Something Else
Blah blah
A table Of InterestSome DataThat NeedsTo BeCommunicated
Blah blah
Table 1: An interesting table