Centre for Information Technology

University of Petroleum & Energy Studies, Dehradun

Guidelines for B. Tech. (Minor/Major) Project as per Outcome Based Approach

Minor/Major Projects are effective tool for outcome assessment of the course and program. CIT
will adhere to the following Project Cycle for smooth progress and record keeping during
intermediate stages.

Steps of the project cycle are as below:

1. Title Assignment and Title Approval

(Please refer Annexure-1S for Students and Annexure-1F for Faculty)

2. Panel Allotment for Projects Assessments at different stages and Formation of Project
Committee

(Please refer Annexure-2S for Students and Annexure-2F for Faculty)

3. Synopsis Submission

(Please refer Annexure-3S for Students and Annexure-3F for Faculty)

4. Monthly Assessment of the project

(Please refer Annexure-4S for Students and Annexure-4F for Faculty)

5. Mid-Semester Assessment of the Project

(Please refer Annexure-5S for Students and Annexure-5F for Faculty)

6. End-Semester Assessment of the Project

(Please refer Annexure-6S for Students and Annexure-6F for Faculty)

 (Annexure-1S for Students)

Title Assignment and Title Approval

1. Project title may be selected by student(s)

2. Student may also approach any faculty member for a Project Title

3. Project Title should be comprehensive and describes the objectives clearly (Pl. refer point no.
8, 9 and 10: Annexure 3S)

4. A Faculty may suggest a change to the Project Title on the basis of feasibility and resource
availability.

5. Project title may not be a direct topic from any course books. For example, Bellman’s Ford
Algorithm, Stack and Queue, Shortest Job First etc. will not be accepted or allotted.

6. One Project Title will not be allotted to more than one project group.

7. One Project Title should be allotted to Project Group having minimum two members and
maximum four members.

8. Individual students will not be allotted any Project Title.

9. Change of Project Title could be done only with consultation and consent of concerned project
supervisor and Activity Coordinator and the Panel Members.

10. Project Title Approval form must be filled by the Project Group and must be approved by the
supervisor and Program Head (Please see Form CIT_P_1)

11. A Project Committee will be formed consisting of Associate Dean, Program Heads, Activity
Coordinator and a Nominated Faculty Member.

12. This phase should start one week prior to completion of the last semester.

13. This phase should complete one week post commencement of current semester.

14. Each project group for Minor-2, Major-1 and Major-2 must get signoff from their last
supervisors of Minor-1, Major-1 and Major-2.
 Form CIT_P_1

Centre for Information Technology

University of Petroleum & Energy Studies, Dehradun

Project Title Approval Form (2015-16)

Minor I/ II Major I/ II

Signoff:

Project Title: Student project name

Project Objective:

Team Member(s):

S. No. Name of the Student Specialization & Semester Roll Number SAP ID
Role of Each Student:

S. No. Role of the Student Sign of the student

1.

2.

3.

4.

Approved By

(Name & Sign) (Name & Sign)

Project Guide Program Head

 Annexure-1F

Title Assignment and Title Approval

1. Faculty may also propose names for Project Title.

2. Each Faculty may guide 4 projects in total with at least one Minor and one major project.

3. More than 4 projects require the approval of Project Committee.

4. Faculty may opt out of any project only with the permission of Associate Dean/Program Head.

5. Association of faculty with any project should consider the Conflict of Interest issue.

6. A Faculty may suggest a change to the Project Title on the basis of feasibility and resource
availability of the resources.

7. Any Change in the Project title should be communicated to Activity Coordinator before next
Assessment.

8. A Project Committee will be formed consisting of Associate Dean, Program Heads, Activity
Coordinator and a Nominated Faculty Member.
 (Annexure-2S for Student)

Panel Allotment for Projects Assessments at different stages and Project Committee
Formation

1. Project Panels will be finalized by Activity Coordinators through consultation with Program
Heads.

2. Project Panels will remain fixed for a given project group.

3. Any dispute related to Projects and Project Panels will be dealt by Project Committee.
 (Annexure-2F for Faculty)

Panel Allotment for Projects Assessments at different stages and Project Committee
Formation

1. Project Panels will be finalized by Activity Coordinators through consultation with Program
Heads.

2. Project Panels will remain fixed for a given project group.

3. Project panel will be constituted on the basis of availability and Domain expertise of faculty
members.

4. Panel members may be changed by Activity Coordinator after consultation with concerned
Program Heads.

