126 Updated

S3-Student Smart Card Services
Developed by
Haroon Shabbir
(29/FBAS/BSIT4/F15)
Usman Ali
(30/FBAS/BSIT4/F15)
Supervised by
Muhmmad Imran
Department of Computer Science & Software Engineering
Faculty of Basic and Applied Science
International Islamic University Islamabad

2019
FINAL APPROVAL
Dated:
It is certified that we have read the project report titled “( S3-Student Smart Card Services)” submitted by
Haroon Shabbir (29/FBAS/BSIT4/F15) and Usman Ali (30/FBAS/BSIT4/F15). It is our judgment that this
project is of sufficient standard to warrant its acceptance by the International Islamic University, Islamabad for
Bachelor’s Degree in Information Technology.
COMMITTEE
External Examiner:
Muhammad Imran Signature:
Lecturer
FBAS, DCS&SE
International Islamic University, Islamabad
Internal Examiner:
Muhammad Nadeem Signature:
Assistant Professor FBAS, DCS&SE
Supervisor:
Muhammad Imran Signature:
Lecturer
FBAS, DCS&SE
ii
"In the Name of ALLAH, the Most Beneficent, the Most Merciful"
iii
S3-Student Smart Card Services Dissertation
A dissertation submitted to
Department of Computer Science & Software Engineering, International Islamic University, Islamabad
As partial fulfillment of the requirements for award of the degree of
Bachelors in Information Technology.
iv
S3-Student Smart Card Services Dedication
Dedication
To the blessings of Allah Almighty who gave the determination and power and guided along the way
for the completion of this “Project” and “Degree”. I dedicate this to my beloved Parents who gave me
this opportunity and provided me the resources, efforts and moral support throughout this Degree and
in my Life. And to my Teachers who guided and supported me at each step during this project and in
general, without their great support, cordial prayers and immense belief in me, the completion of the
degree would have not been possible and this milestone could have been unachievable.
v
S3-Student Smart Card Services Project in Brief
Declaration
We hereby declare that this application is neither as a whole, nor as a part there of has been copied out
from any source to the best of my knowledge. It is further declared that we have developed this
software application and the accompanied report entirely on the basis of our personal effort made under
the sincere guidance of our kind supervisor.
Haroon Shabbir (29/FBAS/BSIT4/F15)
Usman Ali (30/FBAS/BSIT4/F15)
vi
Acknowledgment
All praise to Almighty Allah, who gave me the understanding, courage and patience to complete this
project. Thanks to my parents, friends and all well-wishers, who helped me during my most difficult
times and it is due to their efforts I was able to complete this project. I express my gratitude to my kind
supervisor Sir Muhammad Imran, for providing me opportunity to learn and enhance my knowledge. He
had been ready to help and throughout this project.
vii
Project in brief
Project Title: S3-Student Smart Card Services
Objective: Objective of this project is to create an integrated

system that facilitates students and provides them a
handful of features through a single Student Card
Undertaken By: Haroon Shabbir (29/FBAS/BSIT4/F15)

Usman Ali (30/FBAS/BSIT4/F15)
Supervised By: Muhammad Imran
Date Started: May-2019
Date Completed: November-2019
Technology: PHP Classic, HTML, CSS, Java Script, jQuery, MY SQL
viii
S3-Student Smart Card Services Abstract
Abstract
Student Smart Card is a modern day smart card that provides students with a bunch of facilities around
the university campus along with being a student ID card. Student Smart Card has NFC tag technology
for contactless payments and identification. Student Smart Card is a prepaid card and students are able
to do micro transactions at university cafeteria and book shop, also facilitating the student in issuance
of a book from library and pay academic fines.
ix
S3-Student Smart Card Services Table of Contents
Table of Contents
Contents
Developed by .......................................................................................................................... 1
Supervised by.......................................................................................................................... 1
FINAL APPROVAL .................................................................................................................................. 2
Dated: 2
COMMITTEE .................................................................................................................................... 2
Dedication .................................................................................................................................................. 5
Declaration ................................................................................................................................................. 6
Acknowledgment........................................................................................................................................ 7
Project in brief ............................................................................................................................................ 8
Abstract .............................................................................................................................................. 9
Table of Contents ..................................................................................................................................... 10
List of Figures .......................................................................................................................................... 14
1 Introduction ........................................................................................................................................... 17
1.1 Introduction........................................................................................................................... 17
1.2 Objective ............................................................................................................................... 17
1.3 Problem Statement ................................................................................................................ 17
1.4 Project Scope ........................................................................................................................ 18
1.5 Definitions, Acronyms, and Abbreviations .......................................................................... 18
1.6 Features ................................................................................................................................. 18
1.7 Literature Review ....................................................................................................................... 19
1.7.1 History ......................................................................................................................... 19
1.7.2 Design .......................................................................................................................... 21
1.7.3 Applications ................................................................................................................. 23
x
1.7.4 History of Smart Cards ............................................................................................... 29
1.8 Proposed system ......................................................................................................................... 30
1.9 Need to replace the existing system............................................................................................ 30
1.10 Understanding the proposed system ..................................................................................... 31
1.11 Requirements Analysis ......................................................................................................... 32
1.12.2 Non-Functional Requirements............................................................................................... 34
1.13 Proposed System ...................................................................................................................... 35
Chapter: 2 ................................................................................................................................................. 38
System Analysis ....................................................................................................................................... 38
2.1 Software process model ........................................................................................................ 39
2.2 Iteration 1 ................................................................................................................................... 41
2.3 Iteration 2 ................................................................................................................................... 63
Chapter: 3 ................................................................................................................................................. 91
System Analysis ....................................................................................................................................... 91
3.1 Design:........................................................................................................................................ 92
3.2 ER Diagram ................................................................................................................................ 93
3.3 Class Diagram: ........................................................................................................................... 94
3.4 Design:........................................................................................................................................ 95
Chapter: 4 ................................................................................................................................................. 96
Implementation ......................................................................................................................................... 96
4.1 Implementation of Iteration 1 ..................................................................................................... 97
4.2 Implementation of Iteration 2 ..................................................................................................... 98
4.3 Tools and Technologies ........................................................................................................ 99
4.3.1 Software.................................................................................................................... 99
4.3.2 Hardware.................................................................................................................... 100
4.4 Platform selection ............................................................................................................... 102
xi
4.5 System development ........................................................................................................... 103
Chapter 5 ................................................................................................................................................ 105
Testing .................................................................................................................................................... 105
5.1 Testing and Results .................................................................................................................. 106
Iteration 1 ............................................................................................................................ 106
5.2 Testing and Results .................................................................................................................. 107
5.3 Gantt chart ................................................................................................................................ 108
Chapter 6 ................................................................................................................................................ 109
Conclusion .............................................................................................................................................. 109
6.1 Conclusion and future work ..................................................................................................... 110
6.2 User Guide ................................................................................................................................ 110
6.2.1 User Guide ................................................................................................................. 110
6.3 References..................................................................................................................... 111
xii
S3-Student Smart Card Services List of Table
List of Tables
Table 2.1 Accounts Department Use Case Description ..................................................................52

Table 2.2 Cafeteria and Bookshop inventory System Use Case Description…………………….52
Table 2.3 Student Portal Use Case Description…………..……………………………………...53
Table 2.4 Library Use Case Description…...…………………………………………………….54
Table 2.5 Accounts Department Use Case Description ………………………………...………..79
Table 2.6 Cafeteria and Bookshop inventory System Use Case Description…………………….80
Table 2.7 Student Portal Use Case Description Use Case Description………………………….81
Table 2.8 Library Use Case Use Case Description……………………………………………...82
Table 2.9 Book shop and Inventary Use Case Description……………………………………....83
Table 4.1 Hardware Specification .................................................................................................102
Table 5.1 Test Case for Iteration-I ..................................................................................................106
Table 5.2 Test Case for Iteration-II ................................................................................................108
Table 5.3 Iteration-I Gantt chart .....................................................................................................108
Table 5.4 Iteration-II Gantt chart....................................................................................................108
xiii
S3-Student Smart Card Services List of Figures
List of Figures
Figure 2.1 Iterative Model ................................................................................................ 40

Figure 2.2 Accounts Department Use Case ......................................................................... 41
Figure 2.3 Student Portal Use Case .................................................................................. 42
Figure 2.4 Library Management Use Case ....................................................................... 43
Figure 2.5 Café and Bookshop Use Case ........................................................................... 43
Figure 2.6 Accounts Detail Use Case ................................................................................. 44
Figure 2.7 Library Management Detail Use Diagram ........................................................... 47
Figure 2.8 Student Portal Detail Use Diagram…………………..………………………….49
Figure 2.9 Accounts Department Sequence Diagram ........................................................... 55
Figure 2.10 Bookshop and Cafeteria Sequence Diagram .................................................... 56
Figure 2.11 Student Sequence Diagram............................................................................ 56
Figure 2.12 Login Activity Diagram ................................................................................ 58
Figure 2,13 Account Activity Design ............................................................................... 59
Figure 2.14 Bookshop Activity Diagram .......................................................................... 60
Figure 2.15 Library Activity Diagram ............................................................................. 61
Figure 2.16 Student Activity Diagram…………………………………………………...62
Figure 2.17 Account Use Case Diagram ........................................................................... 63
Figure 2,18 Student Use Case Diagram ............................................................................ 64
Figure 2.19 Library Management Use Case ..................................................................... 65
Figure 2.20 Book Use Case .............................................................................................. 66
Figure 2.21 Cafe Use Case................................................................................................ 67
Figure 2.22 Accounts Detail Use Case ............................................................................. 67
Figure 2.23 Student Detail Use Case ................................................................................ 71
Figure 2.24 Library Detail Use Case ................................................................................ 73
Figure 2.25 Cafeteria Management Detail Use Case ............................................................ 75
Figure 2.26 Bookshop Inventory System Detail Use Case ..................................................... 77
Figure 2.27 Accounts Department Sequence Diagram .................................................... 84
Figure 2.28 Bookshop Inventory System Sequence Diagram................................................. 85
Figure 2.29 Student Portal Sequence Diagram ................................................................. 85
xiv
S3-Student Smart Card Services List of Figures
Figure 2.30 Library System Sequence Diagram ............................................................... 86

