INTER OFFICE NOTE From: Acadetic Cell To: All HODs (B. Tech.) No. SRMGPC/Academic/ION/2016-17/181 al January 2017 ECT ALOT! B {For 2014-18 Batch] 1. The finalization of project topic and subsequent formulation of the project problem generally takes a very, long period in the final. year (VII semester) Project Labs. The semester finally ends up with Project Synopsis Preseatation in the month of Oct/Nov., without initiation of any actual physical working on the project, Final year students are also involved in numerous placement activities (during VII/VIII Sem), therefore at times; the adequate time and attention (as requited) is not given to B. Tech, Project work. 2, In view of this, HODs are requested to initiate the process of Project Allotment from VI semester onwards, Please refer to guidelines for the conduct of Project Lab attached herewith, 3. Kindly note that all:the activities in Project Lab should be planned as per the time frame mentioned in the guidelines. 4, Deadlines for the submission of documents related 10 the above lab are clearly mentioned. HOD/Project Coordinators are requested to adhere to these deadlines and should not wait for reminders from the Academic Cell. , 5. IONs for dofaulters will be issued (by Academic Cell), in case of non-submission of documents (w. 1. t deadlines mentioned) by respective departments 6. For efficient evaluation of documents prepared by student teams in project work (i.e. Pre-Synopsis Reports, ‘Synopsis Reports, Progress Reports, Final Project Report, Presentations, Posters etc.) following points should be taken into care by Project Coordinator(s) as well us Project Guides: (@ Each and every documents/reports prepared by student teams should bs thoroughly examined by respective Project Guide, Thereafter, Project Guide should instruct the students for necessary comrection/changes (if any) ‘or approve these documents for submission to respective Project Coordinators. (©) The final assessment of the documents/teports (submitted by students after approval of Project Guides) should be evaluated by a panel consisting of HOD and Project Coordinator(s) and marks to be awarded. It is hereby clarified that Project Guide should not evaluate any documents/reports submitted by students (©) It has been observed in past that assessments of reports were not supported with remarks/comments (to Justify the transparency of marks deduction) by the evaluator. Further, in certain cases the reports were directly evaluated and marked by Project Guides. To ensure a fair and transparent assessment HODs and Project Coordinator(s) should be cautious about such malpractices (@) It is necessary that Project Guide should be present during the presentation of their project team. These presentations (given by student teams) should be assessed by Project Coordinators and HODs/Senior Faculty members of the department (except respective Project Guide). The assessment of presentation should be made in separate assessment sheets (as per the format attached herewith) by all panel members individually. (©) Its to be noted by all coordinators that marks as well as remarks/comments (in the reports/presentation assessment sheets) should be written by pen only.7. All the assessment records/filed documents should be completely endorsed by Project Coordinators and HODs (wherever necessary). Note: - HODs should ensure that the above instructions have been read and unijerstood by all the faculty members of the department for proper implementation. Department Office Incharges should take the signatures of all the faculty members (to ensure that this document has been read by all) and Keep it as record in their department, (Prof. RK. Jaiswal) \ DirectorPage 1 of 7 GUIDELINES FOR THE CONDUCT OF PROJECT LAB Project Allotment & Assessment [1] Introduetion ‘The project work by the final year undergraduate engineering students is the most important part of their course curriculum, It provides them opportunity to apply their innovative ideas for the unique application of technology for the real world, A blend of the energy of the youth and mature supervision of the faculty members can produce high quality end product that can not only be useful for the college but also for the society. From this point of view, we propose the following procedure for the allotment, supervision and assessment of the project. The scheduling and assessment of the project work in VI & VIL semester is suggested in the following paragraphs- {Il} General Guidelines (1) Following guidelines should be followed for selection of a new project proposal- (@) Preferably, it should be an original idea or any recent idea from technical-magazine, internet, or a technical journal (research paper). College has a good resource of technical Journal subscriptions in the library, students should be encouraged to take maximum usage of them to surf new project ideas. . (b) It should not be a repetition of earlier projects done in the department; however it may bea feasible extension of any previous year’s project. (©) The standard and quality of projects should be so maintained such that atleast few of the good projects should be of standard that they may be forwarded for presentations in atleast national/interational level technical seminars and conferences or could be forwarded for publication in international journals/conferences. (Preferably, maximum twolthree students in a group will be allowed to work for a project. (2) It is recommended to allot atleast 5 good projects from the previous batch 10 the current batch students to workout any feasible enhancement of those projects. (3) Before the submission of the synopsis, students have to submit a Pre-Synopsis Write-Up (one page documentation) during the second/third week of the initiation of this lab. The detailed contents of this write-up are explained later. (A) On-the basis of assessment of this write-up, the HOD/Project Co-ordinator approves or disapproves a project. Upon approval, the students are required to submit a copy of Synopsis report for the project (the detailed guidelines and format for the submission of Project Synopsis is attached). (S)There may, be some projects which can be approved with certain changes/modifications and some may also be rejected. In both the cases, students have to submit the pre-synopsis write-up again within 7 days, (© The, submission of synopsis is followed by the presentation activity in the next three weeks, where each group of students will give a seminar on their proposed project work, the duration of which may not exceed 20 minutes. (7) The, changes/modifications suggested (as decided by the Project Panel/Project Co-ordinator(s)) during the presentation should be incorporated in the Projects through the Project Guides,Page 2 of 7 (8) A proper schedule for the presentation of project groups should be prepared and displayed well in advance. If a student is absent during such presentation as per schedule, he/she should be assessed later on with 50% weightage in this seminar assessment [II] Detailed Action Plan ‘The action plan for the lab is now Phase-I: During the VI" Semester. Phase-II: During the VII" Semester. The activities have been distributed in such a manner that the work of synopsis preparation , submission and evaluation is proposed to be completed during Phase-I (i.e. ‘VI semester). Synopsis presentation, followed by initiation of Project working and subsequent progress monitoring-I to be completed in the Phase-Il (i.e. VIE semester). reated into two phases as ‘Schedule Progress in Project Phase-I:-(VI Semester) During the last week of Jan. & © Addressing of class by the HODs/Project Co- week of Feb. ordinators for initiation of Project Lab during the ‘semester. * Briefing and Introduction of project areas to the students by the HOD/Project Co-ordinators. * Students to decide their working groups, respective areas of work. Details of the same should be collected from students. © A list of faculty members of the department along, with their respective areas of specialization for Project should be displayed on the department Notice Board, Students may contact the respective faculty members for guidance. * Briefing of students for preparation of ‘Pre- synopsis write-up’ by HODs/Project Co-ordinators. Submission to Academic Cell (a) List of Area of specialization of faculty members (©) Copy of Notice mentioning the deadline for submission of Pre-Synopsis Reports by students. ‘© Student Groups have to submit A Pre-Synopsis, \Write-Up (one page typed document) which should include the following- Area of work, Proposeid title, Type of Approach (Software Based/Hardware or Working Model/Both. Software & Hardware Model/Study & Analysis Based); Concepts/Ideas; Objectives; : General Block Diagram of the Model; Requirements (optional); Name of the Team Members; During the last week of FetDuring the 1" & 2" week of Mareh During the last week of March Submission to Academic Cell During the 2" & 3" week of April Page 3 of 7 * Students should mention clearly at the end of this write-up, the important references i.e, source from where they have taken the idea for the project. They should also indicate if the idea is suggested by a particular faculty member. © Evaluations of Pre-synopsis write ups _ by HODs/Project Co-ordinators. by writing ‘comments/remarks and putting signature while awarding marks on the reports. © Discussion with students on this write-up and feedback (if any) to be given for modification. © Topic approval/disapproval to be made on the above basis. On spot feedback should be given to the student related to the weak points and suggested updations by Project Co-ordinators. * Students have to re-submit the topic, in-case of changes, within 7 days. © The allotment of Project Guides can be now made for the finalized/approved Projects topics. ‘This allotment is to be governed strictly by the HODsProject Co-ordinators on the basis of area of specialization, © Students whose topics are finalized should be notified thereafter to submit the synopsis report upon discussion with this respective Project Guides. Students should be instructed and given necessary guidelines for preparation of Project Synopsis Report’ (Refer attached guidelines and format attached in Appendix ‘A’ & ‘B’), (@ List of Project Titles (with description of type of model, Area of work) along with Student University Roll No., Names of Students and Project Guides. (b) Previous Year Projects taken up during this session for enhancement should be highlighted. (©) Notification for submission of Project Synopsis Reports by students, * Submission of Synopsis Report by the students to Project guides for correction and approval. * Project Synopsis should be thoroughly checked by respective Project Guides before giving approval for submission in the department. * Submission of Project Synopsis to Project Co- ordinators (only after approval by the respective Project Guides).Submission to Academic Cell During the 3" week of May During the last week of May Submission to Academic Cell Following activities can be initiated “by students during sunimer vacations Phase-lIl:- (VII Semester) During the 1" & 2" week of Commencement of Classes Submission to Academic Cell During the 3" - 6" week of Commencement of Classes Page 4 of 7 (a) A load Chart of ‘B. Tech, Project Guidance’ of respective departments, (b) List of Marks Awarded on Pre-Synopsis Reports. © Assessment of Project Synopsis by Project, Co-ordinators in consultation with HODs. © Remarks/comments should be mentioned in Synopsis Reports (at the requisite location of errors/anomalies) by the Project Coordinators (w. r +. the assessment done) along with their signatures after awarding marks during the evaluation. © Assessment of the feasibility of the project as well as capability of student to finish it. List of Marks awarded on Synopsis Reports. © After submission of synopsis, student teams may regularly contact their Project Guides for further work. + They should also become familiar with the software platform, which they have proposed to use in their project work. © Students with hardware/working modules may go for purchase of components, © Discussion on evaluated ‘Project Synopsis Report" with students by Project Co-ordinators. * Necessary corrections/modifications to be incorporated, * Display of schedule for ‘Project Synopsis, Presentation on departmental notice boards (@) Finalized list of Project Titles (with description of type of model, Area of work), Student University Roll No., Names of Students and Project Guides. (6) Load chart of ‘B. Tech, Project Guidance’ (in case of any revisions), (©) Schedule of synopsis presentation, (@ List of Marks on Project Synopsis Reports (in case of any revisions). * Conduction of Synopsis Presentation in respective Project Lab sessions (refer format in Appendix 1c. © This Presentation should be (of ‘at least 15-20 minutes) which is to be delivered by the student project teams followed by an exhaustive Question/Answer session,During the 7" week During the 8-11" week Submission to Academie Cell During the 12" & 13" week Page 5 of 7 V. Important. (a) During the presentation in Project Lab it is mandatory that in addition to other faculty members (if any) both the Project Co-ordinators should be present for evaluation, (b) It is mandatory for Project Guides to be present during the presentations but will not be given the evaluation sheet to award the marks. (© All the Project Co-ordinators are requested to maintain the records of individual assessment (containing marks and comments) carried out by faculty members present during the presentation, * Feedback of the presentation performances to the student teams in class by Project Co-ordinators. # Repeat Presentations by defaulters. * Monitoring of the progress in project work of the students. + Students with hardware projects/mechanical models should start up with the necessary testing & fabrication, * Students with software projects should be ready with the necessary algorithms/flowcharts for simulation/implementation/coding. * Display of Presentation schedule for ‘Project Progress Monitoring-P” (a) Schedule of Project Progress Monitoring-I. (b) Notification for submission of Project Progress Reports-I by students. © Student Groups have to submit a Project Progress Report-I (Write-up: one page typed document) which should include the following- Project Title Type of Model (Software Based/Hardware or Working Model/Both Software & Hardware Model/Study & Analysis Based); Project Objectives (his should be appended with a Para to justify how many objectives are achieved as result, along with the percentage of total work completed.) Progress in Work (after approval of Project Synopsis); Difficulties (if any); Name of the Team Members & Project Guide(s); © Assessment of the progress (of students) by Project Coordinators/HODs should be made by evaluatingSubmission to Academic Cell Page 6 of 7 the progress reports, * tis followed by conducting _ presentations (of at- least 10-15 minutes duration) during the lab session (refer format in Appendix ,‘D*) along with demonstration of any prepared hardware or software module (which are developed during this period) by the students. * Total marks of the Project Progress, Monitoring-1 should be awarded (by Project Co-ordinators) on the basis of marks awarded on the Progress Report + subsequent Assessment made during the progress discussions in presentations. * On spot feedback should be given to the students related to the weak points and necessary updations should be suggested i -List of Marks awarded on Project Progress Monitoring-I. During the 14" week Submission to Academic Cell A copy of Finalized Internal Marks List of Project Lab. [IV] Procedure for Allotment of Project Guides (1) HODs in consultation with the Project Co-ordinators should prepare a list of project guides along with their respective areas of specialization, (2) The allotment of Project Guides to the student teams should be made on the basis of the Policy. [Please refer IOM (Ref, No.SRMCEM /Academic/IOM/2011-12 /223 102" March, 2012] (3) HODs should take a verbal feedback at the end of every month from the students regarding their progress in project work and the consultation they are getting from their respective Project Guides. (4) Any previous year project forwarded to students of current batch for enhancement should be allotted to same faculty as Project Guide under whose guidance the project ‘was made previously. {V] Guidelines for Project Guides (1) It is mandatory for students to report to their respective guides at least twice in a week. Project Guides should keep a record of such attendances. They should be regularly updated with the progress of their teams. (2) Project Guides should ensure that all the team members of the group should be reporting together at the time of the discussion. 3) Students should be asked to prepare a note-book to keep a track of for their project work and subsequent discussion with their guides. Upon every meeting with the Project Guides, the minutes of the discussion as well as next targeted assignment to be ‘undertaken should be clearly mentioned in the note-book date-wise, (4) Project Guides should help their teams in deciding the platforms as well as the requirements for their projects based upon the feasibility and practical constraints. (5) Each and every document prepared by student teams in project work i.e. Synopsis, Progress Reports, Final Project Report, Presentations, Poster etc. shoilld be thoroughlyPage 7 of 7 checked by Project Guides prior to giving any approval for final submission of the document fo Project Co-ordinators, to avoid clashes during award of marks. (6) The marks awarded by the Project Guides (on the performance of the students in a team) should be based on the working carried out during the semester, which includes parameters such as: discussions/reporting done by an individual team and overall sincerity of the students in completing the project work. [Vi] Internal Assessment Criteria A general criterion of intemal assessment out of 50 is given below- SNo. | Assessment Marks @_| Pre-Synopsis Wiite-up 05 @_| Synopsis Report Submi 15 G)__| Synopsis Presentation ae 15 @_| Project Progress Report & Monitoring-1 10 (5) __ | Marks awarded by Project Guides 05 (Prof. R. Director Maiswal)UIDELINES FOR PREPARATION OF B.TECH. PROJECT SYNOPSIS : CE sf ME ‘The detailed guidelines and formats for preparation of B-Tech. Project Synopsis report is explained in the succeeding paragraphs:- 1] GENERAL TYPING INSTRUCTIONS (A) (a) Standard A4 size (297mm x 210mm) paper should be used for preparing the report. (b) Tables and figures should conform to the margin specifications (ie, inline with the text), Large size figures should be photographically or otherwise reduced to the appropriate size before insertion, (2) General Page Layout:- | (a) The margins of every page of the report should be as follows Top:-1” Bottom: 1" Right: 1" Lefts - 1.5" () To ensure that the margins are correct: | Header: 0.5" Footer: - 0.5" All the data/text should fit_within the above specified margin (©) requirements (including tables, figures, graphs etc.). Full paper points of diagrams/image should confirm to the sure margins as specified above. (@ Right Header Project Title (In Italicized Font) Name of Department, College. (Eg: IT DEPARTMENT, SRMGPC, Lucknow] (Right Footer Page Number (© Left Footer (3) Other specifications will be as under: (a) Font Type = Times New Roman (b) Chapter _ Center/Right Aligned, Bold and Underlined with Mt Headings Font Size 18. (©) Sub Heading __ Bold & Font Size 14 (may be underlined if required) | (a) Contents - Font Size 12 (e) Paragraphs - Justified (f) Line Spacing Ls (g) Single line spacing should be used for typing Long Tables; References. (h) Foot notes/contents within header/footer can be 9 or 10 point size (ic. should be less than normal text, @_ The Title of the Project should be in ‘Title case’ or ‘ALL CAPS’, {0] TABLES & FIGURES ‘The term ‘Table’, is meant for tabulated numerical data 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’.omy Uv} (a) A ‘Table’ or a ‘Figure’ including their caption should be accommodated within the ribed margin limits. Jt should appear on the page following the text where their fifst reference has been made. (b) Tables and Figures one helf of less in length may appear on the same page along, with the text. However, they should be séparated 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 Tables should be printed on gray scale, (©) The'Figutes caption is always appended at the bottom of the figure, while the Table caption is included at the top of the table. (O Tables and figures appearing anywhere in the project should bear appropriate numbers. NUMBERING INSTRUCTIONS (a) Minimam font size is 10-point for page nos. and should be kept consistent throughout the text. (b). Equations appearing in the report should be numbered serially, however this should be followed consistently throughout the text. All the equations should be center aligned. (¢) Equations should be referred within the text, throughout their respective equation simbers. MANUSCRIPT PREPARATION ‘The sequience in which the Project Synopsis should be arranged is as follows: (1) Cover Page (Refer Appendix A’) (2) Introduction [This may include the general introduction of the project, general background, previous work done in this arca (brief literature survey).} (8) Problem Definition This should consist of Project objective and Proposed Methodology. (a) Project Objective (This should highlight the aims and objectives clearly indicating the scope of the project, the ideas and the approach of proposed work.) (b) Proposed Methodology (This discusses the proposed path of implementation of the project. A complete block diagram should be given followed by description of each block.) (4) Theory (This head should describe the related technology involved in the project, mathematical concepts used, description of the algorithms, salient features of the proposed design etc.), Please ensure that ‘Theory’ should not be used as Chapter Heading. Heading should be given as appropriate with respect to topic/content described. () Software/Hardware Requirements and Specifications (This may include the basic requirements and specifications for the hardware/sofiware setup, depending upon whether the project is a Hardware model/Software model or both).(6 Applications/Advantages/ Limitations along with Proposed Cost (This should cover the various merits and demerits of the project. The advantages should be elaborated as Applications, while limitations serve to be a source for future improvements), (7) References (Refer Appendix-B). Note:- 1. Material downloaded and copied from internet or any Research Paper should be edited properly in the sense to remove comic forits, shadings, hyperlinks etc. 2. Any other point not covered in (1)-(9) can be incorporated at the department level |PROJECT SYNOPSIS On PROJECT TITLE PROJECT TITLE PROJECT TITLE, PROJECT TITLE Submitted for Partial Fulfillment of Award of BACHELOR OF TECHNOLOGY In Electronics & Communication Engineering (2018) By [Name(s) of the Student] Under the Guidance of [Name of the Project Guide] SHRI RAMSWAROOP MEMORIAL GROUP OF PROFESSIONAL COLLEGES, LUCKNOW Affiliated to Dr. APJ ABDUL KALAM TECHNICAL UNIVERSITY, LUCKNOW1) (21 (3) [4] 6) [6] 7 (8) [9] REFERENCES $. Ariponnammal and S. Natrajan, “Transport Phenomena of Semiconductors,” Journal of Medical Physics, Vol. 42, No.5, pp. 421-425, 2005. P. Banerjee, M. Haldar, D. Zaertsky, and R. Anderson, “Overview of 4 Compiler for Synthesizing Matlab Programs onto FPGAs,” IEEE Transactions on Very Large Scale Integration (VLSI) System, Vol. 12, No. 3, pp. 312-324, March 2004. J. Jores (2006), “Contact Mechanics,” Cambridge University Press, U.K., Chapter 6, pp. 144-164. C. Rovers Eds. “Recent Advances in DSP Techniques,” 2” ed. Taylors Frances Group, USA, 2006. R. Smith (2008), “Contact of Cylindrical Surfaces involved in a Non- Steady Motion,”. Available Online at: hitp://www.casphy.cenm.edu/homepage.html HD. Cheng, “Image Features Extraction using Volterra Filters,” Proc. of 5" IEEE Intemational Conference on Machine Vision and Attificial Intelligence, Beijing, China, pp. 42-57, October, 2009. A. K, Barnard, “A Study of Stereo Matching Algorithms for Mobile Robots,” A Thesis Report for University of Bath, U.K., 2005. J, P, Williamson, “Non-Linear Resonant Granit Devices,” US Patent 3 624 12, July 16, 1990. Motorola Semiconductor Data Manual, Motorola Semiconductor Products Inc., Phoenix, AZ, 1987.GUIDELINES FOR PREPARATION OF B.TECH. PROJECT SYNOPSIS CS LIT ‘The detailed guidelines and formats for preparation of B.Tech. Project Synopsis report is explained in the succeeding paragraphs:- (1) GENERAL TYPING INSTRUCTIONS a) @) QB) a (a) Standard Ad size (297mm x 210mm) paper should be used for preparing the report. (b) Tables and figures should conform to the margin specifications (jc, inline with the (ext). Large size figures should be photographically or otherwise reduced to the appropriate size before insertion. General Page Layout: (a) The margins of every page of the report should be as follows. Top:-1" Bottom: 1" Right:- 1” Left: - 1.5" () To ensure that the margins ate correct: Header: -0.5” Footer: - 0.5" All the datwtext should fit within the above specified margin (c) requirements (including tables, figures, graphs ete.). Full paper points of diagrams/image should confirm to the sure margins as specified above. (d) Right Header Project Title (In Italicized Font) Name of Department, College. (@) Left Footer [Bg.: IT DEPARTMENT, SRMGPC, Lucknow] (© Right Footer Page Number Other specifications will be as under: (a) Font Type ‘Times New Roman (b) Chapter _ Center/Right Aligned, Bold and Underlined with Headings Font Size 18. (©) SubHending Bold & Font Size 14 (may be underlined if required) (a) Contents - Font Size 12 (e) Paragraphs - Justified (© Line Spacing - 15 (g) Single line spacing should be used for typing Long Tables; References. (h) Foot notes/contents within header/footer can be 9 or 10 point size (Lc. should be less than normal text. (@ The Title of the Project should be in ‘Title case’ or ‘ALL CAPS’. (]) TABLES & FIGURES ‘The term ‘Table’, is meant for tabulated numerical data 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’.(0) {IV} (a) A ‘fable’ or a ‘Figure’ including their caption should be accommodated within the eseribed margin limits, It should appear on the page following the text where. their firstreference 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 i (©) Two or more small tables or figures may be grouped if necessary in a single page. (@) Unless colors are significant; Figures, Images are Tables should be printed on gray scale. (c) The Figures caption is always appended at the bottom of the figure, while the Table caption is included at the top of the table. (f Tables and figures’ appearing anywhere in the project should bear appropriate numbers NUMBERING INSTRUCTIONS (a) Minimum font size is 10-point for page nos. and should be kept consistent throughout the text. (b) Eqvations appearing in the report should be numbered serially, however this should be followed consistently throughout the text. All the equations should be center aligned. (c) Equations should be referred within the text, throughout their respective equation numbers. MANUSCRIPT PREPARATION ‘The sequence in which the Project Synopsis should be arranged is as follows: (1) Cover Page (Refer Appendix ‘A*) 2) Introduction [This may include the general introduction of the project, general background, previous work done in this area (brief literature survey).] (3) Problem Definition This should consist of Project objective and Proposed Methodology. (a) Project Objective (This should highlight the aims and objectives clearly indicating ‘the scope of the project, the ideas and the approach of proposed work.) (b) Proposed Methodology (This discusses the proposed path of implementation of the project. A complete block diagram should be given followed by description of each block.) (4) Theory (This head should describe the related technology involved in the project, mathematical concepts used, description of the algorithms, salient features of the proposed design etc.). Please ensure that ‘Theory’ should not be used as Chapter Heading. Heading should be given as appropriate with respect to topic/content described (8) Software/Hardware Requirements and Specifications (This may include the basic requirements and specifications for the hardware/software setup, depending upon whether the project is a Hardware model/Software mode! or both). (© Module description (This should describe the proposed input, output and functioning of each module in detail.) (1) Data Flow Diagram (DFD)/Class Diagram & Use Case Diagram (Optional depending on the type of the project) DED; 0-level (Taking project as a whole) (This describes the flow of data through information system.) 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 show what system functions are performed for which actor.) (8) Applications/Advantages/ Limitations along with Proposed Cost (This should cover the various merits and demerits of the project. The advantages should be elaborated as Applications, while limitations serve to be a source for future improvements). (9) References (Refer Appendix-B). Note:- 1. Material downloaded and copied from internet or any Research Paper should. be edited properly in the sense 10 remove comic fonts, shadings, hyperlinks etc. 2, Any other point not covered in (1)-(9) can be incorporated at the department level.PROJECT SYNOPSIS On PROJECT TITLE PROJECT TITLE PROJECT TITLE, PROJECT TITLE Submitted fot Partial Fulfillment of Award of BACHELOR OF TECHNOLOGY In Electronics & Communication Engineering (2018) By [Name(s) of the Student] Under the Guidance of [Name of the Project Guide] SHRI RAMSWAROOP MEMORIAL GROUP OF PROFESSIONAL COLLEGES, LUCKNOW Affiliated to Dr. APJ ABDUL KALAM TECHNICAL UNIVERSITY, LUCKNOW( 2 (3) [5] [6] 7] (8] [9] REFERENCES S. Atiponnammal and S. Natrajan, “Transport Phenomena of Semiconductors,” Journal of Medical Physics, Vol. 42, No.5, pp. 421-425, 2005. P, Banerjee, M. Haldar, D. Zaertsky, and R. Anderson, “Overview of 4 Compiler for Synthesizing Matlab Programs onto FPGAs,” IEEE Transactions on Very Large Scale Integration (VLSI) System, Vol. 12, No. 3, pp. 312-324, March 2004. J. Jores (2006), “Contact Mechanics,” Cambridge University Press, U.K., Chapter 6, pp. 144-164, C. Rovers Eds., “Recent Advances in DSP Techniques,” 2m ed.,Taylors Frances Group, USA, 2006. R. Smith (2008), “Contact of Cylindrical Surfaces involved in a Non- Steady Motion,”. Available Online at: http://www.casphy.cenm.edu/homepage.html H. D. ‘Cheng, “Image Features Extraction using Volterra Filters,” Proc. of 5" IEBE International Conference on Machine Vision and Artificial Intelligence, Beijing, China, pp. 42-57, October, 2009. A.K. Barnard, “A Study of Stereo Matching Algorithms for Mobile Robots,” A Thesis Report for University of Bath, U.K., 2005. J. P. Williamson, “Non-Linear Resonant Granit Devices,” US Patent 3 624 12, July 16, 1990. Motorola Semiconductor Data Manual, Motorola Semiconductor Products Inc., Phoenix, AZ, 1987.UIDELINES FOR PREPARATION OF B.TECH. PROJECT SYNOPSIS EC, EL EN EE ‘The detailed guidelines and formats for preparation of B.Tech. Project Synopsis report is explained in the succeeding paragraphs:- [1] GENERAL TYPING INSTRUCTIONS | (1) (a) Standard Ad size (297mim x 210mm) paper should be used for preparing the report (b) Tables and figures should conform to the margin specifications (ic. inline with the text), Large size figures should be photographically or otherwise | reduced to the appropriate size before insertion. (2). General Page Layout: (a) The margins of every page of the report should be as follows ) Top:-1" Bottom :- 1° Right: - 1”. Left: - 1.5” (b) To ensure that the margins are correct: Header: - 0.5" Footer: -0.5” ‘All the data/text should fit within the above specified margin (©) requirements (including tables, figures, graphs etc.): Full paper points of diagramsfimage should config to the suré margins as specified above, (@) Right Header Project Title (In Italicized Font) Name of Department, College. {Eg.: IT DEPARTMENT, SRMGPG, Lucknow] Right Footer Page Number (©) Left Footer (3) Other specifications will be as under: (a) Fént Type = ‘Times New Roman ) (b) Chapter _ Center/Right Aligned, Bold and Underlined with ~ Headings Font Size 18. (©) SubHeading —_* Bold & Font Size 14 (may be underlined if required) (@) Contents = Font Size 12 (©) Paragraphs ~ Iustified (Line Spacing ets: (g) Single line spacing should be used for typing Long Tables; References. | (h) Foot notes/éontents within header/footer can be 9 or 10 point size should be less than normal text. (i). The Title of the Project should be in ‘Title case’ or ‘ALL CAPS’. [I] TABLES & FIGURES ‘The term ‘Table’, is meant for tabulated numerical data 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 should appear on the page. follow the text where their 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, (c) Two or more small tables or figures may be grouped if necessary in a single page. (@) Unless colors are significant; Figures, Images are Tables should be printed on gray scale, (©) The Figures caption is always appended at the bottom of the figure, while the Table caption is included at the top of the table. (f Tables and figures appearing anywhere in the project should bear appropriate numbers, [11] NUMBERING INSTRUCTIONS (a) Minimum font size is 10-point for page nos. and should be kept consistent throughout the text. (b) Equations appearing in the report should be numbered serially, however this should be followed consistently throughout the text, All the equations should be center aligned. (c) Equations should be referred within the text, throughout their respective equation numbers, [IV] MANUSCRIPT PREPARATION ‘The sequence in which the Project Synopsis should be arranged is as follows: (1) Cover Page (Refer Appendix ‘A’) (2) Introduction [This may include the generat introduction of the project, general background, previous work done in this area (brief literature survey).] (3) Problem Definition ‘This should consist of Project objective and Proposed Methodology. (a) Project Objective (This should highlight the aims and objectives clearly indicating thie scope of the project, the ideas and the approach of proposed work.) (b) Proposed Methodology (This discusses the proposed path of implementation of the project. A complete block diagram should be given followed by description of each block.) (4) Theory (his head should describe the related technology involved in the project, mathematical concepts used, description of the algorithms, salient features of the proposed design etc.). Please ensure that “Theory” should not be used as Chapter Heading, Heading should be given as appropriate with respect to topic/content described. (5) Sofbware/Hardware Requirements and Specifications (This may include the ba requirements and specifications for the hardware/software setup, depending upon whether the project is a Hardware model/Software model or both).(6) Applications/Advantages/ Limitations along with Proposed Cost (This should cover the various merits and demerits of the project. ‘The advantages should be elaborated as Applications, while limitations serve to be a source for future improvements). (7) References (Refer Appendix-B). Note:- 1. Material downloaded and copied from internet or any Research Paper should be edited properly in the sense to remove comic fonts, shadings, hyperlinks etc, 2. Any other point not covered in (1)-(9) can be incorporated at the depariment level.PROJECT SYNOPSIS On PROJECT TITLE PROJECT TITLE | PROJECT TITLE, PROJECT TITLE Submitted fot Partial Fulfillment of Award of BACHELOR OF TECHNOLOGY In Electronics & Communication Engineering (2018) By [Name(s) of the Student] Under the Guidance or [Name of the Project Guide] SHRI RAMSWAROOP MEMORIAL GROUP OF PROFESSIONAL COLLEGES, LUCKNOW Affiliated to Dr. APJ ABDUL KALAM TECHNICAL UNIVERSITY, LUCKNOW .a] (2) By [4] [5] (6] 7] [8] (9) Appendix - B REFERENCES S. Ariponnammal and S, Natrajan, “Transport Phenomena of Semiconductors,” Journal of Medical Physics, Vol. 42, No.5, pp. 421-425, 2005. P. Banerjee, M. Haldar, D. Zaertsky, and R. Anderson, “Overview of 4 Compiler for Synthesizing Matlab Programs onto FPGAs,” IEEE Transactions on Very Large Scale Integration (VLSI) System, Vol. 12, No. 3, pp. 312-324, March 2004. J. Jores (2006), “Contact Mechanics,” Cambridge University Press, U.K., Chapter 6, pp. 144-164. C. Rovers Eds., “Recent Advances in DSP Techniques,” 2” ed., Taylors Frances Group, USA, 2006. R. Smith (2008), “Contact of Cylindrical Surfaces involved in a Non- Steady Motion,”. Available Online at: http://www.casphy.cenm.edu/homepage.html H. D. Cheng, “Image Features Extraction using Volterra Filters,” Proc. of 5" IBEE Intemational Conference on Machine Vision and Aniificial Intelligence, Beijing, China, pp. 42-57, October, 2009. A. K. Barnard, “A Study of Stereo Matching Algorithms for Mobile Robots,” A Thesis Report for University of Bath, U.K., 2005. J. P. Williamson, “Non-Linear Resonant Granit Devices,” US Patent 3 624 12, July 16, 1990. Motorola Semiconductor Data Manual, Motorola Semiconductor Products Inc., Phoenix, AZ, 1987.Aoyenjeag jo ammaeusig 7 raqeq + suopepdy 9 uoutaaosdury Jo seary peysasing ypeqpaay /s}uautuI0D Jeuosiag —l fs 21S | Ts 0) oD iS (so) (or) ied WOIssas none biter squa}00) sydaou0g 3 aanvalqg | ‘on's L Jamsuy /uonsand uoneominunuo3 Vuopewesaid idd| /eapl ui uoneaouuy PODIL Vaforg ron dnorg shea 3 ore E-LS rou] yoaeds Z-4S sapmy welo1g jo aueN T-Ls_ :(s) eyeprpue9 yo ouren, WOne essary SISdOuAS alorg [apop qe] o8fo1g+ dJoyenyeag jo amjeusis 7 ea eee = Suonepdy F 1uWlOAGIdUT| jo Sealy paisosang/SjNOUIMIOD [oNOSIOd — €-Ls I | zs | Tis or) ~ (So) (0) “ON'S yeqoL UOISsas Jamsuy /WORsaNH YAO UI ssa.id01g nidoy, pelorg ron dnosy rdeq 3 eG Bats rou, yoaeds _ 7S rapmy walosg jo owen, T-1s :(s) aeprpue; jo aurey [-}e0qg wonenyery sso.is01g joloig [ a-spusddy | _ [poz qeijpeforg