B.

COM(COMPUTER APPLICATION) – (BCCA)

PROJECT GUIDELINE SESSION

(2022-23)

DEPARTMENT OF COMMERCE, MANAGEMENT & COMPUTER

HISLOP COLLEGE, CIVIL LINES, NAGPUR

 CONTENTS

Sr. No. Topic Page No.

I Message from the Project Coordinator 3

II Calendar for the Project 4

III Proforma for the Approval of the Project Proposal 5

IV Introduction and Objectives 6

V Type of the Project and Eligibility criteria of the Project Guide 7

VI Points to remember while preparing the project proposal 11

VII Points to remember while preparing the project report 13

VIII Assessment guidelines for project evaluation 16

IX Software and broad areas of application 20

X Sample Cover Page 22

I - MESSAGE FROM THE PROJECT CO-ORDINATOR
The B.Com(Computer Application) – (BCCA) programme prepares the students to take
up positions as Systems Analysts, Systems Designers, Software Engineers,
Programmers and Project Managers in any field related to information technology. We
had therefore imparted you the comprehensive knowledge covering the skills and core
areas of computer application courses with equal emphasis on the theory and
practicals.

Approval of the project proposal is mandatory to continue and submit the project
work.

The theoretical background of various courses provides you the necessary foundation,
principles, and practices to develop effective ways to solve computing problems. The
hands on experience gained from the practical courses provides you the knowledge to
work with various operating systems, programming languages, software tools and
testing tools.

The objective of the BCCA project work is to develop quality software solution. During
the development of the project, you should involve in all the stages of the software
development life cycle like requirements engineering, systems analysis, systems
design, software development, testing strategies and documentation with an overall
emphasis on the development of reliable software systems. The primary emphasis of
the project work is to understand and gain the knowledge of the principles of software
development practices, so as to participate and manage a large software development
projects in future.

Students should take this project work very seriously. Topics selected should be
complex and large enough to justify as a UG project. The project should be genuine
and original in nature and should not be copied from anywhere else. If found copied,
the project report will be forwarded to the Exam Discipline Committee of the
University as an Unfair means case for necessary action. Students should strictly follow
and adhere to the project guidelines.

I wish you all the success.

Project Coordinator
II - CALENDAR FOR THE PROJECT

Sr. No. Topic Date

Submission of a preference guide name and
1 project title (at least 3 project topic is mandatory 17/03/2023
for submission)
2 Approval of guide name and project title 18/03/2023
Submission of the project synopsis online as well
3 25/03/2023
as offline (if possible).
4 Submission of the first progress report to guide 10/04/2023

5 Submission of the second progress report to guide 20/04/2023

6 Submission of the project report (softcopy) 25/04/2023

As per university
7 Final project report submission (Hardcopy)
schedules
As per university
8 Viva-Voce to be conducted (Internal)
schedules
9 Viva-Voce to be conducted (External) As per university schedule
III - PROFORMA FOR THE APPROVAL OF THE PROJECT PROPOSAL
Visit the below link for further process.

https://opmshislop.in/
IV - INTRODUCTION AND OBJECTIVES
The Project work constitutes a major component in most professional programmes. It
needs to be carried out with due care, and should be executed with seriousness by the
students. The project work is not only a partial fulfilment of the UG/PG requirements,
but also provide a mechanism to demonstrate your skills, abilities and specialisation.
The project work should compulsorily include the software development. Physical
installations or configuring the LAN/WAN or theoretical projects or study of the
systems, which doesn’t involve s/w development, are strictly not allowed.

OBJECTIVES

The objectives of the project is to help the student develop the ability to apply
theoretical and practical tools/techniques to solve real life problems related to
industry, academic institutions and college computer laboratories. After the
completion of this project work, the student should be able to:

 Describe the Systems Development Life Cycle (SDLC).

 Evaluate systems requirements.
 Complete a problem definition.
 Evaluate a problem definition.
 Determine how to collect information to determine requirements.
 Perform and evaluate feasibility studies like cost-benefit analysis, technical
feasibility, time feasibility and Operational feasibility for the project.
 Work on data collection methods for fact finding.
 Construct and evaluate data flow diagrams.
 Construct and evaluate data dictionaries.
 Evaluate methods of process description to include structured English, decision
tables and decision trees.
 Evaluate alternative tools for the analysis process
 Create and evaluate such alternative graphical tools as systems flow charts and
state transition diagrams.
 Decide the S/W requirement specifications and H/W requirement
