Project Report

Aryabhatta International College of Technical
Education
Ajmer, Rajasthan
A
PROJECT REPORT
ON
Student Faculty Document Sharing Application
Submitted in partial fulfilment for the
Award of the Degree of
BACHELOR OF COMPUTER APPLICATION
2018 – 2019
Submitted to:
Guide
Asst. Prof. Varun Ambrose Thomas
Submitted by: Krishan Kant Gupta

CERTIFICATE
This is to certify that Krishan Kant Gupta of Aryabhatta International
College of Technical Education, Ajmer, has successfully completed the
project work titled Student Faculty Document Sharing Application in partial
fulfilment of requirement for the completion of Under Graduate course as
prescribed by the Maharshi Dayanand Saraswati University, Ajmer.
This project report is the record of authentic work carried out by them during
the period from June, 2018 to February, 2019.
Head of Department
(Asst. Prof. Kriti Sankhla)
Date:
Guide
(Asst. Prof. Varun Ambrose Thomas)
2

ABSTRACT
This project is a portal between students and faculty. This innovative
system allows college faculty to share important data with student. It
consists of a faculty login along with student login. The faculty login is to
be performed through a Mobile. Faculty may upload documents of subject
syllabus, time table, document, e-notes etc. through their provided login.
The documents are uploaded by faculties of college.
We propose to build this system that allows faculty to upload data and
students may view and download required documents through their android
device. Here, students only see and download data. Faculty may access and
upload documents to any semester or add any notice as desired.

ACKNOWLEDGEMENT
I am thankful to Our Faculty Members for their valuable time they have
devoted to us and given us a lot of knowledge and help for the project. We
are also thankful to our Principal and Head of Department for their expert
guidance. It is a great experience for us.
Words defeat us in expressing our deep sense of gratitude for our friends,
whose continued resourceful support and guidance enabled us to overcome
all the challenges we faced whilst developing the project.
Krishan Kant Gupta

Table of Contents
CERTIFICATE................................................................................................2
ABSTRACT.....................................................................................................i
ACKNOWLEDGEMENT...............................................................................ii
Table of Contents...........................................................................................iii
List of Figures..................................................................................................v
List of Tables..................................................................................................vi
Chapter 1: Introduction............................................................................1
1.1 Introduction............................................................................................1
1.2 Purpose..................................................................................................1
Chapter 2: Development Tools........................................................................2
2.1Hardware and Software used for Development..................................2
2.2 Software used for using the Project...................................................2
2.3Feasibility Analysis............................................................................2
2.3.1Technical Feasibility........................................................................3
Technical feasibility determines whether the technology needed for
proposed ` system is available and now how it can be integrated. The
technical feasibility in the proposed system is deals with the technology
used in system. It deals with the hardware and software used in system.
It deals with the hardware and software used in the system whether they
are of latest technology. In this Android Studio needs 8GB minimum
ram to work but we have managed to do that in 4GB ram......................3
2.3.2Operational Feasibility.....................................................................3
Chapter 3: Techniques and Technologies........................................................4
3.1Android...............................................................................................4
Other Android Studio views....................................................................5
3.2SqLite..................................................................................................6
SQLite A Brief History...............................................................................6
3.3Development Strategy........................................................................6

3.3.1 Data Flow Diagram.......................................................................7
Chapter 4: Implementation............................................................................10
4.1Functional Requirements..................................................................10
4.2Design – Database ...........................................................................28
Chapter 5: Limitation and Future Enhancements..........................................30
5.1Limitations........................................................................................30
5.2Future Aspects / Enhancements........................................................30
We can use this app as worldwide for sharing data.......................................30
We will add password reset option in Future................................................30
We will add server or downloading data with internet connectivity.............30
We will add search option in student panel...................................................30
Conclusion.....................................................................................................31
References......................................................................................................32

List of Figures
Figure 1: Faculty DFD
Figure 2: Student DFD

List of Tables
Table 1: Faculty Member Table
Table 2: Student Table
Table 3: Add File Table
Table 4: Student Login

Chapter 1: Introduction
1.1 Introduction
The project is a portal between student and faculty. This innovative system allows college
faculty to share important data with students. It consist of a faculty login along with
student login since college faculty operates through Mobile and document uploading
simpler through Mobile, the faculty login is to be performed through Mobile. Faculty may
upload documents of subject syllabus, time table, document, e-notes etc. through their
provided login. The documents are uploaded by faculty.
1.2 Purpose
The purpose to build this system that allows faculty to upload data and students may view
and download required documents through their android device here students only see
and download data. Faculty may access and upload documents to any semester. File
sharing apps and services help users to share and receive multiple files from other devices
via Internet. These solutions can be used to share various kinds of files, such as
documents and images. They are mostly used to download media files from the internet.
This system is one of the best file sharing services and the frontrunner in all aspects of
file sharing, emphasizing in particular its capacity to satisfy individual and professional
needs with the same flexibility. DocShare was designed to satisfy everyone, which can
also be concluded by its intuitive interface, mobile optimization.
1

Chapter 2: Development Tools
2.1 Hardware and Software used for Development
Hardware used for developing application is Laptop. Software used for developing
application is Android Studio. Operating System used is Windows 10.
Front end tool
• Android SDK
Back end tool
• Sqlite
Software Requirement
• Windows 10
• Android studio
Hardware Requirement
• Processor - i3
• HDR : 4GB
2.2 Software used for using the Project
Hardware used for running application is Mobile. Software used for running application
is DocShare. Operating System used is Android.
Software Requirement
• Android >5.0
• DocShare
Hardware Requirement
• Internal Storage : 8GB
• HBR : 2GB
2.3 Feasibility Analysis
An analysis and evaluation of a proposed project to determine if it (1) is technically
feasible, (2) is feasible within the estimated cost, and (3) will be profitable. Feasibility
studies are almost always conducted where large sums are at stake also called as
feasibility analysis.
2

2.3.1Technical Feasibility
Technical feasibility determines whether the technology needed for proposed `
system is available and now how it can be integrated. The technical feasibility in
the proposed system is deals with the technology used in system. It deals with the
hardware and software used in system. It deals with the hardware and software
used in the system whether they are of latest technology. In this Android Studio
needs 8GB minimum ram to work but we have managed to do that in 4GB ram.
2.3.2Operational Feasibility
Operational feasibility is the measure of how well a proposed system solves the
problems, and takes advantage of the opportunities identified during scope
definition and how it satisfies the requirements identified in the requirements
analysis phase of system development. In this we don’t have android emulator so
we have used USB debugging option and with the help of that we have tested our
application on our personal mobile
3

