VANITA VISHRAM WOMEN’S UNIVERSITY,

SURAT
School of Science and Technology
Department of Computer Science

BACHELOR OF COMPUTER APPLICATIONS (BCA)

Guidelines for Submission of B.C.A. Project

B.C.A. (Sem - 6)
Course Type - CORE COURSE – VI
Course Code - CS11240
Course Name - Software Development Project
With effective from Academic year 2023-24
Purpose of Course:
This course provides an opportunity for students to apply the knowledge and skills acquired in
the core courses to larger and more complex problems and to gain experience to work with
them. And to make students get hands on experience of Software/Website development life
cycle.

Course Objective:
The objectives are to:
1) Address industrial, societal, or scientific issues; and
2) Plan, schedule, and oversee the software project.
3) Coherently developing, coding, and testing a big project.
4) Project Documentation.

Pre-requisites:
Knowledge of Operating System, Computer Networking, Software Engineering, Database,
Application Development Tools, Web Designing Related Tools, Computer Languages

Course Outcome:
1) Completing the assignment will give the student extensive experience in creating massive
projects. This kind of experience will involve running into a variety of technical problems,
looking for solutions to the problems, and ultimately figuring out how to satisfactorily handle
all of these problems.
2) Applying analytical thinking to the process of interpreting complex requirements and data
in order to gain a thorough understanding of the solution approach that will be used.
3) Proficiency in writing and documentation.
4) Time management done right.
5) Collaborating with colleagues and producing a significant amount of work.
6) It will get students ready for future work on big projects and industrial issue analysis and
programming.
7) Present the team's work to the evaluation committee.

Guidelines :
BCA Semester – 6 Project Guidelines are mentioned with following perspectives:

1 Project Definition / Title

• The project definition should be finalized before the Internal Examinations.
• Any solution to a real-world problem with a strong potential for applicability,
whether practical or "good" internally defined, will be accepted.

Page 2|6
 2. Team Size
• If any students will not appear for any Company/Institute/Organization/State Govt
Office/Semi Govt Office for Internship and they are selecting UDP (User Defined
Project), It is recommended that the team must be of 5 students.
• If any students will not appear any Company/Institute/Organization/State Govt
Office/Semi Govt Office for Internship and they are selecting IDP (Industry Defined
Project), It is recommended that the team should be of 2-3 students.
Mode of Project Work Place Minimum Maximum
Students Students
per Group per Group
1) UDP Department of 2-3 5
(User Defined Project) Computer
Science
2) IDP Organization 1/2 5
(Industrial Defined Project)

3. Coding/Reporting Standards :
• Project can be developed using any frontend, backend tool. Any Programming
language using concepts of OOPs with database connectivity and report modules
will be considered. Any cutting edge tools and technology will also be considered.
• Project plan along with the division of work amongst teammates would have been
prepared and got approved within a maximum of 5 days of the start of the project.
• Coding standards should be followed meticulously. At the minimum, the code
should be self-documented, modular, and should use the meaningful naming
convention.
• It is advisable that object-oriented methodology is used with the reusability of
classes and code, etc..
• Frontend and Backend technology should be mentioned and must work in that.
• Data structure (database design) is mandatory. At least portions of code
(preferably full code) are mandatory.
• Documentation should contain Project Frontend, backend technologies, Browser
Compatibility, Editor name etc…
• The output reports must include MIS reports, data analysis and Visualization if
applicable.
• Project Report should contain Date wise, Month wise Admin Side Reports as well
as Client Side reports.
Page 3|6
4. Attendance Criteria :
• For UDP Project – 80% Attendance is required and Students have to regularly
attend college regularly for their Project work and they have to submit
Attendance report duly signed by respective Mentor.
• For IDP Project - 80% Attendance is required and Students have to remain
present regularly to Company/Institute/Organization/State Govt Office/Semi
Govt Office for their Project work and they have to submit Attendance report
mentioning in-time and out-time for every 15 days duly signed by designated
person.

