Final Year Project Software B

Requirement Specification y
For
Student Smart card
Bachelor of Science in Computer Science
S# Registration #/Roll #/Section Mobile # E-Mail
Name

1. Waseem Shakir FA-17-BSCS-175 0349-2651302 [email protected]

2. Gul Mahmood-Ul-Haq FA-17-BSCS-054 0300-7788039 [email protected]

Supervised by:
Mam Maria Tariq (Signature)

Department of Computer Science

Lahore Garrison University
Lahore
 Table of Contents

1. Introduction......................................................................................................Page#
1.1 Purpose ........................................................................................................................
1.2 Document Conventions ................................................................................................
1.3 Intended Audience and Reading Suggestions ..............................................................
1.4 Product Scope ..............................................................................................................
2. Overall Description ...............................................................................................
2.1 Product Perspective......................................................................................................
2.2 Product Functions ......................................................................................................
2.3 User Classes and Characteristics ...............................................................................
2.4 Operating Environment ..............................................................................................
2.5 Design and Implementation Constraints ....................................................................
2.6 User Documentation ..................................................................................................
2.7 Assumptions and Dependencies ................................................................................
3. External Interface Requirements .......................................................................
3.1 User Interfaces ...........................................................................................................
3.2 Hardware Interfaces ...................................................................................................
3.3 Software Interfaces ....................................................................................................
3.4 Communications Interfaces .......................................................................................
4. System Features ..................................................................................................
4.1 System Feature 1 ........................................................................................................
4.2 System Feature 2 (and so on) .....................................................................................
5. Other Nonfunctional Requirements ...................................................................
5.1 Performance Requirements ........................................................................................
5.2 Safety Requirements ..................................................................................................
5.3 Security Requirements ...............................................................................................
5.4 Software Quality Attributes .......................................................................................
5.5 Business Rules ...........................................................................................................
References ....................................................................................................................
 1. Introduction
1.1 Purpose
This document is designed to give full functional report on the requirements of the software its name
is Student smart card. The SRS document details all features upon which student smart card have
currently decided with reference to the manner and importance of their implementation. Student will
able to manage all activities by scanning card to the reader. From this document the user, developers
and engineers will be able to understand the features and functionalities of the software. By the end of
this project, complete working software will be available to users.
1.2 Document Conventions
As the development team is responsible for the SRS document, no ambiguity arises from its usage.
This document is too printed on A4 paper in Times New Roman font. Normal text is size 12 black,
while section headings are size 24 bolded Black. Subheadings are bolded size 14 black and third
subheadings are bolded size 13 black. Bold face is used for main headings and bullet points are used
to introduce a new topic or a specific subject matter. The document is written in Times New Roman.
The color of all the headings and paragraphs would be black.
1.3 Intended Audience and Reading Suggestions
This document advised to users and developers as:
 Developers shall be referred to this document in order to understand the online tools used,
performance, functionalities and processes in the software.
 User shall be referred to this document in order to observe what the software is intended to
provide in term of features, functions through user interface
The document is intended for such as developers, project managers, marketing staff, users and testers.
The rest of SRS document contains product functions, user classes and characteristics, operating
environment, design and implementation hardware and software interfaces. Moreover, it contains
functional and non-functional requirements

1.4 Product Scope

The scope of the project is to implement the system of smart card in all the institutes for purpose of
recognition and security. Student faces so many difficulties to manage their activities.it will help the
student to reduce the burden and save their time. The basic purpose to bring all management related to
the student in one platform. There are no of students and smart card will able to manage their entrance,
fine collection, book issued from library and proxy of attendance. All the data related to the student
stored on the card and this will become one key to open all the door.
2 Overall Description
2.1 Product Perspective
While this software itself is not a continuation of any predecessor or not a part of any other software.
Its implementation is made possible through the code using different languages for front end interface
and back end. Its application is made by the help of android studio. Cloud is used for hosting this
system. Which make it secure because cloud servers are highly secure. There are many different
software in the market for library or attendance but our goal is to take all things on one place in a one
system including fine charges etc. students and administration can easily handle everything with one
tool. Which must be simple to understand and use bhut effective.

Product Functions
The following is a summary of the major features implemented in the system.
1. Allow students to enter in University
2. Allow students from exit in University
3. Check the proxy
 4. Issue and return books in library
5. Pay fine from student account
6. Show student profile
7. Show transaction history

1.4 User Classes and Characteristics

This is a private system of an institute which can only be used by institutional members which
includes Admin, office, librarian and student. Admin can add new students he must have student’s
data, office person can charge fine he must know how much need to be charge for specific reason,
Librarian can issue and return books librarian must have library data and the students who must have
knowledge how to use student smart card and its application.

1.5 Operating Environment

This student smart card system has three parts.