Chapter 3: Techniques and Technologies
3.1 Android
Android is a mobile operating system developed by Google. It is used by several
Smartphone and tablets. Examples include the Sony Xperia, the Samsung Galaxy, and the
Google Nexus One.
The Android operating system (OS) is based on the Linux kernel. Unlike Apple's iOS,
Android is open source, meaning developers can modify and customize the OS for each
phone. Therefore, different Android-based phones often have different graphical user
interfaces GUIs even though they use the same OS.
Android Studio is the official IDE for Android application development, based on IntelliJ
IDEA. On top of the capabilities you expect from IntelliJ, Android Studio offers:
• Flexible Gradle-based build system
• Build variants and multiple apk file generation
• Code templates to help you build common app features
• Rich layout editor with support for drag and drop theme editing
• lint tools to catch performance, usability, version compatibility, and other
problems
• Built-in support for Google Cloud Platform, making it easy to integrate Google
Cloud Messaging and App Engine
• And much more
If you're new to Android Studio or the IntelliJ IDEA interface, this page provides an
introduction to some key Android Studio features.
Android project view
By default, Android Studio displays your project files in the Android project view. This
view shows a flattened version of your project's structure that provides quick access to the
key source files of Android projects and helps you work with the Gradle-based build
system. The Android project view:
• Shows the most important source directories at the top level of the module
hierarchy.
• Groups the build files for all modules in a common folder.
• Groups all the manifest files for each module in a common folder.
4

