Essay: Web application to register the different kinds of cards issued by the government

Chapter 1:
Introduction
1.1 Preamble
“Multipurpose Card” is a simple web application used to register the different kinds of cards issued by the government at one place. This overcomes the drawback of carrying 5 different cards by combining all the cards into one card by providing a unique ID.
It allows the admin to add different officers for the different departments for the smooth functioning of the system.
1.2 Motivation
The motivation behind the “multipurpose Card” was to build a simple application for the government authorities to save time and to make the system automated.
1.3 Goal and Objectives of the Project Report
The application that we are going to implement is mainly to make different identification card in a single card so that it makes comfortable to use and handle. It can be used by different department through single card. In other words we can say that our project has the following. Objectives:-
• Uses single card for multipurpose activity
• Make all the system computerize
• Reduce time consumption
• All system managements are automated
• Centralized database management
• Multipurpose operations for admin of the system
.1.4 Problem Statement
A country provides different identification card such as Driving licenses, Voter id, Passport, Ration card, Pan Card so on. By above cards data can be tracing the information as respected. Each and every card has its own value and its information. Every department has its own identification card as government provided.
1.5 Scope of the Dissertation Report
The proposed project will handle all admin functionalities smoothly. It lets admin to add users and assign tasks to them.
1.6 Outline of the Dissertation Report
Chapter – 1
Introduction: This section gives the introduction of our project “Multipurpose Card”.
Chapter – 2
Literature Survey: This section describes about the Literature Survey.
Chapter – 3
Requirement Analysis: This section gives the information about requirement analysis.
Chapter-4
Analysis and Design: This section gives the information about the analysis and design of our project.
Chapter-5
Implementation: This section gives the information about implementation of our project
Chapter-6
Testing: This section describes how testing is done.
Chapter-7
Snapshots: This section gives the user manual.
Chapter-8
Conclusion & Future Enhancement: This section gives the future scope of the project.
Chapter-9
References: This section gives the various books and sites referred to develop this project.
Chapter 2
Literature Survey
• Many services still maintain paper records which are vulnerable to damages.
• Our application makes all the system automated.
• As the systems are automated one can save their time.
Chapter 3
Requirement Analysis
3.1 Software Requirement Specification
Software Requirement Specification completely describes what the proposed software should do without describing how the software will do it. The basis goal of the requirement phase is to produce the software requirement specification, which describes the complete external behavior of the proposed software. Software requirement can be defined as a condition of capability needed by a user to solve a problem or achieve an objective.
Hardware requirements
 RAM : 1 GB or above
 Hard disk : 40 GB or above
 Processor : 2.4 GHZ or above
Software requirements
 Front end : C#.NET
 Back end : SQLSERVER
3.2 Functional Requirements
3.2.1 Module 1
Login:
It is used to login into application
3.2.2 Module 2
Home:
It contains type card in the application
3.2.3 Module 3
Add user:
Before login user must be added so that through user name and password user can login into application.
3.2.4 Module 4
Type of cards:
It includes different identification card names of user.
3.2.4.1 Passport
It displays respected user Passport details.
3.2.4.2 Ration card
It displays respected user Ration card details.
3.2.4.3 Driving License
It displays respected user DL details.
3.2.4.4 Pan Card
It displays respected user Pan Card details.
3.2.4.5 Voter ID
It displays respected Voter ID details.
3.3 Non Functional Requirements
Non functional requirement, as the name suggests are requirements that are not directly concerned with the specific functions delivered by the system. These are constraints on the services or functions offered by the system. They include timing constraints, constraints on development process and standards. Non functional requirements often apply to the system as a whole. They do not usually just apply to individual system feature or services.
There may be things like, it may be
 Safety
 Speed
 Proper language to understand
 Privacy
 Policies
