The best structure to write subject

The best structure to write subject

Executive Summary/Abstract

Executive Summary (ES) is a one-page explanation that explains to the reader the problem, how it has been tackled, and what the outcomes are. Although it is placed as the first page after the cover page, however, it is normally written at the end of project, when everything is clear! As the name is applying, it is a short summary for the executive management of your project, here the supervisor or the evaluation panel, to let them understand in a glance what the project is about, how it has been done and what the conclusion is.

If the project is a research-based project, usually, Executive Summary is replaced by “Abstract” title. However, the main theme remains similar, largely.

Executive Summary

- It is placed as the first page after the cover page

- It is normally written at the end of project, when everything is clear!

- It is a short summary to show:

• what the project is about,

• how it has been done,

• and what the conclusion is.

- It is NOT an explanation on the report structure!

I have seen many reports within which the students have confused between Executive Summary and Introduction. Be careful on this issue and look the hints on these two to understand their differences.

Introduction

This chapter of your report provides a background of the project, states, in general terms, what the report is about and how it has been structured. Introduction can be divided to subsections such as Overview, Background, and Report Architecture. As you can see below, introduction has a clear-cut difference with the Executive Summary/Abstract. However, I have seen many reports with a transposition of Introduction and ES.

 Literature Review

Although this section mainly applies to the research-based projects, however, it is a good idea to have it in the normal projects as well. In this chapter, you should acknowledge the previous works on the area of the project in order to show their main outcomes, strengths, and spaces for improvement. Consequently, you can show how your project has been built upon the previous ideas and works and how it would contribute to add more to this background.

Methodology

This chapter depicts how you have applied the subjects that we discussed in in chapter 4. Students, sometimes, refer only to the tools that they have used and the subjects that they have studied as their methodology. However, you should not write this chapter, aftermath! Methodology is something that you have to decide on during the early stages of your project. As a result, you can write this chapter as soon as you made your decision. This was one reason, among many, that I mentioned that report writing was an ongoing activity and should not be postponed to the last minute.

Solutions

This chapter can be considered as a subsection to the methodology chapter or as an individual one. Whichever way you choose, you have to clearly state that why you have taken this specific approach to develop the system. If there are more than one solution to your problem, name these solutions and talk about their pros and cons and then explain the reasons behind your decision to take one not the others. For example, you have to explain that why you have used a web-based system and not a desktop one.

Requirement Management

In this chapter, show the project requirements as we discussed in chapter 5. Use the classification that was used or other classifications that you have studied. But, this is important to depict the requirements clearly. Do not forget to pay proper attention to the functional requirements. Try to write this chapter when you finished the activity or at least draft its contents, otherwise, you may loss lots of data when you start writing it at the end of the project.

Analysis

Depending on your methodology, this chapter would contain use case modeling or data flow analysis. Whichever is the case, show the analysis steps and try to use proper figures (e.g. UML diagrams) to show the general view of the system. If you have restrictions on the word count of your report, then provide the main analysis here and move the details to the appendices of your report.

Design

Depending on your methodology, this chapter would contain different materials. However, structuring it as three subsections can be a good idea.

Software Design In this subsection, you should provide your software design. I did not discuss software design in details as it is beyond the scope of this book, and you can find enormous resources about the subject (see the bibliography for instance). However, you should show the system architecture, decompositions, and modularity in this section. If you followed an OO method, then, you may provide package model, class model, and interaction model in this chapter, as well.

User Interface Design

You should introduce the User Interfaces (UI) in this chapter or show a sample of which and explain the way that you have designed it, then, leave the details to the appendices. You can use the approach that I advised you in chapter 6 to combine the UI design with use case description.

 Database Design

 If your project is a database application, I advise you to be as generous as you can with the explanation of your data model and database design. In this subsection, you can provide the ERD and then the normalized version of your database design. Providing the details of your tables can give your project, more flavor and would show your profession. However, you can move some samples of triggers and stored procedures, if you have any, to the appendices section.

 Implementation

Implementation chapter should focus on the codes. In addition, you should present the general architecture of implementation. Provide samples of codes. Explain algorithms used. If you have a considerable amount of code, then either provides them through a supplementary media or as one the appendices.

Testing

Testing chapter should show how the test process has been implemented, in general, and how the verification/validation techniques have been applied, in particular. Samples of test cases and test data explanation should be provided here. Importantly, test results, the outcome not the detail, should be provided as well. You can provide details of the test process as one of the appendices.

Conclusion and Future Works

Although it is usually a short chapter, however, conclusion and future works chapter is the distillation of your report. It should show the main outcome of your project.You should critically discuss the outcomes of your project, and point out your opinion on the results and outcomes. Try to be neutral at this stage and look at the outcomes as an outsider.

Bibliography/References

To clarify, bibliography is the list of resources that you have consulted with for your project but not directly cited, while, references is the list of resources that you have cited.

Most of departments have their suggestion for using bibliographical/citation style. However, in some cases you might not receive any specific suggestion. In this case, choose a style that you are already familiar with such as APA or Harvard citations and bibliography style. Fortunately, most of word processors, e.g. MS Word, can provide you with tools, which support several common citations and bibliographic styles.

 Appendices

Well, the name is pretty much reflecting the content, and hence, there is no need to talk more about it. In addition, in the previous sections I addressed those parts of report that can be extended more by moving material to appendices section, wherever it was appropriate