Report Note Sharing

TRIBHUVAN UNIVERSITY INSTITUTE OF ENGINEERING HIMALAYA COLLEGE OF ENGINEERING

A MINOR PROJECT REPORT ON “NOTE CIRCULATION SYSTEM ” [CT 654].

SUBMITTED BY: ARBIN POKHAREL (32654) KHETULAL KC (32669) PRASHANT BHATTA (32679)

A PROJECT REPORT SUBMITTED TO THE DEPARTMENT OF ELECTRONICS AND COMPUTER ENGINEERING FOR THE PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF BACHELOR'S IN COMPUTER ENGINEERING

DEPARTMENT OF COMPUTER AND ELECTRONICS ENGINEERING CHYASAL, LALITPUR

AUGUST, 2018

TRIBHUVAN UNIVERSITY INSTITUTE OF ENGINEERING HIMALAYA COLLEGE OF ENGINEERING

A MINOR PROJECT REPORT ON “NOTE CIRCULATION SYSTEM ” [CT 654]

SUBMITTED BY: ARBIN POKHAREL (32654) KHETULAL KC (32669) PRASHANT BHATTA (32679)

SUPERVISOR: NHURENDRA SHAKYA

A PROJECT REPORT SUBMITTED TO THE DEPARTMENT OF ELECTRONICS AND COMPUTER ENGINEERING FOR THE PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF BACHELOR'S IN COMPUTER ENGINEERING

DEPARTMENT OF ELECTRONICS AND COMPUTER ENGINEEING LALITPUR, NEPAL

AUGUST, 2018

ii

ACKNOWLEDGMENT We extend our sincere gratitude to Er. Nhurendra Shakya for providing the necessary guidelines and support for understating the feasibility fe asibility and technical aspects for the project. Our special thanks go to Er. Suman Pokharel of Dry Ice Pvt. Ltd. for guiding us through the project and helping us understand its complexity. We would also like to thank HCOE and Department of Electronics and Computer Engineering for  providing us the opportunity to build up the project. Last but not the least; we would like to thank our friends and seniors for helping us in the project. Thanks for making the difference.

iii

ABSTRACT  Note Circulation System deals with borrowing and transferring the notes from senior student to junior student. It is a WEB-based system especially designed for students of particular college. This system is being produced for students interested in borrowing and giving their own notes for the free of cost. It will allow the student to create an a/c and joins the forum. The system automatically generates the coins as per system rules while creating an account and donating and borrowing of notes are done through coins. This Project aims for providing the digital platform for the user where they can request notes as per required and another user of this same platform can supply that notes to the requesting user. To ensure that all the user be benefitted of acquiring the required notes, the rule is created in the system where requester will lose the certain coins and donor will acquire the same number of coins. The user without coin cannot request until the user donates his notes and acquire the coins.

 Keywords: coins, donate, borrow, delivery approval

iv

Table of Contents ACKNOWLEDGMENT........................................................................................ iii ABSTRACT............................................................................................................iv LIST OF FIGURES ............................................................................................... vii LIST OF SYMBOLS AND ABBREVIATION .................................................. viii INTRODUCTION ................................................................................................... 1 1.1 BACKGROUND ........................................................................................... 1 1.2 OBJECTIVES ................................................................................................ 1 1.3 SCOPE AND APPLICATIONS ....................................................................1 2. LITERATURE REVIEW ....................................................................................2 3. IMPLEMENTATION TECHNOLOGIES .......................................................... 3 3.1 PROGRAMMING LANGUAGE .................................................................. 3 3.2 DEVELOPING ENVIRONMENT ................................................................ 3 3.3. OTHE TECHNOLOGIES/APIs ................................................................... 3 3.4 DEVELOPMENT MODEL ...........................................................................4 4. PROJECT DESIGN ............................................................................................. 5 4.1 SYSTEM ALGORITHM ............................................................................... 5 4.2 DATA INSERTION ......................................................................................6 4.2.1 Database Tables ......................................................................................6 4.2.2 Admin Section ........................................................................................ 7 4.3 WORKING METHODOLOGY ....................................................................8 4.4 PAGE BLOCK............................................................................................... 9 4.4.1 Login page .............................................................................................. 9 4.4.2 Admin Page ............................................................................................. 9 4.4.3 Student details Page ................................................................................ 9

