Malla Reddy Institite of TechnologyMaisammaguda, Dhullapally post, Via Hakimpet, Secunderabad

Mini Project Seminar Time Table Branch: COMPUTER SCIENCE AND ENFF

Important Dates

Mini Project First Seminar: 30th July 2011 (Saturday)

Mini Project Second Seminar: 8th October 2011 (Saturday)

Mini Project Final Seminar: 10th December 2011 (Saturday)

Important Note

1. The time and duration of the seminar will be the same for all the 3 seminars.2. All the teams’ members should speak according to their module decided by themselves. ( it is strictly not allowed for only one person to speak for the whole

duration)3. All teams should bring their own storage devices for their seminar presentations. Department will not provide any pen drives or CD/DVD etc. However department

will provide you with LCD projector and a well configured PC for your presentation.4. All project teams must attend the seminar in their allotted time only. Exchange of seminar slot with other teams is strictly not allowed. 5. Postponement of seminars is strictly not allowed and if any team or a student in a team is not present at the time of seminar, they will be marked absent for that

respective seminar.6. All teams should submit hardcopy of their presentation atleast one day before the seminar date for all the three seminars to their respective Guides. Also students

are requested to send a softcopy to cse.it.hod.mrit@gmail.com your project evaluation purposes.7. Students are informed to show the presentation to their respective guides and seek proper guidance regarding their seminar in order to reduce the complexity

towards the project team at the time of seminar.8. Students are also informed to prepare well and present the seminar to a very good extend.

What the First Seminar Should Generally Include (can have up to 15 to 25 slides)1. Project Title2. Aim of the project3. Existing system and proposed system4. Benefits of the project5. Modules of the project6. Assigning of the modules to the team member7. Requirement analysis ( hardware and Software) ( need to justify why these requirements are used)8. Complete project development chart9. Present state of the project10. References11. Conclusion

Note: the above points may vary from project to project, Team to team, project guide to project guide. If you are interested in adding more information or reduce the information do contact your supervisor with your slides and clarify about the presentation with him or her.

What the Second Seminar Should Generally Include (can have 35 -50 slides)1. Project Title2. Aim of the project in Brief3. Existing system and proposed system in brief4. Benefits of the project in brief5. Flow charts etc6. Modules of the project in detail7. Module explanation by each member of the team in detail8. Major functions used in coding (With justification)9. Major classes used in coding (With justification)10. Logics implemented in the project for coding (With justification)11. All UML diagrams used for coding (With justification)12. Justification of requirements if they are modified or changed13. Present stage in project completion chart14. References15. Conclusion

Note: the above points may vary from project to project, Team to team, project guide to project guide. If you are interested in adding more information or reduce the information do contact your supervisor with your slides and clarify about the presentation with him or her.

What the Third Seminar should generally include (can have up to 35 -50 slides)1. This is the final seminar where you include everything which has been performed in the first two seminars. 2. In addition to that, DOCUMENTATION should be submitted for the project which is performed. 3. Also students are informed to explain and demonstrate their developed code.4. Students can also discuss about their difficulties raised during the project for its completion (Only technical Difficulties allowed).5. A TEAM SHOULD SUBMIT 2 COPIES OF THIER DOCUMENTATION MADATORILY AT THE TIME OF THIRD SEMINAR. DEPENDING ON THE

SUPERVISOR YOU MAY BE ASKED TO SUBMIT A THIRD COPY FOR YOUR SUPERVISOR. HOWEVER STUDENT COPIES CAN BE KEPT WITH THE STUDENT ITSELF FOR HIS FUTURE REFERENCE.

6. ALL THE COPIES CREATED MUST BE SIGNED BY HEAD OF THE DEPARTMENT, PROJECT GUIDE AND ALSO SEMINAR COMMITTEE. THE DOCUMENT IS NOT VALID IF IT IS NOT SIGNED PRIOR TO THE SEMINAR.

