Guidelines

Writing the Master's Project

This means that an extensive literature review is not needed in a project-based Capstone project. However, some research must be done to inform the project.

At a minimum finding from your research should support the problem statement and the need to create the project. In other words, the student has to identify a need for the proposed project and how the project will fulfill this need.

The Master's Project should have the standard sections of a research paper, each of which addresses basic questions into 50 - 60 pages. The outline should be 7-12 pages

1. Introduction

What is the project about? Computer Networking

Why is this an important research question? Because technology is the new way of employees. Computer technology is replacing the employees in the work places.

How will you analyze this issue?

2. Background

What do we already know about this issue? What is the history of this issue?

3. Statement of the Problem

A statement of the focus of the project, in other words, what problem with this project solve?

4. Purpose Statement

A statement of the purpose of the project

5. Objectives

Objectives of the project or a justification of why the study or project is needed or important - why it is worth doing.

6. Assumptions

Assumptions that you make related to the area of focus of the project or of the study - what things you assume are already true about the area of focus.

7. Limitations

Identify the limitations of the study or project - what won't be accomplished in this study. In other words, set the expectations of the proposed project or thesis study by delineating the boundaries. This also ensures a clear focus to the researcher.

8. Definition of terms

Define unique terms you will be using so that the reader shares the same meanings.

9. Methodology (or the Design of project)

Full design of project. This will be one of the larger chapters. Go into detail on the design. This includes the materials (software, databases, hardware, etc) to be used. This information needs to be detailed and it needs to be technical.

It will include schemas, schematics, hardware and flow diagrams and all procedures, such as work flow details and user interface descriptions of each screen (if applicable). This section will need a summary.

10. Implementation (this section can be part of the methodology chapter) budget, timeline, resources (people, etc.) This section will also need a summary

4. Discussion of Results

What are the main findings of the project?

In what ways do these modify/add to the existing literature?

Discuss how the implementation addresses the business issues discussed in the purpose and objectives sections. This section will need a summary

5. Conclusions

Summarize your project, including the outcomes, are the purpose results applicable to other projects. Identify how this project adds to the existing literate and research.

This section could contain a recommendations section. This could be anything from the next steps in the process to how others could implement your project

6. References

Which sources did you consult?

7. Appendix

This is an area for technical details, such as, Description of Datasets; detailed work flows, detailed budget or technical specification tables. Etc. What goes here are important details that are secondary to the paper.