v

4.4.4 Faculty Name Page ............................................................................... 10 4.4.5 Semester Page ....................................................................................... 10 4.4.6 Subject Page .......................................................................................... 10 4.4.7 User Page .............................................................................................. 10 4.4.8 Borrow Note Page ................................................................................. 10 4.4.9 Donate Note Page ................................................................................. 10 4.5 PROCESS MODEL .....................................................................................11 4.5.1 System Block Diagram ......................................................................... 11 4.5.2 ER Diagram .......................................................................................... 13 4.5.3 DFD Diagram........................................................................................ 14 4.5.4 CLASS DIAGRAM .............................................................................. 15 5. CHALLENGES ................................................................................................. 16 6. CONCLUSION..................................................................................................17 7. FUTURE DEVELOPMENTS ...........................................................................18 8.REFERENCE...................................................................................................... 19 9. APPENDICE...................................................................................................... 20

vi

LIST OF FIGURES Figure 3.1 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8 9.9 9.10 9.11

Contents

Page no

MVC model

3

Page block diagram

8

System Block Diagram

11

System Flow diagram

12

Use Case Diagram of the System

12

ER Diagram

13

Context Flow Diagram

14

Level-1 DFD

14

Class Diagram

15

Login Area

20

Admin Home Page

20

Student List

21

User Registration

21

List of Faculty

22

Inserting new Faculty

22

Inserting Semester

22

Inserting Subject

23

Borrow Notes

23

Donation and Borrow approval view

24

User Logout

24

vii

LIST OF SYMBOLS AND ABBREVIATION API

Application Programming Interface

AJAX

Asynchronous JavaScript and XML

ASP

Active Server Page

C#

C Sharp

CSS

Cascading Style Sheet

HTML

Hyper Text Markup Language

IDE

Integrated Development Environment

JSON

JavaScript Object Notion

MS-SQL

Microsoft Structured Query Language

MVC

Model View Controller

viii

INTRODUCTION 1.1 BACKGROUND It has always been the tedious process to borrow the notes from the senior. It is very hard to find the right person who can employ with their notes they have passed.  Note circulation system is eradication of this problem. It gives the platform where the person is recommended to the user as per their notes requirement. To ensure the note is circulated from student to student the coins will automatically generated after creating an account. The user can borrow the notes from these coins and to ensure the user continuous to get borrow from the seniors the user must donate his  previous notes which increase the coin.

1.2 OBJECTIVES The general objective of this application is to provide the platform where students can contact the owner of notes efficientl y. The specific objectives of this web application are: -

To provide the platform for the user to connect for the borrowing and donating the notes

-

To ensure that the note circulation is occurred wit hin the user

1.3 SCOPE AND APPLICATIONS Most of the student wants to borrow the notes at free of cost from the seniors. But they could not approach them, if they there is no guarantee that he/she may be is from same faculty ant it is also not confirm that they possess the same notes that they want. This platform eradicates this problem. Thus, this has the huge aspect for the future. This system shows the recommendations list of students that possess the notes that user wants. As this system easily solves the problem of finding the right person for required notes, and also helps to connect them. Thus, this project goanna certainly  be helpful for future students.

1

2. LITERATURE REVIEW Today’s era thanks to science and technology the connectivity is in our daily life  process. Information Technology has revolutionized the life of the world and has made life easier through various kinds of applications. In the light of the rapid changes with the use of IT, there are many tools, technologies and systems that have  been produced and invented. We know the knowledge and information have always an increasing central role in every aspect of life. In the modern era of digital world every problem has its digital solution i.e. everything is within the approach of data [1]. Note circulation gives the platform to choose the right person as per user requirements. If user goes through required process, the user will be provided with contact information.  Note Circulation system is a means of providing information in such a way that it would be most useful to the persons for whom it is intended. In other words, this system is designed to organize or process data such that the res ultant processed data are most informative to it users. A Note Circulation system is an interacting component that operates within a boundary for some purpose. The aim of a system is to provide means for processing information to improve efficiency and effectiveness of the organization. Note Circulation system project indicate potential  benefits such as saving time, enabling more timely decisions, and prevention of unnecessary duplication of activities [2]. Important of aspect of digital platform is the eradication of problem in very effective and efficient manner [3]. There has also been development of different websites to sell and buy old books like friends of books, mad books etc. [5]. There is a feature to share a Notebook. Only the owner of a notebook can share it. A shar ed note that  belongs to an unshared whereas if the notebook is also shared, the shared note with  be presented in its original notebook. Just as for the notes, there are the 3 permission levels. The notes contained in a shared notebook are not automatically shared. However, there are shortcuts propagate the shar ing status of a notebook to its notes and for a note to inherit the sharing status from that of the notebook. [6] It is the system ensuring the old notes and books can be shared in such a way that every user can be fulfilled of their demands.