specifications.
 Plan the systems design phase of the SDLC.
 Distinguish between logical and physical design requirements.
 Design and evaluate system outputs.
 Design and evaluate systems inputs.
 Design and evaluate validity checks for input data.
 Design and evaluate user interfaces for input.
 Design and evaluate file structures to include the use of indexes.
 Estimate storage requirements.
 Explain the various file update processes based on the standard file
organizations.
 Decide various data structures.
 Construct and evaluate entity-relationship (ER) diagrams for RDBMS related
projects.
 Perform normalization for the un-normalized tables for RDBMS related
projects.
 Decide the various processing systems to include distributed, client/server,
online and others.
 Perform project cost estimates using various techniques.
 Schedule projects using both DFD and Flow charts.
 Perform coding for the project.
 Documentation requirements and prepare and evaluate systems
documentation.
 Perform various systems testing techniques/strategies to include the phases of
testing.
 Systems implementation and its key problems.
 Generate various reports.
 Be able to prepare and evaluate a final report.
 Brief the maintenance procedures and the role of configuration management in
operations.
 To decide the future scope and further enhancement of the system.
 Plan for several appendices to be placed in support with the project report
documentation.
 Work effectively as an individual or as a team member to produce correct,
efficient, well organized and documented programs in a reasonable time.
 Recognize problems that are amenable to computer solutions, and knowledge
of the tools necessary for solving such problems.
 Develop of the ability to assess the implications of work performed.
 Get good exposure and command in one or more application areas and on the
software.
 Develop quality software using the software engineering principles.
 Develop of the ability to communicate effectively.
 V - TYPE OF THE PROJECT AND ELIGIBILITY CRITERIA OF THE PROJECT

Type of the Project

The majority of the students are expected to work on a real-life project preferably in
some industry/ Research and Development Laboratories/Educational
Institution/Software Company. Students are encouraged to work in the areas listed at
the end. However, it is not mandatory for a student to work on a real-life project. The
student can formulate a project problem with the help of her/his Guide and submit the
project proposal of the same. Approval of the project proposal is mandatory. If
approved, the student can commence working on it, and complete it. Use the latest
versions of the software packages for the development of the project.

Steps involved in the project work

The complete project work should be done by the student only. The role of guide
should be about guidance wherever any problem encounters during project. The
following are the major steps involved in the project, which may help you to determine
the milestones and regulate the scheduling of the project:

 Select a topic and a suitable guide.

 Prepare the project proposal in consultation with the project guide.
 Submit the project proposal along with the necessary documents to the project
guide concerned.
 Carry out the project-work.
 Prepare the project report.
 Submit the project report to the guide concerned
 Appear for the viva-voce as per the intimation by the university schedules.
Communication of the approval

Communication regarding the project Approval/Non-approval will be sent to you

within four to six days after the receipt of the project proposal by the project
coordinator concerned.

Resubmission of the project proposal in case of non-approval or late submission

In case of non-approval or late submission, the suggestions for reformulating the

project will be communicated to you. The revised project synopsis along with a new
proforma, should be re-submitted along with a copy of the earlier synopsis and non-
approval or rejected project proposal proforma in the next schedule.
The revised project proposal should be sent along with the original copy/ photocopy
of the non-approved proforma of the earlier submitted proposal, to the Project
Coordinator Concerned.

Resubmission of project in case of failed students

If the student is unsuccessful in the project, s/he should ‘re-do’ the whole cycle, right
from the submission of the project proposal. Students are advised to select a new topic
for the project and should prepare and submit the project proposal to the Project
Coordinator concerned as per the project guidelines. There are no separate slots for
the submission of the project synopsis/project reports for the failed students.
Respective submissions of the project synopsis and the project reports should be done
strictly as per the “academic calendar of the project” given in the project guidelines.
 VI - POINTS TO REMEMBER WHILE PREPARING THE PROJECT PROPOSAL

Project Proposal Formulation

The project proposal should be prepared in consultation with your guide. The project
proposal should clearly state the project objectives and the environment of the
proposed project to be undertaken. The project work should compulsorily include the
software development. The project proposal should contain complete details in the
following form:

Proforma for Approval of Project Proposal duly filled and signed by both the student
and the Project Guide with date.

Synopsis of the project proposal (3-4 pages) covering the following aspects

Format of Synopsis for Desktop Application

1. Title of the Project.

2. Objectives of the Project.

3. Project Category (DBMS / RDBMS / OOPS etc.).

4. Tools / Platform and Languages to be used.

5. Complete Structure of the System:

i. Numbers of Modules and its Description.

ii. Modular Chart / System Chart.

iii. Data Structures or Tables.

