UPDATES - SCROLL

FINAL CERTIFIED FAIR REPORT SHOULD BE SUBMITTED ON OR BEFORE 27/03/2015, 9.30 AM

Friday, 13 March 2015

S6 CS B PROJECT REVIEW & LAB EXAM SCHEDULE

S6 CS B
MASM LAB
Mini Project  Final Review
Date
Fore noon
After noon
Fore noon
After noon
19-03-2015
Rajeev P N
Sudheesh V
Harsha G
Sikha Sasidharan
Harivishnu R
Vishnujith N
Anjali A Palayi
Surabhi Suresh
Karthik B
Mirza Zacharia K Z
Amritha K
Maria Antony
Rithul Kumar S
Soumya V
Sravana S Prabhu
Krishnendu S
Muhammed Faizal
Nasibha K T
Sreeraj R
Abhijith Ajithkumar
Abhishek Ramachandran
Athul K S
Senobin Basil
Devi B
Noushad N
Sufna S S
vishnu V
Akshay K Reghu
Ananthakrishnan B
Arunjith Ravi
Vishnu Ravi
Akhil G
Bibin Raj
Rahman Khalid
Anjana B
Agna M S
Aiswarya Narayanan
Meenu Muraleedharan
Saritha M S
Arathy K U
Divya M Kumar
Hasnamol C M
Jishy Johnson




20-03-2015
Devi B
Noushad N
Sufna S S
vishnu V
Akshay K Reghu
Ananthakrishnan B
Arunjith Ravi
Vishnu Ravi
Akhil G
Bibin Raj
Rahman Khalid
Anjana B
Agna M S
Aiswarya Narayanan
Meenu Muraleedharan
Saritha M S
Arathy K U
Divya M Kumar
Hasnamol C M
Jishy Johnson




Rajeev P N
Sudheesh V
Harsha G
Sikha Sasidharan
Harivishnu R
Vishnujith N
Anjali A Palayi
Surabhi Suresh
Karthik B
Mirza Zacharia K Z
Amritha K
Maria Antony
Rithul Kumar S
Soumya V
Sravana S Prabhu
Krishnendu S
Muhammed Faizal
Nasibha K T
Sreeraj R
Abhijith Ajithkumar
Abhishek Ramachandran
Athul K S
Senobin Basil











Sunday, 8 March 2015

REPORT PAGE BORDER, NUMBERING

The mini project report should follow the standards for page borders, headers,footers,numbering, alignment etc in the below sample report. (only for bordering and numbering) For all other contents use the reference report which provided earlier.
Click for Sample Report


For any queries Call 9496881321

Tuesday, 3 March 2015

PROJECT REPORT CHAPTERS HIERARCHY

Project Report Format (Report should be maximum of 120 pages and minimum of 70 pages)
Cover Page
Title Page
Glass sheet
ii. Certificate
iii. Acknowledgement
iv. Abstract
v. Table of Contents
vi. List of figures
vii. List of tables
viii. List of abbreviations (should be alphabetic orders)
1. Introduction
            1.1 Purpose
            1.2 Scope
2. System analysis
            2.1 Existing system (should include the disadvantage of existing system)
            2.2 Proposed System
                        2.2.1 Features of proposed system
            2.3 Proposed SDLC model
            2.4 Feasibility study
                        2.4.1 Technical feasibility
                        2.4.2 Economical feasibility
                        2.4.3 Operational feasibility
                        2.4.4 Social feasibility
            2.5 Gantt Chart (Diagram with detailed description)
            2.6 Cost Estimation
3. System Requirement Specification
            3.1 Functional Requirements
            3.2 Non functional Requirements
            3.3 Hardware Requirements
            3.4 Software Requirements
            3.5 Other Requirements (If any)
4. System Design
            4.1 System Overview
            4.2 System Architecture (if any)
            4.3 Modules
                        4.3.1 Module 1: Description (name the module and give description)
                        .                       .
                        .
            4.4 Algorithms used (if any)
            4.5 UML diagrams (contains minimum 4 UML diagram)
                        4.5.1 First UML diagram name (eg: Class diagram)
                                    a) Purpose
                                    b) Diagram
                                    c) Description (should provide detailed description)
                        4.5.2 Second UML diagram name (eg: Use case  diagram)
                                    a) Purpose
                                    b) Diagram
                                    c) Description (should provide detailed description)
/* The order of UML diagrams should be Class diagram, Object diagram, Use case diagram, Sequence diagram, Collaboration diagram, Activity diagram, State transition diagram, Component diagram, Deployment diagram */

                        .
                        .
            4.6 Data Flow Diagram
                        4.6.1 Purpose
                                    level 0 diagram
                                    level 1 diagram
            4.7 Database tables (should be normalized)
            4.8 ER diagram (if any)