2

3. IMPLEMENTATION TECHNOLOGIES 3.1 PROGRAMMING LANGUAGE C#: The primary programming language used for the development of this project is C#. It is used in conjunction with ASP.Net for the creation of the website. JavaScript: For the client-side programming, we have used JavaScript. It is used  primarily in the events like mouse click, mouse hover etc.

3.2 DEVELOPING ENVIRONMENT ASP .Net: We have used ASP .Net MVC Framework 4.0 for the development of the project. MS-SQL Server: MS-SQL Server 2014 is used as the DBMS with MS-SQL as the query language. Microsoft Visual Studio: Microsoft Visual Studio 2015 is used as our primary IDE for programming in C#. Microsoft SQL Server Management Studio: Microsoft SQL Server Management Studio is used for efficient management of database. Microsoft Edge Developer Tool: They are used for debugging the JavaScript codes.

3.3. OTHE TECHNOLOGIES/APIs  jQuery: It is a JavaScript library which is used primarily in our project for sending and receiving AJAX requests. JSON: It stands for JavaScript Object Notation and is used as the data format for retrieving data from the server sent during AJAX request. AJAX: It is a technology used for communication of browser with the server. With AJAX the data obtained from the server can be displayed on the webpage without completely reloading it. Bootstrap: - Bootstrap is a smooth, powerful and popular HTML, CSS and JavaScript framework for front-end web development. This framework is compatible with most modern browsers and devices. The advantage of using Bootstrap framework is it provides ready to use style for most of your UI elements including Forms, Tables, Lists, etc. Any ASP.NET MVC application’s UI can be

3

made richer in no time using the Bootstrap framework. The ready UI classes for various controls makes the application more interactive to the end-user. CSS-. It is a highly effective HTML tool that provides easy control over layout and  presentation of website pages by separating content from design.

3.4 DEVELOPMENT MODEL This application was built in MVC pattern which is a software architectural  pattern for implementing user interfaces on computer. It divides a given application into three interconnected parts in order to separate internal representations of information from the ways that information is presented to and accepted from the user. The MVC design pattern decouples these major components allowing for efficient code reuse and parallel development.

Fig.3.1 MVC model

4

4. PROJECT DESIGN 4.1 SYSTEM ALGORITHM STEP 1:

if (admin login==True) Goto step 2 If (user login==True) Goto step 3 Else Error found

STEP 2:

Add, Update or Delete Record Goto step 4

STEP 3:

if (coins! = 0) Borrow or Donate Notes If (coins=0) Donate Notes Else You do not have enough coins Goto step 4

STEP 4:

Log Out

5

4.2 DATA INSERTION 4.2.1 Database Tables There are 9 tables in the database for handling of the data. They are named as StudentDetails,

Admin,

UserLogin,

UserRegistration,

facultyName,