Figure 2.31 Cate System Sequence Diagram .................................................................... 86
Figure 2.32 Login Activity Diagram ................................................................................ 87
Figure 2.33 Account department Activity Diagram ......................................................... 88
Figure 2.34 Cafe System Sequence Diagram ................................................................... 89
Figure 2.35 Bookshop Activity Diagram .......................................................................... 89
Figure 2.36 Library System Activity Diagram ................................................................. 90
Figure 2.37 Student Portal Activity Diagram ................................................................... 90
Figure 3.1 ERD Diagram .................................................................................................. 93
Figure 3.2 Class Diagram ................................................................................................. 94
Figure 3.3 Design Diagram ............................................................................................... 95
Figure 4.1 System development Diagram ....................................................................... 103
xv
CHAPTER 1
INTRODUCTION
Introduction Chapter 01
1 Introduction
1.1 Introduction
With the advancement in our daily lifestyle, introducing new products and technologies to our lives
become mandatory. A university student these days is well aware of everything going around and it
becomes the duty of the university to provide latest facilities to its students in order to ease them.
Student Smart Card Service strives to provide a handful of facilities that a student might not feel
important now but will definitely appreciate.
Student Smart Card, a prepaid smart card for students that facilitate its users with wireless /
contactless transactions and identification as well as being a fully functional student id card. Students
are able to deposit money to the withholding Student Smart Card and transaction can be made at
university cafeteria and book shop to pay the required bills, as well as it is also applicable as a library
card for book issuance. Students are also able to pay their academic using Student Smart Card Services
1.2 Objective
Our main objective of this system is to create an integrated system that facilitates students and provides
them a handful of features through a single Student Card.
.
1.3 Problem Statement

In the past decade secured transactions and cashless payments has become a trend around the globe. A
university student most of the time feels uncomfortable carrying a wallet/cash with him. One can also
forget to bring cash on the first hand. One might also worry about theft or loosing cash somewhere.
Therefore we want to bring multifunctional Student Smart Card to the reach of all students. We’ve
decided to pack almost all the things a student usually carries in his wallet, into a single card. Including
a student card, a library card and some extra cash to buy things to eat or just getting some stationery
from book store. Student Smart Card Service certainly be a must have for all the students when they
realize how convenient it could be just to carry on card instead of a bunch in there wallet.
S3-Student Smart Card Services 17

1.4 Project Scope

Student Smart Card Service offers its user with multiple functionalities with the ease of use. Student
these days have to carry a lot already with them such as their laptop, a bunch of books, there
assignments, useful notes and other things all in a heavy bag or in hand. Among with all these things
they also carry a wallet with them which has there CNIC card, student ID card, a library card and some
cash. Well, with Student Smart Card he has to carry just his CNIC and Student Smart Card with him. It
is useful across the university campus paying for cafeteria bills, book shop bills and library and also
help them pay the academic fine.
1.5 Definitions, Acronyms, and Abbreviations

 S3-Student Smart Card Services
 S-Cube
 Web Application.
 Desktop Application
1.6 Features
 Following are the features of S3 (Student Card Sevices) System:
 We have integrated a Library management system for library.
 We have introduced Basic inventory and billing system for cafeteria and book shop.
 We made our database as central database and connected systems through intranet.
 Student Smart Card offered one tap NFC card recognition secured with a PIN.
 We have provided a designated desktop web based application for each desired place.
 Admin panel have all the information regarding all the transactions made and all the sale record
of cafeteria and book shop as well as a complete record of library.
 Students using smartphones having NFC built in are able to tab their Student Smart card on
back of their devices which will automatically take them to a website link with a PIN input
prompt. After logging in using their pin, students are able to see their transaction record.
 A unique ID is also assigned to the Student Smart Card which is used to deactivate the card in
case of theft or getting lost.

 Cafeteria and book shop sales record are also available at accounts office and they can collect
their sales cash as they like.
1.7 Literature Review

A smart card, chip card, or integrated circuit card (ICC) is any pocket-sized card that has embedded
integrated circuits. Smart cards are made of plastic, generally polyvinyl chloride, but sometimes
polyethylene terephthalate based polyesters, acrylonitrile butadiene styrene or polycarbonate. Since
April 2009, a Japanese company has manufactured reusable financial smart cards made from paper. [1]
Smart cards can be either contact or contactless smart card. Smart cards can provide personal
identification, authentication, data storage, and application processing. Smart cards may provide strong
security authentication for single sign-on (SSO) within large organizations.
1.7.1 History
 Invention
In 1968 and 1969 Helmut Gröttrup and Jürgen Dethloff jointly filed patents for the automated chip
card. Roland Moreno patented the memory card concept in 1974. An important patent for smart cards
with a microprocessor and memory as used today was filed by Jürgen Dethloff in 1976 and granted as
USP 4105156 in 1978.In 1977, Michel Ugon from Honeywell Bull invented the first microprocessor
smart card with two chips: one microprocessor and one memory, and in 1978, he patented the self-
programmable onechip microcomputer (SPOM) that defines the necessary architecture to program the
chip. Three years later, Motorola used this patent in its "CP8". At that time, Bull had 1,200 patents
related to smart cards. In 2001, Bull sold its CP8 division together with its patents to Schlumberger,
who subsequently combined its own internal smart card department and CP8 to create Axalto. In 2006,
Axalto and Gemplus, at the time the worlds top two smart card manufacturers, merged and became
Gemalto. In 2008 Dexa Systems spun off from Schlumberger and acquired Enterprise Security
Services business, which included the smart card solutions division responsible for deploying the first
large scale public key infrastructure (PKI) based smart card management systems.[10]
The first mass use of the cards was as a telephone card for payment in French pay phones, starting in
1983.

 Carte Bleue
