Smart fees payment , event notification andv examination result system

A Thesis Submitted By

RAJESH KUMAR 2K10/CSE/60

SUPERVISOR

DR. HYDER ALI NIZAMANI

CERTIFICATE

This is to certify that Mr. Rajesh Kumar has carried out Project

entitled “SMART FESS PAYMENT AND EVENT NOTIFICATION

SYSTEM” during the academic year 2013, under the supervision of

DR. HYDER ALI NIZAMANI in partial fulfillment for the degree of BS (Computer Science).

SMART FEES PAYMENT AND EVENT NOTIFICATION SYSTEM 0

ACKNOWLEDGMENT

I take this opportunity to express my deepest gratitude and appreciation to all those

people who made this project work easier with words of encouragement, motivation and

helped me towards the successful completion of this project work.

First I would like to express my sincere gratitude to my Project Guide and Professor,

Department of Computer Science, Dr.Hyder Ali Nizamani for his insightful advice,

motivating suggestions, invaluable guidance, help and lots of moral support in successful

completion of this Project and also for his constant encouragement and advice throughout

my B.S. (Computer Science) programme.

I would like to thank all other teaching staff for their valuable teaching and constant

advice which made me to finish this program successfully.

Finally my deepest gratitude goes to my parents who have given me much needed

comfort, support, encouragement and inspiration for completing this project.


COPYRIGHT

I, hereby authorize University of Sindh, Jamshoro to supply of my thesis to libraries or

individuals for study purposes. However, no part of this thesis or the information

contained therein may be included in a publication or referred to in a publication without

the prior written permission of the authors. Any reference must be fully acknowledged.

Rajesh Kumar


DECLARATION

This thesis is my original work and has not been submitted, in whole or in part, for a

degree at this or any other university. Nor does it contain, to the best of my knowledge

and belief, any material published or written by another person, except as

acknowledgment in the text.

Rajesh Kumar


CONTENTS

1. INTRODUCTION.................................................................................................... 6

1.1 OVERVIEW......................................................................................................... 61.2 BACKGROUND....................................................................................................... 61.3 FEATURES............................................................................................................. 7

1.3.1 Fee payment system...............................................................................................71.3.2 Event Notification..................................................................................................71.3.3 Information or update regarding the academic results or certificate issuance...........8

1.4 CONCLUSION......................................................................................................... 8

2. BACKGROUND................................................................................................. 9

2.1 USE CASE.............................................................................................................. 92.1.1 Example Use Case: Obtaining Verified Challan....................................................102.1.2 Entity type...........................................................................................................112.1.3 ERD Development Process..................................................................................112.1.4 Relationship.........................................................................................................112.1.5 Key Attributes.....................................................................................................122.1.6 Key Definitions....................................................................................................12

2.2 CLASS DIAGRAM................................................................................................. 122.2.1 Association..........................................................................................................122.2.2 Aggregation.........................................................................................................132.2.3 Composition........................................................................................................132.2.4 Attribute..............................................................................................................13

2.3 ACTIVITY............................................................................................................ 132.4 BROADCAST RECEIVER........................................................................................ 14

2.4.1 Service.................................................................................................................142.4.2 Content Provider..................................................................................................14

2.5 TOOLS AND TECHNOLOGIES................................................................................142.5.1 System Interface..................................................................................................142.5.2 User Interfaces.....................................................................................................152.5.3 Hardware Requirements.......................................................................................152.5.4 Software Requirements........................................................................................152.5.5 Communications Interfaces..................................................................................162.5.6 Installition Requirements.....................................................................................16

2.6 PRODUCT FUNCTIONS.......................................................................................... 172.7 CONSTRAINT....................................................................................................... 172.8 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS................................................17

3. PROBLEM DESCRIPTION............................................................................18

3.1 FEES PAYMENT USE CASE REPORT....................................................................183.1.1 Obtaining Verified Challan..................................................................................18


3.1.2 Electronic Fees Payment System..........................................................................193.1.3 Issue scratch card.................................................................................................20

3.2 EVENT NOTIFICATION USE CASE REPORT..........................................................213.2.1 Event Notification................................................................................................213.2.2 Detail Event Notification.....................................................................................223.2.3 Detail Event Notification.....................................................................................23

3.3 INFORMATION OF RESULTS USE CASE REPORT...................................................243.4 ACTIVITY DIAGRAM FOR SENDING SMS.............................................................25

4. DESIGN AND IMPLEMENTATION.........................................................................26

4.1 ARCHITECTURE DIAGRAM...................................................................................264.2 CLASS DIAGRAM FOR FEES PAYMENT................................................................274.3 CLASS DIAGRAM FOR EXAM RESULT AND EVENT NOTIFICATION.......................284.4 ER DIAGRAM FOR EXAM RESULT AND EVENT NOTIFICATION...........................294.5 USER INTERFACES FOR PAYING ADMISSION FEES AND EXAM FEES...................30