facutySemSubject, Subject, Semester, BorrowNotes & DonateNotes. Following records are inserted into the table: StudentDetails:- This table is manipulated by the admin. Admin add the record of StudentFirstName, StudentMiddleName, StudentLastName, RollNo, MobileNo, Email, Year, Semester, Subject, TokenNo and Faculty. Admin: - The column of this table are Id, FirstName, LastName, UserName and Password. The UserName and Password used in this table are used for admin login. UserRegistration:-This table includes the records of UId, UserName,, MobileNo, Email, Password, Faculty, Years, Semester, RollNo and Coins. It is manipulated by admins. UserLogin: - It includes the record of Id, UserId, UserName and Password. It is navigated by Admin. FacultyName: - The column of this table includes Fid, FacultyName1 and IsActive. It is manipulated by Admin. FacultySemSubject: - The column of this table includes Mid, SID, Fid and SemID. Its navigation properties are table named FacultyName, Semester and Subject. Subject: - This table includes column named SID, SName and IsActive. It’s navigation properties are table named BorrowNotes and FacultySemSubject. Semester: - This table includes column named SID, SName, Year and IsActive. Its navigation properties are table named BorrowNotes and FacultySemSubject. BorrowNotes:- The column of this table includes BID, StudentID, SemID, SubjectID, IsActive, FID and BorrowDate. Its navigation are in the table Semester , table subject and table UserRegistration. DonateNotes:- The column of this table includes DID, SubID, SemID, Fid, DonatedBy, DonatedTo,DonatedDate and isActive.

6

4.2.2 Admin Section

The admin section of the project is designed for the admin of the s ystem to manage the entire system. Admin has access to modify the data used in the system. Admin section can be partitioned into different portions based on the activities performed  by the admin. The activities can be described as: Login: The admin needs to login to enter the admin section. The registration

information of the admin is saved in the database separate from the system database. Add record: Admin can add record in the existing database inside the add portion.

To add the data admin needs to go to the table where new data is to be added. The data is added through a form containing the fields that corresponds to the attributes of the table. The values added in the fields are bound in an object that is the instance of the class corresponding to the table. This object is passed to add corresponding values in the database. The addition made by admin are in the table StudentDetails, facultyName Subject and Semester. Edit and Delete record: Updating of record is very important to keep the record

up-to-date. It also helps in correcting the mistakes in the stored data. Admin has access to update the record stored in the existing database. The edit and delete can  be performed on a particular record obtained after searching or record initially displayed. Each record has its own unique representation to differ fr om another record. To edit the record, system first finds the unique identity of the record and the updated value is stored in the database for that record based on the identity. Admin should be careful not to update the unique identity and in most cases the identity is made not editable. The deletion of record can be performed similarly. The admin should be careful while deleting any record as it removes the record from the database also. The system removes the record along with its identity when the record is deleted.

7

4.3 WORKING METHODOLOGY A browser request from user gets mapped to a controller act ion through a feature of the ASP.NET framework called ASP.NET Routing. ASP.NET Routing is used by the ASP.NET MVC framework to route incoming requests to controller actions. A controller is responsible for controlling the way that a user interacts with an MVC application. A controller contains the flow control logic for an ASP.NET MVC application. A Note Supply controller determines what response to send back to a user when a user makes a browser request fetching the data from the model. The controller actions exposed by the Note Supply returns a view. A view contains the HTML markup and content that is sent to the browser. A view is the equivalent of a page when working with an ASP.NET MVC application. The model contains all application logic, validation logic and database access logic. Microsoft Entity Framework is used to access the database, which create Entity Framework classes (model1.edmx file) in the Models folder. The connection string is manually inserted for the MySQL database that is hosted. In MVC, data table is looped and convert the data to model or model list, then, send it to MVC views. JavaScript is used a client-side programming language whereas C#.Net is used as server-side  programming language. On client-side, the data to be shown to the client side are obtained from our own Database. Ajax is used for communication of browser with the server. With AJAX the data obtained from the server can be displayed on the webpage without completely reloading it.

8

4.4 PAGE BLOCK

Fig 4.1 Page block diagram

4.4.1 Login page This page is also known as login page. For login the user needs to enter the following information for validation. 

Username



Password

4.4.2 Admin Page This page includes student details, subject, faculty name and semester section. Entering into each section re-direct to respective pages.

4.4.3 Student details Page In this student’s detail page admin can view the li st of users. Administer can in this  page create new users. Admin register into the website through this page. For registration the admin needs to enter the following information; 

Unique User Name



Mobile No.



Email address



Faculty



Semester



Roll No



Coins

9

The coins inserted varies for the user of different year.

4.4.4 Faculty Name Page In this page admin can view the List of Faculty and can create new faculty. It can also view the faculty information, edit or delete the faculty information.

4.4.5 Semester Page In this page admin can view the list of semester information. Admin can insert, update or delete the semester’s information.