Chapter 4
ANALYSIS AND DESIGN
4.1 Data Flow Diagram
4.2 Class Diagram
4.3 Sequence Diagram
4.4 Use case Diagram
Use case Diagram for Admin
Use case Diagram for PAN Officer
Use case Diagram for RTO Officer
Use case Diagram for Passport Officer
Use case Diagram for Ration Officer
Use case Diagram for Voting Officer
4.5 ER diagram:
Table Name: LOGIN
Field name Data type Length Constraint type Description
MID INT Primary Key Unique Master ID
ACTIVEFLAG INT NOT NULL Default 1
FULLNAME VARCHAR MAX NOT NULL FULL NAME OF THE USER
USERNAME VARCHAR 50 NOT NULL Name of the user
PASSWORD VARCHAR 50 NOT NULL Password of the user
Table Name: ADMIN
Primary Key: MID
Field name Data type Length Constraint type Description
MID INT Primary key Unique Master ID
ACTIVEFLAG INT NOT NULL Default 1
USERNAME VARCHAR 30 NOT NULL Name of the user
PASSWORD INT NOT NULL Password of the user
CONFIRM INT NOT NULL Confirmation password
TYPE VARCHAR 30 NOT NULL Officer type
CARD DETAILS:
Table Name: PASSPORT DETAILS
Primary Key: USER_RID
Field name Data type Length Constraint type Description
MID VARCHAR 30 NOT NUL Mid
USER_ID VARCHAR 30 Primary key Unique card number
ACTIVEFLAG INT 2 NOT NULL Default 1
CARD_NUMBER INT 2 FOREIGN KEY Pass number
SURE NAME VARCHAR 50 NOT NULL Sure name of card holder
GENERAL NAME VARCHAR 50 NOT NULL Name of card holder
COUNTRY CODE INT 2 NOT NULL Country code
DATE OF ISSUE DATE 15 NOT NULL Date of issue
FATHER NAME VARCHAR 50 NOT NULL Father name of card holder
NAME OF SPOUSE VARCHAR 50 NOT NULL Spouse name
NATIONALITY VARCHAR 50 NOT NULL Nationality of card holder
PLACE OF BIRTH VARCHAR 50 NOT NULL Birth place
DATE OF EXPIRY DATE 15 NOT NULL Date of expiry
MOTHER NAME VARCHAR 50 NOT NULL Mother name of card holder
TALUK VARCHAR 50 NOT NULL Taluk of card holder
DISTRICT VARCHAR 50 NOT NULL District of card holder
OLD PASSPART NUMBER INT 2 NOT NULL Passport old number
FILE NO INT 2 NOT NULL File number
DATE OF BIRTH DATE 15 NOT NULL Birth date
SEX VARCHAR 10 NOT NULL Gender
ADDRESS VARCHAR 30 NOT NULL Address of candidate
Table Name: RATION CARD DETAILS:
Primary Key: USER_RID
Field name Data type Length Constraint type Description
RATION_MID VARCHAR 30 Primary key Unique Master ID
ACTIVEFLAG INT 2 NOT NULL Default 1
CARD_NUMBER INT FOREIGN KEY
TALUK VARCHAR 30 NOT NULL Name of the Taluk
DISTRICT VARCHAR 30 NOT NULL Name of the District
NAME INT 30 NOT NULL Name of candidate
ADDRESS VARCHAR 30 NOT NULL Address of the card holder
FAMILY MEMBERS VARCHAR 30 NOT NULL Details family Members
GAS CONSUMER NUMBER AND DISTRIBUTER NAME VARCHAR 30 NOT NULL Gas consumer number
OFFICE PHONE NUMBER INT NOT NULL Number of Office
Table Name: VOTER ID DETAILS:
Primary Key: USER_RID
Field name Data type Length Constraint type Description
USER_RID VARCHAR 15 Primary key Unique ID number
ACTIVEFLAG INT 2 NOT NULL Default 1
CARD_NUMBER INT FOREIGN KEY Number of card
ELECTOR’S NAME VARCHAR 30 NOT NULL Name of Elector
FATHER’S NAME VARCHAR 30 NOT NULL Name of Father
SEX VARCHAR 15 NOT NULL Gender of Elector
DATE OF BIRTH DATE 10 NOT NULL Birth date of Elector
ADDRESS VARCHAR 30 NOT NULL Address of Elector
DATE DATE 10 NOT NULL Date of registration
Table Name: PAN CARD DETAILS:
Primary Key: USER_RID
Field name Data type Length Constraint type Description
USER_RID VARCHAR 30 Primary key Unique PAN number
ACTIVEFLAG INT 2 NOT NULL Default 1
CARD_NUMBER INT FOREIGN KEY
NAME VARCHAR 30 NOT NULL Name of the card holder
FATHER’S NAME VARCHAR 30 NOT NULL Name of Father
DATE OF BIRTH DATE 15 NOT NULL Birth date of card holder
Table Name: DRIVING LICENSES DETAILS:
Primary Key: USER_RID
Field name Data type Length Constraint type Description
USER_RID INT 15 Primary key Unique DL number
ACTIVEFLAG INT 2 NOT NULL Default 1
CARD_NUMBER INT FOREIGN KEY
NAME VARCHAR 30 NOT NULL Name of the card holder
DATE OF BIRTH DATE 15 NOT NULL Date of birth of holder
VALIDITY DATE 15 NOT NULL Validity of card
DOI DATE 15 NOT NULL DOI
FATHER’S NAME VARCHAR 50 NOT NULL Name of the Father
ADDRESS VARCHAR 50 Allow null Permanent Address
Chapter 5
Implementation
Screenshots:
Login Form:
Registration Window:
REGISTER is made to add user by assigning user full name, user name and password
If Register is not made user cannot login to respected window
If any field in Register is left blank it displays the message box.
Validations are done for each textbox so that it cannot be left blank
The saved user name and password are found in data grid.Grid displayes username,password and officertype
If we click on Edit on grid it will be appeared in respected text boxes.Update will modify the old records into new.
Adding Details:
Admin has only authority to ADD DETAIL
PAN CARD:
The respected pan officer can access details of card through entering the valid card number.
DRIVING LICENSE WINDOW:
Window to display the driving licenses details
The respected RTO officer can access details of card through swiping card.
PASSPORT WINDOW
When save button is clicked then it displays message box as saved successful
DISPLAY WINDOW:
All card details can be viwed through a single window through clicking view other card.
Chapter 6
TESTING
6.1 UNIT TESTING
Unit testing is done primarily by the developers and test engineers need not know about Unit testing. But this is not the case, Unit testing is as important for test engineers as it is for developers.
Unit testing focuses verification effort on the smallest unit of software design that is the module. Unit testing exercises specific paths in a module’s control structure to ensure complete coverage and maximum error detection. This test focuses on each module individually, ensuring that it functions properly as a unit. Hence, the naming is Unit Testing.
Test cases for Login:
SL.no Test Description Test Case Data Expected Result
1. Clicking Login button without entering user name and password Click on Login button Error message will be displayed “Enter user name” and “enter password.
2. Clicking Login button entering incorrect Username and Password Click on Login button Error message will be displayed Invalid user name or password
3. Clicking Login button entering correct Username and Password
Click on Login button Go to next page
4. Clicking Reset button Clicking Reset button All details should be cleared
5. Clicking Exit button Clicking Exit button It closes the application.
Test case for Admin Page:
SL.no Test Description Test Case Data Expected Result
SI.no Test Description Test Case Data Expected Result
1. Clicking Register button Click on Register button Go to Officer’s page
2. Clicking Add Details button Click on Add detail button Go to User Registration page
3. Clicking Logout button Click on Logout button Go to Login page
Test case for Officers Page:
SL.no Test Description Test Case Data Expected Result
1. Clicking ok button without entering user full name, username and password Click on ok button Error message will be displayed
2. Clicking ok button with entering user full name ,username and password
Click on ok button Message will be displayed with “updated”.
3. Clicking clear button Click on ok button All details should be cleared
4. Entering all the fields and edited properly Click on update button Message will be displayed with “updated successfully”
5. Clicking delete button Click on update button Message will be displayed with “deleted successfully”
Test case for User Registration Page:
SL.no Test Description Test Case Data Expected Result
1. Card number is left bank Click on save button Message “Enter card number”
2. Same card number entered Click on save button Message “card number is already entered” will be displayed
3. Do not Entering 10 digit phone number Click on save button Message “Enter valid 10 digit number” is displayed
Test case for Offence Information:
SL.no Test Description Test Case Data Expected Result
1. Card number is left bank Click on save button Message “Please swipe the card” is displayed.
2. Card number is incorrect Swipe the card Message ”Sorry Record not found” is displayed.
3. Clicking the Logout button Click on Logout button Go to Login page
4. Clicking on Search button Click on search button Searches the offence information
5. Entering all the fields properly Click on save button Message “Saved successfully”.
6. Clicking view other cards details Click on “view other cards” Go to display all page.
Test cases for PAN Information:
SL.no Test Description Test Case Data Expected Result
1. Card number is Incorrect Swipe the card Message “Sorry record not found “will be displayed.
2. Clicking on Back button Click on back button Go to Login page
3. Clicking view other cards details Click on ”view other cards” button Go to display page
Test cases for RATION Information:
SL.no Test Description Test Case Data Expected Result
1. Card number is left bank Click on save button Message “Please swipe the card” is displayed
2. Card number is incorrect Swipe the card Message “Sorry record not found “will be displayed.
3. Clicking the Logout button Click on Logout button Go to Login page
4. Clicking on Search button Click on search button Searches and displays the ration details in the data grid
5. Leaving any fields blank Click on save button Message “Please enter all information” will be displayed.
6. Entering all the fields properly Click on save button Message “Saved successfully”.
7. Clicking view other cards details Click on “view other cards” Go to display all page.
Test cases for Voter Information:
SL.no Test Description Test Case Data Expected Result
1. Card number is left bank Click on save button Message “Please swipe the card” will be displayed
2. Card number is incorrect Swipe the card Message “Sorry record not found “will be displayed
3. Clicking the Logout button Click on Logout button Go to Login page
4. Without selecting election type Click on Add button Message Please select the election type” will be displayed.
6. Entering all the fields properly Click on save button Message “Added successfully”.
7. Clicking view other cards details Click on “view other cards” Go to display all page.
Test cases for Passport Information:
SI.no Test Description Test Case Data Expected Result
1. Card number is left bank Click on save button Message “Please swipe the card” will be displayed
2. Card number is incorrect Swipe the card Message “Sorry record not found “will be displayed
3. Clicking the Logout button Click on Logout button Go to Login page
4. Clicking on Search button Click on search button Searches the offence information
5. Leaving any fields blank Click on save button Message “Please enter all information” will be displayed.
6. Entering all the fields properly Click on save button Message “Added successfully”.
7. Clicking view other cards details Click on “view other cards” Go to display all page.
Test cases for All card information:
SL.no Test Description Test Case Data Expected Result
1. Card number is Incorrect Swipe the card Message “Sorry record not found “will be displayed
2. Clicking on Back button Click on back button Go to Login page.
6.2 Integration Testing
Integration Testing is done related to the integration of different modules in a manner for providing a seamless effect between modules. Integration Testing addresses the issues associated with the dual problems of verification and program construction. After the software has been integrated a set of high order tests are conducted. The main objective in this testing process is to take unit tested modules and build a program structure that has been dictated by design.
All the Modules are integrated together and tested as a whole with all the possible Transactions, The Results were as expected.
• .
6.3 System Testing
System Testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements. As a rule, system testing takes, as its input, all of the “integrated” software components that have passed integration testing and also the software system itself integrated with any applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together (called assemblages) or between any of the assemblages and the hardware. System testing is a more limited type of testing; it seeks to detect defects both within the “inter-assemblages” and also within the system as a whole.
Chapter 7
Conclusion & Future Enhancement
This application will make human life comfortable and with this Multipurpose Card many transaction are done. Its easy to carry and use with single unique code very card details can be viewed and certain transaction can be made and The citizens can also view their cards.
Bibliography
• An Integrated Approach to Software Engineering 2nd edition by Pankaj Jalote.
• Software Testing Tools by Dr. K.V.K.K. Prasad
Chapter 9
References