4.5.1 Paying Admission Fees and Exam Fees................................................................304.5.2 Response For Paying Admission Fees and Exam Fees..........................................314.5.3 Response For Paying Certificates Or Degree Fees................................................324.5.4 Response For Paying Certrificate or Degree Fees................................................33

4.6 USER INTERFACE FOR EXAM RESULT INFORMATION..........................................344.6.1 Exam Result Information.....................................................................................344.6.2 Response Of Exam Result....................................................................................35

4.7 USER INTERFACE FOR ADMISSION RESULT INFORMATION..................................364.7.1 Admission Result Information..............................................................................364.7.2 Response Of Admission Result Information.........................................................37

4.8 USER INTERFACE FOR EVENT NOTIFICATION ANDROID APPLICATION:................384.8.1 Event Notification Login Form............................................................................384.8.2 Event Notification Select Program.......................................................................394.8.3 Event Notification Select Batch............................................................................404.8.4 Send Event Notification.......................................................................................414.8.5 Response Of Event Notification...........................................................................42

4.9 USER INTERFACE FOR EXAMINATION RESULT WEBISTE......................................434.9.1 Main Tittle Page..................................................................................................434.9.2 Semester results SMS service...............................................................................444.9.3 Annually Result Announcement...........................................................................454.9.4 Response of Result Announcemnt........................................................................464.9.5 Result Annoucement Sheet...................................................................................474.9.6 Academic Transcript /Marksheet..........................................................................484.9.7 Response Of Acdemic Trancript/Marksheet..........................................................494.9.8 Acadamic Positions..............................................................................................504.9.9 List Of Acadamic Positions..................................................................................514.9.10 Annaully list of sucessful or passed out students..................................................524.9.11 Response of sucessful candidates.........................................................................534.9.12 Course Scheme....................................................................................................544.9.13 Response of Course Scheme.................................................................................554.9.14 Comments and Complains...................................................................................56


4.10 SOFTWARE INTERFACES......................................................................................574.10.1 Main Page Of Software........................................................................................574.10.2 Generate Scratch Card..........................................................................................584.10.3 Faculty Information.............................................................................................594.10.4 Department Information.......................................................................................604.10.5 Program Information............................................................................................614.10.6 Bath Information..................................................................................................624.10.7 Student Information.............................................................................................634.10.8 Part Information...................................................................................................644.10.9 Student Part Registration......................................................................................65

4.11 COMMUNICATIONS INTERFACES..........................................................................66

5. SUMMARY AND FUTURE WORK...............................................................71

5.1 FUTURE WORK.................................................................................................... 715.2 CONCLUSION....................................................................................................... 71

6. APPENDICES....................................................................................................... 72

6.1 APPENDEX A CODING.........................................................................................726.1.1 Connect.java........................................................................................................726.1.2 SMSDemo.java....................................................................................................75

6.2 Appendex B Refrences:......................................................................................76


1. INTRODUCTION

1.1 OVERVIEW

This system allows the user (student) to pay their admission / examination / pass

certificate/ markshet/ degree fees through scratch cards that will be available in

university authorized shops. Students can pay their fees through scratch card by using’

Short Message Service’.

The prepared system will provide services such as university news, update about their

result of admission, update about results of semester, information about degree, and

information about timetable, information about course outlines etc. through ‘Short

Message Service’

1.2 Background

In almost all universities and colleges of our country, there is a lack of the advanced

system for fee payment, event notification, and information / update regarding the

academic or certificate information. Because of this, both, the students and the

administration of the university suffer from increasing work load and wastage of time.

For example, to pay the fee of a semester, the students have to travel to the university to

get the challan form and to fill it up. After wards, they have go to the bank, where they

stand in long big queue to pay the challan fee. After this, they again go to the university

to submit the copy of challan fees. Further, every now and then there are various events

in the university, for example, strikes, boycotts, changes in examination schedule, class

suspension, etc. which the administration must communicate to the students. Due to lack

of immediate communication, the students arrive at university with no academic activity

going on, thus wasting their whole day. Additionally, the students and the administration

of the university suffer from the enquiries regarding the issuance of various certificates,

and for the result and role number of the semesters etc, for which the students have to

visit the concerned department or session and stand in the queue. Most of the times, the


work is delayed from the administration side due to some reasons and the students waste

their whole day without getting any update regarding academic activities or their required

information or certificates. We have come up with a solution to this problem and

introducing an advanced system for fee payment, event notification and update regarding

the academic or certificate information.

1.3 Features

1.3.1 Fee payment system

We have introduced a system through which the students can pay the fee of examination,

admission or any required academic degree or certificate easily without going through

long process of challan fee form etc. This system is based on the use of a card. There are

various types of cards with specific prices, designed according to the fee structure. For