4.4.6 Subject Page In this page admin can view the faculty name, subject name and semester name. It can create new subject of different faculty and semester. It can also edit and delete subject.

4.4.7 User Page In this page the user can view the borrow and donate note sectio n. Entering in each section redirect to borrow note page and donate note page respectively.

4.4.8 Borrow Note Page In this Page user can view the coins he has reserved. In this page, user can select the subject the user wants to borrow selecting from the drop-down list of faculty and semester. After borrowing each page users coin is reduced by 50.

4.4.9 Donate Note Page In this Donate Note page, the above half section of web page user can view the list of different users wanting the notes of different subject of differ ent faculty, semester and year. If the user has any of the given notes user can click on the donate note section. In the below half section of web page, the user can view the delivery approval section. The user can view the user name and phone no of accepting user. The approve button is seen in this page. If user gets the note page from the accepting user the user clicks on the approve button. Then the pop-up button appears in the web page asking yes or no. The click on the yes button increases the accepting user coin by 50.

10

4.5 PROCESS MODEL 4.5.1 System Block Diagram

4.2 System Block Diagram

11

Fig 4.3 System Flow Diagram

Fig 4.4 Use Case Diagram

12

4.5.2 ER Diagram

Fig 4.5 ER Diagram

13

4.5.3 DFD Diagram

Fig 4.6 Context Flow Diagram

Fig 4.7 Level 1 Diagram

14

4.5.4 CLASS DIAGRAM

Fig 4.8 Class diagram

15

5. CHALLENGES The project was not as convenient as we expected it to be and we had to face quite a lot of challenges. Most of them were related to communication between database and webpage we needed for the project. The problems we encountered during our  project are listed below: 1. The database management was a tedious task. We had to run complex queries to manage and store the records. 2. Query processing took a lot of time so we had to perform query optimization. 3. It was very tedious to insert data into database from webpage. 4. Due to very limited knowledge in JavaScript, html, CSS & C# it was very difficult to create the webpage as per our planning.

16

6. CONCLUSION Despite the challenges and problems, we completed our project in specified duration. The program was first tested among the developers and was fin ally with end users. The project is finally obtained as a webpage.

17

7. FUTURE DEVELOPMENTS Despite the effort to make the best system there were still some limitations for the current system to which solutions can be provided as a future development. As for other future developments, the following can be done: 1.  Note Circulation System can be deployed on a web server so that everybody who is connected to the Internet. It can be f urthered enhanced in mobile apps in real time system. 2. This system can be made available to different universities and colleges. 3. It can be enhanced to create a platform to share soft copy notes.

18

8.REFERENCE [1] Gerald V. Post. Database Management Systems, Published 2002 by McGrawHill/Irwin (first published November 28th 1998) [2] P. Drucker, 1994, “The importance of Information and Knowledge”, Accessed 12June,2013http://www.tlu.ee/~sirvir/Information%20and%20Knowledge%20%2 0Management/Development%20of%20IKM/the_importance_of_information_and  _knowledge.html [3]5Reasons

Your

Business

Needs

a

Digital

Platform

https://www.cmswire.com/cms/digital-marketing/5-reasons-your-business-needsa-digital-platform-025880.php [4] Old Bookshops store in Kathmandu Nepal “The longest way to home” [online] https://www.thelongestwayhome.com/blog/nepal/bookshops-in-kathmandu-nepal/ [5]

Popular

social

networking

to

book

share

[online]

website

https://www.goodreads.com/blog/index [6]Note sharing paperwork [online] https://github.com/twostairs/paperwork/wiki/Note-sharing [7] NET Framework Regular Expressions.

[Online]Microsoft.

http://msdn.microsoft.com/en-us/library/hs900312.aspx. [8] Introduction to jQuery. [Online] Microsoft https://mva.microsoft.com/enus/training-courses/introduction-to-jquery-8429?l=oqWOPtKz_494984382.

19

9. APPENDICE

Fig 9.1 Login Area

Fig 9.2 Admin Home Page

20

Fig 9.3 Student List

Fig 9.4 User Registration

21

Fig 9.5 List of Faculty

Fig 9.6 Inserting new Faculty

Fig 9.7 Inserting Semester

22

Fig 9.8 Inserting Subject

Fig 9.9 Borrow notes

23