5. Panel Information will be maintained by Activity Coordinator.

6. Information about inclusion of any faculty in any Panel should be circulated by Activity
Coordinator.

7. Project supervisors and Activity Coordinators will be default members of the Panel for
particular course.

8. A Project Committee will be formed consisting of Associate Dean, Program Heads, Activity
Coordinator and a Nominated Faculty Member.

9. Any dispute related to Projects and Project Panels will be dealt by Project Committee.

10. This phase should be completed and notified by the end of 2nd week of current semester.
 (Annexure-3S for Students)

Synopsis Submission

1. Synopsis presentation should be held in the presence of Activity Coordinator and Project
Panel.

2. Panel Members may approve or disapprove the synopsis.

3. Repeated synopsis presentation should be held within one week of scheduled synopsis
presentation.

4. All the Project members should be present at the time of Synopsis Presentation.

5. Synopsis document should be formatted as per Form CIT_P_2. Format should be followed
strictly.

6. All the project members should come in college uniform and properly dressed during synopsis
presentation. Any kind of casual behavior will not be tolerated.

7. Synopsis should clearly specify the language for implementation and other details.

8. Minor-1 Projects should emphasize:

 Algorithm.
 C as Language.
9. Minor-2 Projects should emphasize:

 UML.
 C, C++ as Language and Backend if necessary.

10. Major-1 and Major-2 Projects should emphasize:

 UML, Agile and other Modelling Tools.

 Any Language and Backend.
11. This phase should be completed by the end of 3rd week of current semester.
 Form CIT_P_2
MINOR/MAJOR PROJECT

SYNOPSIS

ON

INTELLIGENT TYPING TUTOR

Submitted By

Student-1 name Student-2 name Student-3 name Student-4 name

Sap ID Sap ID Sap ID Sap ID

Under the guidance of

GUIDE NAME
Designation

Department of Computer Science & Engineering,

Department of Computer Science and Engineering,

Centre for Information Technology,
UNIVERSITY OF PETROLEUM AND ENERGY STUDIES
Dehradun-248007
2015
 Centre for Information Technology
University of Petroleum & Energy Studies, Dehradun

Project Proposal Approval Form (2015-16)

I/ II I/ II
Minor Major

Project Title:
___________________________________________________________________________________

Abstract: (Half to 2/3 of a page)(Mention Keyword at the Bottom)

Introduction: (Describe the Market Dynamics and background of the project)

Problem Statement:
Literature Review:

Objectives:

Methodology:

System Requirements: (Software/Hardware)

Schedule: (PERT Chart)

References:

Project Outcomes

PO1
PO2
PO3
PO4

* Whole Documents should not be more than 7 pages excluding Front Page

Project Panel

Faculty Name Signature Approve/Comments

 Approved By

(Name & Sign) (Name & Sign)

Project Guide Program Head

 (Annexure-3F for Faculty)

Synopsis Submission

1. All members of a Project Panel should ensure their presence in the synopsis presentation.

2. All members of Project Panel will be informed of their schedules well in time by Activity
Coordinator.

3. Panel Members may approve or disapprove the synopsis.

4. Repeated synopsis presentation should be held within one week of scheduled synopsis
presentation.

5. Panel members should check the synopsis document as per format finalized for students in
CIT.

6. Panel members should specify their comments on the synopsis/project approval format.

7. Panel members should avoid any casual behavior and approach.

8. Panel members should follow the code-of-conduct as per CoES or CIT guidelines.

9. Activity Coordinators may raise a conflict/dispute in special cases where the final decision
will rest with Program Heads/Heads/Associate Deans.

10. Minor-1 Projects should emphasize:

 Algorithm.
 C as Language.
11. Minor-2 Projects should emphasize:

 UML.
 C, C++ as Language and Backend if necessary.

12. Major-1 and Major-2 Projects should emphasize:

 UML, Agile and other Modelling Tools.

 Any Language and Backend.
 (Annexure-4S for Students)

Monthly Assessment of the project

1. Monthly assessment of each project is mandatory.

2. Monthly assessment of each project group will be done by concerned supervisor.

3. Activity coordinators will coordinate the monthly assessment for smooth record keeping.

4. At least two monthly assessments are mandatory for each project group.

5. Schedule for assessment should be finalized or arrived at by each project group with mutual
consent of project supervisor, project group member and Activity Coordinator.

6. Monthly assessment will be performed against project outcome specified in submitted

