Thesis

Faisalabad Citizen Registry
1

Table of Contents
1. I ntroduction ...................................................................................... 6
1.1 Project justification: ........................................................................................................................... 6
1.2 Scope: .................................................................................................................................................. 6
1.3 Objectives/Goal: ................................................................................................................................. 7
1.4 Document Conventions: ...................................................................................................................... 7
2. Overall Description: ........................................................................... 9
2.1 Features: ............................................................................................................................................. 9
2.2 User classes and characteristics: ....................................................................................................... 9
2.3 Operating Environment: ..................................................................................................................... 9
2.4 Design and implementation constraints: ............................................................................................ 9
2.5 Assumptions and Dependencies: ....................................................................................................... 10
2.6 Software Requirement: ...................................................................................................................... 10
2.7 User Documentation: ........................................................................................................................ 10
2.9 External Interface Requirement: ....................................................................................................... 11
2.10 SYSTEM SPECIFICATIONS: ......................................................................................................... 12
2.11 Design Constraints: .................................................................................................................... 13
2.12 System Process Model: ................................................................................................................... 14
2.12.1. Waterfall Model ...................................................................................................................... 14
2.12.2. Phases of Waterfall Model ...................................................................................................... 14
2.12.3. Why Use Waterfall Model? ..................................................................................................... 14
2.13. TOOLS: .......................................................................................................................................... 15
2.13.1 Front End: ................................................................................................................................ 15
3 System Analysis: ............................................................................................................................... 18
3.1 Functional Requirements: ................................................................................................................. 18
Use Case Scenarios ............................................................................... 19
And ......................................................................................................... 19
System Sequence Diagrams ................................................................. 19
3.1.1 (a) Login for Admin, Customer: ................................................. 20

2

Use case 1: .......................................................................................................................................... 20
3.1.1(b) System Sequence Diagram of Login: ..................................................................................... 21
Use Case 2: ......................................................................................................................................... 22
3.1.2 (b) System Sequence Diagram of Logout: .................................................................................. 23
3.1.3(a) ................................................................................................................................................ 24
Use case 3 ........................................................................................................................................... 24
3.1.3 (b) System Sequence Diagram of Manage forms: ...................................................................... 25
Use Case 4 .......................................................................................................................................... 26
3.1.4 (b) System Sequence Diagram of Edit Candidate: ..................................................................... 27
Use Case 5 .......................................................................................................................................... 28
3.1.5 (b) System Sequence Diagram of Delete Candidate: ................................................................. 29
3.1.6(a) ................................................................................................................................................ 30
Use Case 6: ......................................................................................................................................... 30
3.1.6(b) System Sequence Diagram of View Reports: ......................................................................... 31
Use Case 7: ......................................................................................................................................... 32
3.1.7(b) System Sequence Diagram of Request Report: ..................................................................... 33
3.1.8(a) ................................................................................................................................................ 34
Use Case 8 .......................................................................................................................................... 34
3.1.8(b) System Sequence Diagram of Manage Complaint: ............................................................... 35
3.1.9(a) ................................................................................................................................................ 36
Use case 9 ........................................................................................................................................... 36
3.1.19(b) System Sequence Diagram of Give Feedback: ................................................................... 37
3.2 Non-Functional Requirements: ......................................................................................................... 38
3.2.1 Usability : ................................................................................................................................... 38
3.2.2 Reliability: ................................................................................................................................. 38
3.2.3 Supportability: ........................................................................................................................... 39
3.2.4 Security: ..................................................................................................................................... 39
3.2.5 Scalability: ................................................................................................................................. 40
4. Design Models ................................................................................... 43
4.1 Use case ............................................................................................................................................ 43
4.1.1 Top Level Use case .................................................................................................................... 43

3

4.1.2 Detailed Level Use Case ............................................................................................................ 44
4.2 Entity Relationship Diagram (ERD) ................................................................................................. 45
4.3 Class Diagram: ................................................................................................................................. 46
4.4 System Sequence Diagram ................................................................................................................ 47
4.5 Activity Diagram ............................................................................................................................... 48
4.6 TABLE SPECIFICATIONS ............................................................................................................... 49
4.7 DATA FLOW DIAGRAM: ................................................................................................................. 52
4.7.1 CONTEXT DIAGRAM: .............................................................................................................. 53
4.8 Screen Shots: ..................................................................................................................................... 57
Birth Form: ......................................................................................................................................... 59
Divorce Form: .................................................................................................................................... 61
Death Form: ........................................................................................................................................ 62
Divorce Form: .................................................................................................................................... 63
About Us: ............................................................................................................................................ 65
5.System Testing ................................................................................... 68
5.3 Test case 3 ......................................................................................................................................... 72
5.4 Test case 4 ......................................................................................................................................... 73
5.5 Test case 5 ........................................................................................................................................ 74
5.7 Test case 7 ......................................................................................................................................... 76
6.System I mplementation: .................................................................... 78
6.1. Implementation needs ...................................................................................................................... 78
6.1.1 Train End Users ......................................................................................................................... 78
6.2 Convert to New System ..................................................................................................................... 78
6 .3 Post Implementation Review ............................................................................................................ 79
7. Maintenance and Support ................................................................ 81
7.1 System Maintenance: ........................................................................................................................ 81
7.2 System Recovery: .............................................................................................................................. 81
7.3 Technical Support: ............................................................................................................................ 81
7.4 System Enhancement ......................................................................................................................... 82
Glossary ................................................................................................. 83

