Project with title signal generator using matlab and the all information. 

DETAILED STRUCTURE OF FINAL YEAR PROJECT PLANNING REPORT

General Instructions:

1. The final Project Planning Report should be submitted to candidate's supervisor for review well in advance as per the instruction given by supervisor.

2. The final Project Planning Report should be spiral bound (Two Copies) and it should be submitted at least two (working) days before the final presentation.

3. The front cover of the report should be in printed form along-with the MEC logo. The required print spacing on front cover page is as follows.
Top: 1.0 inches, Left: 1.5 inches, Right: 1.0 inches, Bottom: 1.0 inches.

4. Only one side of the page should be printed. The other side should be left blank.

5. The font used should be TIMES NEW ROMAN, 18 Points for chapter number and chapter title, 16 points for sections, 14 points for subsections and 12 Points for the running text with 1.5 line spacing between two consecutive lines. Footnotes shall be single spaced typing.

6. Use "Justification" alignment for the running text or body of the text.

7. Use "Center Justification" for chapter headings.

8. Use "Left Justification for Section Heading / sub-section headings"

9. The page number should be in footer at middle.

10. Only the reports according to the above format will be considered and graded. The details about the structure of project report are enclosed.

PROJECT PLANNING REPORT FORMAT

TABLE OF CONTENTS
Contents
DECLARATION vi
APPROVAL FORM vii
ACKNOWLEDGEMENT viii
ABSTRACT ix
TABLE OF CONTENTS x
LIST OF FIGURES xi
LIST OF TABLES xii
LIST OF ABBREVIATIONS xiv
LIST OF SYMBOLS xv
1. INTRODUCTION 1
1.1 Background of the Project 1
1.2 Project Objectives 1
1.3 Project Limitations 1
1.4 Overview of the Project Report 1
2. METHODOLOGY 3
3. LITERATURE REVIEW/THEORY 4
4. BUDGETING AND PROJECT MANAGEMENT 5
4.1 Project Budget 5
4.2 Project Schedule 5
4.3 Risk Management 5
5. DESIGN AND ANALYSIS 6
5.1 System Initial Design 6
5.2 Technical Requirements 7
5.3 Schematic Diagram 7
5.4 System Design & Analysis 7
6. CONCLUSIONS 8
REFERENCES 9

Appendix A 121. INTRODUCTION

Write a general introduction about the content of this chapter. At least two sentences will suffice.

Your introduction should provide the reader with a general introduction to the topic area. The writer should introduce clearly and succinctly, the rationale for choosing the topic under discussion. The introduction should provide the reader with a definitive statement of the problem under consideration and the potential benefit of the application. The author should indicate the objectives of the project and the general rationale for choice of methodology (if required).

1.1 Background of the Project

This should give a brief introduction on why a project is chosen. Set the project into its wider context and background. Explain its relevance and importance. What is the need?

1.2 Project Objectives
This will give an outline on what are the expected outputs to be produced in the project. List the main objectives of your project. These should correspond to your original brief.

1.3 Project Limitations
Limitations of the project should be listed out here.

1.4 Overview of the Project Report
This is an optional section which is briefly outlining the structure and content of this project work report.
[Note: this template assumes a "software development" type project, but even these vary considerably and you should feel free to use whatever report structure you consider most appropriate for your own project. However, we expect all reports to have the same "outer" structure with only the "middle" sections differing substantially. Thus all reports should start with an Introduction and finish with a Conclusions section. We also expect all reports to have a Project Management section, although this need not have any particular position in the section order.

2. METHODOLOGY
Indicate the systematic approach you have adopted to take you from the problem definition through to your solution. In particular explain the reasons for choosing the approach.

3. LITERATURE REVIEW/THEORY
Every Honors project needs to do a certain amount of "research" into relevant problem areas, appropriate solutions and the technologies that support them, and also a review of existing examples covering these areas or other projects that have tackled similar problems. Try to illustrate how this research has led to or justified the decisions you've taken.

4. BUDGETING AND PROJECT MANAGEMENT
The subsections shown below are only one possible structure for this section covering the project management and project budget.
4.1 Project Budget
This could include the tentative cost of different components/parts of your project and an approximate total cost of the project.
4.2 Project Schedule
This could include the work breakdown structure, Gantt chart, and comments about how well you managed to keep to the original plan, or what adjustments were necessary.
4.3 Risk Management
Risk identification, analysis and mitigation plan. Did any risk actually materialise?

5. DESIGN AND ANALYSIS
Write a general introduction about the content of this chapter. At least two sentences will suffice.

6. CONCLUSIONS
The Conclusions section should be a summary of the aims of project, what has been learnt and what has been achieved during planning stage. An effective set of conclusions should not introduce new material. Instead it should briefly draw out, summarize, combine and reiterate the main points that have been made in the body of the project report and present opinions based on them. Be honest and objective in your conclusions.

Attachment:- PROJECT PLANNING REPORT.rar