synopsis (Please see CIT_P_2) and rubrics specified in Appendix 1.

7. Two poor reports will render project group failed for the same.

8. This phase should complete in 2nd week of 2nd, 3rd and 4th month of current semester.
 (Annexure-4F for Faculty)

Monthly Assessment of Projects

1. Monthly assessment is project wide assessment parameters.

2. Activity coordinator should coordinate the monthly assessment for smooth and formal
assessment.

3. Assessment records will be maintained by ACs.

4. Project supervisors will assess each project group assigned to him or her.

5. Project supervisor may assign satisfactory or unsatisfactory progress to project or project

group as per project outcomes finalized in synopsis.

6. Monthly assessments should be part of gross awards allotted to the project group or project
members.

7. Monthly assessment will be performed against project outcome specified in submitted

synopsis (Please see CIT_P_2) and rubrics specified in Appendix 1.
 (Annexure-5S for Students)

Mid-Semester Assessment of the Project

1. Mid-Semester assessment of each project is mandatory.

2. Mid-Semester assessment of each project group will be done by Panel finalized for the Project
Group.

3. Project Group members must contact their ACs who will coordinate the Mid-Semester
assessment for smooth record keeping.

4. Schedules for Mid-Semester assessment will on working Saturdays.

5. Absence of one or more project group members in Mid-Semester will result in zero mark.

6. Mid-Semester assessment will performed as per rubrics in Appendix 1.

7. Mid-Semester assessment will not be rescheduled except under unavoidable circumstances.

8. This phase should be completed by the end 4th week of 3rd month of current semester.
 (Annexure-5F for Faculty)

Mid-Semester Assessment of the Project

1. All the members of panel must be available during Mid-Semester assessment.

2. Panel should follow the evaluation rubrics available with this document.

3. Activity Coordinators and Project Supervisor ought to accompany the panel during Mid-
Semester assessment.

4. Activity Coordinators must communicate the schedules of Mid-Semester assessment at least

one-week before the scheduled assessment.

5. Activity Coordinators must ensure that monthly assessment record is also available during
Mid-Semester assessment.

6. Schedules for Mid-Semester assessment should be on working Saturdays.

7. Panel members and ACs must ensure the formal evaluation environment during Mid-Semester
assessment.

8. Mid-Semester assessment should assess each project group member and allocate awards to
individuals as per evaluation rubric.

9. Mid-Semester assessment will performed as per rubrics in Appendix 1.

10. This phase should be completed by the end 4th week of 3rd month of current semester.
 (Annexure-6S for Students)

End-Semester Assessment of the Project

1. End-Semester assessment of each project is mandatory.

2. End-Semester assessment of each project group will be done by Panel finalized for the Project
Group.

3. Project Group members must contact their ACs who will coordinate the End-Semester
assessment for smooth record keeping.

4. Schedules for End-Semester assessment will be during last week of semester.

5. Absence of one or more project group members in End-Semester will result in zero mark for
absentee.

6. End-Semester assessment will performed as per rubrics in Appendix 1.

7. End-Semester assessment will not be rescheduled at all.

8. This phase should be completed by the end 4th week of 4th month of current semester.
 (Annexure-6F for Faculty)

End-Semester Assessment of the Project

1. All the members of panel must be available during End-Semester assessment.

2. Panel should follow the evaluation rubrics available with this document.

3. Activity Coordinators and Project Supervisor ought to accompany the panel during End-
Semester assessment.

4. Activity Coordinators must communicate the schedules of End-Semester assessment at least

one-week before the scheduled assessment.

5. Activity Coordinators must ensure that monthly assessment record is also available during
End-Semester assessment.

6. Schedules for End-Semester assessment should be during last week of the semester.

7. Panel members and ACs must ensure the formal evaluation environment during End-Semester
assessment.

8. End-Semester assessment should assess each project group member and allocate awards to
individuals as per evaluation rubric in Appendix 1.

9. This phase should be completed by the end 4th week of 4th month of current semester.
 Appendix – 1 (Project Report Evaluation Rubrics)

Rubric for evaluation of project report and the presentation for the B. Tech
(minor/major) Project: Direct measure 1

B. Tech (Minor/Major) Project – Rubric

(B. Tech CoES)

(A). B. Tech (Minor/Major) Project Report Evaluation (35 Marks)

Name: _______________________________________ Enrolment No. ________________ _________

Semester: _________________________________