example, cards for admission and examination fee will be of different price. The card for

any certificate issuance will be of different price. The card contains specific series of

numbers, hidden by a coated material. These card numbers are already registered with

and issued by the university accounts branch. The card are sold to the various shops in

the city, where the students can buy the required card. After scratching the card, the

student can type the hidden series of numbers in his mobile number and send it along

with his own information, i.e., name and seat number etc. to the university. The

university system will receive this information and automatically acknowledge the

receipt of the payment of the requested procedure.

1.3.2 Event Notification

We have introduced a software, in which we put the names and their contact numbers of

the students. Any new event if happens in the university, such as, admission or

examination date announcement, or class suspension due to any reason, the concerned

person will send a message of that event through this system to the all students. I this

way, the students will be able to get any updated information of the event. As the system

contains various groups of students according to the semester. Any information which


needs to be delivered to the students of a specific semester, can be sent to only those

students by selecting that group in our system. Thus, all or any group of the university

students can be kept updated from the latest events in the university.

1.3.3 Information or update regarding the academic results or certificate issuance

We have introduced a system, through which the students will be able to get the

information of their semester result, admission date or any certificate issuance etc. The

student will simply type his role number and semester part and send it from his mobile

to the given university number or check result. The system will reply with all the

required information. In this way, the students will be able to get the information and

update without any suffering and wastage of time.

1.4 Conclusion

In the presented thesis work, we have introduced a software system, through which both,

the students and the administration of the university will get the benefits. Through this

system, the long procedures of fee payment, events notification and information

regarding any academic inquiry will easily be provided to the students through sms

service within seconds. This system will save the time and money of the university staff

and the students.


2. BACKGROUND

2.1 Use Case

A use case specifies the behavior of a system or a part of a system, and is a description of

a set of sequences of actions, including variants, that a system performs to yield an

observable result of value to an actor.” i

“An actor is an idealization of an external person, process, or thing interacting with a

system, subsystem, or class. An actor characterizes the interactions that outside users may

have with the system.” ii

A use case is rendered as an ellipse in a use case diagram. A use case is always

labeled with its name.

Figure: 2.1.1.1: Eclipse

An actor is rendered as a stick figure 2.1.1.2 in a use case diagram. Each actor

participates in one

Student or more use cases.

Figure: 2.1.1.2: Actor


2.1.1 Example Use Case: Obtaining Verified Challan

Figure 2.1.1: Obtaining Verified challan

Name: Obtaining Verified challan

Description: the student gets the challan from clerk and pay fees to the bank

Actor: Student, clerk, bank

Main scenario:

1. The student provides information and verifies challan.

2. The Bank receives the challan and fees.

Activity Diagram:

An activity diagram is essentially a flowchart, showing the flow of control from activity

to activity.


Use activity diagrams to specify, construct, and document the dynamics of a society of

objects, or to model the flow of control of

an operation. Whereas interaction diagrams emphasize the flow of control from object to

object, activity diagrams emphasize t he

flow of control from activity to activity. An activity is an ongoing non-atomic execution

within a state machine.

Entity Relationship Modeling (ERM)

A technique used to analyze & model the data in organizations using an Entity

Relationship (E-R) diagram

2.1.2 Entity type

A class of entities with the same attributes

2.1.3 ERD Development Process

• Identify the entities.

• Determine the attributes for each entity.

• Select the primary key for each entity.

• Establish the relationships between the entities.

• Draw an entity model.

• Test the relationships and the keys.

2.1.4 Relationship

An association between two or more entities that is of particular interest


2.1.5 Key Attributes

• Certain attributes identify particular facts within an entity, these are known as KEY

attributes.

• The different types of KEY attribute are:

• Primary Key

• Composite Primary Key

• Foreign Key

2.1.6 Key Definitions

• Primary Key:

• One attribute whose value can uniquely identify a complete record (one row of data)

within an entity.

• Composite Primary Key

• A primary key that consists of two or more attribute within an entity.

• Foreign Key

• A copy of a primary key that exists in another entity for the purpose of forming a

relationship between the entities involved

2.2 Class diagram

A diagram that shows a collection of declarative (static) model elements, such as classes,

types, and their contents and relationships.

2.2.1 Association

Association is a relationship where all object have their own lifecycle and there is no

owner. Let’s take an example of Teacher and Student. Multiple students can associate

with single teacher and single student can associate with multiple teachers but there is no


ownership between the objects and both have their own lifecycle. Both can create and

delete independently.

2.2.2 Aggregation

Aggregation is a specialize form of Association where all object have their own lifecycle

but there is ownership and child object cannot belongs to another parent object. Let’s

take an example of Department and teacher. A single teacher cannot belongs to multiple

departments, but if we delete the department teacher object will not destroy. We can

think about “has-a” relationship.

2.2.3 Composition

Composition is again specialize form of Aggregation and we can call this as a “death”