• Shows resource files from all Gradle source sets.
• Group resource files for different locales, orientations, and screen types in a single
group per resource type.
The Android project view shows all the build files at the top level of the project hierarchy
under Gradle Scripts. Each project module appears as a folder at the top level of the
project hierarchy and contains these four elements at the top level:
• Java/ - Source files for the module.
• Manifests/ - Manifest files for the module.
• Res/ - Resource files for the module.
• Gradle Scripts/ - Gradle build and property files.
For example, Android project view groups all the instances of the ic_launcher.png
resource for different screen densities under the same element.
Other Android Studio views
When you use the Project view in Android Studio, you should notice that the project
structure appears different than you may be used to in Eclipse. Each instance of Android
Studio contains a project with one or more application modules. Each application module
folder contains the complete source sets for that module, including src/main/ and
src/androidTest/ directories, resources, build file and the Android manifest. For the most
part, you will need to modify the files under each module's src/main/ directory for source
code updates, the gradle.build file for build specification and the files under
src/androidTest/ directory for test case creation
You can also customize the view of the project files to focus on specific aspects of your
app development:
• Packages
• Project Files
• Scratches
• Problems
• Production
• Tests
For example, selecting the Problems view of your project displays links to the source files
containing any recognized coding and syntax errors, such as missing an XML element
closing tag in a layout file.
5

3.2 SqLite
SQLite is an in-process library that implements a self-contained, serverless, zero-
configuration, transactional SQL database engine. The code for SQLite is in the public
domain and is thus free for use for any purpose, commercial or private. SQLite is the
most widely deployed database in the world with more applications than we can count,
including several high-profile projects.
Why SQLite?
SQLite does not require a separate server process or system to operate (serverless).
• SQLite comes with zero-configuration, which means no setup or administration
needed.
• A complete SQLite database is stored in a single cross-platform disk file.
• SQLite is very small and light weight, less than 400KiB fully configured or less
than 250KiB with optional features omitted.
• SQLite is self-contained, which means no external dependencies.
• SQLite transactions are fully ACID-compliant, allowing safe access from multiple
processes or threads.
• SQLite supports most of the query language features found in SQL92 (SQL2)
standard.
• SQLite is written in ANSI-C and provides simple and easy-to-use API.
• SQLite is available on UNIX (Linux, Mac OS-X, Android, iOS) and Windows
(Win32, WinCE, WinRT).
SQLite A Brief History
• 2000 - D. Richard Hipp designed SQLite for the purpose of no administration
required for operating a program.
• 2000 - In August, SQLite 1.0 released with GNU Database Manager.
• 2011 - Hipp announced to add UNQl interface to SQLite DB and to develop
UNQLite (Document oriented database).
3.3 Development Strategy
Here you explain the model by which you proceeded with the project. Here you mention
the SDLC model that you followed for developing the project.
6

3.3.1 Data Flow Diagram
This is the context level D.F.D. of the proposed system the whole system has been
depicted in a single bubble, primary input and output has been carefully noted and
depicted in the way so that information flow continuity should not be lost in the
next level. The purposed system is shown as a whole process and the inputs and
outputs are shown with incoming and outgoing arrow from the system.
A DFD provides no information about the timing of processes, or about whether
processes will operate in sequence or in parallel. It is therefore quite different
from a flowchart which shows the flow of control through an algorithm, allowing
a reader to determine what operations will be performed, in what order, and under
what circumstances, but not what kinds of data will be input to and output from
the system, nor where the data will come from and go to, nor where the data will
be stored (all of which are shown on a DFD).
There are several notations for displaying data flow diagrams. The notation
presented above was described in 1979 by Tom DeMarco as part of Structured
Analysis.
For each data flow, at least one of the endpoints (source and / or destination) must
exist in a process. The refined representation of a process can be done in another
data flow diagram, which subdivides this process into sub-processes.
The data flow diagram is part of the structured analysis modelling tools. When
using UML, the activity diagram typically takes over the role of the data flow
diagram. A special form of data flow plan is a site-oriented data flow plan.
Data flow diagrams can be regarded as inverted Petri nets, because places in such
networks correspond to the semantics of data memories. Analogously, the
semantics of transitions from Petri nets and data flows and functions from data
flow diagrams should be considered equivalent.
7

Figure 1: Faculty DFD
8
ADD_S
TU
ADD NOTICE
SUB_NAME,
TOP_NAME,
YEAR
ADD STUDENT
DOCUMENT
UPLOAD
NOTICE UPLOAD
UPLOAD
DOCUME
NT
UPLOA
D
NOTIC
E
ADD
STU_ID
ADD FILE
SUB_NAME,
TOP_NAME,
YEAR
FATUCLTY LOGIN
FACULTY
LOG
IN
RESPONS
E
STU_ID