Poor Good Very Good Excellent Total

Points Required (0-2) (3-5) (6-8) (9-10)
1.Introduction Introduction does Introduction somewhat
(10) not clearly explain explains the Introduction to a good
the background and background and extent explains the Introduction very
significance of the significance of background and aptly explains the
project, lacks the project with some significance of background and
conceptual clarity, conceptual clarity, and the project with enough significance of
and motivation for motivation for conceptual clarity, and the project with much conceptual
the study is the study can be traced Motivation for the study clarity, and
completely missing. with difficulty. can be traced. Motivation for the study is clearly
visible.

2. Exploration of Exploration of idea is
ideas (10) insufficient and lacks
relevance, does not
contain recent
publications in
adequate numbers and
lacks consistency with
project questions. Ideas
are vague.
Exploration of idea is Exploration of idea is Exploration of idea is strong,
barely sufficient and sufficient and mostly adequate in numbers and recent.
vaguely relevant. Does relevant. Contains some Supports the project problem
not contain recent recent publications in and identifies gaps in the project
publications in adequate numbers and is very well. Ideas are innovative in
adequate numbers and able to connect project the field of study.
connects project questions. . Ideas have
question vaguely. Ideas relevance.
have some relevance.
3. Problem & Problem is not clear at
Objectives all, variables pertaining
(10) to the project problem
have been ignored, and
it does not relate to the
objectives.
4. Methodology/ Methodology is not clearly
Design of written or the one that is
experiment/ written is completely
Modelling & inappropriate to the study.
Simulation (20) Experiment is
inappropriate.
Problem is somewhat Problem is clear, most of
clear, some variables the variables pertaining to
related to the project the project problem have
problem are stated and been identified. Objectives,
it barely connects to the to a good extent, justify the
objectives stated. project problem.
Methodology Methodology written is, to
a good extent, appropriate
is sketchy, barely a
to the project problem,
few elements make
while there are still gaps
sense, whereas the
that need to be addressed.
rest do not fit the
Experiment has been
study in question
designed properly.
appropriately
Modelling & Simulation is
Problem is clearly defined and all
the relevant variables pertaining
to the project problem are
identified and the objectives
drawn are meaningful to address
the project problem
Methodology
is well-structured, project
Design is appropriate with all of
the elements logically sequenced
to carry out the study
meaningfully and also address all
the objectives stated. Experiment
design is excellent. Modelling

Experiment is giving good results. and simulation are giving very

somewhat useful to good results.

the study.

5. Analysis & Analysis is not
Interpretation
Synchronized with
(30)
project objectives.
Interpretations
are erroneous
and not related
to the objectives.
Analysis is Analysis is mostly Analysis is synchronized with
sometimes In line In line with project project objective.
with project but is
objectives and somewhat Interpretations are meaningful. It
vague. clear. is very much possible to address
Interpretation Interpretation are all the project objectives from the
somewhat meaningful analysis.
can barely draw
and possible to draw some
some inferences
meaningful inferences.
related to the
objectives.

6. Findings, Findings drawn are A few findings Some findings Most of the
Conclusion & completely not in line
are in line with are in line with findings
Recommendations with objectives and
(10) therefore, Conclusions project project are in line with
& Recommendations
don’t make any sense. objectives and objectives and project

therefore, therefore, objectives and

a few conclusions some therefore,

and a few conclusions conclusions

Recommendations
can be logically and drawn and
drawn. recommendations address
Recommendations the project questions and
can be logically
 drawn. objectives.

7. References & References are References are References are adequately References are neatly covered as
Appendices inconsistent somewhat consistent covered and are as per the per prescribed format with all
(optional) with review of literature prescribed relevant sources covered. Tables
with review of
and presented as per Format. Tables / figures / / figures / questionnaires are
literature and also
(10) the prescribed format. questionnaires are appended as per the project
not as per the
Sources are not clearly included. guidelines.
prescribed format..
mentioned
Sources are missing,
& tables /figures /

tables/figures/ questionnaires are not

appended.
Questionnaires are
not appended.

Total (1 to 7)

*Marks assigned under point required are indicative on the scale of 10 marks. In case of
different marks in attribute rows, the actual marks can be assigned accordingly. To
elaborate the mark for example under max marks of 10 excellent is 9-10, however on the
scale of 20 it will become 18-20. Evaluation is carried out of 100 marks and then
weightage is taken out of 35 marks.