iv. Process Logic of each Module.

v. Types of Report Generation.

6. References.

Format of Synopsis for Web Application

1. Title of the Project.

2. Objectives of the Project.

3. Project Category (DBMS / RDBMS / OOPS etc.).

4. Tools / Platform and Languages to be used.

5. Complete Structure of the System:

i. Number of pages and links their short description.

ii. Use / Information of Pages.

iii. Feedback Form (if any).

6. References.
 VII - POINTS TO REMEMBER WHILE PREPARING THE PROJECT REPORT

1. Project Report Formulation:

The project report should contain the following:
(i) Original copy of the Approved Proforma and Project Proposal.
(ii) Certificate of Originality.
(iii) Project documentation.
(iv) A CD consisting of the executable file(s) of the complete project should be attached
on the last page of the project report. In no case, it should be sent separately. The
student needs to retain the identical copy of the CD that should be carried while
appearing for the viva-voce along with the project report.
2. The project documentation may be about 100 to 125 pages (excluding coding). The
project documentation details should not be too generic in nature. Appropriate project
report documentation should be done, like, how you have done the analysis, design,
coding, use of testing techniques/strategies, etc., in respect of your project. To be
more specific, whatever the theory in respect of these topics is available in the
reference books should be avoided as far as possible. The project documentation
should be in respect of your project only. The project documentation should include
the topics given below. Each and every component shown below carries certain
weightage in the project report evaluation.
Project Report Formulation
Front Page.
College Certificate Page
Declaration Page
Acknowledgment Page.
Project Profile.
Index or Content Page.
i. *Contents ——————————.
Appendices
i. List Figures, Tables& Charts.
ii. Approved copy of Synopsis.
* Contents
 i. Introduction.
ii. Objectives.
iii. Preliminary System Analysis.
Preliminary Investigation.
Present System in Use.
Flaws in Present System.
Need of New System.
Feasibility Study.
Project Category.
iv. Software Engineering Paradigm Applied
Modules
System / Modular Chart
v. Software & Hardware Requirement Specification.
vi. Detailed System Analysis.
Data Flow Diagram.
Numbers of Modules and Process Logic.
Data Structures and Tables.
Entity-Relationship Diagram.
vii. System Design.
Form Design.
Source Code.
Input screen & Output Screen.
viii. Testing &Validation Checks.
ix. System Security Measures.
x. Implementation, Evaluation and Maintenance.
xi. Future Scope of the project.
xii. Suggestion & Conclusion
xiii. Bibliography& References.
Should attach a copy of the CD containing the executable file(s) of the complete
project.
3. The project report should normally be printed with single line spacing on A4 paper
(one side only). All the pages, tables and figures must be numbered. Tables and figures
should contain titles.

4. If any project report is received in the absence of the approved project proposal
proforma (in original), project synopsis with her/his signature on it, certificate of
originality and CD it will be summarily rejected and returned to the student for
compliance.

5. Through out the project report, the title of the project should be the same as per the
approved synopsis. Signature of the Project Guide in the Certificate of Originality
should match with the signature in the Project Proposal proforma also.

6. Only one copy of the original project report in the bound form along with the CD
(containing the executable file(s) of the project should be enclosed in the last page) is
to be submitted to the project coordinator. One photocopy of the same Project Report
and the CD containing the executable file(s) must be retained by the student, which
should be produced before the examiner at the time of viva-voce.

7. A photocopy of the project report is not acceptable for submission.

8. Student should be involved in each and every phase of Project Development. If it is

found that student is not involved in any phase for example coding phase, it may lead
to the rejection/disqualifying of the project at any stage.

9. Title of the project should be kept the same throughout the project.

The following suggested guidelines must be followed in preparing the Final Project
Report: Good quality white executive bond paper A4 size should be used for typing.
Care should be taken to avoid smudging while creating the copies.

Page Specification :(Written paper and source code) Left margin - 3.0 cms 3 Right
margin- 2.0 cms Top margin 2.54 cms Bottom margin 2.54 cms Page numbers - All text
pages as well as Program source code listing should be numbered at the bottom center
of the pages.

Normal Body Text: Font Size: 12, Times New Roman, Double Spacing, Justified. 6 point
above and below para spacing

Paragraph Heading Font Size: 14, Times New Roman, Underlined, Left Aligned. 12
point above & below spacing.

Chapter Heading Font Size: 20, Times New Roman, Centre Aligned, 30 point above and
below spacing.

Coding Font size : 10, Courier New, Normal