Figure 2: Student DFD
9
STUDENT
REPONSE
DOUMENT
REPONSE
DOUMENT
REQUEST DOCUMENT
REQUEST DOCUMENT
USER_ID &
PASSWORD
RESPONSE
STUDENT LOGIN
VIEW
DOCUMENT
DOWNLOAD
DOCUMENT
LOG
IN
VIEW
DOWNLOA
D

Chapter 4: Implementation
In this chapter you mention all the details you specified in SRS about the functional
requirements.
4.1 Functional Requirements
In software engineering and systems engineering, a functional requirement defines a
function of a system or its component, where a function is described as a specification of
behaviour between outputs and inputs.
Functional requirements may involve calculations, technical details, data manipulation
and processing, and other specific functionality that define what a system is supposed to
accomplish. Behavioural requirements describing all the cases where the system uses the
functional requirements are captured in use cases. Functional requirements are supported
by non-functional requirements (also known as "quality requirements"), which impose
constraints on the design or implementation (such as performance requirements, security,
or reliability). Generally, functional requirements are expressed in the form "system must
do <requirement>," while non-functional requirements take the form "system shall be
<requirement>." The plan for implementing functional requirements is detailed in the
system design, whereas non-functional requirements are detailed in the system
architecture.
• A Profile’s Module contents should be:
o Entries should be made user-friendly
o zIt should contain a unique user name in order to provide security.
o All the necessary requirements should be filled
o Can purchase anything only by registering themselves.
o If the user is not registered, then he can only visit the site.
• Faculty Member
o Login: Admin can Login in our Application.
o Manages all types of Processes like Add Student, Update Student, Upload
notes, Upload Timetable and Upload Book.
• Student
o Login: Student can Login in Application by giving valid id and password.
o Manages to download or view Timetable, Books, Notes
10

4.2 Design – Interface (User Manual)
Here you give all the screenshots of the project’s pages/activities that you’ve created and
a brief explanation of each.
• Home
This is the home screen which consists of Faculty Login and Student Login. When
you click on Faculty login the faculty will enter into Faculty Login page and when
you click on Student Login the student will enters into Student Login page
11

By clicking on Faculty login you will be redirected to Faculty login . Now it will
ask to enter userid and password for successful login. If faculty member gives right
information then it will redirected to Faculty menu otherwise gives error.
• Faculty Menu
After successful Login multiple option will appear which consists of Add Student,
Upload Books, Upload Timetable, Update Student, Upload Notes and Logout
button.
When Faculty member clicks on any button they would be redirected to following
option
13

• Add Student
After clicking on Add Student Button it will redirect to Add Student panel where
you have to insert student id, student name, student phone no., student course and if
14

the inserted data is correct then it will insert data in database and if not correct then
it will show error of wrong input. And with the help of logout button you will
redirected to faculty menu.
• Upload Book
15

After clicking on Upload Book Button it will redirect to Upload Book panel where
you have to insert book name, book type, course and then click on browse button to
insert file and then click on upload button and if the inserted data is correct then it
will insert data in database and if not correct then it will show error of wrong input.
And with the help of logout button you will redirected to faculty menu.
• Update student
16

After clicking on Update Student Button it will redirect to Update Student panel
where you have to insert student id, student name, student phone no., student course
and if the inserted data is correct then it will insert data in database and if not
correct then it will show error of wrong input. And with the help of logout button
you will redirected to faculty menu.
17

After clicking on Upload Timetable Button it will redirect to Upload Timetable
panel where you have to insert timetable name, course, type .and by clicking on
browse button select timetable and upload it by clicking on upload button if the
inserted data is correct then it will insert data in database and if not correct then it
will show error of wrong input. And with the help of logout button you will
redirected to faculty menu.
20

After clicking on Upload Notes Button it will redirect to Upload Notes panel where
you have to insert note name, course, type .and by clicking on browse button select
notes and upload it by clicking on upload button if the inserted data is correct then it
will insert data in database and if not correct then it will show error of wrong input.
And with the help of logout button you will redirected to faculty menu.
• Student Login
22

By clicking on Student Login you will be redirected to Student Login. Now it will
ask to enter user_id and password for successful login. If students gives right
information then it will redirected to Student menu otherwise gives error.
• Student Menu
After successful Login multiple option will appear which consists of Time-Table,
Books, Notes, Logout button. When Student clicks on any button they would be
redirected to following option.
24