relationship. It is a strong type of Aggregation. Child object does not have their lifecycle

and if parent object deletes all child object will also be deleted. Let’s take again an

example of relationship between House and rooms. House can contain multiple rooms

there is no independent life of room and any room cannot belongs to two different house

if we delete the house room will automatically delete.

2.2.4 Attribute

A named slot within a classifier that describes a range of values that instances of the

classifier may hold.

2.3 Activity

An Activity is, fundamentally, an object that has a lifecycle. An Activity is a chunk of

code that does some work; if necessary, that work can include displaying a UI to the user.

It doesn't have to, though-some Activities never display UIs. Typically, we will designate

one of our application's Activities as the entry point to our application.


2.4 Broadcast Receiver

Broadcast Receiver is yet another type of component that can receive and respond to any

broadcast announcements.

2.4.1 Service

A Service is a body of code that runs in the background. It can run in its own process, or

in the context of another application's process, depending on its needs. Other components

"bind" to a Service and invoke methods on it via remote procedure calls. An example of

a Service is a media player; even when the user quits the media-selection UI, she

probably still intends for her music to keep playing. A Service keeps the music going

even when the UI has completed.

2.4.2 Content Provider

Content Provider is a data storehouse that providesaccess to data on the device; the

classic example is the Content Provider that's used to access the user's list of contacts.

Our application can access data that other applications have exposed via a Content

Provider, and we can also define our own Content Providers to expose data of our own.

2.5 Tools And Technologies

2.5.1 System Interface

Front End Client:

Mobile

DataBase Server:

MySQL, Operating System (any)

Back End:

Java, Hibernate, MySQL, Operating System (any)


2.5.2 User Interfaces

Client (student) on Mobile will be using GSM protocol

2.5.3 Hardware Requirements

P-IV or faster Processor.

Minimum 1GB hard disk space.

500 MB of RAM or more.

Display capable of showing 16 bit colors or more.

Bluetooth enabled machine Or GSM Device.

2.5.4 Software Requirements

DBMS:

Name: MYSQL

Version Number: 5.6

Source: www. mysql .com

IDE:

Name: NeatBean

Version: 7.3.1

Source: https://netbeans.org/downloads/

Java:

Name: JDK 1.7.0

Version: 1.7.0

Source : http://java.com/en/download/index.jsp

Hibernate: 3.0

http://java.com/en/download/index.jsp

https://netbeans.org/downloads/

http://www.mysql.com/


2.5.5 Communications Interfaces

Client (student) on Mobile will be using GSM protocol

2.5.6 Installition Requirements

1. Install Jdk 1.7

2. Install MySQL Server 5.6

3. Java Communications API

There is a trick to install the Java Communications API correctly on a Windows system

Machine.

The following files are the core of JAVA Communication API, and they are very

important to

have them installed on your system for a proper operation:

• comm.jar

• win32com.dll

• javax.comm.properties

For the jdk (Java Developnment Kit) to recognize the serial ports on your machine, it is

important to properly place these files in the right folders on your local machine :

comm.jar should be placed in:

jdk//lib

jdk/jre/lib/ext

win32com.dll should be placed in:

jdk/bin

jdk/jre/bin


c://System32

javax.comm.properties should be placed in:

jdk/lib

jdk//jre/lib

2.6 Product Functions

This software will perform send and receive sms.

2.7 Constraint

GUI is only in English

Roll number and card number is used for the pay fees of student.

Only registered students are authorized to use the services.

This system is working for single server.

2.8 Definitions, Acronyms, and Abbreviations

SQL Structured Query Language

JVM Java Virtual Machine

API Application Programming Interface

SMS Short Message Service


3. PROBLEM DESCRIPTION

3.1 Fees Payment Use Case Report

3.1.1 Obtaining Verified Challan

Figure 3.1.1: obtain verified Challan

Name: Obtaining Verified challan

Description: the student gets the challan from clerk and pay fees to the bank

Actor: Student, clerk, bank

Main scenario:

1. The student provides information and verifies challan.

2. The Bank receives the challan and fees.


3.1.2 Electronic Fees Payment System

Figure 3.1.1: obtain verified Challan

Name: Electronic fees payment

Description: The student gets the card from a shop and pays fees

Actor: student

Main scenario:

1. The student provides data such as year and roll number

2. The system provides available information about the student

Alternative scenario:

1. If the input data is not correct, then the system shows the following options:

1a. The system notifies the “roll number”, “card number”, or ”purpose” to be put. If

these information’s are not found by the system, then it displays that “you are not

registered” or “invalid”.

2. If the student has no card than pay the fees through bank challan.

3. If the registration of semester is not done then student goes to the admission office.


3.1.3 Issue scratch card

*Fig. 3.1.3 Card Issue

Name: Issue scratch card

Description: University issue the card for the student to pay fees.

Actor: Administration, Shop, Student.

