16-03-2012, 05:03 PM
TABLES & -FIGURES
synopsis.pdf (Size: 2.42 MB / Downloads: 351)
The term 'Table', is meant for tabulatednumericaldata in the body of the report.All .
other non-verbal material used in the body of the report as charts,. graphs, maps,
photographs and diagrams may be designated as 'Figures'.
(a) A 'Table' or a 'Figure' including their caption should be accommodated within the
prescribed margin limits. It must appear on the page following the text where their
first reference has been made. .
(b) Tables and Figures one half or less in length may appear on the same page along
with the text. However, they should be separated from the text both above and below
by appropriate spacing.
© Two or more small tables or figures may be grouped if necessary in a single page.
(d) Unless colors are significant;Figures, Images are Tablesshould be printed on gray scale.
(e) The Figures caption is always appended at the bottom of the figure, while the Table
caption is included at the top of the table. (Please Note)
numbers. The rule for assigning such numbers is illustrated through an example. Eg:-
If a figure in Chapter 3 happens to be the fourth then assign Figure:?.4. Identical
rules apply for tables except that the word figure is replaced by the word Table.
[III] MANUSCRIPT PREPARATION
The sequence in which the Project Synopsis should be arranged is as f()llows:
(1) Cover Page (Refer Appendix 'A')
(i) Introduction [This may include the general introduction of the project, general
background, previous work done in this area (brief Jiterature survey).]
(3) Problem Definition .
This must consist of Project objective and Proposed Methodology.
(a) Project Objective (This must highlight the aims and objectives clearly indicating
the ideas and approachof the proposed work in not more than 200 words.)
(b) Proposed Methodology (This discusses the proposed path of implementation of
the project. A complete. block diagram must be given followed' by brief.
description of each block.)
(4) Theory (This must describe the related technology involved in the project,
mathematical concepts used, description of the algorithms, salient features of the
. proposed design etc.) .
(5) Software/Hardware Requirements and Specifications
(6) Module description (This must describe the proposed input, output and functioning
of each module in detail.)
(7) Data Flow Diagram (DFD)/Class Diagram & Use Case Diagram (Optional
depending on the type of the project)
DFD: O-level(Taking project as a whole)
--tTh:i-s-deseribes-the"flew-ef-cla-t-a-thre1fgh-iffi{Wffi-atiBfl-sys-
Class Diagram: High level class diagram (should only include domain level classes)
(This describes the static structure of a system by showing the system's classes, their
attributes, operations and relationships among classes.)
Use Case Diagram: (The main purpose of use case diagram is to shO\vwhat system
functions are performed for which actor.)
(8) Applications/Advantages! Limitations along with Proposed Cost (if required)
(9) Future Scope of the Project (This must highlight the utility of project in future.)
(10) References (Refer Annexure-B).
synopsis.pdf (Size: 2.42 MB / Downloads: 351)
The term 'Table', is meant for tabulatednumericaldata in the body of the report.All .
other non-verbal material used in the body of the report as charts,. graphs, maps,
photographs and diagrams may be designated as 'Figures'.
(a) A 'Table' or a 'Figure' including their caption should be accommodated within the
prescribed margin limits. It must appear on the page following the text where their
first reference has been made. .
(b) Tables and Figures one half or less in length may appear on the same page along
with the text. However, they should be separated from the text both above and below
by appropriate spacing.
© Two or more small tables or figures may be grouped if necessary in a single page.
(d) Unless colors are significant;Figures, Images are Tablesshould be printed on gray scale.
(e) The Figures caption is always appended at the bottom of the figure, while the Table
caption is included at the top of the table. (Please Note)
numbers. The rule for assigning such numbers is illustrated through an example. Eg:-
If a figure in Chapter 3 happens to be the fourth then assign Figure:?.4. Identical
rules apply for tables except that the word figure is replaced by the word Table.
[III] MANUSCRIPT PREPARATION
The sequence in which the Project Synopsis should be arranged is as f()llows:
(1) Cover Page (Refer Appendix 'A')
(i) Introduction [This may include the general introduction of the project, general
background, previous work done in this area (brief Jiterature survey).]
(3) Problem Definition .
This must consist of Project objective and Proposed Methodology.
(a) Project Objective (This must highlight the aims and objectives clearly indicating
the ideas and approachof the proposed work in not more than 200 words.)
(b) Proposed Methodology (This discusses the proposed path of implementation of
the project. A complete. block diagram must be given followed' by brief.
description of each block.)
(4) Theory (This must describe the related technology involved in the project,
mathematical concepts used, description of the algorithms, salient features of the
. proposed design etc.) .
(5) Software/Hardware Requirements and Specifications
(6) Module description (This must describe the proposed input, output and functioning
of each module in detail.)
(7) Data Flow Diagram (DFD)/Class Diagram & Use Case Diagram (Optional
depending on the type of the project)
DFD: O-level(Taking project as a whole)
--tTh:i-s-deseribes-the"flew-ef-cla-t-a-thre1fgh-iffi{Wffi-atiBfl-sys-
Class Diagram: High level class diagram (should only include domain level classes)
(This describes the static structure of a system by showing the system's classes, their
attributes, operations and relationships among classes.)
Use Case Diagram: (The main purpose of use case diagram is to shO\vwhat system
functions are performed for which actor.)
(8) Applications/Advantages! Limitations along with Proposed Cost (if required)
(9) Future Scope of the Project (This must highlight the utility of project in future.)
(10) References (Refer Annexure-B).