BSCS Handbook 2011

HANDBOOKfor

BSCS Final Project

Faculty of Information Technology

University of Central Punjab

PREFACE

This document forms the rules and guidelines for the successful completion of the Final Project.

The primary objective of this handbook is to assist those who presently enrolled or contemplating enrollment in the final project, in understanding the culminating degree requirement while also ensuring a quality contribution to the Faculty of Information Technology research. This handbook addresses the following:

• It answers typical questions raised by students related to project work.

• It brings up-to-date various aspects of project work. • It lists some important dates and deadlines.

This handbook is also useful for the project advisors / supervisors to better understand the university requirements and guide the students accordingly.

In this document you will find all information regarding the requirements and procedures for doing project at the Faculty of Information Technology, University of Central Punjab. This document and other useful information can be found on the University web portal http://projects.ucp.edu.pk

http://projects.ucp.edu.pk/

TABLE OF CONTENTS

CONTENTS Page Number

1. Introduction 12. Objectives 13. Project Overall Procedure 14. Registration / Duration 15. Basic Requirements and Necessary Skills 26. Choosing a topic 27. Grouping and Group Size 28. Transfer from Other Campuses / Universities 29. Extension / Re-Registration 210. System Allocation 311. Change of Project Title 312. Change of Project 313. Change of Group 314. Change of Advisor 315. Additional Help Through Seminars and Tutorials 316. Additional Hardware 417. Backups 418. Web – Based Projects 419. Evaluation and Results 420. Early Evaluation of Project 421. Re-Evaluation 522. Distribution of Marks and Deadlines 523. Penalty For Not Meeting Deadlines 524. Responsibilities of the Advisor 625. Plagiarism 626. Student Responsibilities 627. Future use of the Project 628. Final Submission Procedure & Requirements 7

a. Content Requirement for Documentation (Implementation Projects)7

b. Content Requirement for CD 8c. Formatting Requirements 10d. Illustrative Materials 11

29. Contents of Project Presentation11

30. Important Notes12

Handbook for Final Project / Research Thesis

INTRODUCTION

The final project at University of Central Punjab offers the challenge to demonstrate your ability to set up and to carry out a scientific project in a self-responsible and independent manner.

OBJECTIVES

There are three objectives that should be accomplished within the project.

1. Technical accomplishment: The technical results presented in the project should reflect the maturity of a senior level student in both the depth to which the subject is developed and in the degree to which a variety of information or viewpoints is brought to bear on the problem.

2. Diligent execution: The project will be independent work by the student / group, developed under his / her own initiative and on a timetable under the student's control. The instructor who supervises the senior project is expected to supply only general advice and guidance and to help the student avoid pitfalls and blunders; the day-to-day activities which affect the execution of the project are up to the student.

3. Effective communication: The project should represent a well polished piece of writing. Standard procedures of footnoting, referencing, and symbol usage as used in the technical literature should be employed. All computer programs are to be completely and fully documented.

PROJECT OVERALL PROCEDURE

After completion of 100 credits towards degree or on special approval of the dean IT, a student can take Final Project.

The student then chooses a Project topic and Advisor preferably from within Faculty of Information Technology of UCP.

A project allocation form is submitted to project office. A formal Project Proposal is required to be submitted to project office

within 15 days after the close of add drop week. Within 07 Days of Proposal submission, a student is required to defend

the proposal through a presentation in front of evaluators from industry and UCP faculty.

On successful defense students may start working on the project under the guidance of their advisor

After completion of each phase a student will have to present his work done.

At the end of project term one month before the final submission the students are required to give an intimation of their submission through (Notification Form)

Following the intimation, the final submission is required one week before the evaluation dates.

The final evaluation has been performed according to the announced dates and grades are forwarded to the Controller of Exams.

REGISTRATION / DURATION

Final Project is a 6 credit hours course, spread over a period of one full year(3 semesters). In order to ensure that the student has an adequate background and maturity to effectively under-take the senior project, students will be required to be within one year of graduation before beginning a final project.

Updated August 2011 1


BASIC REQUIREMENTS AND NECESSARY SKILLS

A project can be started only after successful defense of project proposal and get approved by the Evaluators. For the commencement of final project an advisor is needed preferably should be part of the UCP faculty.

• The template for Project Proposal can be obtained from the university web portal http://projects.ucp.edu.pk

For all students of BSCS and MCS it is necessary that they take up a final project which should include sufficient amount of coding / implementation.