Main scenario:

1. University administration issue the scratch card.

2. Issued card available on shop.

3. Student will purchase scratch card from shop to pay fees.

U2: Manual Challan


3.2 Event Notification Use Case Report

3.2.1 Event Notification

Figure 3.2.1: Event Notification

Name: Event Notification

Description: The staff sends notification via sms to the students

Actor: student, staff (clerk)

Main scenario:

1. The staff member sends the information about time table or emergency messages, etc

to the students or the whole batch.


3.2.2 Detail Event Notification

Figure 3.2.2: Detail Event Notification

Name: Detail Event Notification

Description: The clerk send notifications via sms to the students

Actor: student, clerk

Main scenario:

1. The clerk sends the information about time table or emergency messages, course

outlines, seminar library information and faculty member’s information to the students or

the whole batch.


3.2.3 Detail Event Notification

Figure 3.2.3: Detail Event Notification

Name: Detail Event Notification

Description: The clerk send notification via sms to the students

Actor: student, clerk

Main scenario:

The clerk sends the information about Exam Fees or emergency admission fees,

scholarship forms and emergency messages to the students or the whole batch.


3.3 Information Of Results Use Case Report

Figure 3.2.2: Information about exam or test result

Name: Information about exam or test result

Description: The student send roll number or seat number via short message to the

university number and system provides available information about the student

Actor: student

Main scenario:

1. The student provides information about the year and roll number or seat number

2. The system send available information to the student


3.4 Activity Diagram for Sending SMS

Figure 3.4: Sending SMS

User is made to send purpose, roll number and card number , they are verified and if the

roll number and card number are verified displayed indicating he is fees payment

successfully else they are asked “card no or roll number invalid”


4. DESIGN AND IMPLEMENTATION

4.1 Architecture Diagram

Figure 4.1: Architecture Diagram

Description: This system architectural diagram consists of three parts, Computer,

Database (Server), GSM Device (Cell Phone) as shown in figure 4.1. GSM device is

connected with computer which provides facility of sending and receiving SMS from

computer. Computer is connected with database. Computer will receive information

through ‘GSM device’ via short message service and it will response to client after

fetching information from database.


4.2 Class Diagram For Fees Payment

Figure 4.2: Class Diagram

Description: The Faculty class represents the major type of category of education in

university for example arts, science etc. The department represents the fields regarding to

specific faculty for example department computer science represents the natural science

faculty. Program class represents the different type of degree program regarding to

specific department for example bachelor, masters etc. Batch class represents the yearly

group of admitted students in a specific program. Class Event Message represents the

notification issued or sent to specific batch of students. Every program contains specific

number of years to complete that program, the Part class represent the year of every

batch. Student class represents student itself studying in university. Fees class represents

yearly paid fee of student. Scratch Card class represents the cards issued from university

for students to pay their fee.


4.3 Class Diagram For Exam Result and Event Notification

Figure 4.3: class diagram


4.4 ER Diagram For Exam Result and Event Notification

Figure 4.4: erd dia gram for exam result and event notifaction


4.5 User Interfaces For Paying Admission Fees and Exam Fees

4.5.1 Paying Admission Fees and Exam Fees

Figure 4.4.1: Pay admission and exam fees

Description: Figure 4.4.1 shows that Student will pay admission, exam, degree or

certificate fess. Student send information ‘Purpose’ ‘Roll Number’ and ‘Card Number’

On given University Number for Example university given number is: ‘03332836705’ or

2345

Ex: write ‘admin 2K10/CSE/60 1234456789765’ sms send on ‘03332836705’ or ‘2345’.


4.5.2 Response For Paying Admission Fees and Exam Fees

Figure 4.4.2: Reply of admission or exam fee

Description: Figure 4.4.2 shows that Student will see conformation message of fees

payment.


4.5.3 Response For Paying Certificates Or Degree Fees

Figure 4.4.2: Paying Certificates or Degree Fees

Description: Figure 4.4.2 shows that Student will see options of certificates.


4.5.4 Response For Paying Certrificate or Degree Fees

Figure 4.4.4: Reply of Paying Certificates or Degree Fees

Description: Figure 4.4.4 shows that Student will see conformation message of fees

payment.


4.6 User Interface For Exam Result Information

4.6.1 Exam Result Information

Figure 4.5.1 exam result information

Description: Figure 4.5.1 shows that student will see exam result. Student write ‘Roll

Number’ space ‘Part Number’ and send university given number for Example

University Number is: ‘03332836705’ or 2345

Example: Write ‘2k10/CSE/60 1’ sms send on ‘03332836705’ or 2345.


4.6.2 Response Of Exam Result

Figure 4.5.2: Reply of exam result

Description: Figure 4.5.2 shows that Student will see on mobile information of semester

result.


4.7 User Interface For Admission Result Information

4.7.1 Admission Result Information