4

DFD: ................................................................................................................................................... 83
US: Use Case ...................................................................................................................................... 84
Use case Diagram: ............................................................................................................................. 84
System Sequence Diagram: ................................................................................................................. 84
References: ............................................................................................ 85
BIBILIOGRAPHY: .............................................................................................................................. 87


5

Chapter#1
I ntroduction


6

1. I ntroduction
1.1 Project justification:
Faisalabad Citizen Registry is the online system to help the Faisalabad citizens to apply
for their registration certificates like birth, death, marriage etc.
The primary objective of this web site is to give awareness about the government or legal
documents and its registration details as well as to help to register or apply for those documents.
1.2 Scope:
Online Faisalabad Citizen Registry has been developed for Faisalabad union council to keep
record of citizen. This project aims at tracking birth form, marriage form, divorce form, death
form, and voters form. This system allows registered users of the system to login in the site and
enters the record in database. It facilitates union council to online their citizen record for the sake
of easy accessibility. The information is provided by the union council member. The purpose of
developing this system is to computerized the tradition way of tracking record.
The purpose of this document is to analyze and document on a high-level, the need and features.
The Faisalabad Citizen Registry System has been developed to provide the union council with a
centralized location for obtaining the data.
The Faisalabad Citizen Registry supposed to have the following features.
The system provides Administrator with accounts, which can be accessed using logins.
The system provides the Administrator with the option to add, edit, and delete a citizen
record.
The system provides the search facility to administrator.
The features that are described in this document will be used in the future phases of the
software development cycle. The features described here meet the needs of all the users. The
success criteria for the system are based in the level up to which the features described in this

7

document are implemented in the system.
1.3 Objectives/Goal:
The main aim of implementing this system is to provide union council with a centralized
location for gathering information.
Citizen Perspective:
It will be easy for the citizens to give only a few details for the purposes as many of
the information will be already exists in our record and it will also provide the facility
to verify any record.
Union council Perspective:
The system will allow the union council members to enter the information easily and
if they want to edit the information, they can do by just clicking. They can also delete
the information if they needs. Their work will be fast using this system
1.4 Document Conventions:
Main Headings: Times new Roman, Font-size: 18, Bold, Italicized, Left-Align,
underline
Sub Headings: Times new Roman, Font-size: 16, Bold
Text: Times new Roman, Font-size: 12, Align-Justified
Line Spacing: 1.5


8

Chapter#2
Overall Description


9

2. Overall Description:
2.1 Features:
The Online Faisalabad Citizen Registry is a system to be used to simply the task of keeping
records of Faisalabad citizens. The Online Faisalabad Citizen Registry system is developed to
benefits greatly the union council members. The system provides will the members with easy
and efficient way to share and collect knowledge. A feedback page is also made along with this
users can give feedback to share their experience.
2.2 User classes and characteristics:
There will be a wide variety of users for this software.
Union councils: Union councils would use this system for registering the citizens
of Faisalabad city.
Walk in user: The one who just happens to visit the website and is not the citizen of
Faisalabad.
Registered users: The one who is registered in union council and he/she can send
request for certificates, and also give feedback about the services of this online system.
Administrator: The administrator interacts with the database and the web portal. He
manages the website. They are managing the overall system so there is no incorrect
information within it.
2.3 Operating Environment:
This product will be developed using visual studio 2010.This product is web-based. This
product can be viewed by any web browser, and has been tested for compliance with
Mozilla, Internet Explorer, Opera and Google Chrome.
2.4 Design and implementation constraints:
As this is a website, so any web browser of any platform can run this system.

10

2.5 Assumptions and Dependencies:
Assumptions:
We have made the following assumptions
The users have sufficient knowledge of computers.
The computer on which system is to be hosted should have Internet connection
and Internet server capabilities.
The users know the English language, as the user interface will be provided in English
The system can access and modify the database.
Dependencies:
It will need a web browser for working.
2.6 Software Requirement:
Programming Environment:
Microsoft Visual Studio 2010, MS Access 2007.
Platform: Any
2.7 User Documentation:
A user document should be provided at the end of the development. It should have the
following
An about us page that will tell the user about our system.
A well documented user manual.


11

2.8 Data Requirements:
I nputs: The inputs that the software will take, is the citizens data from the user.
Output: The user can preview the in a browser is given only as the final output.
General Constraints, Dependencies &Assumptions:
This system assumed that the user have an internet available and have a knowledge
to use computer.
User view of the website:
This software will have graphical user interface that are very user friendly. The user
will have no difficulty in working with these user interfaces. The users will login to the
system and can edit and delete the records easily.
All these operations will be made easy by the websites user interfaces.
2.9 External I nterface Requirement:
The user interface is an important part of this website and will make the website very
user friendly.
Preview Screen:
The preview screen should be able to show the data in a proper format.
Publish Screen:
The user interfaces of this software are expected to be as follows
Hardware I nterface:
Faisalabad Citizen Registry will procedure a computer system or any system that
can open a website will be enough to avail the services.

12

For server side, it should be a fast system to run the website.
Software I nterface:
As it is a website so there should be a web browser to run this site. This website is best
viewable in Google chrome.
2.10 SYSTEM SPECI FI CATI ONS:
HARDWARE DESCRI PTI ON:
The selection of hardware is very important in the existence and proper working of any
software. When selecting hardware, the size and requirements are also important.

