Admission Phone No: 0824 - 2441022, 2411383

 0824 - 2441022, 2411383   principalsims@srinivasgroup.com

BCA Project

 

PAPER-XXIII BCA-501: PROJECT WORK/DISSERTATION 432hours
ProjectWork/Week:

36Hrs

Credits:16

   

I.A:160

Exam:640

 

 >> Project Guides List

PROJECT GUIDELINES

Preamble: Project work has been made a part of BCA course to give students exposurein development of quality software solution. The primary emphasis of the project work is to understand and gain the knowledge of the principles of software engineering practices. As such, during the development of the project students shall involve themselves in all the stages of the software development lifecycle(SDLC) like requirements analysis, systems design, software development/coding, testing and documentation, with an overall emphasis on the development of reliable software systems. Since, the project work spans over the entire final semester, the students shall be advised to take up projects for solving problems of software industry or any research organization or the real life problems suggested by the faculty in-charge of BCA project work in the institutions. Topics thus selected, should be complex and large enough to justify as a BCA project. The project should be genuine and original in nature and should not be copied from any whereelse.

 

GENERAL GUIDELINES TO THE INSTITUTIONS

Calendar of Project Work shall be announced before the commencement of the Sixth semester. Calendar shall contain tentative schedules on submission of Project proposals, Project Acceptance, Project Synopsis, Problem Analysis document, System Design, Detailed Design, coding and testing, final report, internal assessment exams (at least two), Viva/Voce etc.

Students shall undertake projects with real life problems (that has direct relevance in day-to-day activities or to knowledge extension) either in their colleges or in industry/research and development laboratories/software companies as recommended by the faculty in-charge of BCA project work in the institutions. If a student intends to do industry project, the faculty in-charge shall ensure that the projects are genuine and original in nature.

There shall be not more than three members in a Project team.

At least two internal assessment exams shall be conducted to evaluate the progress made by the students at different stages of project work. Such exams may include written tests, presentations, work demonstration, group discussion, viva-voce etc. so as to objectively assess the understanding gained by the students in course of their project work.

 

GUIDELINES TO EXAMINERS REGARDING PROJECT VIVA-VOCE

External and internal Examiners shall together conduct project viva-voce objectively. To begin with, the finer details about various points contained in the scheme of valuation may be conclusively agreed upon through mutual consultation. During project evaluation, a student shall present his/her work through live demonstration of the software application developed as a part of project. However, if live demonstration is not possible due to the reason that some companies do not divulge source code on account of ownership rights or copyrights, students may be allowed to make PPT presentation of their authentic works. In such cases, candidates shall produce necessary declarations issued by the companies to this effect. However, students shall be enabled to present their work in entirety. The primary objective of project evaluation shall be to assess the extent of effort that was put in to meet the objectives of the project and also to gauge the understanding gained by the students in course of their project works.

While evaluating Project Reports, examiners shall scrutinize whether Software Development Life Cycle (SDLC) principles have been consistently followed in the project work and the same are documented well in the Reports. However, the relative and overall emphasis of these principles to a particular problem domain chosen may be taken into account so that project evaluations remain fair and objective.

 

THE SCHEME OF PROJECT EVALUATION

 

Sl.No Particulars Marks
 

 

 

 

 

 

 

 

1

  Report Evaluation:400marks
 

1.1

Innovativeness and utility of the project for Industry/Academicor

society(Utility)

 

40

1.2 Related studies about the project(Adequacy) 40
 

 

 

 

1.3

Project plan & implementation-targe tachieved/output delivered

(effectiveness)

 
1.3.1 Analysis 80
1.3.2 Design 80
1.3.3 Implementation 80
1.3.4 Testing 40
 

1.4

Other mandatory documents & information (certificates, contents, tables, figures, bibliography etc.)  

40

 

 

 

 

 

2

  Viva-Voce:240marks
 

2.1

Live Demonstration (Softwareexecution)or Dryruns(Presentation of authentic screenshots or captured videos may be used to walk through complete scenarios)-consistency and completeness  

160

2.2 Question and Answer(OralonlyorOralandwritten) 60
 

2.3

SoftSkills-Communication skills,Teamspirit(if any for working in group)  

20

 

Total Marks

 

640

 

 FORMAT OF PROJECT SYNOPSIS

  1. The project proposal (Synopsis) should contain the following details:
  1. Title of the Project.
  1. Introduction and objectives of the Project.
  1. Project Category (Database/Web Application/ Client-server/Networking/ Multimedia/

gaming etc.).

  1. Tools / Platform, Hardware and Software Requirement specifications.
  1. Analysis (DFDs at least up to second level, ER Diagrams/ Class Diagrams, Database Design etc. as per the project requirements).
  2. A complete structure which includes:
  1. Number of modules and their description to provide an estimation of the student’s effort on the project, Data Structures as per the project requirements for all the modules, Process logic of each module, Testing process to be used, Reports generation (Mention tentative content of report).
  2. Whether Industry Defined/Client Defined/User Defined Project? Mention the type. Mention the Name and Address of the Industry/Client.
  3. Limitation of the project.
  1. Future scope and further enhancement of the project.

 

 

THE PROJECT REPORT

The project report shall contain the following:

Introduction Objectives Tools/Environment used

Requirement Analysis Document ( include SRS in proper structure based on Software Engineering concepts, E-R diagrams/Class diagrams/any related diagrams (wherever applicable), Data Flow Diagrams/other similar diagrams (if applicable), Data dictionary)

Design Document (System & Detailed – Modularization details, Data integrity & constraints including database design, Procedural design, User interface design)

Program code (Complete code (well indented)/Detailed specification instead of code, Comments & Description. The program code should always be developed in such a way that it includes complete error handling, passing of parameters as required, placement of procedure/function statements as needed.)

Testing (Test case designs are to be included separately for Unit testing, Integration testing, System testing; Reports of the outcome of Unit testing, Integration testing, System testing are to be included separately)

Input and Output Screens

Limitations Future scope Bibliography

AWARD OF MARKS

Particulars Max.Marks
Internal Exam Marks 160
FinalExamMarks
Project Dissertation 400
Project Viva/voce 240
Total 800