Figure 4.6.1: Admission result

Description: Figure 4.6.1 shows that Student will see Admission result. Student send

information ‘Seat Number’ On University Number for Example Univeristy Number is:

‘03332836705’ or 2345

Example: Write ‘1234’ sms send on ‘03332836705’ or 2345.


4.7.2 Response Of Admission Result Information

Figure 4.6.2: reply of admission result information

Description: Figure 4.6.2 shows that Student will see on mobile information of

admission result.

The system automatically response and send student information on mobile.


4.8 User Interface For Event Notification Android Application:

4.8.1 Event Notification Login Form

Figure 4.6.2: Login Form OF Event Notification

Description: Figure 4.6.2 shows that each department contain own user name and

password.


4.8.2 Event Notification Select Program

Figure 4.7.2: select program

Description: Every department’s admin will see only particular degree program related to

that department.


4.8.3 Event Notification Select Batch

Figure 4.7.3: select batch

Description: After selecting particular program, current batches will be shown in list in

which single can be selected to sent message.


4.8.4 Send Event Notification

Figure 4.7.4: send message to the batch

Description: Figure 4.7.4 shows that Any new event if happens in the university, such

as, admission or examination date announcement, or class suspension due to any reason,

the concerned person write ‘Event Message’ and select batch and group system will send

a message to the all students. The students will receive message on mobile phone.


4.8.5 Response Of Event Notification

Figure 4.7.5: response of event notification

Description: Message sent by event notification will be received to all students of that

particular batch of program, which were selected.


4.9 User Interface For Examination Result Webiste

4.9.1 Main Tittle Page

Figure 4.8.1: main tittle page

Description: Home page of website of examination. This web contains all the examination positions and results including course scheme according to previous and current batches. You can check on this link : http://usindhexam.stbb.edu.pk

http://usindhexam.stbb.edu.pk/


4.9.2 Semester results SMS service

Figure 4.8.2: Semester results SMS service

Description: This service provide students to check their results via sending a message with this pattern.


4.9.3 Annually Result Announcement

Figure 4.7.3: Annually Result Announcement

i

? The Unified Modeling Language User Guide, Addison-Wesley, 1999. [Bos00] J. Bosch

ii J Rumbaugh, I Jacobson, G Booch - New York: Addison-Wesley, 1999


Description: student can see results announcement year wise and select the academic

year and department.

4.9.4 Response of Result Announcemnt

Figure 4.8.4: result announcement sheet

Description: Announcement of results of every department annually.


4.9.5 Result Annoucement Sheet

Figure 4.8.5: result announcement sheet

Description: in above figure 4.8.4 you select the batch and figure 4.8.5 shows the result of batch.


4.9.6 Academic Transcript /Marksheet

Figure 4.8.6: Academic Transcript

Description: student can see their semester results by typing the roll number of student

and select the academic year and part.


4.9.7 Response Of Acdemic Trancript/Marksheet

Figure 4.8.7: Response Academic Transcript

Description: Reply of typing the roll number of student and select the academic year.


4.9.8 Acadamic Positions

Figure 4.8.8: Academic Positions

Description: student can see their List of positions holder of every department by select

the department and select the academic year.


4.9.9 List Of Acadamic Positions

Figure 4.8.9: List of Academic Positions

Description: List of positions holder of every department.


4.9.10 Annaully list of sucessful or passed out students

Figure 4.8.10: List of successful candidates

Description: student can see their List of successful candidates of every department by select the department and select the academic year.


4.9.11 Response of sucessful candidates

Figure 4.8.11: Response of successful candidates

Description: student can see the successful candidates list


4.9.12 Course Scheme

Figure 4.8.12: course scheme

Description: student can see their Course Scheme of every department by select the

department and select the scheme year.


4.9.13 Response of Course Scheme

Figure 4.8.13: course scheme

Description: List of Course Schemes


4.9.14 Comments and Complains

Figure 4.8.14: comments and complains

Description: you can submit your views and ideas in comment box


4.10 Software Interfaces

4.10.1 Main Page Of Software

Figure 4.9.1: Main page

Description: Figure 4.9.1. Shows the main windows of software


4.10.2 Generate Scratch Card

Figure 4.9.2: Generate scratch card

Description: Figure 4.9.2 shows that University generate various types of cards with specific prices, designed according to the fee structure. For example, cards for admission and examination fee will of different price. The card for any certificate issuance will be of different price. The card contains specific series of numbers. These card numbers are store in university database. The card are sold to the various shops in the university, where the students can buy the card and pay fees.


4.10.3 Faculty Information

Figure 4.9.3: Faculty information

Description: Figure 4.9.3 show that to add faculty example university of Sindh eight

faculties currently faculty natural science arts, Islamic studies, education commerce &

business Administration, Pharmacy & Faculty of Law.


4.10.4 Department Information

Figure 4.9.4: Department information