5. Implementation
            Provide the overview of implementation
            5.1 Language used (should include the features of language)
            5.2 Installation and deployment
            5.3 Screenshots ( Each screen shot should be supported with detailed description)
6. Testing
            Provide an overview of testing and goal of testing
            6.1 Code testing
            6.2 Unit Testing
                        6.2.1 Black box testing
                                                 Black box testing with derived test cases and output result of each                                                             test cases as a table
                       

6.2.2 White box testing
White box testing with derived test cases and output result of each                                                 test cases as a table

            6.3 Integration Testing
Describe the integration approach applied with the help of structure chart
            6.4 Validation Testing
            6.5 Output Testing
6.6 System testing
            6.7 Test reports
7. Conclusion
8. Future Scope
9. References (minimum 10)
Appendix
A: Sample Program Code (Maximum 5 Pages)
Index
           


Monday, 2 March 2015

SAMPLE PROJECT REPORT FORMAT (NOT FINAL)

This is just a sample report to understand the outlook of a project report. Dont try to copy paste the contents. Chapters are different from this report. The detailed chapters hierarchy for final report will be provided shortly.


CLICK HERE FOR REFERENCE REPORT

Saturday, 28 February 2015

GUIDELINES FOR THE PREPARATION OF B. Tech MINI PROJECT FINAL REPORTS

These are standard guidelines for preparing your final project report.


1. Project reports should be typed neatly only on one side of the paper with 1.5 or double line spacing on a A4 size bond paper (210 x 297 mm). The margins should be: Left - 1.25", Right - 1", Top and Bottom - 0.75".                                                                                                                                                           
2The total number of reports to be prepared are
  • One copy to the department
  • One copy to the college library.
  • One copy to the concerned guide  (Optional)
  • One copy to the candidate.
3. Before taking the final printout, the approval of the concerned guide(s) is mandatory and suggested corrections, if any, must be incorporated.
4. For making copies dry tone Xerox is suggested.
5.Every copy of the report must contain
  • Inner title page (White)
  • Outer title page with a plastic cover
  • Certificate in the format enclosed both from the college and the organization where the project is carried out.
  • An abstract (synopsis) not exceeding 100 words, indicating salient features of the work. 


6.The organization of the report should be as follows
  1. Inner title page
  2. Bonafide Certificate
  3. Abstract or Synopsis
  4. Acknowledgments                      
  5. Table of Contents
  6. List of Figures 
  7. List of Tables(optional)
  8. List of abbreviations
Usually numbered in roman
  • Chapters (to be numbered in Arabic) containing Introduction-, which usually specifies the scope of work and its importance and relation to previous work and the present developments, Main body of the report divided appropriately into chapters, sections and subsections.
  • The chapters, sections and subsections may be numbered in the decimal form for e.g. Chapter 2, sections as 2.1, 2.2 etc., and subsections as 2.2.3, 2.5.1 etc.
  • The chapter must be centered (font size 16).  Followed by the title of chapter centered (font size 18), section/subsection numbers along with their headings must be left justified with section number and its heading in font size 16 and subsection and its heading in font size 14. The body or the text of the report should have font size 12.
  • The figures and tables must be numbered chapter wise for e.g.: Fig. 2.1 Block diagram of a serial binary adder, Table 3.1 Primitive flow table, etc.
  • The last chapter should contain the summary of the work carried, contributions if any, their utility along with the scope for further work.
Reference OR Bibliography: The references should be numbered serially in the order of their occurrence in the text and their numbers should be indicated within square brackets for e.g. [3].  The section on references should list them in serial order in the following format.
  1. For textbooks - A.V. Oppenheim and R.W. Schafer, Digital Signal Processing, Englewood, N.J., Prentice Hall, 3 Edition, 1975.
  2. For papers - Devid, Insulation design to combat pollution problem, Proc of IEEE, PAS, Vol 71, Aug 1981, pp 1901-1907.
  • Only SI units are to be used in the report.  Important equations must be numbered in decimal form for e.g.
  •        V = IZ                                      ..........                  (3.2)
  • All equation numbers should be right justified.
  • The project report should be brief and include descriptions of work carried out by others only to the minimum extent necessary.  Verbatim reproduction of material available elsewhere should be strictly avoided.  Where short excerpts from published work are desired to be included, they should be within quotation marks appropriately referenced.
  • Proper attention is to be paid not only to the technical contents but also to the organization of the report and clarity of the expression.  Due care should be taken to avoid spelling and typing errors.  The student should note that report-write-up forms the important component in the overall evaluation of the project
  • Hardware projects must include: the component layout, complete circuit with the component list containing the name of the component, numbers used, etc. and the main component data sheets as Appendix.  At the time of report submissions, the students must hand over a copy of these details to the project coordinator and see that they are entered in proper registers maintained in the department.
  • Software projects must include a virus free disc, containing the software developed by them along with the read me file.  Read me file should contain the details of the variables used, salient features of the software and procedure of using them: compiling procedure, details of the computer hardware/software requirements to run the same, etc.  If the developed software uses any public domain software downloaded from some site, then the address of the site along with the module name etc. must be included on a separate sheet.  It must be properly acknowledged in the acknowledgments. The disc should contain a notepad named "contact us" which include the name, address, contact number and mail id of all group members 
    