Note: the above points may vary from project to project, Team to team, project guide to project guide. If you are interested in adding more information or reduce the information do contact your supervisor with your slides and clarify about the presentation with him or her.

What should the documentation include:

In exceptional cases, if you feel that your project documentation does not fit the below structure, you may agree an alternative with your supervisor, however the completed project documentation must both describe and evaluate the project you have undertaken. Most project documentation will contain the following components :

Abstract Introduction

Literature Review

Research Methodology OR product development

Statement of Results

Analysis and Discussion

Conclusion

Bibliography

Appendices (if necessary)

Abstract

Each printed copy should contain a one A4 page abstract of the whole work.

Introduction (rationale and objectives)The introduction should identify the context for your project and the rationale for doing the work. For example if your project is connected with your workplace you should describe the type of organisation you work for and the problem that needs addressing. You should aim to offer a persuasive reason why your selected topic is important and interesting.

It is critical that in this section you include your main objectives, in a clear and well-argued fashion. A set of bullet points, one for each main objective is advisable. You must seek to offer a convincing set of objectives which form the basis for a research project which is appropriate for graduate level. Your review of how well your work has met these objectives will form the basis of your evaluation in the analysis and discussion section – see below.

Literature reviewThe literature review provides a frame of reference for the work that has been undertaken and for the discussion and analysis that takes place elsewhere in the project documentation. Remember you are reviewing the literature. You should not just repeat what is in papers and articles you have read. You need to analyse critically what you find, and present it in a structured and insightful manner to your readership.

Research methodology Or Product Development / Application of findings (as appropriate)Here you should explain which development approach and/or research method(s) you have used. However, this is insufficient of itself. You should also provide an analysis of the strengths and limitations of the research methods employed and provide an account of the academic, ethical and technical issues encountered in the project. The description of what you did is really intended only to provide a basis for this analysis.

For those projects where a product is to be developed then the role of the product should be discussed. Why it is necessary to develop it, how it was developed and any alternatives to various aspects of its development. The evaluation of the product will appear in the following “Statement of Results / Analysis” Sections (e.g. how effective the product is at meeting the requirements you have identified).

Where the project is such that a product is not appropriate, then you must discuss your research findings, and clearly show how your findings can be applied to the problem you have identified. An evaluation of whether these findings are appropriate to the problem will appear in the following “Statement of Results / Analysis” Sections (e.g. how effective the project outcomes you have might be at meeting the requirements you have identified).

Statement of Results, Analysis and Discussion, Conclusions

In some project documentation these topics are covered in separate chapters; in others they are merged into fewer chapters. What is important is not the number of chapters but that you demonstrate that you have critically evaluated the outcomes of the research (as well as any evidence collected) by relating them to their context as considered in the literature review. It is expected that candidates for a Engg degree will be able to balance their conclusions by providing evidence for them, and reflect upon the outcomes, making recommendations as appropriate.

Bibliography

It is stressed that the Harvard System of citation must be used consistently and correctly. Web search is recommended for knowing information on Harvard System Referencing styles.

AppendicesIf required, you should include background material (code samples, data etc.) in appendices. You should take advice from your supervisor over what to include in the appendix. NOTE: full program listings and data sets should appear only in electronic form.

Length

The project documentation is normally of the order of 15,000 words with a maximum of 20,000 words for project documentation that do not involve a product and 10,000 – 15,000 for ones that do. If your project documentation is overly long then it should be carefully edited.

Marking Criteria

In assessing your Project Work, the following criteria are addressed (each criterion carries equal weighting):

Critical review of related research: Context clearly identified; research discussed with reference to the problem

You should address this in the literature review section of your work, supported by parts of the introduction

Analysis of problem scenario: Clear definition of requirements; well-argued discussion of methods available, clearly applied to the project

The problem should be defined in the introduction section, and further analysis reported in the product development / research methodology section. You should clearly discuss any ethical considerations of your project or indicate that there are none.

Design and development of problem solution: Clear relationship between requirements and solutions

The remainder of the product development / research methodology section should show how your ideas are applied to addressing the problem