Description: Figure 4.9.4 show that add department faculty wise.

Example: arts faculty contains Sindhi, English, Urdu department.


4.10.5 Program Information

Figure 4.9.5: Program information

Description: figure 4.9.5 show that insert or add program.one department offers one or

more degree programs such as computer science department offers BS(CS), MSC(Pass),

MCS, PGD(CS), MPhil and PHD in computer science.


4.10.6 Bath Information

Figure 4.9.6: Batch information

Description: Figure 4.9.6 show that insert or add batches.one department offers one or


MCS, PGD(CS), MPhil and PHD in computer science. One program offers one or more

batches such as BS (CS) contains 2010, 2011, 2012 batches etc.


4.10.7 Student Information

Figure 4.9.7: Student information

Description: Figure 4.9.7 show that insert or add students.one department offers one or



batches such as BS (CS) contains 2010, 2011, 2012 batches etc. One Batch contain one

or more students. Example in 2010 has 80 students add data of each student. We store

roll number, phone number and other information phone number useful for sending event

notification and roll number useful for fees payment and identification of student etc.


4.10.8 Part Information

Figure 4.9.8: Part information

Description: Figure 4.9.8 show that insert or add parts.one department offers one or

more degree programs such as science department offers BS(CS), MSC(Pass), MCS,

PGD(CS), MPhil and PHD in computer science. One program offers one or more batches

such as BS (CS) contains 2010, 2011, 2012 batches etc.one batch contains one or more

parts such as 2010 batch of computer science contains 4 parts


4.10.9 Student Part Registration

Figure 4.9.9: Student part registration

Description: Figure 4.9.9 show that insert or add parts.one department offers one or



batches such as BS (CS) contains 2010, 2011, 2012 batches etc.one batch contains one or

more parts such as 2010 batch of computer science contains 4 parts and we register the

students in each part or we shift the students.


4.11 Communications Interfaces

Connect the mobile phone to your PC in PC Suite mode using any available

connection (Bluetooth, USB, or IR).

Make sure that you have installed the correct GSM modem driver on your PC.

You can check it from Control Panel | System | Hardware | Device Manager.

Check the Modems section. If you see something like "Nokia XY USB Modem"

or "Nokia XY Bluetooth Modem", the device has a built-in GSM modem. If you

don't have it, go to the Nokia Web site and download the driver from the product

page of your device.

http://www.developer.nokia.com/Community/Wiki/File:Controlpanel_gsmmodem.png


Right Click on Nokia N95 8GB USB Modem and find the port used by selecting

the modem tab, in our case it is COM 4. Also it is good to test the modem by

selecting Diagnostics | Query Modem, this will tell us if the modem is working

properly.

Open the HyperTerminal, which is a communication utility on Microsoft

Windows OS. HyperTerminal is located in Start | Programs | Accessories

Communication.

Create a new connection set on HyperTerminal and give a name to the

connection.

Select the port number by selecting drop down box "Connect using". In our case

the port number is COM 4

You need to select some settings related to ASCII setup, To do select File |

Properties | Settings (tab) | ASCII Setup

http://www.developer.nokia.com/Community/Wiki/File:Selectportatcommand.png


You may need to set some parameters, such as baud rate (for example, 9600),

handshaking mode (Xon-Xoff), parity bit (default), and so on.

http://www.developer.nokia.com/Community/Wiki/File:Asciisetup.png


Note that you also need to

select the communication

port on which your

mobile has been

connected. The port

number can be found by

right-clicking the modem

item in Control Panel.

http://www.developer.nokia.com/Community/Wiki/File:Hyperterminal_settings.png


After this, you

can give the

basic AT

command.

Simply type AT

in the window

and you will get

the "OK"

response.

http://www.developer.nokia.com/Community/Wiki/File:Controlpanel_gsmmodem_port.png


5. SUMMARY AND FUTURE WORK

5.1 Future Work

In future all payment system will be integrated in this system such as certificate fess, degree fess, admission fees etc.

In future all notification will be send to cell phone. Example: timetable, new schedule, test score, exam score, fess payment notification, prepare degree certificate, etc.

In future all Banking Transaction Perform through Mobile Using (SMS). Example: Like UBL Bank

5.2 Conclusion

We have introduced a software system, through which both, the students and the

administration of the university will get the benefits. Through this system, the long

procedures of fee payment, events notification and information regarding any academic

inquiry will easily be provided to the students through sms service within seconds. This

system will save the time and money of the university staff and the students.


6. APPENDICES

6.1 Appendex A Coding

6.1.1 Connect.java

import java.io.*;import java.util.TooManyListenersException;import java.util.logging.Level;import java.util.logging.Logger;import javax.comm.CommPortIdentifier;import javax.comm.SerialPort;import javax.comm.SerialPortEvent;import javax.comm.SerialPortEventListener;