• Time Table
In this panel student can only view the time table of his course only he cannot
downlode or share time table to any one.
• Books
25

In book panel studen can view and download the book to his device by clicking on
image he will able to open the book.
• Notes
27

In notes panel studen can view the notes in device by clicking on image he will able
to open the notes.
4.2 Design – Database
Here you give all the screenshots of the project’s database design where you’ve used
to store the data to be used in the project along with their data types, ranges, default
values, keys, etc.
Table1: Faculty Member Table
Name Type Description
Id int, auto increment Unique no assign to each record
user_id varchar(15) Store the user id of admin
user_pass varchar(10) Store the password of admin
Table 2: Student Table
28

id int, Auto increment Unique no assign to each record
s_id varchar(50 Use to store student id
name varchar(50) Use to store name
mob_no int(10) Use to store mobile no
Course varchar(25) Use to store course
Table3: Add File Table
Id int, Auto increment Unique no assign to each record
Semester int(1) Use to store semester
Name varchar(50) Use to store name
Type enum (book,assignment,extra) Use to store type of notice
Table 4: Student Login
Name Type
id int, auto increment
stu_id varchar(15)
stu_pass varchar(10)
29

Chapter 5: Limitation and Future Enhancements
5.1 Limitations
Each and every thing in this world have some limitations. Nothing is there in this world,
which do not have any limitations. And it is also the case with Student Faculty Document
Sharing Application. Let’s discuss some of the limitations of Student Faculty Document
Sharing Application. In our Application we have not provided the functionality of Student
Signup by itself. Student cannot update his details
• Student cannot sign up by itself.
• Student has no rights to see other Profile.
• Student cannot share documents.
• Faculty members cannot able to upload video lectures.
• It is only for Student and Faculty.
5.2 Future Aspects / Enhancements
Our application can be enhanced in the future to give much functionality, which we have
not yet included. As you all know the E-Siksha is so wide an area there are so many
things, which can come under it. It is not possible to provide all the functionality as per
budget and limitations of resources. So here we will discuss some of the enhancements,
which can be made to our application. A password reset feature is added. Auto course
updating is added.GUI improved in near future. Search option is added.
We can enhance our application to manage the Data to be displayed on the pages of our
application.
• We can use this app as worldwide for sharing data.
• We will add password reset option in Future.
• We will add server or downloading data with internet connectivity.
• We will add search option in student panel.
• We will improve GUI in near future.
30

Conclusion
We have developed a new approach to sharing information between students and
lecturers in order to enhance quality of information in campus environment.
We describe networks for distributing campus information among students and lecture.
The concept of developing this system is to ensure that student can access information at
any time, at any locations.
The project is a portal between student and faculty. This innovative system allows college
faculty to share important data with students. It consist of a faculty login along with
student login since college faculty members operates through Mobile and document
uploading simpler through Mobile, the faculty login is to be performed through Mobile.
Faculty may upload documents of subject syllabus, time table, document, e-notes etc.
through their provided login. The documents are uploaded by faculty.
Student can view or download Time-Table, Notes and Books and can share it with other
if he downloads it in his portable device. But before performing all this task he would
have to login to student panel by giving userid and password if the userid and password is
correct then only he can login otherwise error message is shown and if a user exceeded
the wrong enter limit he would not abe to login at that instance.
This is my first attempt in developing a mobile application which gives us a basic
understanding of development and challenges of mobile application development. The
application has been implemented and tested on real device.
31

References
Books
1. Android Programming for beginners
Author: John Horton
Edition: 2017 Edition
2. Android Programming
Author: Willy
Edition: 2018 Edition
3. Java: A beginners Guide
Author: Herbert Schildt
Edition: 6th Edition
Websites
 Android Studio
o https://developer.android.com/studio/
 SqLite
o https://www.sqlite.org/index.html
 Tutorial of connectivity android with Sqlite
o https://www.youtube.com/watch?
v=T0ClYrJukPA&list=PLS1QulWo1RIaRdy16cOzBO5Jr6kEagA0
7&index=3
 Java
o https://www.tutorialspoint.com/java/
32

Project Report

More Related Content

Similar to Project Report

Recently uploaded

Project Report