CHAPTER : 1
Introduction
1.1) Project Summary :
In this Smart Pocket For College firstly the admin will do registration of the student which consist of fields like Name , Gender , Address ,Date Of Birth , Field , Blood Group, Enrolment no, Roll no ,Pin code, Email id , Contact no and Semester. Then the admin will take money from student to insert the amount in student’s unique card ,then admin will issue a unique card to the student.
When student will go in the library at the time of issuing the book the unique card will be scanned and when the student return the book the card is again scanned and if the book is returned late then the fine will be directly deduct from the student’s card , if there is less balance in student’s card then the librarian will instruct the student to refill the card and will not accept the book .
When student will go in canteen the student will place the order and give the card for paying the money canteen person checks in the database whether sufficient amount is present in the card or not .If there is less amount the order will not be taken .If sufficient amount deduct the money from the card .
When student goes to transport department and give the card to pay the transport fees. The transport department checks in the database about enough money for fees if there is less money in card the inform the student to go to admin and refill the amount . If enough money for fess is there then deduct the money and issue the bus pass.
At the time of paying the exam fees student gives card to faculty to deduct the exam fess. Faculty checks in the database about enough money for fees if there is less money in card the faculty will not give the form. . If enough money for fess is there then deduct the money and give the form to student to fill.
The student goes to the stationary and selects item/ product to buy or give the pen-drive for print of the document or zerox of the document and then the student gives the card for payment the stationary person will checks in the database about enough money or not fees if there is less money in card then will not give the product and if enough money is there then give the student the product.
At the time of the registration for workshop/seminar the student will give the card to pay workshop fess to faculty if there is less money in card the no registration will be done . If enough money for fess is there then deduct the money and do student registration.
1.2) Purpose :
We are developing this application to ease the student’s college activities. This application would also be helpful at various places like library , canteen , stationary etc. Because as this application reduces the work of various modules like librarian, admin staff, transport person , stationary person .Digitalizing the transaction for the clients like canteen, library , stationary etc . So the according to this application the student need not to carry the cash amount he/she just need to carry the unique card.So, the problems like change of money, theft of money etc can be avoided.The main goal of the system is to save the time of student as well as various places like library , canteen , stationary etc.
1.3) Scope :
In today’s world it seems that all the activities done by student like paying library fine , paying money in canteen , paying money in stationary , paying various fees like exam fees , visit fees , seminar fees etc is simple but it is time consuming . Some time proper change of money is not available , sometime student forgets the money at home , so such problem is resolved in this project
as student just need to carry the unique card hence time is saved and safe mode of transaction is possible. And record is also maintained so information retrival is simple and easy.
System provides features such as :
1) Easy Interation : As the environment of the system is very interactive to the user ,the users who is new to the system can have faster grep on the system.
2) Reliable : This system works according to the users inputs or request and never fails in any of the operation.
3) Time Saving : In this system the payments are done via the unique card hence the time is saved which used to wasted in exchanging the change of money .
4) Good System GUI : The front end is designed in such a way that the user would experience good interaction.
5) Faster Computation : With the use of the circuit to scan the card makes the process of paying money faster.
6) Fruad Avoidance : As the cash money is not used the money cannot be theft.
CHAPTER : 2
SYSTEM
REQUIREMENT STUDY
2.1) User Characteristics :
(1) STUDENT :
• In this system the student plays an important role. Student perform work like registration in the system an activities are –
• Issue book
• Pay fine
• Order food pay money
• In stationary buy product and pay money
• Pay exam visit seminar fee
(2) ADMIN :
• Issue smart card
• Register student and users
(3) LIBRARAIN:
• Take fine / scan card
• Update student record
• Maintain book record
(4) CANTEEN PERSON:
• Scan card and give food item
• Update student records
(5) STATIONARY PERSON:
• Scan card and give item to student.
• Update student records
(6) STAFF ADMIN:
• Take exam, seminar, visit fees using card.
• Update student records.
(7) TRANSPORT PERSON:
• Scan card, give bus pass.
2.2) Hardware Requirements and Software Requirements :
Software Requirements:
Application Software : Browser (Mozilla Firefox, Internet Explorer, Google Chrome etc.)
Operating System : Window 2008,Window XP, Linux
Hardware Requirements:
Graphic Card : 512 MB
Processer : P3
Minimum Memory Required [Ram] : 512 MB
[Hard disk] : 40 GB
2.3) Timeline chart and process model :
Timeline Chart
Phases Start Date End Date Duration
Project Definition 25 -June- 2017 05- July 2017 11 Days
Requirement Gathering 06- July – 2017 20 – July – 2017 15 Days
Analysis 21 – July – 2017 05 – August – 2017 15 Days
Designing 06 – August – 2017 04 – September- 2017 30 Days
Coding 05 – September- 2017 10 – November – 2017 66 Days
Testing 11 – November – 2017 28 – December – 2017 17 Days
Implementation 29 – December – 2017 22 – January – 2018 23 Days
Phase 25 –06-2017 05- 07-2017 06- 07- 2017 20-07-2017 21-07-2017 05-08-2017 06-08-2017 04-09-2017 05-09-2017 10-11-2017 11-11-2017 28-12-2017 29 -12-2017 22-01-2018
Project Definition
RequirementGathering
Analysis
Designing
Coding
Testing
Implementa—tion
Process Model :
WATERFALL MODEL
CHAPTER : 3
SYSTEM ANALYSIS
3.1) Study Of Current System :
In the current system the student manually pay the money . He has to stand in queue for the for the payment of any of the bill, for the payment of fine so, it is very time consuming and student’s time is wasted. And the student also face fraud like theft of money or student also face problem like forget the money at home.
3.2) Problem and Weakness of Current System :
• Change of money is sometimes not available. .
• Student money may be lost.
• Students money may be theft.
• Student may forget money at home.
• Current system is time consuming
3.3 ) Requirements Of New System
We are developing this application to ease the student’s college activities.
This application would also be helpful at various places like library , canteen , stationary etc.
Because as this application reduces the work of various modules like librarian, admin
staff, transport person , stationary person .
Digitalizing the transaction for the clients like canteen, library , stationary etc.
So the according to this application the student need not to carry the cash amount he/she just need to carry the unique card.
So, the problems like change of money, theft of money etc can be avoided.
The main goal of the system is to save the time of student as well as various places like library , canteen , stationary etc.
System Platform:
• Microsoft Windows XP/2007
• P3 Processor
• 2.40 GHz
• 512 MB RAM
• 40 GB HDD
Development Tools:
• Visual Studio 2013 (ASP.Net 4.0)Tools and Technology
• Database Server – MS-SOL Server 2005
• Technologies – ASP.Net using C#.Net
• Web Browser – Internet Explorer 7.0, Mozilla Firefox 3.0.1
3.4) Feasibility study
An Important part of initializing a project is justifying it. In other words, determine whether or not it should be built. The main goal of feasibility study is to define the best implementation solution for the project undertaken and justify why it is best.
The feasibility study uses technique that helps to evaluate a project and or compare it with other projects.
Objective Of System Feasibility Analysis :-
• Identify the user’s need
• Evaluate the system concept for feasibility.
• Perform economic and technical analysis.
• Allocate Functions to H/W, S/W, people, database and other system analysis.
• Establish cost and schedule constrains.
• Create system definition forming the foundation for all subsequent work.
Feasibility study mainly focuses on whether the system is feasible or not. It concentrates on various kinds of feasibility such as;
a) Technical feasibility:
• Can the work for the project be done with the present equipment, current procedures, existing
• Software technology and available personal? This will be requiring a close examination of the present system.
The technical feasibility should ask questions related to:
1. Adequacy of available technology.
2. Adequacy of hardware.
3. Availability of computer.
4. Operating time and support facilities etc.
This is mainly concerned with specifying equipment and software that will successfully satisfy the user requirement. You can write: We studied our project is technically feasible with the equipments and software provided to us.
b) Operational feasibility:
• Will the system be used, if it is implemented?
• This is necessary because “equipment does not cry but people do cry”. The existing personnel normally worry.
• About job security, loss of peer group, changes in job context and so on whenever new systems are proposed.
• If their voices are not hard at this stage, the problem will be magnified at the implementation stage and appear as direct or indirect resistance to new system.
It is mainly related to how the system will be operated by the user. And whether the new user will feel ease to use the system. You can write: Our Project is feasible in this aspect because any user of the system can operate the system easily without much training needed and time wasted for it.
c) Social feasibility:
This is concerned with the determination of whether the system will be acceptable to the
people or not. You can write: Our Project is acceptable to the user from all the aspects with its predefined factors.
d) Economic feasibility:
• Firstly identify the alternative.
• Determine costs and expected savings of the alternative.
The costs must include both onetime costs and recurring costs:
1. Feasibility study costs.
2. The cost for converting from present system to new system.
3. Construction or remodeling of computer room facility.
4. Costs involved in software packages.
This is most frequently used technique for evaluating the effectiveness of a proposed System. This is the procedure to determine the benefits and savings that are expected from proposed system and compare them with cost. You can write: Our Project is economically feasible.
e) Management feasibility:
This is used for determination of whether our project is acceptable to management or not. If management does not accept project, the analyst will tend to view the project as non-feasible.
f) Legal feasibility:
This is determination of whether our project is proposed project infringes on known as well as any pending legislation.
g) Time feasibility:
This is mainly concerned with the determination of whether the system project can be implemented fully within stipulated time period. You can write: Our Project is feasible with aspects of time as it would be fully prepared and could be implemented in the given period of our project training.
f) Behavioural Feasibility
People are inherently resistant to change, and computers have been known to facilitate change. An estimate should be made of how strong a reaction the user staff is likely to have toward the development of a computerized system. It is common knowledge that computer installation has something to do with Turnover, Transfers and changes in employee Job Status
3.5)Requirements validations
List Of Validations :
1) Requiredfield validator :
This validator is used to not allow the further process without filling the required details .
2) Custom Validator :
This validator is used to fill the data in a user specific pattern .
3) Range Validator :
This validator is used to fill data between specified range .
4) Compare Validator :
This Validator is used to compare value of one field with the another .
5) Regularexpression Validator :
This validator is used to fill the data in a specific pattern .
3.6) Functions Of System :
3.6.1) Use Case Diagrams :
3.6.1.1) Use Case Model for Admin
Fig : 1 Use Case Model for Admin
3.6.1.2) Use Case Model for student
Fig : 2 Use Case Model for Student
3.6.1.3) Use Case Model for admin staff
Fig : 3 Use Case Model for Admin Staff
3.6.1.4) Use Case Model for librarian
Fig : 4 Use Case Model for Librarian
3.6.1.5) Use Case Model for canteen person
Fig : 5 Use Case Model for Canteen Person
3.6.1.6) Use Case Model for stationary person
Fig : 6 Use Case Model for Stationary Person
3.6.1.7) Use Case Model for transport person
Fig : 7 Use Case Model for Transport Person
3.7) Data Modeling
3.7.1) E-R Diagram
Fig : 8 E-R Diagram
3.7.2 ) Activity Diagrams :
3.7.2.1) Admin
Fig : 9 Activity Diagram Of Admin
3.7.2.2) Student
Fig : 10 Activity Diagram Of Student
3.7.2.3) College admin staff
Fig : 11 Activity Diagram Of Admin Staff
3.7.2.4) Librarian
Fig : 12 Activity Diagram Of Librarian
3.7.2.5) Canteen person
Fig : 13 Activity Diagram Of Canteen Person
3.7.2.6) Transport person
Fig :14 Activity Diagram Of Transport Person
3.7.2.7) Stationary Person
Fig : 15 Activity Diagram Of Stationary Person
3.7.3) Data Dictionary
1) Login
Field Data Type Null Description
Username varchar2(10) No username of the user.
Password varchar2(15) No Password of the user.
Table : 01 Login
2) Type_Master
Field Data Type Null Description
Type varchar2(15) No type of the user.
Table : 02 Type_Master
3) User_Registration
Field Data Type Null Description
first_name varchar2(10) No first name of the user.
middle_name varchar2(10) No middle name of the user.
last_name varchar2(10) No last name of the user.
Username varchar2(10) No username of the user.
Password varchar2(15) No password of the user.
confirm_password varchar2(15) No confirm password of the user.
email_id varchar2(15) No email id of the user.
mobile_no int(12) No mobile number of user.
u_address varchar2(50) No address of the user.
Table : 03 User_Registration
4) Student_Registration
Field Data Type Null Description
student_name varchar2(10) No name of the
student.
enr_no int(12) No enrolment number of the student.
Branch varchar2(20) No branch of the student.
s_address varchar2(50) No Address of the student.
s_state varchar2(20) No state of the student.
s_city varchar2(20) No city of the student.
s_country varchar2(20) No country of the student.
mobile_number int(12) No mobile number of student.
Dob date No birth date of the student.
blood_group varchar2(3) No blood group of the student.
s_password varchar2(15) No password of the student.
sconfirm_password varchar2(15) No confirm password of the student.
Username varchar2(10) No username of the student.
Table : 04 Student_Registration
5) Book_Master
Field Data Type Null Description
book_id varchar2(10) No id of the book.
book_name varchar2(30) No name of the book.
Author varchar2(20) No author of the book.
Publication varchar2(20) No name of the publication .
Price int(4) No price of the book.
Table : 05 Book_Master
6) Fine_Master
Field Data Type Null Description
day date No days after return date.
amount int(3) No amount of fine.
Table : 06 Fine_Master
7) Fooditem_Master
Field Data Type Null Description
fooditem_name varchar2(10) No name of the food item.
fooditem_amount int(3) No amount of the food item.
Category varchar2(12) No category of food item.
Table : 07 Fooditem_Master
8) Fooditem_Category
Field Data Type Null Description
category_name varchar2(12) No category of food item.
Table : 08 Fooditem_Category
9) Transport_Master
Field Data Type Null Description
city_name varchar2(20) No name of the city.
Area varchar2(20) No area of the city.
Amount int(5) No amount of bus fees.
Table : 09 Transport_Master
10) City_Master
Field Data Type Null Description
city_name varchar2(20) No name of the city.
Table : 10 City_Master
11) Area_Master
Field Data Type Null Description
city_name varchar2(20) No name of the city.
area varchar2(20) No area of the city.
Table : 11 Area_Master
12) Examfees_Master
Field Data Type Null Description
exam_title varchar2(15) No title of the exam.
exam_date date No date of the exam.
fees_amount int(4) No amount of exam fees.
Table : 12 Examfees_Master
13) Workshop_Master
Field Data Type Null Description
workshop_title varchar2(15) No title of the workshop.
workshop _date date No date of the workshop.
workshop_fees int(4) No amount of workshop fees.
Table : 13 Workshop_Master
14) Recharge
Field Data Type Null Description
enr_no int(12) No enrolment number of the student.
card_id varchar2(15) No unique number of the card.
recharge_date date No date of recharge.
recharge_amount int(4) No amount of the recharge.
Table : 14 Recharge
15) Allocate_Card
Field Data Type Null Description
enr_no int(12) No enrolment number of the student.
card_id varchar2(15) No unique number of the card.
issue_date date No issue date of the card.
Table : 15 Allocate_Card
16) Stationary_Master
Field Data Type Null Description
product_name varchar2(20) No name of the product of stationary.
product_amount int(3) No amount of the product.
Table : 16 Stationary_Master
17) Book_Issue
Field Data Type Null Description
enr_no varchar2(12) No enrolment number of the student.
book_id varchar2(10) No id of the book.
issue_date date No issue date of the book.
Table : 17 Book_Issue
18) Visit_Master
Field Data Type Null Description
enr_no varchar2(12) No enrolment number of the student.
visitfess_amount int(3) No amount of visit fees.
visit_date date No date of the visit.
Table : 18 Visit_Master
3.7.4 ) Flow diagram
Fig : 16 Flow Diagram
3.8) Main module of New system :
(1) STUDENT :
• In this system the student plays an important role. Student perform work like registration in the system an activities are –
• Issue book
• Pay fine
• Order food pay money
• In stationary buy product and pay money
• Pay exam visit seminar fee
(2) ADMIN :
• Issue smart card
• Register student and users
(3) LIBRARAIN:
• Take fine / scan card
• Update student record
• Maintain book record
(4) CANTEEN PERSON:
• Scan card and give food item
• Update student records
(5) STATIONARY PERSON:
• Scan card and give item to student.
• Update student records
(6) STAFF ADMIN:
• Take exam, seminar, visit fees using card.
• Update student records.
(7) TRANSPORT PERSON:
• Scan card, give bus pass.
CHAPTER : 4
SYSTEM DESIGN
4.1) Input / Output and interface design
1) User Id :
The user id helps in identifying the user uniquely in the system .
2) Password :
This is the password associated with the user id .
4.2) Sequence Diagram :
4.2.1) Admin :
Fig : 17 Sequence Diagram Of Admin
4.2.2 ) Library :
Fig : 18 Sequence Diagram Of Library
4.2.3) Canteen
Fig : 19 Sequence Diagram Of Canteen
4.2.4) Transport
Fig : 20 Sequence Diagram Of Transport
4.2.5) Staff Admin :
Fig : 21 Sequence Diagram Of Admin Staff
4.2.6) Stationary :
Fig : 22 Sequence Diagram Of Stationary
CHAPTER : 5
SCREENSHORTS
Home Page :
About us :
Contact us:
login.aspx :
Registration Page ( Student) :
Registration Page ( Employee) :
Admin Panel :