Minimum Requirements:
Processor : Pentium 4
RAM : 512MB
Hard Disk Drive : 3GB
Video : 800X600, 256 colors
CD-ROM : Required
The proposed System is developed on:
Processor : INTEL Core 2 Duo
RAM : 1GB
Hard Disk Drive : 40GB
Key Board : Standard 101/102 or Digi Sync Family
Monitor : Display Panel (1024 X 764)
Display Adapter : Trident Super VGA
Network Adapter : SMC Ethernet Card Elite 16 Ultra
Mouse : Logitech Serial Mouse

SOFTWARE DESCRI PTI ON:
Operating System : Windows 7
Front- End : VB. NET with ASP. NET

13

Back- End : MS ACCESS 2007

2.11 Design Constraints:

2.12 Software Language Used:
The languages that shall be used for coding is HTML/CSS/ASP and database will be MS
ACCESS.
Project will be done in ASP. NET with VB as front end and MS ACCESS 2007 as back end.
Microsoft .NET is software that connects information, people, systems and devices. It spans
clients, servers and developer tools and consists of:
The .NET Framework programming model that enables developers to build Web-based
applications which expose their functionality programmatically over a network using
standard protocols such as SOAP and HTTP.
Developer tools such as Microsoft Visual Studio .NET, which provide a rapid application
integrated development environment for programming with the .NET Framework.
A set of servers including Microsoft Windows 2000, Microsoft SQL, Server and
Microsoft BizTalk Server that integrates, runs, operates and manages XML Web services
and applications.
Client software such as Windows 7, Windows XP, Windows CE and Microsoft Office
XP that helps developers deliver a deep and compelling user experience across a family
of devices and existing products.
The .NET Framework is the programming model of the .NET environment for building,
deploying and running Web- based applications, smart client applications and XML Web
services. It manages much of the plumbing, enabling developers to focus on writing the business
logic code for their applications. The .NET Framework includes the common language runtime
and class libraries.
1. Development Tools:

14

We will make use of the online references available for developing programs in HTML and the
scripting will be done using visual studio 2010

2. Class Libraries:
We need to develop some libraries for web-based application to provide necessary
functionalities.
2.12 System Process Model:
A system process model is an abstract representation of a process. It presents a
description of a process from some particular perspective.
2.12.1. Waterfall Model
The waterfall model is a sequential design process, often used in software development
processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the
phases of Conception, Initiation, Analysis, Design, Construction, Testing,
Production/Implementation, and Maintenance.
2.12.2. Phases of Waterfall Model
Definition Study/Analysis
Basic Design
Technical Design/Detailed Design
Construction
Testing
Integration
Management and Maintenance.
2.12.3. Why Use Waterfall Model?
Design errors are captured before any software is written saving time during the
implementation phase.
It allows for departmentalization and managerial control.

15

Simple and easy to understand and use.
Easy to manage due to the rigidity of the model each phase has specific deliverables
and a review process.
Phases are processed and completed one at a time.
The approach is very structured and it is easier to measure progress by reference to
clearly defined milestones.
The total cost of the project can be accurately estimated after the requirements have
been defined (via the functional and user interface specifications).
Testing is easier as it can be done by reference to the scenarios defined in the
functional specification.
Because our requirements are well known, clear and fixed. Our product definition is stable,
technology is understood. There are no ambiguous requirements.
2.13. TOOLS:
2.13.1 Front End: ASP.NET
ASP.NET is a server-side Web application framework designed for Web development to
produce dynamic Web pages. It was developed by Microsoft to allow programmers to build
dynamic web sites, web applications and web services.
ASP stands for Active Server pages and .NET is a software framework developed by Microsoft
that runs primarily on Microsoft Windows.
ASP.NET takes an object-oriented programming approach to Web page execution. Every
element in an ASP.NET page is treated as an object and run on the server. An ASP.NET page
gets compiled into an intermediate language by a .NET Common Language Runtime-compliant
compiler.
ASP .NET is the natural choice for versatile and commercial web application building because:
Less Coding
Multi-language Compatibility
Ability to create web forms

16

Security
Uninterrupted processes
Easy Deployment
Auto Debugging

2.13.2 Back End:
MICROSOFT DATA ACCSS COMPONENTS (MDAC)
Microsoft Data Access Components (MDAC) is a collection of core files provided to help
applications by providing a means of accessing data. MDAC includes core files for Open
Database Connectivity (ODBC), ActiveX Data Objects (ADO), OLEDB, Network libraries and
client configuration tool for SQL Server. Depending on your data access strategy, you may need
to ensure that MDAC is installed on the client computers, the business servers, the Web servers
or the database servers


17

Chapter#3
System Analysis


18

3 System Analysis:
To be used efficiently, all computer software needs certain hardware components or other
software resources to be present on a computer. These prerequisites are known as (computer)
system requirements and are often used as a guideline as opposed to an absolute rule. Most
software defines two sets of system requirements: minimum and recommended. With increasing
demand for higher processing power and resources in newer versions of software, system
requirements tend to increase over time. Industry analysts suggest that this trend plays a bigger
part in driving upgrades to existing computer systems than technological advancements.
3.1 Functional Requirements:
The Online Faisalabad Citizen Registry System provides simple mechanism for users to share
and acquire knowledge. This section describes in detail all the functional requirements.
Admin Account and Login Capabilities:
The system shall provide the Admin with Admin Accounts. The user accounts will be made
accessible through Login capabilities. This can be integrated with login functionality .The
user must login before he can use the online Faisalabad Citizen Registry.
Sharing the knowledge:
The system will allow the union council members to share the data among other
branches
Evaluation of knowledge:
The system will provide a view to check the records from the database.
User experience sharing:
The system will allow users to share their feedback from the feedback page.
Candidate record :
Admin can check any candidate record.
Candidate Requests:
System should provide that admin can response all the requests of candidates.