The minimum requirement for taking up a project is that you have the basic knowledge of the domain and have studied the basic courses necessary for the particular project.

CHOOSING A TOPIC

Final Projects are offered by the faculty members or internal / external advisors or software engineers, however a student may suggest a project which will be presented in front of board of studies for final approval and upon approval this may be taken as final project.Projects are expected to be conceived, designed, and executed at a graduate level of sophistication. Some students may elect to do original research papers in the areas of their interest. Typically, a project will involve sophisticated software development. Generally, the amount of work required for a project is expected to be comparable to that entailed by two graduate courses. Student who want to work on a topic other that those suggested by advisors, they may suggest projects through advisors at least one month before the projects are offered. In such cases choose a project which is sellable in market and uses latest tools and technologies or at least very stable technologies.

GROUPING AND GROUP SIZE

For the students of BSCS and MCS projects it is optional to work in groups or as a single candidate. In case of BSCS the group size may NOT exceed 3 while for MCS the group size may not exceed 2 group members.A student is NOT allowed to join a running group. Preferably a student of one batch may not make a group with student of another batch, unless they have registered Final Project in the same semester. Similarly students of one degree program can not make a group with students of another degree program.

TRANSFER FROM OTHER CAMPUSES / UNIVERSITIES

If you have been transferred from other chartered universities and you were already allotted a final project, your project title will be re-evaluated by the Board of Studies and a new advisor will have to be chosen from within the Faculty of Information Technology. If the board accepts the current project then you may continue with the current project else you will have to choose a fresh project. In case of a fresh project the time duration for project will start from the first day of the semester in which the proposal is approved. In any case New Fees will not be required.

EXTENSION / RE-REGISTRATION

It is strongly recommended that the groups should complete their projects within the specified time (3 semesters). However, a project may be submitted in later semester after paying half fee for one



semester (4 months max.). After this late semester a grade ‘W’ will be awarded and student has to re-register him / her self with full fee. No discount will be applicable to the re-registration fee.



SYSTEM ALLOCATION

In the start of Second Term students are allocated systems in the project lab for implementation of projects. The allocation is done on a request by the group using “System Allocation Form”.

CHANGE OF PROJECT TITLE

A student may change the project title at any time before the final submission provided that the title does not change the overall scope of the project. It is important that the title should be carefully selected and should be small and relevant to the end product or main problem area of thesis.

CHANGE OF PROJECT

You need to be extremely careful in selecting a project. A project once selected can NOT be changed.

Within 21 days of the first course registration of Project, you may apply for a change of project with a justified reason to change along with a fresh proposal and signatures of the advisor. This change will only take effect if the change is permitted by the Project Manager and Dean Faculty of Information Technology and the new project is approved by the Board of Studies. Please note that such application will be initiated by the whole group and there will be NO change in the number or members of the group.

Any such application will NOT be entertained that are submitted 21days after the registration and do not justify the need for the desired change.

If after the 21 days period mentioned above, during the One Year period of project the group wants to change the project they may drop the current project, register the Project with MIS again along with fresh payment of Fee. In such cases the one year duration of Project will start all over again and will last for One Full Year.

CHANGE OF GROUP

A student may NOT change the group once selected so it is advised that the students should make the project group with extreme care.

CHANGE OF ADVISOR

All faculty members of the University are very well qualified and the projects offered by them are from their areas of expertise. Any application for change of advisor will NOT be entertained unless the faculty member has left the university and sufficient amount / time of project work is remaining.In case of any serious disagreement between the Advisor and Students the case will be presented in front of the DEAN for an appropriate solution.

ADDITION HELP THROUGH SEMINARS AND WORKSHOPS

Additional help may be provided to students in areas where they find difficulty in the conduct of their projects. This additional help can be in the form of Seminars, Workshops, Tutorials, Study Material and/or Class Sessions. The procedure to invoke such session is through “Seminar Request Form” duly endorsed by the project advisor. Wherever such sessions are arranged, it is mandatory for interested students to get registered with project office for attending the seminar. In case of students who register and do not attend, attendance policy as per college rules applies.



ADDITIONAL HARDWARE

The University tries to provide all necessary hardware required by the students in the fulfillment of their final project beforehand. However if additional hardware is needed, the students may request for the hardware using “Hardware request Form”. Hardware worth amount not exceeding 60% of the fee actually deposited by the group for final project may be requested.