VIII - ASSESSMENT GUIDELINES FOR PROJECT EVALUATION
Each and every component of the project work and the viva voce carries its own
weightage, so the student needs to concentrate on all the sections given in the project
report formulation. In this section, we have given a few general parameters as
checkpoints for the assessment of any software development project. You can note
these points and emphasise them during the project report preparation and
examination. Basically, assessment will be based on the quality of your report, the
technical merit of the project and the project execution. Technical merit attempts to
assess the quality and depth of the intellectual effort, you have put into the project.
Project execution is concerned with assessing how much work you have put in.

Analysis
In Project planning include cost estimation and project scheduling. The Cost and efforts
estimation is to be done with the help of functional point analysis or other similar
methods. The project scheduling is identified with:
(i) PERT chart: Proper decomposition of stages, and
(ii) Gantt chart: Time, line structure and validity of chart.
You may know that the software requirement specification (SRS) document is one of
the important documents of your project. The indicators for SRS document is whether
you have used some standardisation like IEEE standards or any other international
standard, or whether your SRS has a proper structure based on sound software
engineering concepts as given in unit 3 or it is given in a running text. Project analysis
for DBMS/Application development projects should contain the ER diagram, Data Flow
Diagram and Data Dictionary, so you should include these with the following
requirements. However, for other categories of project you should prepare class
diagrams, behaviour model and/or state transition diagram and details of various data
structures used.
The Entity Relationship diagram (ER Diagram) should have:
o Proper symbol of attributes, entities, relationships, cardinality mentioned, and
o Relationship of ER diagram to SRS with strong association
Data Flow Diagram (DFD) should have:
o All Data flow should be levelled and should have proper input and output.
o Relationship of data flow to data dictionary Context Diagram, Level 1 and Level 2.
Data Dictionary: It should explain each entity and relationship in ER diagram and data
flow in DFD.

Design
Project design should include the desired features and operations in detail, including
user interface design, program structure, schema design and normalised tables and
data integrity and constraints. You should include them with the requirements given
below:
Program Structure: It should have the proper modularisations of software and
specification of each module.
Schema Design and Normalised Tables: Normalise the table to minimum 3NF. If any
demand of Demoralisations clearly explain the reasons.
Data Integrity and Constraints: Explain the referential diagram. Define entity integrity,
which should include keys, alternate keys and other keys, value constraints and ranges.
Procedural Design: Explain using Flowchart / Pseudo code / PDL.
User Interface Design: Coherence with dataflow and processor; Consistency of
interface and naming convention. Validation checks should be kept wherever
necessary.
Architecture: Program architecture and explanation on suitability of data structure
used.

Coding
Coding phase of software development includes different activities like refining the
algorithms for individual components, transferring the algorithms into a programming
language (coding), translating the logical data model into a physical one and compiling
and checking the syntactical correctness of the algorithm with these activities. You
should include the comments and description in code, use the standardisation in
coding, use the methodology for error handling and security implementation. These
parameters ensure software quality and reliability. You should include them with the
requirements given below:
 Comments and Description: Should have comments with functional description
which include the input, output, total function calls to/from other functions,
 function parameters, description of main variables, Data type, logic description,
etc.
 Standardizations of Coding: Use of naming convention of variable and
functions, nested depth, naming constant, use of data structure and style.
 Error Handling: Explain exceptions handling and conditional checking.
 Parameter passing and calling: Check the technique used for this purpose, how
it optimizes the coding.

 Security Mechanisms: Maintain confidentiality, integrity and authorization

according to the requirement and needs of the system. Also maintain database
level security, use of Views, use of revoke and grant, user and access rights and
ensure steps taken against hacking of the system.
(a) Testing
Testing is a process of devising a set of inputs to a given piece of software that will
cause the software to exercise some portion of its code. The developer of the software
can then check if the results produced by the software are in accordance with his or
her expectations. It includes, number of activities such as correcting syntactically and
semantically erroneous system components, detecting as many errors as possible in
the software system, and assuring that the system implementation fulfils system
specification.
It ensures the quality, efficiency and reliability of the software, which is measured by
the testing methodology and techniques used for unit, integrated, system testing etc.
The testing should not be too generic containing only definitions. You should give all
the test case designs, reports and results of test cases for unit, integrated, system
testing etc. How debugged your code is and what actions you have taken too improve
the code, must, be explained. Good testing can be measured by criteria such as
correctness, reliability, user friendliness, maintainability, efficiency and portability of
software.

(b) System Security Measures