19

Use Case Scenarios
And
System Sequence Diagrams


20

3.1.1 (a) Login for Admin, Customer:
Use case 1:
Use Case Title Log in

Abbreviated Title Log in
Use Case Id UC 1

Description: This use case is about logging in the system with valid user name and password.
Pre Conditions:

Task Sequence Exceptions
1. Administrator enters valid user name and password.

2. System confirms the user name and password.

3. Allow admin to access the system.

Post Conditions: Admin is successfully login in the system.

Authority: Administrator .

21

3.1.1(b) System Sequence Diagram of Login:


22

3.1.2(a)
Use Case 2:

Use Case Title Log out
Abbreviated Title Log out
Use Case Id UC 2
Description: This use case providing the facility to administrator to logout from the system.
Pre Conditions:
1: Administrator and Customer must be login in the system.

1: Administrator and customer simply logout from the system
Post Conditions: Administrator successfully log out.
Authority: Administrator .
Author: Namra , Hania
Description: This use case providing the facility to administrator to log out from system.


23

3.1.2 (b) System Sequence Diagram of Logout:


24

3.1.3(a)

Use case 3

Use Case Title Manage forms
Abbreviated
Title
Manage Forms
Use Case Id UC 3
Description: This use case providing the facility to admin to manage forms.
Pre Conditions:
1: Administrator should be login in the system.
1: Administrator login successfully.
2:Manage birth form.
3: Manage marriage form.
4: Manage death form.
5: Manage divorce form.
6: Manage voters form.
Post Conditions: Admin must login successfully.
Authority: Administrator.
Author:Namra ,Hania.
Description: This use case providing the facility to admin to manage the forms.


25

3.1.3 (b) System Sequence Diagram of Manage forms:


26

3.1.4(a)
Use Case 4
Use Case title edit Candidate
Use Case id UC4
Description: This use case is about editing the record of existing candidate with the privileges
defined at time of user account creation.
Pre Conditions:
1. All must-required information to be edited about the user should be available.
2. Database should be available.
Task Sequence
1 Administrator opts to edit a candidate.
1. System asks for necessary information.
2. Administrator provides all the required information and opts to complete the operation.
3. There is a problem in the data provided; some data needs to be corrected.
Administrator checks the available information and corrects the error.
Administrator continues from the step 3.
4. System after confirmation adds the new candidate.
Post Conditions:
user record is successfully edited.
Authority: Admin
Author: Namra, Hania.


27

3.1.4 (b) System Sequence Diagram of Edit Candidate:


28

3.1.5(a)
Use Case 5
Use Case Title Delete Candidate
Use Case id UC5
Description: This use case is about deleting an existing user to existing system with the
privileges defined at time of user account creation.
Pre Conditions:
- All must-required information about the deleting user should be available.
- Database should be available .
Task Sequence
1Administrator opts to delete an existing user account.
2. System asks for necessary information.
3. Administrator provides all the required information and opts to complete the
operation.
4. There is a problem in the data provided; some data needs to be corrected.
- Administrator checks the available information and corrects the error.
- Administrator continues from the step 3.
5. System after confirmation deletes the existing user account.
Post Conditions:
- An existing user account is successfully deleted.
Authority:Admin.
Author: Namra , Hania.


29

3.1.5 (b) System Sequence Diagram of Delete Candidate:


30

3.1.6(a)
Use Case 6:

Use Case Title View reports.
Abbreviated
Title
View reports.
Use Case Id UC 7.
Description: This use case is about search criteria of the forms.
Pre Conditions:
1: Admin must login successfully.
1: Admin login the system successfully.
2: search required reports and also print them.
Post Conditions: Database is well maintained.
Authority: Administrator.
Description: This use case is about searching the attributes.


31

3.1.6(b) System Sequence Diagram of View Reports:


32

3.1.7(a)
Use Case 7:

Use Case Title Request Report.
Abbreviated
Title
Request Report.
Use Case Id UC 7
Description: This use case providing the facility to visitor / candidate to request for
reports/certificate.
Pre Conditions:
1: The candidate / visitor must be registered.