5. Mentor Allocation :
• For UDP/IDP Project – Semester – 6 Project Coordinator from Department of
Computer Science will allocate mentors for various projects once you submit
the project title. It might possible to have more than one mentor for individual
project.
• Mentor have rights to cancel / reject / modify project title if he/she is not found
suitable.

6. For IDP Project - Students must maintain 80% attendance, be frequently present
at the company, institute, organisation, state government office, or semi-
government office for their project work, and turn in an attendance report that
includes their in- and out-time for every 15 days which is duly signed by a
designated person.

7. Project Reviews :
1. All students have to compulsorily come in College Uniform along with their
College I-Card on the day of Review.
2. Attendance will be taken at 10.30 AM.
3. Students have to present following work in their project Review :
• Review – 1
Students have to present 25% work of their project which includes following -
Project Definition, Scope, Objectives, Functional Modules
• Review – 2
Students have to present 50% work of their project which includes following : Project
Definition, Scope, Objectives, Functional Modules, Timeline Chart, Data Dictionary,
Diagrams, User Interfaces, References (Minimum 3 working Forms with coding +
Validation with Database Operations)
• Review – 3
Students have to present 70% work of their project with necessary changes discussed
in previous review suggested by review panellist and Students also have to present the
following in review : Project Definition, Scope, Objectives, Functional Modules,
Timeline Chart, Data Dictionary, UML Diagrams(Class diagram, Use cases, Activity

Page 4|6
 diagram, Sequence diagram), minimum 10 User Interfaces (All working Forms with
coding + Validation with Database Operations) and Report module.
• Review – 4 (Final)
Students have to present 100% work of their project with necessary changes discussed
in last review.
• Prepare your final documentation as per given instructions.
• Attached Certificate page in your documentation.
• Approved your final documentation with your respective mentor before final
review date.
• Finalize your Presentation PPT with your mentor before final Review.
5. Review dates will be declared by the concerned Department which will be
applicable to all UDP/IDP project students.
6. IDP students have to remain present and have to take prior leave from their
institute/company.
8. Documentation:

• The project has to be well-documented in the form of a Project Report (at least 50 pages
comprising of the design, data dictionary, source code, screenshots, etc.).
• Format: Print out on both the side of page with single line spacing. Use Times New
Roman of size 10 for normal text.
• Unfair cases of copied versions of the project synopsis and project reports will be sent
to Unfair Means Committee for action.
• Two Hard bound original copy (in Black Colour Binding) of the project report is to
be submitted to the department. One copy submitted to Department and One copy of
the same Project Report is to be retained with the student and the student is supposed
to carry her copy while appearing for viva voce.

Page 5|6
 TABLE OF CONTENTS
Company Profile (i)
Acknowledgement (ii)
List of Figures (iii)
List of Tables (iv)
1. Introduction
1.1. Existing System
1.2. Need for the New System
1.3. Objective of the New System
1.4. Problem Definition
1.5. Core Components
1.6. Project Profile
1.7. Assumptions and Constraints
1.8. Advantages and Limitations of the Proposed System
2. Requirement Determination Analysis
2.1 Requirement Determination
2.2 Targeted Users
3. System Design
3.1. Use Case Diagram
3.2. Class Diagram
3.3. Interaction Diagram
3.4. Activity Diagram
3.5. Data Dictionary
4. Development
4.1. Coding Standards
4.2. Screen Shots
5. Testing
6. Proposed Enhancements
7. Conclusion
8. Bibliography

Evaluation Method:
• 40% Internal Assessment
• 60% External Assessment

Internal Evaluation: Internal Evaluator Faculties will be nominated by the Head of the
Department or the senior most faculty in absence of the Head to evaluate the performance of
the students’ presentation.
External Evaluation: The evaluation should be as per the following break up:
Criteria for Evaluation of Software Projects

• Project Definition: 10%

• Related project Study Analysis: 20 %
• Design & Development: 40%
• Implementation & Testing: 10%
• Creation of Project Report and Presentation: 20%
Page 6|6