Evaluation of problem solution and process: Cross referenced to original objectives; honest evaluation

The statement of results; analysis and discussion and conclusions sections allow you to give an overall evaluation of the work you have done

Professional management and presentation of project: Project planning and meeting attendance; overall look and feel of the Project Work .

Remember that half of the marks for this section are allocated to the two formal meeting events; the remainder are allocated for presentation and structure of your Project Work

TIME TABLE FOR MINI PROJECT SEMINARSIMPORTANT NOTE:

1. ONLY ONE TEAM IS ALLOWED FOR THE SEMINAR. 2. THERE WILL BE REGULAR CLASSES ASUSUAL. HENCE IT IS INFORMED TO THE STUDENTS TO ATTEND THE REGULAR CLASSES UNLESS THIER TURN FOR THE

SEMINAR IS OCCURED ON THAT DAY.

ROLL NO NAME PROJECT TITLE PLATFORM

DATE 1 DATE 2 DATE 3 TIME GUIDE

08RJ1A0518 D.PRATEEK EXPOCITION FOCAL POINT DOTNET 30/07/11 08/10/11 10/12/11 9:40

08RJ1A0519 D.PURUSHOTHAM EXPOCITION FOCAL POINT DOTNET 30/07/11 08/10/11 10/12/11 TO TIRUPATHI KUMAR

08RJ1A0520 M.SHARANYA EXPOCITION FOCAL POINT DOTNET 30/07/11 08/10/11 10/12/11 10:00

G.S. NIKHIL PROJECT SCHE--- DOTNET 30/07/11 08/10/11 10/12/11 10:00

DEVENDRA PROJECT SCHE--- DOTNET 30/07/11 08/10/11 10/12/11 TO ANIL REDDY

SHIVA PRASAD GOUD PROJECT SCHE--- DOTNET 30/07/11 08/10/11 10/12/11 10:20

08RJ1A0516 D.UPESH REDDY VIDEO STENOGRAPHY JAVA 30/07/11 08/10/11 10/12/11 10:20

08RJ1A0520 SHIVA SAI KUMAR VIDEO STENOGRAPHY 30/07/11 08/10/11 10/12/11 TO MOUNITHA

08RJ1A0505 SARIKA VIDEO STENOGRAPHY 30/07/11 08/10/11 10/12/11 10:40

08RJ1A0549 P.VAMSHIDHAR CAPTCHA JAVA 30/07/11 08/10/11 10/12/11 10:40

08RJ1A0504 B.ARCHANA CAPTCHA 30/07/11 08/10/11 10/12/11 TO MOUNITHA

08RJ1A0508 B.SAIRAM CAPTCHA 30/07/11 08/10/11 10/12/11 11:00

08RJ1A0515 ASSET MANAGEMENT SYATEM JAVA 30/07/11 08/10/11 10/12/11 11:00

08RJ1A0532 ASSET MANAGEMENT SYATEM 30/07/11 08/10/11 10/12/11 TO ANIL REDDY

08RJ1A0509 ASSET MANAGEMENT SYATEM 30/07/11 08/10/11 10/12/11 11:20

08RJ1A0557 K.S.SONAM PLACEMENT OFFICE AUTOMATION JAVA 30/07/11 08/10/11 10/12/11 11:20

08RJ1A0539 M.TEJESWI PLACEMENT OFFICE AUTOMATION JAVA 30/07/11 08/10/11 10/12/11 TO U RAJU

08RJ1A0537 VENKATESH PLACEMENT OFFICE AUTOMATION JAVA 30/07/11 08/10/11 10/12/11 11:40

08RJ1A0522 G.SRIKANTH REDDY SMART CARD JAVA 30/07/11 08/10/11 10/12/11 11:40 NAGI REDDY

08RJ1A0529 J.CHAITHANYA SMART CARD JAVA 30/07/11 08/10/11 10/12/11 TO

12:00

08RJ1A0562 VIJAY ONINE VECHLE HIRING DOTNET 30/07/11 08/10/11 10/12/11 12:00