1. Entrance scanner:
Scanner at entrance and exit must be connected with internet for cross checking the
information from cloud server.
2. Web view:
It is a web-based system which can be operate from any computer which have internet
connection. The computer must have input devices. Which include mouse, keyboard and a
scanner for scanning smart card.
3. Mobile application:
It will be an android application for smart phones. A smart phone must have an internet for
running this application. It will support android 8.0-8.1 (Oreo) and above.
1.6 Design and Implementation Constraints
The major constraints in design department for the development team will be to design environment in
such a way that the user can easily understand and operate the system without any specific training.
The second thing was about speed of storing and fetching data from server. The third and the most
important issue was the security because this system just not transferring data but also making
transactions which must be highly secure. The system requirements were also need to be under
consideration for this system we required a fast internet at every place specially at the entrance and
exit place to reduce traffic.
2.6 User Documentation
The system will come equipped with a separate instruction section bar in which the user when first
start the system if wanting can go to the instruction section bar in order to learn the mechanics so
that in their first time the user don’t get confused.
2.7 Assumptions and Dependencies
This system required internet to work

3. External Interface Requirements

3.1 User Interfaces
User interface is divided into two parts one for the students and second for the administration

Home screen:
The first viewable screen upon starting up the application, containing multiple options for login.

Admin Login:
Admin can login by its user name and password. Admin can see following options.
  Add new students
 Add balance in student’s account
 Add documents to student’s profile
 View student’s profile
 Change password
 Logout

Office Login
Office can login by its user name and password. He can see following options.

 New transaction (charge fine)

 View transaction history
 View students’ profile
 Change password
 Logout
Library Login
Librarian can login by its user name and password. He can see following options.

 Issue books
 Return books
 New transaction (charge fine)
 View transaction history
 View students’ profile
 Change password
 Logout

Student Login
Student can view following options in their interface on web and also on mobile application
 View his profile/documents
 Transaction history
 Library books issued details
 Account Balance

3.2 Hardware Interfaces

This smart card system will on work on that computer which have internet and input devices like mouse,
keyboard and specially scanner to scan the card. It required a scanner with internet at entrance. This
scanner has system to scan the card and after computation allow student to enter in institute.
3.3 Software Interfaces
Since this software is developed for computer and mobile as well, a computer’s operating system must be
windows 7 or above and mobile android version must be 8.0-8.1 (Oreo) or above.
Android studio is used for creating user interface of applic ation
3.4Communications Interfaces
The software will get data from smart card with the help of scanner. This system in
online but there is no communication between students and staff through software or application.

4. System Features

4.1 Website Features

 Website will allow to students and administration to login and perform their respective task. Home page
will ask to choose their Status and ask to login according to that.
Admin can add new students, add balance in student’s account, add documents to student’s profile,
view student’s profile and logout.
Office can make new transactions and charge fine from students account, view students’ profile, view
transaction history, change password and logout.
Librarian can issue books, return books, charge library fine from student’s account, change password
and logout.
Student can view their profile, their documents and can download them any time anywhere. Students
can view their balance, fine history, issue books details.

4.1 Application Features

Application is design for students thorough which they view their profile details and
transaction history, keep an eye on balance, they can top up their account by admin, they can see
and download their documents. They can watch their library history and due date of issued books.
They get notification before due date to avoid get charged for late return.
4.1.1 Entrance/Exit Scanner
Students will scan their smart card at the time of entering in institute the scanner will verify
student’s data and only students can enter in institute. Students also scan card at exit. Attendance
can only me marked present if student scan card at entrance scanner. Which make sure that student
is in university.

5. Other Nonfunctional Requirements

5.1. Performance Requirements
For any software development, we must need to build and design the software capabilities
for a better work. The most important thing is we can be managed a system regularly
and updating the system at the time. One of the most important requirements is the
finding and removing the bugs that are installed whenever we updating the system.
5.2. Safety Requirements
Safety information’s are highly important the application and software will not affect
the hardware like overheating. User side is also saved. The software and application
will also not cause any overheating of the user’s phone; therefore, the user's internal
components will not be damaged
5.3. Security Requirements.
Student smart card contain personal information and security concerns are highly
important that’s why its not a web bases that can accessed easily.it will use separate
server of the organization. We also using the passive smart card it will activated only
by the reader.
5.4. Software Quality Attributes.

To ensure reliability and correctness, software will respond to the user’s commands in a
timely manner. If the student wants to check he record of its activities software
produces the result effectively. For adaptability and flexibility, Software will
automatically save the student progress after every Scanning.

5.5. Business Rules

The software will be working on the principles of android operating systems as well as
on the systems, will be used by different no of individuals and will have different roles
of them. This software is more effectively usable among organizations who faces data
transfer issues; this software will provide both facilities in a platform. For commercial
and public use, any platform can purchase it from us
References

WWW.GOOGLE.COM
WWW.YOUTUBE.COM
WWW.PYTHON.ORG
WWW.SLIDESHARE.COM