After the Télécarte, microchips were integrated into all French Carte Bleue debit cards in 1992.
Customers inserted the card into the merchant's point of sale (POS) terminal, then typed the personal
identification number (PIN), before the transaction was accepted. Only very limited transactions (such
as paying small highway tolls) are processed without a PIN. Smart-card-based "electronic purse"
systems store funds on the card so that readers do not need network connectivity. They entered
European service in the mid-1990s. They have been common in Germany (Geldkarte), Austria (Quick
Wertkarte), Belgium (Proton), France (Moneo), the Netherlands (Chipknip Chipper (decommissioned
in 2001)),
Switzerland ("Cash"), Norway ("Mondex"), Sweden ("Cash", decommissioned in 2004),
Finland ("Avant"), UK ("Mondex"), Denmark ("Danmønt") and Portugal ("Porta-moedas
Multibanco").[10]
Since the 1990s, smart-cards have been the Subscriber Identity Modules (SIMs) used in European
GSM mobile phone equipment. Mobile phones are widely used in Europe, so smart cards have become
very common.
 EMV
Europay MasterCard Visa (EMV)-compliant cards and equipment are widespread. The United States
started using the EMV technology in 2014. Typically, a country's national payment association, in
coordination with Master Card International, Visa International, American Express and Japan Credit
Bureau (JCB), jointly plan and implement EMV systems.
Historically, in 1993 several international payment companies agreed to develop smartcard

specifications for debit and credit cards. The original brands were MasterCard, Visa, and Europay. The
first version of the EMV system was released in 1994. In 1998 the specifications became stable.
EMVCo maintains these specifications. EMVco's purpose is to assure the various financial institutions
and retailers that the specifications retain backward compatibility with the 1998 version. EMVco
upgraded the specifications in 2000 and 2004[9].
EMV compliant cards were first accepted into Malaysia in 2005 and later into United States in 2014.

MasterCard was the first company that was allowed to use the technology in the United States. The
United States has felt pushed to use the technology because of the increase in identity theft. The credit
card information stolen from Target in late 2013 was one of the largest indicators that American credit
card information is not safe. Target made the decision on April 30, 2014 that it would try to implement
the smart chip technology in order to protect itself from future credit card identity theft. [10]
Before 2014, the consensus in America was that there was enough security measures to avoid credit
card theft and that the smart chip was not necessary. The cost of the smart chip technology was
significant, which was why most of the corporations did not want to pay for it in the United States. The
debate came when online credit theft was insecure enough for the United States to invest in the
technology. The adaptation of EMV's increased significantly in 2015 when the liability shifts occurred
in October by the credit card companies.
 Development of Contactless Systems
Contactless smart cards do not require physical contact between a card and reader. They are becoming
more popular for payment and ticketing. Typical uses include mass transit and motorway tolls. Visa
and MasterCard implemented a version deployed in 2004–2006 in the U.S. Most contactless fare
collection systems are incompatible, though the MIFARE Standard card from NXP Semiconductors
has a considerable market share in the US and Europe.
Smart cards are also being introduced for identification and entitlement by regional, national, and
international organizations. These uses include citizen cards, drivers’ licenses, and patient cards. In
Malaysia, the compulsory national ID MyKad enables eight applications and has 18 million users.
Contactless smart cards are part of ICAO biometric passports to enhance security for international
travel.
1.7.2 Design
A smart card may have the following generic characteristics:
Dimensions similar to those of a credit card. ID-1 of the ISO/IEC 7810 standard defines cards as
nominally 85.60 by 53.98 millimeters (3.37 in × 2.13 in). Another popular size is ID-000 which is
nominally 25 by 15 millimeters (0.98 in × 0.59 in) (commonly used in SIM cards).
Both are 0.76 millimeters (0.030 in) thick.

Contains a tamper-resistant security system (for example a secure crypto processor and a secure file
system) and provides security services (e.g., protects in-memory information).
Managed by an administration system which securely interchanges information and configuration
settings with the card, controlling card blacklisting and application-data updates. Communicates with
external services via card-reading devices, such as ticket readers, ATMs, DIP reader, etc.
 Contact Smart Card
Contact smart cards have a contact area of approximately 1 square centimeter (0.16 sq. in), comprising
several gold-plated contact pads. These pads provide electrical connectivity when inserted into a
reader, which is used as a communications medium between the smart card and a host (e.g., a
computer, a point of sale terminal) or a mobile telephone. Cards do not contain batteries; power is
supplied by the card reader.
The ISO/IEC 7810 and ISO/IEC 7816 series of standards define:
 Physical shape and characteristics
 Electrical connector positions and shapes
 Electrical characteristics
 Communications protocols, including commands sent to and responses from the card
 Basic functionality
Because the chips in financial cards are the same as those used in subscriber identity modules (SIMs)
in mobile phones, programmed differently and embedded in a different piece of PVC, chip
manufacturers are building to the more demanding GSM/3G standards. So, for example, although the
EMV standard allows a chip card to draw 50 mA from its terminal, cards are normally well below the
telephone industry's 6 mA limit. This allows for smaller and cheaper financial card terminals.
Communication protocols for contact smart cards include T=0 (character-level transmission protocol,
defined in ISO/IEC 7816-3) and T=1 (block-level transmission protocol, defined in ISO/IEC 7816-3).
 Contactless Smart Card
A second card type is the contactless smart card, in which the card communicates with and is powered
by the reader through RF induction technology (at data rates of 106– 848 Kbit/s). These cards require
only proximity to an antenna to communicate. Like smart cards with contacts, contactless cards do not

have an internal power source. Instead, they use an inductor to capture some of the incident radio-
frequency interrogation signal, rectify it, and use it to power the card's electronics.
APDU transmission via a contactless interface is defined in ISO/IEC 14443-4.
 Hybrids
Hybrid cards implement contactless and contact interfaces on a single card with dedicated
modules/storage and processing.
 Dual Interface
Dual-interface cards implement contactless and contact interfaces on a single card with some shared
storage and processing. An example is Porto's multi-application transport card, called Andante, which
uses a chip with both contact and contactless (ISO/IEC 14443 Type B) interfaces.
 USB
The CCID (Chip Card Interface Device) is a USB protocol that allows a smartcard to be connected to a
Computer, using a standard USB interface. This allows the smartcard to be used as a security token for
authentication and data encryption such as Bit locker. CCID devices typically look like a standard USB
dongle and may contain a SIM card inside the USB dongle.
1.7.3 Applications
 Financial
Smart cards serve as credit or ATM cards, fuel cards, mobile phone SIMs, authorization cards for pay
television, household utility pre-payment cards, high-security identification and access-control cards,
and public transport and public phone payment cards.
Smart cards may also be used as electronic wallets. The smart card chip can be "loaded" with funds to
pay parking meters, vending machines or merchants. Cryptographic protocols protect the exchange of
money between the smart card and the machine. No connection to a bank is needed. The holder of the
card may use it even if not the owner. Examples are Proton, Geldkarte, Chipknip and Moneo. The
German Geldkarte is also used to validate customer age at vending machines for cigarettes.

These are the best known payment cards (classic plastic card):
 Visa: Visa Contactless, Quick VSDC, "qVSDC", Visa Wave, MSD, payWave
 MasterCard: PayPass Magstripe, Pay Pass MChip
 American Express: ExpressPay
 Discover: Zip
 Union pay: QuickPass
Roll-outs started in 2005 in the U.S. Asia and Europe followed in 2006. Contactless (nonPIN)
transactions cover a payment range of ~$5–50. There is an ISO/IEC 14443 PayPass implementation.
Some, but not all PayPass implementations conform to EMV.
Non-EMV cards work like magnetic stripe cards. This is common in the U.S. (PayPass Magstripe and
Visa MSD). The cards do not hold or maintain the account balance. All payment passes without a PIN,
usually in off-line mode. The security of such a transaction is no greater than with a magnetic stripe
card transaction.
EMV cards can have either contact or contactless interfaces. They work as if they were a normal EMV
card with a contact interface. Via the contactless interface they work somewhat differently, in that the
card commands enabled improved features such as lower power and shorter transaction times.
 SIM
The subscriber identity modules used in mobile-phone systems are reduced-size smart cards, using
otherwise identical technologies.
 Identification
Smart-cards can authenticate identity. Sometimes they employ a public key infrastructure (PKI). The
card stores an encrypted digital certificate issued from the PKI
provider along with other relevant information. Examples include the U.S. Department of Defense
(DoD) Common Access Card (CAC), and other cards used by other governments for their citizens. If
they include biometric identification data, cards can provide superior two- or three-factor
authentication.

• Smart cards are not always privacy-enhancing, because the subject may carry incriminating
information on the card. Contactless smart cards that can be read from within a wallet or even a
garment simplify authentication; however, criminals may access data from these cards.
• Cryptographic smart cards are often used for single sign-on. Most advanced smart cards
include specialized cryptographic hardware that uses algorithms such as RSA and Digital
Signature Algorithm (DSA). Today's cryptographic smart cards generate key pairs on board, to
avoid the risk from having more than one copy of the key (since by design there usually isn't a
way to extract private keys from a smart card). Such smart cards are mainly used for digital
signatures and secure identification.
• The most common way to access cryptographic smart card functions on a computer is to use a
vendor-provided PKCS#11 library. On Microsoft Windows the Cryptographic Service
Provider (CSP) API is also supported.
• The most widely used cryptographic algorithms in smart cards (excluding the GSM socalled
"crypto algorithm") are Triple DES and RSA. The key set is usually loaded (DES) or generated
(RSA) on the card at the personalization stage.
• Some of these smart cards are also made to support the National Institute of Standards and
Technology (NIST) standard for Personal Identity Verification, FIPS 201.
• Turkey implemented the first smart card driver's license system in 1987. Turkey had a high
level of road accidents and decided to develop and use digital tachograph devices on heavy
vehicles, instead of the existing mechanical ones, to reduce speed violations. Since 1987, the
professional driver's licenses in Turkey have been issued as smart cards. A professional driver
is required to insert his driver's license into a digital tachograph before starting to drive. The
tachograph unit records speed violations for each driver and gives a printed report. The driving
hours for each driver are also being monitored and reported. In 1990 the European Union
conducted a feasibility study through BEVAC Consulting Engineers, titled "Feasibility study

with respect to a European electronic drivers license (based on a smart-card) on behalf of

Directorate General VII". In this study, chapter seven describes Turkey's experience.
• Argentina's Mendoza province began using smart card driver's licenses in 1995. Mendoza also
had a high level of road accidents, driving offenses, and a poor record of recovering fines.
Smart licenses hold up-to-date records of driving offenses and unpaid fines. They also store
personal information, license type and number, and a photograph. Emergency medical
information such as blood type, allergies, and biometrics (fingerprints) can be stored on the
chip if the card holder wishes. The Argentina government anticipates that this system will help
to collect more than $10 million per year in fines.
• In 1999 Gujarat was the first Indian state to introduce a smart card license system.[13] As of
2005, it has issued 5 million smart card driving licenses to its people.[14]
• In 2002, the Estonian government started to issue smart cards named ID Kaart as primary
identification for citizens to replace the usual passport in domestic and EU use. As of 2010
about 1 million smart cards have been issued (total population is about 1.3 million) and they
are widely used in internet banking, buying public transport tickets, authorization on various
websites etc.
• By the start of 2009 the entire population of Spain and Belgium became eID cards that are used
for identification. These cards contain two certificates: one for authentication and one for
signature. This signature is legally enforceable. More and more services in these countries use
eID for authorization.
• On August 14, 2012, the ID cards in Pakistan were replaced. The Smart Card is a third
generation chip-based identity document that is produced according to international standards
and requirements. The card has over 36 physical security features and has the latest encryption
codes. This smart card replaced the NICOP (the ID card for overseas Pakistani).

• Smart cards may identify emergency responders and their skills. Cards like these allow first
responders to bypass organizational paperwork and focus more time on the emergency
resolution. In 2004, The Smart Card Alliance expressed the needs: "to enhance security,
increase government efficiency, reduce identity fraud, and protect personal privacy by
establishing a mandatory, Government-wide standard for secure and reliable forms of
identification". Emergency response personnel can carry these cards to be positively identified
in emergency situations. WidePoint Corporation, a smart card provider to FEMA, produces
cards that contain additional personal information, such as medical records and skill sets.
• In 2007, the Open Mobile Alliance (OMA) proposed a new standard defining V1.0 of the
Smart Card Web Server (SCWS), an HTTP server embedded in a SIM card intended for a
smartphone user. The non-profit trade association SIMalliance has been promoting the
development and adoption of SCWS. SIMalliance states that SCWS offers endusers a familiar,
OS-independent, browser-based interface to secure, personal SIM data. As of mid-2010,
SIMalliance had not reported widespread industry acceptance of SCWS. The OMA has been
maintaining the standard, approving V1.1 of the standard in May 2009, and V1.2 is expected
was approved in October 2012.
 Public Transit
Smart cards and integrated ticketing are used by many public transit operators. Card users may also
make small purchases using the cards. Some operators offer points for usage, exchanged at retailers or
for other benefits. Examples include Singapore's CEPAS, Toronto's Presto card, Hong Kong's Octopus
Card, London's Oyster Card, Dublin's Leap card, Brussels' MoBIB, Québec's OPUS card, San
Francisco's Clipper card, Auckland's AT Hop, Brisbane's go card, Perth's SmartRider and Sydney's
Opal card. However, these present a privacy risk because they allow the mass transit operator (and the
government) to track an individual's movement. In Finland, for example, the Data
Protection Ombudsman prohibited the transport operator Helsinki Metropolitan Area Council (YTV)
from collecting such information, despite YTV's argument that the card owner has the right to a list of
trips paid with the card. Earlier, such information was used in the investigation of the Myyrmanni
bombing.

The UK's Department for Transport mandated smart cards to administer travel entitlements for elderly
and disabled residents. These schemes let residents use the cards for more than just bus passes. They
can also be used for taxi and other concessionary transport. One example is the "Smartcare go" scheme
provided by Ecebs.The UK systems use the ITSO Ltd specification.
 Computer Security
• Smart cards can be used as a security token.

• Mozilla's Firefox web browser can use smart cards to store certificates for use in secure web
browsing.
• Some disk encryption systems, such as Microsoft’s BitLocker, can use smart cards to securely
hold encryption keys, and also to add another layer of encryption to critical parts of the secured
disk.
• GnuPG, the well-known encryption suite, also supports storing keys in a smart card. Smart
cards are also used for single sign-on to log on to computers.
 Schools
Smart cards are being provided to students at some schools and colleges. Uses include:
• Tracking student attendance

• As an electronic purse, to pay for items at canteens, vending machines, laundry facilities, etc.
• Tracking and monitoring food choices at the canteen, to help the student maintain a healthy diet
• Tracking loans from the school library
• Access control for admittance to restricted buildings, dormitories, and other facilities. This
requirement may be enforced at all times (such as for a laboratory containing valuable
equipment), or just during after-hours periods (such as for an academic building that is open
during class times, but restricted to authorized personnel at night), depending on security needs.
• Access to transportation services
 HealthCare
Smart health cards can improve the security and privacy of patient information, provide a secure carrier

for portable medical records, reduce health care fraud, support new processes for portable medical
records, provide secure access to emergency medical information, enable compliance with government
initiatives (e.g., organ donation) and mandates, and provide the platform to implement other
applications as needed by the health care organization.
 Other Uses
Smart cards are widely used to protect digital television streams. Video Guard is a specific example of
how smart card security worked.
1.7.4 History of Smart Cards

Milestones in the development of smart card technology:
• 1970 - Dr. Kunitaka Arimura of Japan filed the first and only patent on the smart card concept.
• 1974 - Roland Moreno of France filed the original patent for the IC card, later dubbed the
"smart card".
• 1977 - Three commercial manufacturers, Bull CP8, SGS Thomson, and Schlumberger began
developing the IC card.
• 1979 - Motorola developed the first secure single chip microcontroller for use in French
banking.
• 1982 - Field testing of serial memory phone cards took place in France - the world's first major
IC card test.
• 1984 - Field trials of ATM bank cards with chips were successfully conducted.
• 1986 - 14,000 cards equipped with the Bull CP8 were distributed to clients of the Bank of
Virginia and the Maryland National Bank. 50,000 Casio cards were distributed to clients of
First National Palm Beach Bank and the Mall Bank.
• 1987 - First large-scale smart card application implemented in the United States with the U.S.
Department of Agriculture's nationwide Peanut Marketing Card.
• 1991 - First Electronic Benefits Transfer (EBT) smart card project launched for the Wyoming
Special Supplemental Nutrition Program for Women, Infants, and Children (WIC).
• 1992 - A nationwide prepaid (electronic purse) card project (DANMONT) was started in
Denmark.

• 1993 - Field test of multi-function smart card applications in Rennes, France, where the
Telecarte function (for public phones) was enabled in a Smart Bank Card.
• 1994 - Europay, MasterCard, and Visa (EMV) published joint specifications for global
microchip-based bank cards (smart cards).
• Germany began issuance of 80 million serial memory chip cards as citizen health cards.
• 1995 - Over 3 million digital mobile phone subscribers worldwide begin initiating and billing
calls with smart cards.
• The first of 40,000 multi-functional, multi-technology MARC cards with chips were issued to
U.S. Marines in Hawaii.
• 1996 - Over 1.5 million VISACash stored value cards were issued at the Atlanta Olympics.
• 1998 - The U.S. Government's General Services Administration and the United States Navy
joined forces and implemented a nine-application smart card system and card management
solution at the Smart Card Technology Center in Washington, D.C. The Technology Center's
primary purpose is to demonstrate and evaluate the integration of multi-application smart cards
with other types of technology, showcasing systems available for use in the Federal
Government.
• Microsoft announced its new Windows smart card operating system.
• France began piloting a smart health card for its 50 million citizens.
• 1999 - Smart Access Common ID Project. Federal agencies to acquire a standard, interoperable
employee identification card. The U.S. Government (General Services Administration) starts
true multi-application Java card pilot in the Washington, D.C.
1.8 Proposed system

Our propose system is based on Student Smart Card which is functional within the premises of the
institute, providing an Identification, an alternative to cash to be used at cafeteria and Book Shop,
added ability to use it as a library card and providing a handful of features on the online student
portal such as fine payments etc.
1.9 Need to replace the existing system

As existing system has some drawbacks. Like It can be quite difficult for Account Office to manage the

cash if there are thousands of students or other users to deposit or withdraw their amounts. So, there
would be a need to replace the Account Office as a Bank to manage the cash efficiently.
1.10 Understanding the proposed system

1.10.1 Stakeholders List (Actors)
A person that has an effect or concern to a system is known as a Stakeholder (Actor). Stakeholders can
affect or be affected by the system's actions and objectives. For examples stakeholders can be creditors,
directors, employees, government, owners, suppliers and admin.
Following are the stakeholders for this project:
 Admin Officer
 Librarian
 Cafeteria
 Bookshop Man
 Students
The system is mainly developed to provide facility to the students of the universities. We have
confidently achieved our set goals and provided students with feature packed smart card system
equipped with Library management system, inventory systems for Cafeteria and Book Shop, a Student
portal with set functionality and Cash transfer facility. Cards are generated and managed through
accounts office as well as the cash
1.10.2 Requirements elicitation
Requirement elicitation is the practice of collecting the requirements of a system from users, customers
and other stakeholders. The practice is also sometimes referred to as "requirement gathering".
For requirements elicitation we have visited to the university students and employees like the people
running cafeterias or bookshops as they are the part of this system

1.11 Requirements Analysis

1.11.1 Functional Requirements:
Student Smart Card is modernized ID card specifically designed for the ease of students, adding a
bunch of features and reducing the total number of items a student has to normally carry in his wallet.
FR1: 1 Card management and Cash Handling

Card generation and cash deposition work will be done in accounts department. Following things will
be done in this dept.
• Admin Login
• Card Generation
a) Add new card
b) View all
c) View Deactivated Cards
d) View Blocked Cards
• Card Amounts (cash)
• Payment Records
a) Cafeteria database (sales records)
b) Book Shop database (sales records)
• Fine Record
a) Add New Fine List
b) View All Fine Lists
• Settings
a) Change Password.
b) Log out
FR2: Library management