08RJ1A0507 JAVEED ONINE VECHLE HIRING DOTNET 30/07/11 08/10/11 10/12/11 TO MOUNITHA

08RJ1A0502 A.SRIKANTH ONINE VECHLE HIRING DOTNET 30/07/11 08/10/11 10/12/11 12:20

08RJ1A0546 P.JYOTHSNA CARGO LOGISTICS DOTNET 30/07/11 08/10/11 10/12/11 12:20

08RJ1A0526 G.NARESH CARGO LOGISTICS 30/07/11 08/10/11 10/12/11 TO SHIVA KRISHNA

08RJ1A0517 D.SANDEEP CARGO LOGISTICS 30/07/11 08/10/11 10/12/11 12:40

08RJ1A0525 G.RAMAKRISHNA NETPOLING DOTNET 30/07/11 08/10/11 10/12/11 12:40

08RJ1A0527 G.SNEHA NETPOLING 30/07/11 08/10/11 10/12/11 TO RAGHAVENDRA

08RJ1A0545 M.SANDEEP NETPOLING 30/07/11 08/10/11 10/12/11 13:00

08RJ1A0551 P.GOPAL KRISHNA CONFINED WEB SPIDERS DOTNET 30/07/11 08/10/11 10/12/11 13:00

08RJ1A0533 K.VINAY KUMAR CONFINED WEB SPIDERS 30/07/11 08/10/11 10/12/11 TO RAGHAVENDRA

08RJ1A0558 RENUKA NAIDU CONFINED WEB SPIDERS 30/07/11 08/10/11 10/12/11 13:20

08RJ1A0544 NEERAJ KUMAR SHARMA

QUERY REDRESSAL SYSTEM DOTNET 30/07/11 08/10/11 10/12/11 13:20 KIRAN KUMAR

08RJ1A0524 G.AMOOLYA REDDY QUERY REDRESSAL SYSTEM DOTNET 30/07/11 08/10/11 10/12/11 TO

13:40

08RJ1A0550 P.SWATHI DEFECT TRACKING SYSTEM DOTNET 30/07/11 08/10/11 10/12/11 13:40

08RJ1A0540 M.ANIVESH REDDY DEFECT TRACKING SYSTEM DOTNET 30/07/11 08/10/11 10/12/11 TO ANIL REDDY

08RJ1A0530 K.KRANTHI KIRAN DEFECT TRACKING SYSTEM DOTNET 30/07/11 08/10/11 10/12/11 14:00

08RJ1A0554 S.RAKESH E2M DOTNET 30/07/11 08/10/11 10/12/11 14:00

08RJ1A0543 N.SHRAVANI PRIYA E2M DOTNET 30/07/11 08/10/11 10/12/11 TO TIRUPATHI

14:20

08RJ1A0511 CH.Chandana WORK SHIFT MANAGEMENT SYSTEM DOTNET 30/07/11 08/10/11 10/12/11 14:20

08RJ1A0531 k.rajesh WORK SHIFT MANAGEMENT SYSTEM DOTNET 30/07/11 08/10/11 10/12/11 TO LAXMINARAYANA

08RJ1A0547 P.HARISH RAJU WORK SHIFT MANAGEMENT SYSTEM DOTNET 30/07/11 08/10/11 10/12/11 14:40

08RJ1A0564 K.V.SURESH REDDY GLID PROCESSING DOTNET 30/07/11 08/10/11 10/12/11 14:40

08RJ1A0548 P.RAHUL REDDY GLID PROCESSING DOTNET 30/07/11 08/10/11 10/12/11 TO SATEESH

08RJ1A0523 G.BHAVANA GLID PROCESSING DOTNET 30/07/11 08/10/11 10/12/11 15:00

Any left over 30/07/11 08/10/11 10/12/11 15:00

Batch/team 30/07/11 08/10/11 10/12/11 TO

30/07/11 08/10/11 10/12/11 15:20