BACKUPS

You cannot obtain a degree without having passed your project. Like with any coursework, it is your responsibility to keep a back-up of your project. If you have lost your project work due to, for example, a virus or a broken hard disc or a computer theft, you will NOT be given any relaxation. In order to make a backup, you can regularly copy your project work to your home directory and request for a backup on a CD provided by you, or you can regularly copy your work on a Flash / Pen Drive or use FTP from home and make backups.

WEB BASED PROJECTS

All projects that are web-based (i.e., developed in JSP, ASP.NET or any other web based programming language) are required to be hosted on a real time domain purchased preferably from an outside domain vendor. This will provide students with a real time hosting experience and they will be able to learn about and solve bottle necks of actual hosting.

EVALUATION & RESULTS

The final evaluation will be in form of a Seminar and Viva. The Presentation will be an open seminar. In the seminar at least one internal and one external examiner related to the project area will be present. After this seminar / presentation, Viva of the students will be conducted by these examiners.All students will be evaluated for the Final Project based on 6 Credit Hours for a total of 100 Marks. These marks will then be converted to an equivalent grade as per prevailing Grading System of the University. A minimum of 50 percent marks are required to qualify the Project. The attained grades will be displayed amongst other semester grades. Please note that the Grade attained in Final Project will count towards calculation of your CGPA.All project members must participate in all phases of the project development. The distribution of work cannot be based on the phases of a project life cycle; it should rather be based on the modules of a system project.Although the students present their final project in groups but please be sure that the examiners evaluate each student independently for his / her performance and the students of the same group might get different grades based on their performance.If a project is not the original work of students and it has been copied from some source, the project will be cancelled; the case will be presented in front of the board which may decide any further action.

EARLY EVALUATION OF PROJECT

Students will need to work consistently on the project over the period allocated to it. As a policy the projects are evaluated only after passing the desired span of time. Though in certain circumstances, if at least 80% time has passed, the project may be evaluated before time subject to a prior approval of Dean of Faculty of Information Technology. Please note that students of the same group will NOT be evaluated separately at different times, they will be evaluated collectively and have to take part in presentation at the time of evaluation.



RE-EVAULATION

Within three days of the declaration of result, a group of students may request for re-evaluation (as a group) by paying a re-evaluation fee of Rs.1000/- per student, if they are confident that they could get a better grade. Please keep in mind that as soon as re-evaluation is applied, the previous grade becomes null and void and the Re-Evaluation process can result in an increase or decrease of the grade.A Re-Evaluation of project will be done one time only; a second request will NOT be entertained.

DISTRIBUTION OF MARKS AND DEADLINES

From start of the project till its completion there are various documents that must reach the project office on time. Below is the list of activities, documents, which must be completed / submitted according to last date, given in the table. Week mean ‘Monday to Saturday’.

Activity Marks Duration Document to be submitted Last Date Total

Weeks

Submission of Project Proposal

052 Weeks Allocation Form with

ProposalWithin 2 weeks after the Close of Add Drop Week. 02