Student Smart Card is also integrated with a library management system to keep a record of books in
the central database. It is a web based Interface with back end and database present on the central
database.
Note: Admin password will be needed to log on to the library management system.
FR3: Usage as a Library Card

Students are able to use Student Smart Card as a fully functional library card. To get a book issued, a
student will have to hand over the book to librarian and scan the card by tapping it on the NFC device.
The system will automatically show the student’s book issuance record, either he has already lend 2
books (max limit for a student to lend books from a library will be 2 and the max time given for book

return will be 7 days, after that fine will be charged as Rs.20 per book per day), if the student is eligible
for book issuance, librarian will enter the ISBN number of the book and issue the book to the student.
FR4: Cafeteria and Book Shop inventory and Sales Record management
Cafeteria and book shop is provided with inventory system to keep a record of available items and sold
items with the ability to add or edit items whenever wanted. This is a web based interface with all the
back end and data located and directly fetched at central database.
Note: Admin password will be needed to log on to the Cafeteria/bookshop inventory and sales system.
FR5: Prepaid debit card for use in Cafeteria and Book shop
To use the Student Smart Card for buying stuff from cafeteria or book shop, shop owner will first add
the items on the buy list and the student will be asked to tap the card on the NFC device, “Enter PIN”
will be automatically prompted on the screen and student will be allowed to enter the secured PIN in
full privacy. After students confirmation order will be checked out and the dues will automatically be
deducted from student’s Smart card.
FR6: Hassle free fine payment