Monday, 23 February 2015

S6 CS A MIDWAY REVIEW MARKS

Name Topic Marks(50)
Archit M D METAMORPHIC CRYPTOGRAPHY              ( Joyce) 45
Kukku Suresh 32
Naziya Noushad 37
Vidya O Kuttan 34

Adhil K
PUZZLE MASTER (Aswathy)
43
Ashik K 45
Lijin Raj 27
Vishnu satheeshan 42

Amal J
COLLEGE KNOWLEDGE MANAGEMENT SYSTEM (Meenu )
26
Aiswarya Saseendran 14
Anjali S Varier 32
Raina T A 28

M. Arjun
EMERGENCY HELPER (Aswathy)
33
Hemanth P V 26
Sivanand D 33
Sreejith K V 26

Abhijith K S
CEC EXAM HALL ARRANGEMENT (Janu Miss)
37
Arun C Bose 47
Deepak Prakash 37
Sujith R Nath 37

Krishna K R
TRAFFIC FREE DRIVE -(Josna)
28
Osni Therasa V X 28
Sruthi P 28
Telin Tom 28

Deepthi M P
VIRTUAL EXAM (Pramod)
44
Neena A T 43
Neethu Elizabeth Punnoose 45
Neethu Moidu 46

Aingel Rajan
RESULT ANALYSIS (Aswathy)
19
Aneesha Nazer 20
Sajeeha K T 19
Sayujya Jayakumar 19

Akhila S
RESERVATION BASED SMART PARKING SYSTEM (Rohini)
20
Amrutha P U 25
Jusna P Kumar 25
Shiyana S 23

Ganga Sreekumar
TIME TABLE SCHEDULE GENERATION (Pramod)
18
Meera Roy 12
Reshma Raj R 18
Sujisha S 15

Beena Christy
CEC ADMISSION  DESK (Rohini)
22
Divya B 22
Haritha 22


VP = Viva pending

Saturday, 21 February 2015

S6 CS B MINI PROJECT MIDWAY REVIEW MARKS

Group No Name Topic                                      Marks(50)
1 Rithul Kumar S CLOUDMOV: CLOUD BASED MOBILE SOCIAL TV(Fathima) 12
Soumya V 27
Sravana S Prabhu 17
2 Krishnendu S EASY LIBRARY (Judy) 33
Muhammed Faizal 45
Nasibha K T 33
Sreeraj R 35
3 Abhijith Ajithkumar CECAPP (Fathima) 45
Abhishek Ramachandran 42
Athul K S 37
Senobin Basil 37
4 Devi B MOBILE LOCATION ALARM (Josna) 43
Noushad N 42
Sufna S S 29
vishnu V 32
5 Akshay K Reghu ATTENDANCE MANAGEMENT SYSTEM (Rohini) 26
Ananthakrishnan B 21
Arunjith Ravi 21
Vishnu Ravi 21
6 Akhil G 8085 ANDROID EMULATOR (Athira) 24
Bibin Raj 34
Rahman Khalid 23
Anjana B 27
7 Agna M S PERSUASIVE CUED - CLICK POINT (Pramod) 46
Aiswarya Narayanan 46
Meenu Muraleedharan 45
Saritha M S 46
8 Arathy K U LAND SURVEYOR (Pramod) 41
Divya M Kumar 48
Hasnamol C M 40
Jishy Johnson 48
9 Rajeev P N BINGO MULTIPLAYER USING WIFI (Asha) 44
Sudheesh V 44
Harsha G 38
Sikha Sasidharan 32
10 Harivishnu R MY TUTOR (Asha) 5
Vishnujith N 6
Anjali A Palayi 7
Surabhi Suresh 7
11 Karthik B AUTODOC (Asha) 41
Mirza Zacharia K Z 43
Amritha K 45
Maria Antony 39