The student should clearly emphasize the various levels of security measures
implemented in the project.
(c) Report Generation
The project report should include the various sample reports for ready reference.
(d) Cost Estimation of the project
The student needs to incorporate the estimated cost of the project using the suitable
mechanism/model given in the Software Engineering.
(e) Screen Layouts/Screen Shots/Screen dumps
Screen dumps for various screens/user interfaces should also be placed in a proper
order in the project report for ready reference.
(f) Organisation of the Project Report
Report organisation improves the professional attitude of writing reports. You should
emphasise on the proper binding of the project report, the cover page, page
numbering, organisation of content, and proper printout of text and images.
(g) Viva Voce
Other than the questions related to the project related areas and the courses
concerned, student may be requested to show the demo of the project. Also, you may
be told to write the portions of the code for a problem to demonstrate her/his coding
capabilities.
While appearing for the viva-voce, along with the project report the student should
needs to carry the identical copy of the CD of the executable file(s) which s/he
submitted at the time of project report.
(h) Project Evaluation
The Project Report is evaluated for 100 marks and the viva-voce is for 50 marks. Viva-
voce is compulsory and forms part of evaluation. A student in order to be declared
successful in the project must secure 40% marks in each component (i) Project
Evaluation and (ii) Viva voce. Pass in both the components is compulsory.
Report & Documentation 40
Viva voice (External) 40
Viva voice (Internal) 20
---------------------------------------------------------------------------------
Total Marks 100
IX SOFTWARE AND BROAD AREAS OF APPLICATION
Visual Basic, Power Builder, X-Windows (X/lib, X/motif,
FRONT END / GUI Tools
X/Intrinsic), Oracle Developer 2000,VC++, Jbuilder , NetBeans
Oracle, Ingres, Sybase, Progress, SQL Plus, Versant, MY SQL, SQL
RDBMS/BACK END
Server, DB2, Point base
LANGUAGES C, C++, Java, VC++, C#, eclipse
SCRIPTING LANGUAGES PERL, SHELL Scripts (Unix), TcL/TK
Oracle, Ingres, Sybase, Progress, SQL Plus, Versant, MY SQL, SQL
RDBMS/BACK END
Server, DB2
Web Platform and
PHP , JQuery , Bootstrap
framework
.NET Platform VB.Net, C#. Net, Visual C#. Net, ASP.Net
MIDDLE WARE
COM/DCOM, Active-X, EJB, WINCE, MSMQ, BEA, MessageQ,
(COMPONENT)
MTS, CICS
TECHNOLOGIES
OS INTERNALS Device Drivers, RPC, Threads, Socket programming
ARCHITECTURAL CONCEPTS CORBA, TUXEDO, MQ SERIES
DHTML, Java script, VB Script, Perl & CGI script, Java, Active X,
RMI, CORBA, SWING, JSP, ASP, XML, EJB, Java Beans, Servlets,
INTERNET TECHNOLOGIES Visual Age for JAVA, UML, VRML, WML, Vignette, EDA,
Broadvision, Ariba, iPlanet, ATG, BigTalk, CSS, XSL, Oracle ASP
server, AWT, J2EE, LDAP, ColdFusion, Haskell 98, PHP,NetBeans
NETWORK/WIRELESS
Blue Tooth, 3G, ISDN, EDGE
TECHNOLOGIES
OPERATING SYSTEMS WINDOWS 7,8 and 10
Financial / Insurance / Manufacturing / Multimedia / Computer
Graphics / Instructional Design/ Database Management
APPLICATION AREAS System/ Internet / Intranet / Computer Networking-
Communication Software development/ ECommerce/ ERP/
MRP/ TCP-IP programming / Routing protocols programming/
 Socket programming.

NOTE:

(i) Projects should not be developed using the old packages like Dbase III plus, Foxpro, Visual Foxpro and
MSAccess. Also, projects should not be developed using the combination of Visual Basic as the front end
and MS-Access as the back end. The project work should compulsorily include the software development.
Latest versions of the software are to be used. The project work should compulsorily include the software
development. Physical installations or configuring the LAN/WAN or theoretical projects or study of the
systems, which doesn’t involve s/w development, are strictly not allowed.

(ii) C/C++ languages should not be used for any Information Management System Project for example
Hospital/Reservation/Library/School/College Management System etc.

(iii) Students can also develop applications using tools/languages/software not listed above, if they are
part of latest technologies. Use the latest versions of the software packages for the project development.
X – Sample Cover Page
Sr. No. Pages Page No.
1 Synopsis front page 20
2 Project report cover page / front page 21
3 College certificate page 22
4 Declaration page 23
5 Acknowledgement page 24