Fine payment is a process that almost every other student has to go through in order to be considered
eligible for examination. Research shows that many students get belated in appearing for examination
just because they had to pay the fines and get the roll no. slip. That being said many students
approaching the account office all at once can take a lot of time to process all the student fines and
providing roll no. slips manually. This is where Smart Card will come in handy. Student Smart Card
web portal is accessible to every card holder and provides an easy way to pay their fines by logging in
using their roll no. and a password.
FR7: Contactless transactions using NFC and RFID technology

Smart Card is a modern and much more functional of card technology using NFC/RFID cards and NFC
readers. These modern day NFC readers don’t even need a card to be tapped upon, instead they can
detect a card automatically whenever it comes to their proximity of 5cm. They can scan the card even
if it is being carried in a wallet etc.

FR8: Web Based System and Central Database

Student Smart Card is a web based interface to all the related areas of functionality, connected through
intranet and having all the data in a central database keeping it safe and secure from reach and
infiltration.
FR9: Sudent portal

Smart Card provide students with an online portal with the following facilities:
• Login
• Roll no.
• Password
• Card status (incl. remaining cash) and Transaction history.
• Fine payment
• Library fine
• Academic fine
• Settings
• Change portal password
• Change Card Pin
• Deactivate Card
• Log Out
.
1.12.2 Non-Functional Requirements
Non-functional requirements (NFR) provide guidelines on how to build a Web Based app correctly
(such requirements are also known as quality requirements or design requirements).
Following are the non-functional requirements of S cube
 Usability Requirements:
Student Smart Card Service is very easy to use system with not much guidance or orientation needed
to be done on the student’s (card user’s) side. However for accounts department, library management,
cafeteria and book shop management, a brief work shop will be conducted to make them familiar of the
system they are about to use. Student Smart Card Service is very easy to use and simplistic so it won’t
bother anyone using it because of any complexity issuer software should be failure free software .There
are no chances for errors to affect the system. We can use it on window 7, window 8, window 10.It has
time to repair depends upon the bugs condition.

 Efficiency Requirements:
Student Smart Card Service is an offline intranet based connected system so execution speed is
maximum. Being responsive on the user end and handling the database collectively on an offline
institute based server will increase efficiency and reduce the risk of failure to a major leap.
 Performance Requirements:
For optimum performance it will be advised to the institute to use well managed and networked system
for fastest possible data transfer.
 Space Requirements:
Student Smart Card Service is designed to be a storage efficient system by storing compressed images
and concise format of data, thus no huge amount of storage is needed for Student Smart Card to be
functional.
 Reliability Requirements:
As Student Smart Card Service is based upon a local server, thus chances of it crashing mainly depend
upon the maintenance and care of the network structure being used and the type of storage media used
in the server. Otherwise it will be assured that no crash occurs due to any software issue.
.
 Portability Requirements:
As Student Smart Card Service provide a web based interface to all the related areas of
functionality thus it is easily functional on any of the modern day PC operating systems.
1.13 Proposed System

1.13.1 Detailed description of proposed system
Our proposed system is appealing to us because we have gone through all these things which a
university student faces and which we are trying to improve through our Student Smart Card. We strive
to bring new and latest technologies to the ease of use for our fellow students and remove the gap

between just seeing new technology and actually implementing it in useful ways to help others. Our
goal is to set a new example of field work for our fellows and juniors to learn new things and make
what’s good even better. We don’t see this kind of stuff being implemented in abundance in our
surrounding educational institutes, that’s why we want to make it better implemented if not beginning
the whole concept. We want every student in our university and any other institute that will implement
Student Smart Card to feel the comfort of carrying just one card that will be their identity and be a
source to pay their little payments across the university premises. A more useful and intuitive system
with less to carry and less to worry about.
1.13.2 Features of proposed system
Following are the features of Student Smart Card Services (S3)
• We have introduced Basic inventory and billing system for cafeteria and book shop. We
made our database as central database and connected systems through intranet. Student Smart
Card offered one tap NFC card recognition secured with a PIN.
• We have provided a designated desktop web based application for each desired place.
• Students would have to pay Rs.1000 as a security fee for Student Smart Card this Rs.1000 is
used in case if the actual debited amount goes less than required amount to be transacted.
• After the security fee has been used, card will be blocked and will be functional after at least
the security fee is re debited.
• Admin panel have all the information regarding all the transactions made and all the sale record
of cafeteria and book shop as well as a complete record of library.
• Students using smartphones having NFC built in are able to tab their Student Smart card on
back of their devices which will automatically take them to a website link with a PIN input
prompt. After logging in using their pin, students are able to see their transaction record.
• A unique ID is also assigned to the Student Smart Card which is used to deactivate the card in
case of theft or getting lost.

• Student Smart Card is a prepaid and cash, debited through account office.
• Cafeteria and book shop sales record are also available at accounts office and they can collect
their sales cash as they like.
1.13.3 Advantages of proposed system
Following are the advantages of Digital Signage System:
• System is more efficient and reliable.
• It is low budget and affordable solution for students and other users.
• Students can pay their fine and dues online from their accounts.
• No worry about to keep cash in pocket for students.
• Useful for all kind of universities and colleges.
• Allows to perform Contactless Transactions.
• No need to issue a separate Library Card as Student Service Smart Card would have all the
Record in it and also use as an Identity.
• Being easy to manage huge amount of users (students or other users).
• Integrating the Databases as a Central Database.
• The main advantage of this project is that it has made Easiness for the Students.
1.13.4 Scope of proposed System
Student Smart Card Service offers its user with multiple functionalities with the ease of use. Student
these days have to carry a lot already with them such as their laptop, a bunch of books, their
assignments, useful notes and other things all in a heavy bag or in hand. Among with all these things
they also carry a wallet with them which has there CNIC card, student ID card, a library card and some
cash. Well, with Student Smart Card he has to carry just his CNIC and Student Smart Card with him. It
is useful across the university campus paying for cafeteria bills, book shop bills and library and also
help them pay the academic fine.

Chapter: 2
System Analysis
System Analysis Chapter 02
2.1 Software process model

Design is the first step in the development phase for any techniques and principles for the purpose of
defining a device, a process or system in sufficient detail to permit its physical realization.
Once the software requirements have been analyzed and specified the software design involves three
technical activities - design, coding, implementation and testing that are required to build and verify the
software.
The design activities are of main importance in this phase, because in this activity, decisions ultimately
affecting the success of the software implementation and its ease of maintenance are made. These
decisions have the final bearing upon reliability and maintainability of the system. Design is the only
way to accurately translate the customer’s requirements into finished software or a system.
Design is the place where quality is fostered in development. Software design is a process through
which requirements are translated into a representation of software. Software design is conducted in
two steps. Preliminary design is concerned with the transformation of requirements into data.
There are various kinds of methods in software design:
They are as follows:
• Use case Diagram
• Descriptive Use case
• Sequence Diagram
• Activity Diagram
In my system we are going to use iterative model for development process.
2.1.1 Iterative Model:

Iterative development is a way of breaking down the software development of a large application into
smaller chunks. In iterative development, feature code is designed, developed and tested in repeated
cycles. With each iteration, additional features can be designed, developed and tested until there is a
fully functional software application ready to be deployed to customers.
An iterative life cycle model does not attempt to start with a full specification of requirements. Instead,
development begins by specifying and implementing just part of the software, which can then be

System Analysis Chapter 02
reviewed in order to identify further requirements. This process is then repeated, producing a new
version of the software for each cycle of the model.
In the diagram above when we work iteratively we create rough product or product piece in one
iteration, then review it and improve it in next iteration and so on until it’s finished. As shown in the
image above, in the first iteration the whole painting is sketched roughly, then in the second iteration
colors are filled and in the third iteration finishing is done. Hence, in iterative model the whole product
is developed step by step.
Figure 2.1 Iterative Model

System Analysis
2.2 Iteration 1
2.2.1 Use Case
2.2.1.1 Accounts Department
Figure 2-2: Accounts Department

System Analysis
2.2.1.2 Students Portal
Figure 2-3: Student Portal

System Analysis
2.2.1.3 Library Management
Figure 2-4: Library Management
2.2.1.4 Café and Bookshop
Figure 2-5: Café and Bookshop

System Analysis
2.2.2 Detail Use Case
Figure 2-6: Cash Record

2.2.2.2 Card Record
Figure 2.6.1: Card Record

System Analysis
2.2.1.3 Fine Record
Figure 2.6.2: Fine Record

2.2.2.3 Payment Record
Figure 2.6.3: Payment Record

3
S -Student Smart Card Services
System Analysis
2.2.2.4 Settings
Figure 2.6.4: Settings
2.2.2.5 Items Record
Figure 2.6.5 Items Record