Proposal Defense(Presentation # 1) 01 Project Proposal

(Hard copy & soft copy)Within 01 week of the previous activity. 03

Submission of SRS ver 1.0

1008

SRS Ver 1 (Functional and Non-Functional

requirements).

Within 8 weeks from previous activity. 11

Presentation # 2 01 Within 1 week from previous activity. 12


2012 SRS Ver 2 (Analysis

and Design)Within 12 weeks from previous activity. 24



2012

SRS Ver 3 (Initial Operational capabilities

and test cases)

Within 12 weeks from previous activity. 37



4509 SRS Ver 3 + Final

ProductWithin 09 weeks from previous activity. 47


Re-Evaluation Re-Evaluation Form Within 3 working days of the declaration of result.

Total: 100 48 Weeks

NOTE: All versions of SRS Template are available on the web portal http://projects.ucp.edu.pk

PANELTY FOR NOT MEETING DEADLINES

In case of running out of deadlines every group has to face delay in subsequent activity. For example if one group fails to submit his SRS ver. 1 in time i.e. till the end of 11th week of semester, then he has to


http://projects.ucp.edu.pk/


wait until 11th week of next semester (one whole semester delay). Consequently it will result in complete project delay and financial loss too.

RESPONSIBILITIES OF THE ADVISOR

In addition to being a technical consultant to the student and providing suggestions that will permit him or her to be more effective, the instructor who acts as project advisor evaluates the work internally.

It is customary for the students and advisor to meet regularly so that their communication may be continuous and effective. Regular contact with your advisor is essential, whether you are working hard or have done little or no work. In the first case your advisor can ensure that you are going in the right direction; in the second case your advisor can help you to get you back on track, moreover the advisor pulls you out of the bottle necks that you might have during the project work.

Establish a schedule for work and meetings with your advisor, meet him / her at least once a week, even if it is only for 5 minutes. If things start to go away, contact your advisor. If he / she is not giving you enough time, talk to the Project Manager. Don't hesitate in doing this, as it will take us time to notice this, time is the most difficult thing to replace.

The advisor may require supplementary reports and may modify the nature of the required reports at his / her discretion. Although the advisor is proficient in the project area you have chosen but he is not expected to write code of the project for you in any circumstances.

PLAGIARISM

You are required to make sure that, except where it is marked to the contrary, all submitted work is your own. It is essential that no suspicion of plagiarism attaches to your report. It is implausible that the examiners will award a passing mark to any project where plagiarism (as opposed to referenced reporting) is suspected. If in doubt, check carefully with your advisor / supervisor.

STUDENT RESPONSIBILITIES

The project is a student’s original work and he or she is solely responsible for its content. The student must pick a topic, select an advisor among the full time faculty preferably in the Faculty of Information Technology, manage their own time, perform and organize the project work which follow the appropriate set of rules and guidelines for preparing a project / writing a logically cohesive thesis, and defend it. The advisor is there to guide you and ensure you meet the quality standards as determined by the faculty and complying with the UCP regulations but, it must be recognized that, in all instances, the student is solely responsible for authorship and management of his or her project. You have an obligation to give your best work in exchange for the time the faculty invests in you. Nothing less than your most outstanding work is acceptable.

Be sure to understand the UCP rules since they are not negotiable. If you do not defend your project within the dates specified, you will be required to register again in the following semester. These rules are among the most rigidly enforced in the University, so please plan ahead. Faculty are not expected to be put in a position to "bend the rules" on a student's behalf, nor is it considered appropriate for a student to seek special dispensation from carrying out their responsibilities in a professional and timely manner.



FUTURE USE OF PROJECT

It is possible that you will have been helped in your project by use of material from a similar project in the past, or by having the opportunity to study one or more reports from previous years. Similarly you project will be placed in Library / Digital Library as a reference material for University students who are interested to work in the same domain.

FINAL SUBMISSION PROCEDURE & REQUIREMENTSStudents are required to submit all of the items listed below to have their Projects evaluated.

1. Form For Notifying Final Submission – one month before final submission(Available at the college book store in green colour)

2. Final Project Completion Certificate(Please do not include this in binding, give one certificate only as a separate sheet)

3. Two Hard Bound Copies of Final Document (one copy each for Library & Project Office)

4. A Compact Disk (CD) containing the content as required

CONTENTS OF DOCUMENTATION (IMPLEMENTATION PROJECTS)

Once the Project is complete, BS and MCS students are required to submit three hard bound copies of documentation and CD containing the content as explained later. Final evaluation will be conducted only after the submission of this. Document should not be less than 50 pages and there is no limit for maximum number of pages. Following should be the content/chapters of the documentation.

Chapter #

Title & Description

Title PageAs per performa “FinalThesisTitlePage”Signatures PageShould contain the signatures of the Project Advisor, page should be made as per performa “FinalThesisSignaturesPage”AbstractA maximum of one page containing a complete go through of your Project. As explained in document “WhatIsAnAbstract”DedicationA maximum of one page each.Preface or AcknowledgmentA maximum of one page each.Table of Contents Table of Contents with page references starting with Individual listing

of preliminary pages Dedication, Preface or Acknowledgments. Do NOT list abstract.

List of Chapter or Section Headings; Individual listing of Tables, Figures, Illustrations, Software

Specifications, if included. Appendices; Bibliography

Chapter 1 Introduction to the ProblemChapter 2 Existing Solutions and Proposed Solution



Chapter 3 Analysis

Chapter 4 Design

Chapter 5 Testinga. Test case specificationsb. Black Box Test Cases

i. Equivalence Partitions / Classesc. White Box Test Cases

i. Cyclomatic Complexityd. Performance Testing, Stress testing, System testing, Regression

TestingChapter 6 Tools Used

a. Languagesb. Applicationsc. Librariesd. Classes

Chapter 7 Summary and ConclusionsChapter 8 User ManualChapter 9 Lessons Learnt and Future Work / Enhancements

AppendicesAppendix A

Project Management Documentsa. Team Structureb. Roles & Responsibilitiesc. WBS (Work Breakdown Structure)d. PERT Diagram (Based on 10 Months of Work)e. Critical Pathf. Scope Statementg. Project Charterh. Meetings Summary

Appendix B Bibliography/References On standard format as explained in document “Bibliographic Citation”


Object Oriented Approach

Structured Approach

Analysis Document Vision Document Supplementary Specification Software Quality Assurance Plan Software Configuration

Management Plan Use Case Modal Use Cases (Essential) Use Cases (Elaborated) Software Architecture Screen Shots

Analysis Document Vision Supplementary Specification Software Architecture Screen Shots

Object Oriented Approach

Structured Approach

Design Document Database Design Domain Model Operations Contracts System Sequence Diagrams Sequence/Collaboration Diagrams Interaction Diagrams (Optional) Design Class Diagram Component Diagram Deployment Diagram

Design Document Database Design (Normalized),

ERD, Data Dictionary. PLD (Pseudo Code) Flowcharts Decision tables and Decision

trees Data Flow Diagrams Activity Diagram Structure Charts PSpecs Data Dictionary State Transition Diagrams Component Diagram Deployment Diagram

For Web Systems (In addition to the above requirements) Wire Frames Blue Prints


Appendix C IndexBlank Page

CONTENT OF CDs / DVDsThe CD should be labeled by the Group ID, Project Title and Registration Numbers of all students in group.

MAKING THE COVERThe cover of the CD should contain the following

Group ID Project Title Advisor Name UCP Logo Registration Number 1 and Student Name 1 Registration Number 2 and Student Name 2 Registration Number 3 and Student Name 3

* Template for cover and organizing folders is available in “\\shares\projects\templates”

ARRANGING THE CONTENTPut a text file named “group description” in CD containing the following.

Group IDProject TitleAdvisor NameRegistration Number 1 and Student Name 1Registration Number 2 and Student Name 2Registration Number 3 and Student Name 3

The CD should contain the following Folders/content.LIST OF FOLDERSImplementation Projects ThesisFolder Name Content Folder

Name Content

Source Source Code of the Project Research

All of the research material found during the research work.

Documents

Soft copy of Documentation

Soft copy of User Manual

Read Me File as included below

HTML-Help or WIN-Help file containing the compiled help on how to use the application

Documents

Soft copy of Documentation

PDF File A single PDF file of documentation / report to be

PDF File A single PDF file of documentation / report to be



placed in electronic library placed in electronic library

Setup

Compiled setup (Ready to install)

Text file named CD Key containing the installation key, if any

Text file named Read Me, explaining everything needed to get an overview of the project and make it running.

Database

(MDF and LDF) or database backup in case of SQL Server

Mdb file in case of access

Backup file created with backup utility in case of ORACLE

Backup file in all other cases

Prerequisites

Put all software required for the use of your application in this folder.

Also provide list of all the software you have used in coding the software and is required to compile your code.

NOTE: * Please make sure the CD contains all the requirements of the Deployment, because at the time of evaluation you will have to compile and install the application you submit on a newly formatted system containing only the operating system, without any additional software help available.

FORMATTING REQUIREMENTS (Thesis / Documentation / Report and Reference Manual)

The single-sided, normal character spaced manuscript is to be arranged as follows:

BINDING

Three hard-bound copies of the final project documentation /Thesis are required by project office before the Final Evaluation along with a CD named after the Group ID of the group, containing the content as described in detail.

Note: Spine of binding must contain Group ID and Project Title as shown in figure on the left.

Please keep in mind that the binding takes 3-4 days to completeCOLOUR OF BINDINGFor Masters the color of binding should be black with golden text (foreground color) and for BS dark blue back ground with silver text.

PAPER Use 80 grams paper; A4 (8.27 x 11.69) except for oversized items. All copies to be submitted should be printed, photocopies will not be accepted.

FONTS AND SPACING



The preferred font is Times New Roman; acceptable font size is between 10 and 12; different typefaces (e.g., italics) may be used only to show differences in captions and special text. Spacing must be 1.5 between the lines.

Chapter heading 14 PTS BOLD Centre Align All CapsMain Heading 14 PTS BOLD Left Align Paragraph CaseSub-heading 12 PTS BOLD Left Align Paragraph Case

Wherever code is given use Courier New with font size 10

PRINT QUALITY Use laser printers or minimum 600 dpi inkjet printers.

MARGINS AND PAGINATION Left Margin 1 inch from edge of paper Gutter 0.5 inch Top Margin 1 inch from edge of paper Bottom Margin 1 inch from edge of paper Right Margin 1 inch from edge of paper Pages preceding (before) Chapter 1 must have lower case Roman

numerals, right aligned ½ inch from bottom of page, starting with the signatures page that is numbered “ii”. Title page is unnumbered, but is the implied number “i”.

First page of text uses the Arabic number “1” and pages thereafter carry consecutive Arabic numbers, including the pages in the Appendices and the Bibliography.

Arabic numbers are positioned in the bottom right-hand corner, ½ inch from the bottom and one inch in from the right edge of the paper.

HEADER, FOOTER AND FOOTNOTES

Header & Footer Dimensions 0.5 inchesText font in Header & Footer 8 Pts Times New RomanHeader Contents Project Title (Left)

Chapter Title (Right) Alignment JustifyFooter Contents Page Number (Right)Footnote (References) References given in the paragraph must be

mentioned in detail in the footnote and same as mentioned in the Bibliography.

Note: Do not put any lines or boxes in header and footer other than the content as explained above.

ILLUSTRATIVE MATERIALS

TABLES AND FIGURES Color may be used, however, when it is microfilmed, it will be in black and white. If color is used, students must label or number the table or figure so that meaning

can be determined in black and white.

OVERSIZED MATERIALS Oversize foldout pages may be included, though ample margins for binding must

be included. Leave oversize pages unfolded. All pages must be appropriately numbered if bound in the text.



If the oversize pages are bulky, place them in a special pocket at the back. If a pocket is required, it must be listed in the Table of Contents, but no page numbers are required.

A duplicate set of all oversized materials must be submitted.

PHOTOGRAPHS Photographs may be reproduced on 100 percent cotton paper and placed within the standard text margins.

CONTENT OF PROJECT PRESENTATION

Each presentation will be strictly limited to twenty minutes followed by the Demonstration and a Question and Answer session which may last for 1 hour to 1½ hours in total. If you plan ahead and use your time wisely, this is plenty of time. You should endeavor to make your presentation interesting, informative and memorable.

The goal of almost all presentations is to get your evaluators interested enough in what you are talking about that they will want to extract from your discussion and to make evaluators understand and remember the most important idea from your project. You cannot expect to convey a lot of technical information (which they already know), but you should be able to motivate your work and convince them why it is important and interesting, make it abundantly clear what you actually did. There should be some technical content in your talk, including an explanation of conclusions that came out of your work.



1. Introduction a. Project Title, Advisor name and Group Members (with CGPAs)b. What will you cover in your presentationc. Motivation

i. Convey why the problem you are solving is interesting, important and exciting

ii. Existing Solutions Studied : Place your work in context: how is it different from what others have done

d. Scope (as per proposal submitted by you)Project Main Goals & Key Issues: Give the audience a reason to listen to the rest of your talk. Technical presentations should state the main conclusion up front, so your audience knows the point you will be making.

e. Division of workDo Include contribution of each group member

2. Guts a. Explain what you did (in terms of design and/or

implementation)i. Use case modelii. ERDiii. Class diagram

b. Analysis i. Did your work solve the problem? ii. What are the important results of your work?

3. Tests performed on your system4. Bottlenecks and Constraints of the system developed5. Future Enhancements6. Conclusion - Summarize your project with one key point.7. Demonstration

IMPORTANT NOTES:1. Try to avoid using long sentences or paragraphs.2. Preferably make points and explain in your own words orally.3. Limit your slides to a maximum of 30 – 35.4. While choosing a template or background of slides, try using light colors,

keep in mind that the colors don’t look as bright on projector as it appears on your monitors.

5. Avoid using snap shots of system, as you will be displaying them in demonstration as well.

6. Including things you have not done yourself is plagiarism, include reference to the content of slides in the footer of each slide.

7. For the demonstration of your project make sure to add sufficient data to your database so that you don’t need to do this while presenting.

8. Upload your websites on real domains.


BSCS Handbook 2011

Documents

Transcript of BSCS Handbook 2011