1: The candidate/ visitor go on home page.
2: Send requestfor required certificate. `
Post Conditions: Candidate records are properly maintained in database.
Authority:
Description: This use case providing the facility to user to request for certificate.

33

3.1.7(b) System Sequence Diagram of Request Report:


34

3.1.8(a)
Use Case 8

Use Case Title Manage complaint
Use Case id UC8
Requirement
id
8
Description: This use case is about complaint to existing system with the defined privileges.
Pre Conditions:
- All must-required information about the new and existing complaint should be available.
- Database should be available .
Task Sequence
1. The user/visitor complaints about the new or existing system.
2. System submits the complaint of visitor/user.

Post Conditions:
- A new/existing complaint is successfully managed.
Authority: Admin.


35

3.1.8(b) System Sequence Diagram of Manage Complaint:


36

3.1.9(a)
Use case 9

Use Case Title Give feedback
Abbreviated
Title
Give feedback
Use Case Id UC 9
Description: This use case is providing the Visitor the facility to give feedback.
Pre Conditions: Visitor should be the registered customer.

1: Visitor go on home page.
2: Give feedback about the services.
Post Conditions: Feedback is posted by Visitor.
Authority:
Author:Namra, Hania.
Description: This use case is providing the Visitor the facility to give feedback.


37

3.1.19(b) System Sequence Diagram of Give Feedback:


38

3.2 Non-Functional Requirements:
This section describes in detail all the non-functional requirements.
3.2.1 Usability :
The system shall allow the users to access the system from the Internet using HTML or
its derivative technologies like CSS. The system uses a web browser as an interface. .
Key factors contributing to usability are the presentation of information and the
management of user interaction.
Since all users are familiar with the general usage of browsers, no special training is
required.
The system is user friendly and online help makes using the system easy.
Usability includes two other measures, affordability and accessibility.
Affordability:
o Implemented system shall be intuitive to use and will not involve any
significant learning curve.
Accessibility:
o The operations that each category of users can perform are well defined and
documented.
o The system should be well documented on every phase of the project.
o The system will provide the help facility to the users.
3.2.2 Reliability:
The system has to be very reliable due to the importance of data and the damages that can be
caused by incorrect or incomplete data.

39

Available:
The system is available 100% for the user and is used 24 hours a day and 365 days a year.
The system is intended to be operational 24 hours a day and 7 days a week.
Accuracy:
The system should accurately provide real time information taking into consideration various
concurrency issues.
Access Reliability:
The system shall provide 100% access reliability.
3.2.3 Supportability:
I nternet Protocols:
The system shall be comply with the TCP/IP protocol standards and shall be designed
accordingly. System will be making use of HTTP at application level.
Maintenance:
The maintenance of the system shall be done by the developers as and when needed.
Standards:
The coding standards and naming conventions will be as per the American
standards.
3.2.4 Security:
o The application shall verify the identity to all of its users before allowing them
to use its capabilities.
o The system will ensure that users can only access data and services for which
they have been properly authorized.
o System has secure management of usernames and passwords.

40

3.2.5 Scalability:
The system's ability to handle a large amount of data.
o The system should be able to contain atleast 100 users.
o The system shall accept 100 requests per second.


41

Gant Chart


42

Chapter#4
Design Models


43

4. Design Models
4.1 Use case
Use case diagrams are graphical presentation of set of elements and shows a set of use
cases and actors and their relationships. It projects a system, or visualizes a system from different
angles and perspectives. It illustrates the static view of a system and is important in Organizing
and modeling the behaviors of a system.
4.1.1 Top Level Use case

Top Level UC


44

4.1.2 Detailed Level Use Case

Detailed Level UC

45

4.2 Entity Relationship Diagram (ERD)
An Entity-Relationship diagram (ERD) typically serves as the main deliverable of a conceptual
data model. While newer approaches to E-R modeling have developed, the E-R approach is still
cited by some professionals as the premier model for conceptual database design. An ERD is a
logical representation of an organizations data, and consists of three primary components:
Entities: Major categories of data and are represented by rectangles
Attributes: Characteristics of entities and are listed within entity rectangles
Relationships: Business relationships between entities and are represented by lines

ERD of Faisalabad Registery System

46

4.3 Class Diagram:
A class diagram is a category or group of things that have similar attributes and common
behavior. It shows that how the classes relate to one another. Class diagrams enable analysts to
talk to a client in the clients terminology.

Class Diagram of Faisalabad Registery System


47

4.4 System Sequence Diagram
Sequence Diagrams are used throughout the design process to demonstrate the interaction
between actors and objects as system executes over time. Due to their intuitive nature and
versatility sequence diagrams have become integral to the front end modeling activities of the
processes.

Sequence Diagram Of Faisalabad Registery System


48

4.5 Activity Diagram

Activity Diagram of Faisalabad Registry System


49

4.6 TABLE SPECI FI CATI ONS
Table Name: Users
Field Name Data Type
User_id (PK) Number
Email Text
Password Text
Username Text

Table Name: Birth
Birth_id (PK) Number
Dob Date
Full_name Text
Father_cnic Number
Mother_cnic Number
Birth_place Text
Bform_cnic Number
Gender Text
Religion Text
Caste Text
Language Text
Informer_cnic Number
Actual_date Date
Address Text
Marital_status Text


50

Table Name: Marriage
Marriage_id (PK) Number
Gbirth_id (FK) Number
Bgbirth_id (FK) Number
Marriage_date Date
Dowry Number

Table Name: Divorce
Divorce_id (PK) Number
Marriage_id (FK) Number
Nature Text
Childs Number
Divorces Number
Divorce_date Date
Divorce_cause Text


51

Table Name: Death
Death_id (PK) Number
Birth_id (FK) Number
Dod Date
Death_place Text
Graveyard_name Text
Death_cause Text
Informed_date Date
Informer Number

Table Name: Vote
Vote_id (PK) Number
Birth_id (FK) Number
Catg Text
Block Number
Constituency Number
Vote_date Date
Vote_for Text


52

4.7 DATA FLOW DI AGRAM:
A Data Flow Diagram (DFD) is a diagram that describes the flow of data and the processes that
change data throughout a system. Its a structured analysis and design tool that can be used for
flowcharting in place of or in association with information. Oriented and process oriented system
flowcharts. When analysts prepare the Data Flow Diagram, they specify the user needs at a level
of detail that virtually determines the information flow into and out of the system and the
required data resources. This network is constructed by using a set of symbols that do not imply
physical implementations. The Data Flow Diagram reviews the current physical system, prepares
input and output specification, specifies the implementation plan etc.
Four basic symbols are used to construct data flow diagrams. They are symbols that represent
data source, data flows, and data transformations and data storage. The points at which data are
transformed are represented by enclosed figures, usually circles, which are called nodes.

DATA FLOW DI AGRAM SYMBOLS:-

- Source or Destination of data

- Data Flow

- Process

- Storage


53

Steps to Construct Data Flow Diagrams

Four steps are commonly used to construct a DFD
o Process should be named and numbered for easy reference. Each name should be
representative of the process.
o The destination of flow is from top to bottom and from left to right.
o When a process is exploded in to lower level details they are numbered.
o The names of data stores, sources and destinations are written in capital letter

4.7.1 CONTEXT DI AGRAM:

Level 1 DFD- Visitor:

View Report
Request Report
Details
Visitor
Faisalaba
d Citizen
Registry
System
Database

View Report
Manage
View Details Request Report
Faisalabad
Citizen
Registry
System
Visitor
Administrator

54

Level 1 DFD- Administrator:

Verifications & Approvals
Login Details
Faisalaba
d Citizen
Registry
System
Logi
n
Administrator
Login
Visitor
Overall
Control


55

Level 2 DFD- Administrator:

Name, Place
Reg: Details
Time
Add Details
Add Details
Login Details
Login
Office
Managemen
t
Admin
Login
Birth
Registratio
n
Marriage
Registratio
n
Death
Registratio
n
Birth Files
Marriage Files
Death File
Voters
Form
Voters Files
Help
Desk
Help Desk Files

56

Level 2 DFD- Visitor:

Feedback
Enquires
Reg: Details
Marriage Registration,
Death Registration
View Ads Details
Request Report
Visitor
Faisalabad
Citizen
Registry
System
Posted
Ads
Registration
s
Office Files
Help
Desk
Help Desk Files

57

4.8 Screen Shots:
Home:


58

Login:


59

Birth Form:


60

Marriage Form:


61

Divorce Form:


62

Death Form:


63

Divorce Form:


64

Voters Form:

65

About Us:


66

Contact US:


67

Chapter#5
System Analysis


68

5.System Testing
Testing is a process to show the correctness of the program. Testing is needed to show
completeness, it improve the quality of the software and to provide the maintenance aid. Some
testing standards are therefore necessary reduce the testing costs and operation time. Testing
software extends throughout the coding phase and it represents the ultimate review of
configurations, design and coding. Based on the way the software reacts to these testing, we can
decide whether the configuration that has been built is study or not. All components of an
application are tested, as the failure to do so many results in a series of bugs after the software is
put to use.
Blackbox Testing:
Blackbox testing, also called behavioral testing, focuses on the functional requirements of
software. This testing approach enables the software engineer to derive the input conditions that
will fully exercise all requirements for a program. Blackbox testing attempts to find the errors
like
Incorrect or missing functions
Interface errors
Errors in datastructures or external database access
Behavior or performance errors
Initialization and termination errors
In Blackbox testing software is exercised over a full range of inputs and outputs are observed for
correctness.
Whitebox Testing:
Whitebox testing is also called Glassbox testing is a test case design control; structure of the
procedural design to derive test cases using Whitebox testing method, the software engineer can
derive the test cases that guarantee that all independent paths within the module have been
exercised at least once. Exercise all logic decisions on their true or false sides. Execute all loops
at their boundaries and within their operational bounds. Exercise internal datastructure to ensure
their validity.


69

Software Testing Strategies:
Testing involves
Unit testing
Integration testing
Acceptance testing

The first level of test is unit testing. The purpose of unit testing is to ensure that each
program is fully tested.
The second step is integration testing. In this individual program units or programs are
integrated and tested as a complete system to ensure that the software requirements are met.
Acceptance Testing involves planning and the execution of various types of tests in order
to demonstrate that the implemented software system satisfies the requirements. Finally our
project meets the requirements after going through all the levels of testing.


70

Test Cases
5.1 Test case 1
Project: Faisaalabad Citizen Registry System.
Module: Login In page (lP=Login Page).
Test case Id Steps(Description)

Expected Results

Pass/Fail
LP 01 1. Open the main page. The main page is open. Pass
LP 02

1. On the page, there
should be a text field for
User name.

Verify that the text box for
User name exists.

Pass

LP 03 1. On the page, there
should be a text field for
Password.
Verify that the text box for
Password exists.
Pass
LP 05

1. Enter incorrect User
name and correct
password and click Sign
In button.
The system should display
the following message,
"User name or Password
does not match. Please
try again."

Pass
LP 06

1. Enter correct User
name and incorrect
password and click Sign
In button

The system should display
the following message,
"User name or Password
does not match. Please
try again."

Pass


71

5.2 Test case 2
Project: Faisaalabad Citizen Registry System.
Module: Logout page (log =Logout Page).
Test case Id Steps(Description)

Expected Results

Pass/Fail
Log 01 1. Open the main page. The main page is open. Pass
Log 02

should be a button for
logout.

Verify that the button for
logout exists.

Pass

LP 03 1. .On clicking the logout
button ,the system sends
the confirmation
message
Verify that the system
sends the confirmation
message.
Pass
Log 04

1. Enter ok to logout
savely.
The system should logout.

Pass


72

5.3 Test case 3
Project: ONLI NE FAI SALABAD CI TI ZEN REGI STRY SSYSTEM
Module: Main page (MP=Main Page)
Test Case
ID
Steps(Description)

Expected Results

Pass/Fail

MP 01

1. Open the main page. The main page is
open.
Pass
MP 02

1. On the page, there should
be Birth, Marriage, Death,
Divorce,Voters id, and logout
links to proceed next.

Verify that Birth,
Marriage, Death,
Divorce,Voters id,
and logout links
exists.

Pass
MP 03

1. Click on the links to
proceed next.

Verify that on
clicking link
proceeding occur.

Pass
MP 04 1. Click on the first link. The system will
proceed next and show
next form.
Pass


73

5.4 Test case 4
Project: ONLI NE FAI SALABAD CI TI ZEN REGI STRY SYSTEM
Module: Manage Forms
Author: Namra, Hania
Test Case
ID
Steps(Description)

Expected Results

Pass/Fail

MF 01

1. Open the main page. The main page is open. Pass
MF 02

should be Birth, Marriage,
Death, Divorce, voters id
form to proceed next.

Verify that s all form
exists.

Pass
MF 03

1. Click on the forms to
proceed next.

Verify that on clicking
forms occur.

Pass
MF 04 1. Click on the first form. The system will proceed
next and show attributes.
Pass
MF 05 1. There should be text
fields .
Verify that the text boxes
exist.
Pass
MF 06 1. There should be a edit
,delete. Update, and
submit button.
Verify that the all buttons
exist.
Pass
MF 07 1.Click on next form and
so on.
The system will proceed
next and show attributes.
Pass


74

5.5 Test case 5
Module: Reports (R=Reports)
Test Case
ID
Steps(Description)

Expected Results

Pass/Fail

R 01

1. Open the form. The form is open. Pass
R 02

1. On the form there
should be report link to
proceed next.

Verify that report link
exists.

Pass
R 03

1. Click on the report link
to proceed next.

Verify that on
clicking link
proceeding occur.

Pass
R 04 1. Click on the sub link for
report type.
The system will
proceed next and
show next form.
Pass
R 05 1. There should be text box
for report type.
Verify that text box
for report type exists.
Pass
R 06 1. Click on the show
button.
.Verify that the show
button exist .The
system should display
the result after
processing.
Pass


75

5.6 Test case 6
Module: Reports REPORTS (RR=Reports)

Test Case
ID
Steps(Description)

Expected Results

Pass/Fail

R 01

1. open the main page. The main page is
open.
Pass
R 02

1. On the main page there
should be link to proceed
REQUEST REPORT.

Verify that report link
exists.

Pass
R 03

1. Click on the report link
to proceed next.

Verify that on
clicking link
proceeding occur.

Pass
R 04 Click on the submit button
to send Request.
Pass


76

5.7 Test case 7
Module: Feedback (F=Reports)
Test Case
ID
Steps(Description)

Expected Results

Pass/Fail

F 01

1. open the main page. The main page is
open.
Pass
F 02

1. On the main page there
should be link to
feedback.

Verify that feedback
link exists.

Pass
F 03

1. Click on the feedback
link to proceed next.

Verify that on
clicking link
proceeding occur.

Pass
F 04 Click on the submit button
to sendfeedback.
Pass


77

Chapter#6
System I mplementation


78

6.System I mplementation:

6.1. I mplementation needs
An effective online Faisalabad citizen registry needs to focus on the records of the candidates,
manages the reports and request certificates .
6.1.1 Train End Users
No system can be successful without proper training, whether it involves software,
hardware, or manufacturing. A successful information system requires training for users,
managers and IT staff members. The entire system development effort can depend on whether or
not people understand the system and know how to use it effectively.
Users are trained in groups, with separate training programs for distinct groups.
Users are trained to use proposed system by providing learning by hearing, seeing,
and doing.
Traditional training manuals, printed handouts are distributed at all levels.
Training is delivered step by step instructions by using all the features of the
information system.
A full scale simulation is rehearsal is conducted for users and other related staff so
that they can get valuable experience and build confidence for everyone involved
with the new system.
6.2 Convert to New System
The parallel operation is used to convert old system into new proposed system. Both
the old and the new information systems are operated fully for specified period. Data is input
into both systems, and output entered by the new system is compared with the equivalent output
from the old system when end users, management, and the top IT group are satisfied that the new
system operates correctly, the old system is terminated and converted to new information
system.
Database setup by creating tables in Microsoft accsess.

79

Database connectivity through Connection object.
Finding and removing the errors in the interface.
Inserting some sample data in the application.
Finalizing the interface, making all the forms to give consistent look and feel.
6 .3 Post I mplementation Review
Once the new system is operational, it is to perform a post implementation evaluation to
assess the overall quality of the new proposed information system. The new system is thoroughly
checked and verified that the new system is meeting specified requirements, complies with user
objectives, and achieves the anticipated benefits. In post implementation evaluation all aspects of
the development effort and the end product are examined. The overall evaluation of the system is
conducted by performing following activities.
Accuracy, completeness, and timeliness of information system output
User satisfaction level
System reliability and maintainability
Adequacy of system controls and security measures
Hardware efficiency and plate form performance
Effectiveness of database implementation
Completeness and quality of documentation
Quality and effectiveness of training


80

Chapter#7
Maintenance and Support


81

7. Maintenance and Support
7.1 System Maintenance:
In the system operation and support phase proper maintenance is performed during the
useful life of the system. Maintenance varies significantly during the systems operational life
and includes changing programs, procedures, documentation to ensure correct system
performance, adapting the system to changing requirements, and making the system operate
more efficiently. In the new proposed sales information system maintenance is implemented by
corrective, adaptive, perfective and preventive maintenance.
Corrective maintenance is performed to fix errors
Adaptive maintenance to add new capability and enhancements
Perfective maintenance to improve efficiency
Preventive maintenance to reduce the possibility of future system failure
7.2 System Recovery:
System recovery support is group of such activities that reduce the possibility of future
problems to avoid problems before they happen. It requires analysis of areas where trouble is
likely to occur. Activities involves in system recovery are:
Install new anti-virus software
Develop standard backup and recovery schedule
Implement regular defragmentation process
Analyze problem report for patterns
Implement fire wall preventing unauthorized requests
Tighten all cable connections on switches, hubs and computers
7.3 Technical Support:
During technical support of system maintenance phase errors and diagnosed and fixed
during the successful operational life of the new system. In addition to this following activities
are performed for the provision of technical support.
Replace defective network cabling

82

Restore proper configuration settings
Debug program code
Update drivers
Install software patch
7.4 System Enhancement

System enhancement adds enhancements to an operational system and makes the system
easier to use. An enhancement is a new feature or capability. Its need usually arise form business
environment changes such as new products or services, new manufacturing technology. The
maintenance team analyzes designs and implements the new features such as:
Add online capability
Create new reports
Add new data entry field to input screen
Install links to web site
Add new input form


83

Glossary
SRS: Software Requirement Specification (SRS) is the starting point of the software developing
activity. As system grew more complex it became evident that the goal of the entire system
cannot be easily comprehended. Hence the need for the requirement phase arose. The software
project is initiated by the client needs. The SRS is the means of translating the ideas of the
minds of clients (the input) into a formal document (the output of the requirement phase.)
ERD: Entity Relationship Diagram
SSD: System Sequence Diagram
TC: Stands for Test Case
CLR: Common Language Runtime
CLI : Common Language Infrastructure
DFD: Data Flow Diagram
Class Diagram: Class diagrams are the most common diagrams used in UML. Class diagram
consists of classes, interfaces, associations and collaboration. Class diagrams basically represent
the object oriented view of a system which is static in nature. Active class is used in a class
diagram to represent the concurrency of the system. Class diagram represents the object
orientation of a system. So it is generally used for development purpose.
Component Diagram: Component diagrams represent a set of components and their
relationships. These components consist of classes, interfaces or collaborations. So Component
diagrams represent the implementation view of a system.


84

US: Use Case
Use case Diagram: Use case diagrams are a set of use cases, actors and their relationships.
They represent the use case view of a system. A use case represents a particular functionality of a
system. So use case diagram is used to describe the relationships among the functionalities and
their internal/external controllers. These controllers are known as actors.
System Sequence Diagram: A system sequence diagram is an interaction diagram. From the
name it is clear that the diagram deals with some sequences, which are the sequence of messages
flowing from one object to another. Interaction among the components of a system is very
important from implementation and execution perspective. So Sequence diagram is used to
visualize the sequence of calls in a system to perform a specific functionality.


85

References:
www.nadra.gov.pk/
www.wikipedia.org/wiki/Civil_registry
www.associatedcontent.com
www.members.tripod.com
Resources have been used from Dr. Cuberts website,
www.cise.ufl.edu/~rmc/se/, and this SRS was modeled after one found
online at http://www.processimpact.com/process_assets/srs_template.doc.
"Team SpyLane." Computer Science and Engineering. N.p., n.d. Web. 19
Nov.2012.
http://www.cse.msu.edu/~cse435/Projects/F2012/LMS-2/web/
http://searchsoftwarequality.techtarget.com/answer/Functional-
requirements-and-nonfunctional-requirements-in-software-engineering-
explained
Hoodat, H., & Rashidi, H. (2009). Classification and Analysis of Risks in
Software Engineering. World Academy of Science, Engineering &
Technology, 56446-452. Retrieved from EBSCOhost.
Boban, M., Pozgaj, Z., Sertic, H. Strategies for successful software
development risk management, <www.efst.hr/management/Vol8No2-
2003/4-boban-pozgaj-sertic.doc>
Risk Management <http://en.wikipedia.org/wiki/Risk_management>
Software Engineering Risk: Understanding & Management (SERUM)
<http://www.thedacs.com/databases/url/key/270/277/3535>.

http://www.google.com/uml

86

http://www.wikipedia.com/
http://www.tutorialspoint.com/uml
http://www.webopedia.com/
http://www.slideshare.com/
http://www.yahoo.com/
http://www.ask.com/
http://www.ehow.com/


87

BI BI LI OGRAPHY:

Windows programming Charles Petzoid
ASP. NET Unleashed Stephen Walther
Visual Basic .NET Black Book Steven Holzer
Professional ASP. NET Web services Alex Homer, Dave Sussman
SQL Server Essential Reference Sharon Dooley

Thesis

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

Thesis

Uploaded by

Copyright:

Available Formats

Faisalabad Citizen Registry

You might also like