System Analysis
2.2.2.6 Make Order
Figure 2.6.6: Make Order
2.2.2.2 Library Management System
 2.2.3.1 Book Record
Figure 2.7 : Book Record

System Analysis
 2.2.3.2 Issue Book
Figure 2.7.1: Issue Book
 Settings

System Analysis
2.2.2.3 Student Portal
 Card Status
Figure 2.8.1: Card Status
 Transaction History
Figure 2.8.2 : Transaction History 6.2.4.3 Fine

System Analysis
 Payment
Figure 2.8.3 : Fine Payment

System Analysis
 Settings

System Analysis
2.2.3 Descriptive Use Case
Uc no 01
Uc Name Accounts Department
Description Player can select any service he would like to use from the list.
Actor Player(Admin Officer)
Pre-Condition To use these services player must be logged in
Success Guarantee A list of multiple services allows the user to select the desired field
and use it.
Main Scenario
(Action) Player make a choice of service from list.
Main Scenario
(Response) Select a Particular Service to use.
Special Requirement N/A
Frequency of Whenever player start this system.

Occurrence
Table 2.1 Accounts Department.
2.2.3.2 Cafeteria and Bookshop inventory System
Uc no 02
Uc Name Cafeteria & Book Shop Inventory System

System Analysis
Description Player can manage the cafeteria and book shop inventory system by
adding, deleting new items. Make order & Card Scan
Actor Player(Admin)
Pre-Condition To use these services player must be logged in.
Success Guarantee A Player can use any of the available options to continue operating
this system.
Main Scenario
(Action) Player can add, Delete new items, Make order & Check records
Main Scenario
(Response) Updation in inventory System
Frequency of Whenever player use the system and clicks on Cafeteria & Book
Occurrence Shop Inventory System.
Table 2.2 Cafeteria & Book Shop Inventory System
Uc no 03
Uc Name Student Portal
Description A Student can manage his/her account.
Actor Player(User)

System Analysis
Success Guarantee Player checks all of its account history & Status.
Main Scenario Player can pay fine, update password, check transaction history, and check
(Action) card status.
Main Scenario Managed Student Account & all the changes made.
(Response)
Frequency of Whenever player login and clicks on Student Portal

Occurrence
Table 2.3 Student Portal
Uc no 04
Uc Name Library Management
Description A complete management system for library having all details of

available & borrowed books, fine data, students records
Actor Player(Admin)
Success Guarantee Player can manage all the books, fine record and student record
according to the need.
Main Scenario
(Action) Player can pay add book, delete book, make a fine list of students,
view issued book, check scan cards.
Main Scenario
(Response) An issued book and a fine to student on late return of book.
Frequency of Whenever player login and clicks on Library Management

Occurrence
Table 2.4 Library Management.
3
System Analysis
2.2.4 Sequence Diagrams
Figure 2.9 : Accounts Department

System Analysis
2.2.4.2 Bookshop and Cafeteria
Figure 2.10: Bookshop and Cafeteria
2.4.3 Student
Figure 2.11: Student Portal

3
System Analysis
Figure 6-23: Library Management System

System Analysis
2.2.5 Activity Diagram
2.2.5.1 Login
Figure 2.12: Login

System Analysis
Figure 2.13: Accounts Department

System Analysis
2.2.5.3 Cafeteria and Bookshop
Figure 2.14: Cafeteria and Bookshop

System Analysis
Figure 2.15: Library Management

System Analysis

System Analysis
2.3 Iteration 2
In Iteration II we have done a lot of changes according to the test cases we have done through our
project. We have changed our design and many features, so here are the UML diagrams according to
new changes we made.
2.3.1 Use Case

Figure 2.17: Accounts Department

System Analysis

System Analysis
Figure 2.19: Library Management system

System Analysis
2.3.1.4 Bookshop Inventory System
Figure 2.20 Bookshop Inventory System

System Analysis
2.3.1.5 Cafeteria Management System
Figure 2.21: cafeteria management system

System Analysis
2.3.2 Detail Use Case
 Cash Record
Figure 2.22.1: Card Record

System Analysis
 Fine Record
Figure 2.22.2: Fine Record
 Payment Record
Figure 2.22.3: Payment Record

System Analysis
 Trash
Figure 2.22.4: Trash
 Settings

System Analysis
 Card Status
Figure 2.23.1: Card Status
 Check Pay Fine
Figure 2.23.2: Check Pay Fine


Figure 2.23.3: Payment History

3
System Analysis
 Cash Transfer
Figure 2.23.4: Cash Transfer
Figure 2.23.5 Setting

System Analysis

 Book Record
Figure 2.24.1: Book Record
Figure 2.24.2: Issue Book

System Analysis

Figure 2.24.3: Return Book
 Trash
Figure 2.24.4 : Trash

System Analysis
 Items Record
Figure 2.25.1: Items Record
 Trash
 Make Order
Figure 2-25.3: Make Order

3
System Analysis
 Sales Record
Figure 2-25.4: Sales Record
 Settings

System Analysis
2.3.2.5.Bookshop Inventory System
 Items Record
Figure 2.26.1 : Items Record
 Trash

 Make Order
Figure 2.26.3: Make Order

System Analysis
 Sales Record
Figure 2.26.4: Sales Record
 Settings

System Analysis
2.3.3 Descriptive Use Case
Table Accounts Department.
Uc no 01
Uc Name Accounts Department
Description Player can select any service he would like to use from the list.
Actor Player(Admin Officer)
Pre-Condition To use these services player must be logged in
Post Condition User can View Accounts Options
Success Guarantee A list of multiple services allows the user to select the desired field and
use it.
Main Scenario (Action)

Player make a choice of service from list.
Main Scenario
(Response) Select a Particular Service to use.
Frequency of Whenever player start this system.

Occurrence
Table 2.5

System Analysis
Table Cafeteria Management System.
Uc no 02
Uc Name Cafeteria Management System
Description Player can manage the cafeteria management system by adding, deleting
new items. Make order & Card Scan
Actor Player(Admin)
Post Condition The player views the inventory details.
Success Guarantee A Player can use any of the available options to continue operating this
system.

Player can add, Delete new items, Make order & Check records
Main Scenario
(Response) Updation in Management System
Frequency of Whenever player use the system and clicks on Cafeteria Management
Occurrence System.
Table 2.6

System Analysis
Table Student Portal
Uc no 03
Uc Name Student Portal
Description A Student can manage his/her account.
Actor Player(User)
Post Condition The player can use the services.
Success Guarantee Player checks all of its account history & Status.

Player can pay fine, update password, check transaction history, and
check card status.
Main Scenario
(Response) Managed Student Account & all the changes made.
Frequency of Whenever player login and clicks on Student Portal

Occurrence
Table 12.7

System Analysis
Table Library Management.
Uc no 04
Uc Name Library Management
Description A complete management system for library having all details of

available & borrowed books, fine data, students records
Actor Player(Admin)
Post Condition Player can view Library Options
Success Guarantee Player can manage all the books, fine record and student record
according to the need.
Player can pay add book, delete book, make a fine list of students, view
issued book, check scan cards.
Main Scenario
(Response) An issued book and a fine to student on late return of book.
Frequency of Whenever player login and clicks on Library Management

Occurrence
Table 2.8

System Analysis
Table Book Shop Inventory System.
Uc no 05
Uc Name Book Shop Inventory System
Description Player can manage the Book Shop inventory system by adding, deleting
new items. Make order & Card Scan
Actor Player(Admin)
Post Condition The player views the inventory details.
Success Guarantee A Player can use any of the available options to continue operating this
system.

Player can add, Delete new items, Make order & Check records
Main Scenario
(Response) Updation in inventory System
Frequency of Whenever player use the system and clicks on Book Shop Inventory
Occurrence System.
Table 2.9

System Analysis
2.3.4 Sequence Diagram

System Analysis
Figure 2.28: Bookshop Inventory System

System Analysis
Figure 2.30: Library Management System
Figure 2.31: Cafeteria Management System

System Analysis
2.3.5 Activity Diagram
2.3.5.1 Login
Figure 2.32: Login

\

System Analysis

System Analysis
2.3.5.3
Figure 2.34: Cafeteria Management System
2.3.5.4
Figure 2.36: Bookshop Inventory System

System Analysis
2.3.5.5
Figure 2.37: Library Management System
2.3.5.6

System Analysis
Chapter: 3
System Analysis

System Analysis
3.1 Design:
System design is that the method of shaping the weather of system like the design modules and parts
the various interfaces of these parts and also the information that goes through that system, it means
satisfy the precise desires and requirement of a business or organization through the engineering of a
coherent and well running system

System Analysis
3.2 ER Diagram

System Analysis
3.3 Class Diagram:

System Analysis
3.4 Design:
Figure 3.3 Design diagram

System Analysis
Chapter: 4
Implementation

Testing Chapter 05
4.1 Implementation of Iteration 1

In the first iteration we have successfully achieved the following phases of the project
 Front End Design using HTML & CSS

The frontend of an application is distinctly human. It’s what the user sees, touches and experiences.
The frontend of an application is less about code and more about how a user will interpret the interface
into an experience.
• The overall Programming languages involved in designing the front end is HTML, CSS &
JAVA SCRIPT.
• HTML is the language for describing the structure of Web pages. HTML gives authors the
means to:
• Publish online documents with headings, text, tables, lists, photos, etc.
Retrieve online information via hypertext links, at the click of a button.