public abstract class Connect implements SerialPortEventListener{ private boolean autoDeleteMessage = false; String line1 ; String line2 ; int index=0; CommPortIdentifier portId; String messageString = "Dont consider this sms, just for testing....:-D"; char ch = '"'; String dest =""; String s = ""; InputStream inputStream;

SerialPort serialPort; OutputStream outputStream; // Connect Serial Port of Blutooth public Connect(String port)throws Exception { portId = CommPortIdentifier.getPortIdentifier(port);

serialPort = (SerialPort) portId.open("Sms_GSM", 0); System.out.println("SMS Sending....Port Found"); inputStream = serialPort.getInputStream(); outputStream = serialPort.getOutputStream(); serialPort.notifyOnDataAvailable(true); serialPort.setSerialPortParams(9600,SerialPort.DATABITS_8,SerialPort.STOPBITS_1, SerialPort.PARITY_NONE);


System.out.println("setted serial port parameters"); recieve(); } public void addEventListener(SerialPort serial){ try{ serialPort.addEventListener(this); } catch (TooManyListenersException e){ System.out.println("Exception in Adding Listener" + e); } } @Override public void serialEvent(SerialPortEvent event) { BufferedReader input = new BufferedReader(new InputStreamReader(inputStream)); index = 0; if(event.getEventType()==SerialPortEvent.DATA_AVAILABLE){ try { while((s=input.readLine())!=null){ System.out.println("line : "+s); if(s.contains("CMTI")){ new Thread(){ public void run(){ if((index=s.indexOf(','))!=-1){ s=s.substring(index+1); index = Integer.parseInt(s.trim()); System.out.println("Index:"+index); try { outputStream.write("AT+CMGF=1\r\n".getBytes()); outputStream.write(("AT+CMGR="+index+"\r\n").getBytes()); outputStream.flush(); Thread.sleep(200); } catch (Exception ex) { ex.printStackTrace(); } } } }.start(); } if(s.contains("+CMGR:")){ String msg = (s+"\n"+input.readLine()); System.out.println("Message: "+msg); String from = msg.split(",")[1];


String message = msg.substring(msg.lastIndexOf("\"")+1);

handleMessage(from.replaceAll("\"", ""),message ); if(autoDeleteMessage)deleteMessage(index); } } } catch (IOException ex) { ex.printStackTrace();} } } // Send SMS TO CLINET synchronized public void send(String phoneNo,String message){ dest = ch + phoneNo + ch; messageString = message; System.out.println("To: "+dest); System.out.println("Message: "+message); line1 = "AT+CMGF=1\n"; line2 = "AT+CMGS=" + dest + "\n"; //String line1 = "AT+CREG=2"; //String line2 = "AT+CGREG?"; try { Thread.sleep(400); System.out.println("now sending..."); outputStream.write(line1.getBytes()); outputStream.write(line2.getBytes()); outputStream.write(messageString.getBytes()); outputStream.write(26); outputStream.flush(); Thread.sleep(400); } catch (Exception e) { System.out.println("Error writing message " + e); } }

// READ CONTACT public void contactEntries(int index){ String command = "AT+CPBR="+index+"\r\n"; try{ outputStream.write(command.getBytes()); outputStream.flush(); byte[] b = new byte[20]; inputStream.read(b , 0,20);


String s = new String(b,0,b.length); System.out.println("read : "+s+": length"+s.trim().length() ); }catch (Exception e){ System.out.println("Error writing message " + e); } } //RECIEVE SMS public void recieve(){ try{ String s = "AT+CNMI=1,1,0,0,0\r"; String source = "AT+CPMS=\"SM\"\r\n"; outputStream.write(s.getBytes()); outputStream.write(source.getBytes()); outputStream.flush(); addEventListener(serialPort); }catch(Exception ex){ex.printStackTrace();} } // DELETE MESSAGE FROM SIM synchronized public void deleteMessage(int index){ String source = "AT+CMGD="+index+"\r\n"; try { outputStream.write(source.getBytes()); outputStream.flush(); } catch (IOException ex) { Logger.getLogger(Connect.class.getName()).log(Level.SEVERE, null, ex); } } public void setAutoMessageDeleteFromSIM(boolean b){ this.autoDeleteMessage = b; } public abstract void handleMessage(String phoneNumber, String message);}

6.1.2 SMSDemo.java

public class SMSDemo { public static void main(String[] args)throws Exception { Connect con = new Connect("COM6"){ @Override public void handleMessage(String phoneNumber, String message) { System.out.println(" Recieved Text:"+message+" Phone Number Of Message: "+phoneNumber); }


}; con.setAutoMessageDeleteFromSIM(true); con.send("+923332836705", "Test Message Send"); } }

6.2 Appendex B Refrences:

Smart fees payment , event notification andv examination result system

Education

Transcript of Smart fees payment , event notification andv examination result system