Bachelor of Computer Applications

BCA-2651
Project Guidelines

Babu Banarasi Das University

Lucknow

Academic Session 2020-21

School of Computer Applications

I Floor, H-Block, BBDU, BBD City, Faizabad Road, Lucknow (U. P.) INDIA 226028
PHONE: HEAD: 0522-3911127, 3911321 Dept. Adm. & Exam Cell: 0522-3911326 Dept. T&P Cell: 0522-3911128; E-Mail: [email protected]

w w w . b b d u . a c . i n
 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 fulfillment of the BCA requirements, but also provide a mechanism to demonstrate
your skills, abilities and specialization. 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.

Students are required to submit the project proposals after entering into the 6th semester of MCA, as
per the calendar of the project.

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 research
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 GANTT and PERT 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.
 POINTS TO REMEMBER WHILE PREPARING THE PROJECT REPORT

1. Project Report Formulation:

The project report should contain the following:
 Certificate of Originality.
 Project documentation.
 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 60 to 80 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. 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.
 Table of Contents/Index with page numbering
 Introduction/Objectives
 System Analysis:
 Identification of Need
 Preliminary Investigation
 Feasibility Study
 Project Planning
 Project Scheduling (PERT Chart and Gantt Chart both)
 Software requirement specifications (SRS)
 Software Engineering Paradigm applied
 Data models (like DFD), Control Flow diagrams, State Diagrams/Sequence
diagrams, Entity Relationship Model, Class Diagrams/CRC Models/Collaboration
Diagrams/Use-case Diagrams/Activity Diagrams depending upon your project
requirements
 System Design:
 Modularization details
 Data integrity and constraints
 Database design, Procedural Design/Object Oriented Design
 User Interface Design
 Test Cases (Unit Test Cases and System Test Cases)
 Testing :
 Testing techniques and Testing strategies used
 Testing Plan used
 Test reports for Unit Test Cases and System Test Cases
 Debugging and Code improvement
  System Security measures (Implementation of security for the project developed):
 Database/data security
 Creation of User profiles and access rights
 Cost Estimation of the Project along with Cost Estimation Model
 Reports (sample layouts should be placed)
 Future scope and further enhancement of the Project
 Bibliography
 Appendices (if any)
 Glossary.
 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 1.5 line spacing on A4 paper (one side only). All
the pages, tables and figures must be numbered. Tables and figures should contain titles.

4. Throughout the project report, the title of the project should be the same as per the approved
synopsis.

5. Two copies 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 .

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

7. If two or more students have been allowed to work on a project, the project synopsis and project
reports by them must include only different modules undertaken/worked upon individually. Each
student must submit a separate project reports related to her/his modules. Completely identical
project synopsis and/or project reports are not allowed. Only introductory and possibly concluding
remarks may be similar or common. Each student has to undergo all the phases/stages of the
software project development life cycle.

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 or
disqualifying of the project at any stage.

9. Title of the project should be kept the same throughout the project.
Babu Banarasi Das University, Lucknow (Guidelines for Project Report submission)

 Two copies of the Project Report (Hard bound) should be submitted for Project Evaluation.
 The Project Report should be in the specified format as given below:
 The back and front cover of the Project Report copy should be in Maroon Color with
Golden Font Color.
 The Project Report should be typed in 1.5 spacing using Garamond font with 12 font
size.
 Main Heading (Section) : 14 font Bold
 Subsection Heading 12 font, bold, italic
 Project Report should be printed single side but main heading should start from a new
page.
 Sequencing of the Topics to included in Project Documentation
 Cover Page
 Certificates:
1. School of Computer Applications
2. Company
 Acknowledgement
 Table of Contents
 Introduction of the Project
 Need of Identification
 Problem Statement
 Analysis
 SRS
 High Level Design
1. DFD
2. ERD
 Low Level Design
1. Data Dictionary
 Screen Shots
 Conclusion
 Future Scope
 Bibliography
 Two requisite number of hard bound copies [1. Central Library Copy, 2. Students Copy]
incorporating all the corrections suggested by the Project Coordinators is to be deposited in
the department.
 CD: containing the Executable file of related software.