Design forms for conducting transactions with remote services, for use in searching for information,
making reservations, ordering products, etc.
Include spread-sheets, video clips, sound clips, and other applications directly in their documents.
• With HTML, authors describe the structure of pages using markup. The elements of the
language label pieces of content such as “paragraph,” “list,” “table,” and so on. On the other
hand CSS is the language for describing the presentation of Web pages, including colors,
layout, and fonts. It allows one to adapt the presentation to different types of devices, such as
large screens, small screens, or printers.
• CSS is independent of HTML and can be used with any XML-based markup language. The
separation of HTML from CSS makes it easier to maintain sites, share style sheets across pages,
and tailor pages to different environments.
 Back End Development Using PHP

The programming language which we have used for our backend development is PHP.
We have almost completed 60% of our back end development using PHP. We have used SQL for
database.
In order to make the server, application, and database communicate with each other we used the server-
side language PHP to build our project, and used SQL Server to find, save, or change data and serve it
Digital Signage System 97

Testing Chapter 05
back to the user in frontend.
 Technology for Hardware Integration

We have used JAVA for hardware integration with our project.
 Modules
We have developed only one module up till now and it is Accounts Department. Every part of it
performing well and we have gone through testing on them we found some expected results too.
4.2 Implementation of Iteration 2

In the II iteration we have successfully achieved the following phases of the project.
 NFC ACR 122U

We have used a hardware NFC ACR 122U, which is a PC-linked contactless smart card reader/writer.
Its connectivity is through java applet to the web server. It has the proximity of 50 mm to detect the
card.
• NFC stands for Near Field Communication. The tech involved is deceptively simple. Evolved
from radio frequency identification (RFID) tech, an NFC chip operates as one part of a
wireless link. Once it's activated by another chip, small amounts of data between the two
devices can be transferred when held a few centimeters from each other.
• NFC has been getting more attention by the media after becoming a technology for mobile
payments and creative marketing. Most of the recent mobile devices support NFC, but most
people don’t really know about or use it. Most people still think that NFC is only used for data
transfer. That is not true!
• There is more fun and practical stuff you can do with NFC: using NFC tags! And that’s what S
cube is all about. We’ve extended the mainstream ideology associated with NFC with the use
of NFC tags in S cube.

Testing Chapter 05
 Changes to front end design

We have adopt a little change to the frontend for the better user interface. As the friendly user interface
counts a lot in any of your project/software success so we have make it friendlier and easy to use which
it wasn’t before.
 Modules
We have successfully completed all of our modules which we described in the beginning. Accounts
Department, Library Management System, Cafeteria Management System, Student Portal, and
Bookshop Inventory System all these modules are working fine
4.3 Tools and Technologies
4.3.1 Software
PHP, HTML, CSS, Java Script, MySQL
 PHP
• PHP is a server scripting language, and a powerful tool for making dynamic and interactive
web pages.
• PHP is a widely-used, free and efficient alternative to competitors such as Microsoft’s ASP.
 HTML
• HTML is the standard markup language for creating Web pages.
• HTML stands for Hyper Text Markup Language
• HTML describes the structure of Web pages using markup
• HTML elements are the building blocks of HTML pages
• HTML elements are represented by tags
• HTML tags label pieces of content such as "heading", "paragraph", "table", and so on Browsers
do not display the HTML tags, but use them to render the content of the page
 CSS
CSS is a style language that defines layout of HTML documents. For example, CSS covers fonts,

Testing Chapter 05
colors, margins, lines, height, width, background images, advanced positions and many other things.
Just wait and see!
HTML can be miss used to add layout to websites. But CSS offers more options and is more accurate
and sophisticated. CSS is supported by all browsers today.
 JAVASCRIPT:
JavaScript is a cross-platform, object-oriented scripting language. It is a small and lightweight
language. Inside a host environment (for example, a web browser), JavaScript can be connected to the
objects of its environment to provide programmatic control over them. JavaScript contains a standard
library of objects, such as Array, Date, and Math, and a core set of language elements such as
operators, control structures, and statements. Core JavaScript can be extended for a variety of purposes
by supplementing it with additional objects; for example:
• Client-side JavaScript extends the core language by supplying objects to control a browser and
it’s Document Object Model (DOM). For example, client-side extensions allow an application
to place elements on an HTML form and respond to user events such as mouse clicks, form
input, and page navigation.
• Server-side JavaScript extends the core language by supplying objects relevant to running
JavaScript on a server. For example, server-side extensions allow an application to
communicate with a database, provide continuity of information from one invocation to another
of the application, or perform file manipulations on a server.
 MySQL:
MySQL is an open source relational database management system (RDBMS) based on Structured
Query Language (SQL). MySQL runs on virtually all platforms, including Linux, UNIX, and
Windows. Although it can be used in a wide range of applications, MySQL is most often associated
with web-based applications and online publishing and is an important component of an open source
enterprise stack called LAMP. LAMP is a Web development platform that uses Linux as the operating
system, Apache as the Web server, and MySQL as the relational database management system and
PHP as the object-oriented scripting language.
4.3.2 Hardware

Testing Chapter 05
NFC card Reader & Writer