Part (B) is the Presentation: 35 marks.

Total: (A) + (B) = 70 Marks

 (Project Presentation Evaluation Rubrics)
(B). B. Tech (Minor/Major) Project Presentation (100 Marks)

Particulars Poor Good Very good Excellent Total

(0-5)
(6-13) (14-20) (21-25)
1. Structure(25) The structure The structure of the Structure of the The structure of the
 Sequence completely lacks presentation barely presentation is mostly presentation is

 Logical logical structure meets guidelines. logical in line with the completely as per

 Language against guidelines. Some plot and guidelines. Some plots the guidelines.
Plots and diagrams diagrams are and diagrams do not Appropriate plots
 Contents
are inappropriate or appropriate. Needs make sense. The and diagrams are
 Plots/tables/
completely missing. lot of improvement in language is good but employed.
 flow diagram
Language is very the language. could be improved.
loose with many
grammatical errors.
2. Knowledge of Project (25) Project problem Project problem is Project problem is Project problem is
 Depth completely misses not defined well, defined, partially defined, fully

 Accuracy the practical aspects, lacks integration with integrated with the integrated with the

 Practical project problem is the background of background of the background of the

vague and variables the problem, problem, variables problem, variables
 Content
are not defined at all. variables not defined defined explicitly but defined explicitly at
 Recent facts
Analysis of problem explicitly, and the analysis is not the same time
is missing. project problem is completely validated. analysis is
not analyzed in Managerial statistically
detail. implications are not validated.
very well defined. Managerial
implications are
defined well and
meets all the project
objectives
3. Findings conclusions Findings, conclusions Some findings, Many findings, Most or all of the
and suggestions (25) and suggestions are conclusions and conclusions and findings,
 Factual completely in suggestions are suggestions are conclusions and

 Objective consistent with the consistent with the consistent with the suggestions are

 Consistent flow objectives objectives objectives consistent with the

objectives.
 Practical applications
 Recommendations

4. Presentation Skills & Handling Poor language, with Barely good language Good language and very Very good and
of Questions (25) many grammatical with some few grammatical errors. grammatically
 Verbal Communication errors, meek body grammatical errors. Confident body correct language.
 Confidence language and no eye Body language not language but slide Very confident body
  Precise & concise contact while very confident. Poor layout and language and eye
 Body Language presenting. Very poor slide layout and professionalism could contact. Slides layout

 Aesthetics of Slides slide layout and somewhat be improved. is appropriate and a

unprofessional. professional. professional
approach is
exhibited.
Total (1 to 4)

*Evaluation is carried out of total (200) and converted into 70 marks.

Total Marks (A + B) =

Evaluator 1 ________________________________

Evaluator 2 ________________________________

Date:
 (Continuous Project Report Evaluation Rubrics)
Part C:

Poor Good Very Good Excellent Total

Points Required (0-2) (3-5) (6-8) (9-10)

1. SRS and
No SRS prepared SRS prepared and (or) no SRS prepared and no No SRS prepared and
Design DFDs established for the DFDs established for no DFDs established
and no DFDs
(10) problem being solved the problem being for the problem
established for the
1st Monthly through minor/major solved through being solved through
problem being
Assessment project. But SRS don’t minor/major minor/major project
solved through
convey complete project, Partially and meets Project
minor/major information about meets Project Objectives
project. Don’t meet project. Don’t meets Objectives.
any Project Project Objective or

Objectives. Poorly Meets Project

Objectives.

2.
No Modularization and Partial Modularization Satisfactory Satisfactory
Modularization
non-executing code and Partial executing Modularization and Modularization and
and Coding
code Don’t meets Project . Partially Executing Completely
(10) Don’t meet any Project
Objective or Poorly Meets Modules Partially Executing code and
Objectives.
2nd Monthly Project Objectives. meets Project Meets Project
Assessment Objectives. Objectives
3. Integration
Poorly Integrated Code Satisfactory Integrated Satisfactory Satisfactory
and Testing
and available in chunks Code with Not Testing. Integration code and Integrated Code and
(10)
Testing done and Testing Done and
3rd Monthly No Testing done. Don’t meets Project .
Partially meets Meets Project
Objective or Poorly Meets
Assessment Project Objectives. Objectives
Don’t meet any Project
Project Objectives.
Objectives.

Total (1 to 3)

Continues assessment by Mentor 30 marks

Total Marks (A + B+C) = 100