<< Project Title>>

<< Project Title>>. Supervisor <Name of the Supervisor Designation>.

2. Objective. Goal of the project to be clearly described in a single statement..

3. Motivation. Motivation behind the project. Use relevant statistical reports or pictures..

4. Introduction to the Domain. Introduction to the domain.

5. Project Description. Salient features and techniques involved in the project to be introduced with relevant information..

6. Base Paper. <Name of the author(s)> <Year of Publication>, “<Title of the Paper>”, <Publication Details> Example: D. Schwarz, H. Kloeden, and R. Rasshofer (2016), “Ko-TAG—Cooperative senso technology for traffic safety applications,” in Proc. Int. Workshop Intelligent Transportation, vol 2. no. 5, pp 245-250..

7. Supporting Paper 1. Contribution Methodology Outcome Challenges Future Scope.

8. Supporting Paper 2. Contribution Methodology Outcome Challenges Future Scope.

9. Inference of Literature Review. Base Paper To design a device such that it will reduce the incidents of accidents on roads and various premises, with subsequent reduction in loss of life and property Supporting Paper 1 To assess the driving safety indicator through making scores on driver background and driving habits synthetically. System architecture is explained in detail for the analysis process and three algorithms. Supporting Paper 2 To assess the driving behavior through dashboard data and analyze the behavior and send human readable vehicular information to the mobile phone. <Any other reference>.

10. Extraction from the Literature Survey for the proposed system.

11. Problem Definition. Description of problem identified..

12. Proposed Solution. Proposed solution / innovation with the technology to be used..

13. Proposed Solution - Justification. <Justify the need of the technology/algorithm to be used in the proposed system>.

14. Requirement Specification. FRONT END TOOLS BACK END TOOLS MARKUP LANGUAGES SCRIPTING LANGUAGES MIDDLE WARE TECHNOLOGIES IDE SIMULATION TOOLS NETWORK/WIRELESS TECHNOLOGIES ANY OTHER.

15. Requirement Specification - Justification. <Justify the need of the Software/Hardware components> Comparison table may be presented.

16. Architecture Diagram. Overall architecture diagram of the project Appropriate UML diagrams shall also be used to give pictorial representation about the overall components of the project.

17. Module Description. List and describe individual modules in different slides. Describe the functionality (User perspective) of each module. Describe the development strategy individual modules as developer perspective For each and every module, the input, the functional process (algorithm/strategy) and the output to be fed as input next module (interaction) should be explained diagrammatically using functional block diagram..

18. Database Design. Database schema for database oriented projects.

19. Algorithm Explanation. Explain the algorithm used – steps/psudocode/flowchart, in different slides.

20. Implementation. Explain the program logic (part of coding) used, in different slides.

21. Screenshots. Present the screen shots of work progress/deliverables of modules.

22. Conclusion and Future Scope. Conclude the work done Present the avenues for further development.

23. Details of Technical Paper Presentation / Publication.

24. References. 1. <Name of the author(s)> <Year of Publication>, “<Title of the Paper>”, <Publication Details> Example: Ivan Lequerica, Pedro M. Ruiz and Victor Cabrera (2010), “Improvement of Vehicular Communications by Using 3G Capabilities to Disseminate Control Information”, IEEE Network., vol. 24, no. 1, pp 32-38. Schwarz D, Kloeden H, and Rasshofer R (2016), “Ko-TAG—Cooperative sensor technology for traffic safety applications,” in Proc. Int. Workshop Intelligent Transportation, pp 245-250..

THANK YOU.