The ACR122U NFC Reader is a PC-linked contactless smart card reader/writer developed based on
13.56 MHz Contactless (RFID) Technology.
• USB 2.0 Full Speed Interface
• Read/write speed up to 424 kbps
• Built-in antenna for contactless tag access, with card reading distance of up to 50 mm
(depending on tag type
• Built-in anti-collision feature (only 1 tag is accessed at any time)
 NFC and How does it work
• NFC stands for Near Field Communication. The tech involved is deceptively simple. Evolved
from radio frequency identification (RFID) tech, an NFC chip operates as one part of a wireless
link. Once it's activated by another chip, small amounts of data between the two devices can be
transferred when held a few centimeters from each other.
• NFC has been getting more attention by the media after becoming a technology for mobile
payments and creative marketing. Most of the recent mobile devices support NFC, but most
people don’t really know about or use it. Most people still think that NFC is only used for data
transfer. That is not true!
• There is more fun and practical stuff you can do with NFC: using NFC tags! And that’s what S
cube is all about. We’ve extended the mainstream ideology associated with NFC with the use of
NFC tags in S cube.
ACR122U USB NFC READER
• The ACR122U NFC Reader is a PC-linked contactless smart card reader/writer developed
based on 13.56 MHz Contactless (RFID) Technology.
• It is a plug-and-play USB device allowing interoperability with different devices and

Testing Chapter 05
applications. With an access speed of up to 424 kbps and a full USB speed of up to 12 Mbps,
ACR122U can also read and write more quickly and efficiently.
• The proximity operating distance of ACR122U is up to 5 cm, depending on the type of

contactless tag in use. The ACR122U comes with an optional stand to hold the smart card
reader at an optimal angle, so that users can tap contactless cards or NFCenabled devices onto
the ACR122U with ease.
 Specification
Figure 4-1:
4.4 Platform selection

We have selected PHP Classic as a platform for my project development. PHP is a server-side scripting
language which offers amazing versatility while developing dynamic websites. The beauty of PHPis

Testing Chapter 05
that despite being an open-source development platform, it offers a plethora of functionalities and
benefits like a paid scripting language would. Web- designing done using PHP guarantees a robust and
durable website structure which is capable of handling mass-traffic. Although, the requirement for
using PHP is that a user needs to have a grip on programming languages, which makes it selectively
accessible to developers only.
4.5 System development

It is a conceptual model used in project management that describes the stages involved in an
information system development project. There are a number of Software Development Life Cycle
Models, each having its strengths and weaknesses and suitable in different situations and project types.
A typical SDLC consist of the following stages including: Stages of SDLC:
• Plan
• Design
• Develop
• Deploy
• Maintenance
Figure 4.1 System Development

Testing Chapter 05
4.5.1 Plan
• Functional Requirements
• Initial User Interface
• Technology Platform Selection
• Technical Architecture
• Project Plan
4.5.2 Design
• Details Specifications
• Finalized User Interface
• Application Architecture
• System Interface Design
• Test Plans
4.5.3 Develop
• Application Code Development
• System Interface Development
• Integration with Existing Applications
• Unit and Integration Testing
4.5.4 Deploy
• System Testing
• User Acceptance Testing
• Installation on Staging Environment
4.5.5 Maintenance
• Installation on Production
• Production Testing
• Transition on Operations
• Post Development Support
• Bugs Check
• On-going Maintenance

Testing Chapter 05
Chapter 5
Testing

Testing Chapter 05
5.1 Testing and Results

Iteration 1
Software testing is necessary for a project. Testing is made so as to evaluate and get the result for
developed software. Software testing is made is controlled form with all normality’s and abnormalities
deals with the system.
In this project up till now we have faced several issues and have done test on them but didn’t get the
expected result. Here are the test cases which didn’t give us the expected results other than these all the
functions were working up to the mark.
Following are the test cases which we have done for this project and the output we got.
Test No Test case Expected Result Actual Result Pass/F

ail
1. Accounts Department The system shouldn’t It was accepting Fail
Acceptance of Integers have to accept these input the integers and
/Strings from the user from users. strings input.
input.
2. Input of Negative values The system should not It was Fail

in the Fathers name field accept the negative value. accepting the
in accounts department. negative value.
3. Input of Negative values The system should not Same as Pass
in the Student name accept the negative value. expected.
field in accounts
department.
4. Burn Cards. The hardware should burn It wasn’t Fail
Cards. burning cards.
5. Make order in inventory The system should It was not Fail
system calculate price calculate the price against calculating
against the quantity of the quantity. according to the
items. scenario.
6. In burning a card only Every card should have its The cards didn’t Fail
one id should burn unique id. have unique id.
against one card.
7. Change of password It shouldn’t have to accept It was Fail
single space. accepting a
single space.

Testing Chapter 05
8. Status of Student Card The card should show the It was not Fail
current status whether the showing any
card is active or deactivate
status
9. Cash transfer The system should notify It wasn’t notify Fail
notification the transfer amount. anything in the
statement
10. Issuing of book System should issue only 2 It was issuing Fail
books at same time more than 2
books
Table 5.1
5.2 Testing and Results

Iterationn 2
Software testing is necessary for a project. Testing is made so as to evaluate and get the result for
developed software. Software testing is made is controlled form with all normality’s and abnormalities
deals with the system.
In this project the issues we faced in the beginning has overcome by us and have done test on them, got
the expected results now. Other than these all the functions were working properly. Following are the
test cases which we have done for this project and the output we got.
Test No Test case Expected Result Actual Result Pass/Fail
1. Accounts Department The system shouldn’t

Acceptance of Integers have to accept these input Same as
/Strings from the user from users. Expected Pass
input.
2. Input of Negative values The system should not It wasn’t

in the Fathers name accept the negative value. accepting the Pass
field in accounts negative value.
department.
3. Burn Cards. The hardware Burns the card Pass
should burn as expected
Cards.

Testing Chapter 05
4. Make order in inventory The system should

system calculate price calculate the price against Same as Pass
against the quantity of the quantity. Expected
items.
5. In burning a card only Every card should have its Cards have the
one id should burn unique id. actual unique id. Pass
against one card.
6. Change of password It shouldn’t It was working Pass
have to accept properly.
single space.
7. Status of Student Card The card should show the It showed the Pass
current status whether the status
card is active or
deactivate
8. Cash transfer The system should notify Same as Pass
notification the transfer amount. Expected
9. Issuing of book System should issue only Same as Pass
2 books at same time Expected
Table 5.3
5.3 Gantt chart

5.3.1 Iteration-I Gantt chart
Table 5.3
5.3.2 Iteration-II Gantt chart
Table 5.4

Chapter 6
Conclusion
Conclusion Chapter 06
6.1 Conclusion and future work

We started working on this project keeping some specific requirements in our mind. We have
confidently achieved our set goals and provided students with feature packed smart card system
equipped with Library management system, inventory systems for Cafeteria and Book Shop, a Student
portal with set functionality and Cash transfer facility. Cards are generated and managed through
accounts office as well as the cash. Keeping in mind the simplicity of a University card, we have
extended its usability and provided extra functionality with it.
• We have some future related ideas to do some work on this project in future.
• Here are some features which we can add in the future.
• Face Recognition : For Secured Entrance and Attendance
• Extended Student Portal : Chat Box with file sharing and ability to block other students
• Parking : Automated spot allocation vehicle parking
• Affiliated Banking : Cash deposit through Bank account
6.2 User Guide

6.2.1 User Guide

6.3 References
1. Wu Hairong.Design of Campus Smart Card System[J].Journal of Ningxia University:Natural
Science Edition,2002,23(4):346-349.
2. Qiu Shuwei. Design and Implementation of Campus Card System Construction [J]. Journal of
Hunan University of Technology, 2010， 24(4):61-64.
3. Xu Wenshuan,Xin Yunwei.Design and Implementation of Middle Ware-Based E-Card System for

Campus[J].Computer Engineering and Design,2007,28(7):1723-1726.
4. Zhou Yilu,Zhong Jian,Pu Xun.A Frame Work of Campus-Grid Service Based on Bank
a. Card[J].Journal of Southwest University:NaturalScienceEdition,2007,29(3):160-163
5. Liu Dongming. The Design and Implementation of Campus Smart Card System in Hangzhou
Academy of Scientific Professional Technology[D]. Shanghai:East China Normal
University,2009:15
6. HU Rong.Construction and Practice of Campus One Card[J]. Research and Exploration in

Laboratory, 2012,31(7):404-405.
7. M. Hendry,\Smart Card Security and Applications, "Artech House, Inc., 1997.
8. Riya Lodhaa, Suruchi Guptaa, Harshil Jaina, Harish Narulaa,\Bluetooth Smart based Attendance
Management System. "Procedia Computer Science 45 ( 2015 ) 524 527.
9. What’s so smart about smart cards? Available at www.gemplus.com [2/12/02]
10. Smart Card Technology: Past, Present, and Future L. A Mohammed, Abdul Rahman Ramli, V.
Prakash, and Mohamed B. Daud* Department of Computer and Communication Systems
Engineering *Department of Biology and Agricultural Engineering 43400, UPM Serdang Selangor,
Malaysia.
11. M. Villano, “Campus cards: Too smart for their own good,” University Business, March 2004,
http://universitybusiness.ccsct.com/page.cfm?p=475.
12. M. Arami, M. Koller, and R. Krimmer, “User Acceptance of Multifunctional Smart Cards,” The
European Conference on Information Systems, Paper 18, 2004.
13. A. A. Mirza, and K. Alghathbar, “Acceptance and Applications of Smart Cards Technology in
University Settings,” Eighth IEEE International Conference on Dependable, Autonomic and Secure
Computing, pp. 746-748, 2009.
14. J. K. Lee, and C. Y. Yang, “Evolutionary Business Models of E-Cash with Smart Cards,” in
Proceedings of the International Conference on Electronic Commerce, Seoul, Korea, 2000.

15. [15]. Quisquater J-J. (1997), The adolescence of smart card, Future Generation Computer
Systems,

126 Updated

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

126 Updated

Uploaded by

Copyright:

Available Formats

S3-Student Smart Card Services

Department of Computer Science & Software Engineering

Faculty of Basic and Applied Science

International Islamic University Islamabad

Haroon Shabbir (29/FBAS/BSIT4/F15)

Usman Ali (30/FBAS/BSIT4/F15)

Objective: Objective of this project is to create an integrated

Undertaken By: Haroon Shabbir (29/FBAS/BSIT4/F15)

Date Started: May-2019

Date Completed: November-2019

Technology: PHP Classic, HTML, CSS, Java Script, jQuery, MY SQL

FINAL APPROVAL .................................................................................................................................. 2

Project in brief ............................................................................................................................................ 8

Table of Contents ..................................................................................................................................... 10

List of Figures .......................................................................................................................................... 14

1.2 Objective ............................................................................................................................... 17

1.3 Problem Statement ................................................................................................................ 17

1.4 Project Scope ........................................................................................................................ 18

1.5 Definitions, Acronyms, and Abbreviations .......................................................................... 18

1.6 Features ................................................................................................................................. 18

1.7 Literature Review ....................................................................................................................... 19

1.7.1 History ......................................................................................................................... 19

1.7.2 Design .......................................................................................................................... 21

1.7.3 Applications ................................................................................................................. 23

1.7.4 History of Smart Cards ............................................................................................... 29

1.8 Proposed system ......................................................................................................................... 30

1.9 Need to replace the existing system............................................................................................ 30

1.10 Understanding the proposed system ..................................................................................... 31

1.11 Requirements Analysis ......................................................................................................... 32

1.12.2 Non-Functional Requirements............................................................................................... 34

1.13 Proposed System ...................................................................................................................... 35

System Analysis ....................................................................................................................................... 38

2.1 Software process model ........................................................................................................ 39

2.2 Iteration 1 ................................................................................................................................... 41

2.3 Iteration 2 ................................................................................................................................... 63

System Analysis ....................................................................................................................................... 91

3.2 ER Diagram ................................................................................................................................ 93

3.3 Class Diagram: ........................................................................................................................... 94

4.1 Implementation of Iteration 1 ..................................................................................................... 97

4.2 Implementation of Iteration 2 ..................................................................................................... 98

4.3 Tools and Technologies ........................................................................................................ 99

4.3.2 Hardware.................................................................................................................... 100

4.4 Platform selection ............................................................................................................... 102

4.5 System development ........................................................................................................... 103

Chapter 5 ................................................................................................................................................ 105

Testing .................................................................................................................................................... 105

5.1 Testing and Results .................................................................................................................. 106

Iteration 1 ............................................................................................................................ 106

5.2 Testing and Results .................................................................................................................. 107

5.3 Gantt chart ................................................................................................................................ 108

Chapter 6 ................................................................................................................................................ 109

Conclusion .............................................................................................................................................. 109

6.1 Conclusion and future work ..................................................................................................... 110

6.2 User Guide ................................................................................................................................ 110

6.2.1 User Guide ................................................................................................................. 110

6.3 References..................................................................................................................... 111

Table 2.1 Accounts Department Use Case Description ..................................................................52

Figure 2.1 Iterative Model ................................................................................................ 40

Figure 2.30 Library System Sequence Diagram ............................................................... 86

1.3 Problem Statement

S3-Student Smart Card Services 17

1.4 Project Scope

1.5 Definitions, Acronyms, and Abbreviations