Project Record

Citizenship information management system
1. Introduction
1.1 Scope:
The scope of this project is to build a DB2 based data architecture in which
the Citizenship Information is being processed.The batch application of COBOL
processing helps to update the Citizenship module and CICS based screens does
provide the pattern for updating and viewing the information. This medium sized
prototype is advanced which can be implemented in large size for bigger states like
Tamil Nadu & Andhra.
1.2 Objective:
The objective of this project is to create a mainframe environment based

Citizenship Information Management System which provides various features online
that becomes a duplex usage for the citizens and Government as well.
The main modules are:
1. Birth Registration.
2. Death Registration.
3. Ration card Registration.
4. PAN card Registration.
5. Passport Registration.
1.3 Description:
This system creates a File-based data base access method in which the user
logins using user name and password and authentication is made for registration .It
also provides different sub-requests like Birth Certificate, Death Certificate ,Voter ID
request ,Passport request through various entries in the mainframe screens which are
enabled through the CICS. Any dates to update in the database are designed in a way
where the VSAM file gets updated by rewriting the master file. Any report
1
generations are routed the COBOL report generation programs where the data again
gets retrieved from the VSAM and DB2 file through CICS.
1.4 Introduction to modules:
1.4.1 Birth registration:

This application will have a separate window for entering the birth details like
child name, date of birthplace of birth ,name of the mother,father,gender .Once this
data is being feed through online in the vendor machine at the corporation which is
available 24*7 or through the internet, Then the administration can take the data from
it and verify and then provide them a authenticated certificate on request. This is
made feasible through the mainframe VSAM cluster based file which updates the data
through the day which serves as a online system and gets processed in the night and
the reports, certificates and updating in the main file happens which are termed as
batch processing system.
The advantage for this type of system is
a.) The citizen need not wait in queues or spend a day in the corporation
office whereas he can get connected through the net and load his data.
b.) Those who are unable to get connected to internet (like illiterates) can
make use of the vending machines which would be available at the offices
or at the hospitals with a person to assist and thereby helping those in
need.
1.4.2 Death registration :
This module will also be available in the mail application through a separate
window (screen) .For entering the death details like Name, date of death place, mode
of death , name of the dependants like wife, mother, father, gender .Once this data is
being feed through online in the vendor machine at the corporation which is available
24*7 or through the internet, Then the administration can take the data from it and
verify and then provide them a authenticated certificate on request. This is made
feasible through the mainframe VSAM cluster based file which updates the data
through the day which serves as a online system and gets processed in the night and
2
the reports, certificates and updating in the main file happens which are termed as
batch processing system.
The advantage for this type of system is the death registration would be made feasible
in the hospital itself or through the internet, for this every hospitals which right now
possess internet connectivity can upload the data and download the death registration
certificate too.
1.4.3 Ration card application/Updating:

This application would also have another window which comes from the main screen
that asks for updating of ration card which is a very important nationality as well as
identity proof. The citizen has to fill the application form for ration card online and
specify properly the name of the area in which you wish to get new ration card. The
following Xerox copies can also be submitted through online like Voter identity card
and Residential proof like
•Receipt of tax payment, Document of rent agreement, Gas bill, Bank passbook
Electricity bill, Telephone bill.
1.4.4 PAN Card application/Updating:

This module will also be available in the mail application through a
separate window (screen).The user can enter the online application details like
name, age, address ,contact details, education details, job details .Apart from
this the citizen would also need to give the residence proof like ration card ,
Receipt of tax payment, Document of rent agreement, Gas bill, Bank
passbook. Also the age proof like 10th certificate ot TC would also be required.
Thus these data would be directly feed through online system
Once these data are acquired online through VSAM files then these data get
processed in the PAN card system which is a separate mode of line and thus
the consolidation of all activities takes place in a single stretch.
1.4.5 Passport application:
This sub module which comes from the main screen has an option to enter
the application for new passport and passport renewal system .This system
3
will have the all the data collected through the day as online processing
through the CICS system and also transferring the same during the night .the
main information that the citizen would require are to fill up his name,
surname, gender, permanent and current address, contact phone numbers
,address poof and age proof certificates. Thus the data would be transferred to
the main Passport application receive system and the citizen information
would be required.
1.5 Feasibility Study:
The feasibility study is the important step in any software development process. This
is because it makes analysis of different aspects like cost required for developing and
executing the system, the time required for each phase of the system and so on. If
these important factors are not analyzed then definitely it would have impact on the
organization and the development and the system would be a total failure. So for
running the project and the organization successfully this step is a very important step
in a software development life cycle process.
The feasibility study varies based on the system that would be developed.
a. Feasibility study is made on the system being developed to analyze whether

the system development process require training of personnel. This help in
designing training sessions as required in later stage.
b. Is the system developed has scope for expanding or scope for switching to
new technology later if needed in ease. In other study is made to find the
portability of the system in future.
c. Is the cost of developing the system high or does it meet the budgeted costs.
That is a cost benefit analysis is made. In other words an analysis is made on
cost feasibility of the project. This helps in identifying whether the
organization would meet the budgeted costs and also helps the organization in
making earlier and effective plans for meeting extra costs because of the
system development
Advantages of making Feasibility study
4
a. This study being made as the initial step of software development life cycle
has all the analysis part in it which helps in analyzing the system requirements
completely.
b. Helps in identifying the risk factors involved in developing and deploying the
system
c. The feasibility study helps in planning for risk analysis
d. Feasibility study helps in making cost/benefit analysis which helps the
organization and system to run efficiently.
e. Feasibility study helps in making plans for training developers for
implementing the system.
In project development and feasibility studies stage of the SDLC, software engineers
and developers should be able to
Estimate Investment and Reward on the Project
In project planning, the investment on a certain project has to be revealed. This

will be the backbone of every project. For one, investment will dictate how much the
company will spend to create certain software. This is even truer for companies that
usually hire project based developers. Investment will dictate how many people will
be working for the project. Aside from investment, project planning and feasibility
studies should show how much the company will earn once the project is created. If
it’s just a tool for businesses, it should show how it can increase the productivity of
the employees and its actual impact in financial sense.
Analyze Feasibility
Researchers or proponents of the software will actually show why the software is
needed in the actual business sense. Statistical data will always play a crucial role in
proving why the particular software is good for public use. Most of the time,
researchers will be interviewing individuals in order to get their opinion if they will
use if that software is available in the market. It will also take a look at the possible
competition and how will the software be different compared to other companies.
Outline Technical Needs

In project planning, developers should be able to come up with the possible
technical needs of the software. These are very important since without them,
5
software development is nearly impossible. Within the realms of the budget,

developers should get the best devices to help them in project development.
2. System Analysis:
2.1 Introduction:
The citizenship information management system would be the base which

would become a role model for all the major towns and cities. This new system would
be possessing a new type of cluster based key management DB2 method in the
mainframe which would be accessible in the internet and in the respective government
offices as well.
Moreover each and every person time would be saved by entering the offices
and waiting in queue .Thus the complexity in submitting the information gets reduced
and the administration department work too gets reduced. In this project I designed
five modules which are minimum needs for the every person in the world. The
modules are Birth registration, Death registration, Ration card registration/Updating,
Passport application/Updating, PAN card application/Updating.
2.2 Existing System
In today’s trend of Citizenship Information system there is not any integrated

system that would incorporate all the basic amenities that a citizen would like to apply
for, update and retrieve as well. Such like are Birth & death registration , Passport
updating, Ration card application etc.
The current environment does possess the hi-tech sophisticated systems like web
based enquiry system for the passport, application, etc. But there are certain limits as
the government cannot afford to such a huge population a one-stop place where the
information regarding everything could be obtained and retrieved easily by the user
and by the government admin people as well.
2.3 Proposed System
6
The new system would be the base which would become a role model for all the
major towns and cities. This new system would be possessing a new type of cluster
based key management VSAM access method in the mainframe which would be
accessible in the internet and in the respective government offices as well. Moreover
each and every person time would be saved by entering the offices and waiting in
queue .Thus the complexity in submitting the information gets reduced and the
administration department work too gets reduced.
1. Birth registration
2. Death registration
3. Ration card application/Updating
4. Passport application/updating
5. PAN Card details / updating.
2.4 Advantages of Proposed System
The advantage for this type of system is
c.) The citizen need not wait in queues or spend a day in the corporation
office whereas he can get connected through the net and load his data.
d.) Those who are unable to get connected to internet (like illiterates) can
make use of the vending machines which would be available at the offices or
at the hospitals with a person to assist and thereby helping those in need.
e.) The advantage for this type of system is the death registration would be
made feasible in the hospital itself or through the internet, for this every
hospitals which right now possess internet connectivity can upload the data
and download the death registration certificate too.
2.4 Software and Hardware Requirement Specifications:
1. The hardware requirements : IBM PC & Compatibles , TN3270-
Mainframe environment with Internet
2. The Operating System : Mainframe ZOS/390
3. The Database to be used : DB2 and VSAM.
4. Programming Language : JCL,COBOL.

7
5. Online Transaction protocol : Customer Information communication
System (CICS)
6. Special software : TSO/ISPF, IBM UTILITIES
3. System Design
3.1 Introduction:
3.1.1 Use Case Diagram
Description
• A use case diagram shows a set of use cases, actors and their relationships.
• Usecase diagram illustrates the static view of a system.
• Usecase diagrams are important in organizing and modeling the behaviours of a
system.
3.1.2 Class Diagram:
Description
• A class diagram shows a set of classes, interfaces and collaborations and their
relationships.
• Class diagram are the most common diagrams found in modeling object
oriented systems.
• Class diagrams are used to illustrate the static design view of a system.
• Class diagrams that include active classes are used to address the static
process view of a system.
3.1.3 Sequence Diagram
Description
• A sequence diagram is an integration diagram that emphasizes the timing

order of messages.
8
• A sequence diagram shows a set of objects and the messages sent and
received by these objects.
• Sequence diagrams are used to illustrate the dynamic view of a system.
3.1.4 Collaboration Diagram
Collaboration diagrams belong to a group of UML diagrams called Interaction

Diagram. Collaboration diagrams, like Sequence Diagrams, show how objects interact
over the course of time. However, instead of showing the sequence of events by the
layout on the diagram, collaboration diagrams show the sequence by numbering the
messages on the diagram. This makes it easier to show how the objects are linked
together, but harder to see the sequence at a glance.
• Instance: An instance of a class shows a sample configuration of an object.

On the sequence diagram, each instance has a lifeline box underneath it
showing it's existence over a period of time.
• Message: The message indicates communication between objects. The order
of messages from top to bottom on your diagram should be the order in which
the messages occur.
3.1.5 Activity Diagram

An activity diagram shows the flow from activity to activity. The activity
diagram emphasizes the dynamic view of a system. It consists of activity states,
action states, transition, and object.Activity State is a kind of states in activity
diagram; it shows an ongoing non-atomic execution within a state machine. An
activity states can be further decomposed.
• Action State is a state of the system, each representing the execution of an
action. An action states can’t be further decomposed.
• Transition specifies the path from one action or activity state to the next
action or activity state. The transition is rendered as a simple directed line.
• Object is a concrete manifestation of an abstraction; an entity with a well

defined boundary and identity that encapsulates state and behavior; an instance
9
of a class. Objects may be involved in the flow of control associated with an

activity diagram.
3.2 Design Principles:
To produce the design for large module can be extremely complex task. The
design principles are used to provide effective handle the complexity of the design
process, effectively handling the complexity will not only reduce the effort needed for
design but can also reduce the scope of introducing errors during design.
For solving the large problems, the problem is divided into smaller pieces, using
the time-tested principle of “divide and conquer”. This system problem divides into
smaller pieces, so that each piece can be conquered separately. For software design,
the problem is to divide into manageable small pieces that can be solved separately.
This divide principle is used to reduce the cost of the entire problem that means the
cost of solving the entire problem is more than the sum of the cost of solving all the
pieces.
In design, the most important quality criteria are simplicity and

understandability. In this each the part is easily related to the application and that
each piece can be modified separately. Proper partitioning will make the system to
maintain by making the designer to understand, problem partitioning also aids design
verification.
Before implementation of the component, abstract is very useful to consider a

component at an abstract level, abstraction of a component describes the external
behavior of that component, without considering the internal behavior. Abstraction is
essential for problem partitioning and is used for exiting components plays an
important role in the maintenance phase. Abstraction is used in the reverse manner
for understanding design process of the system.
In the functional abstraction, the main four modules to taking the detail and
computing for further actions. In data abstraction it provides some services.
The system is a collection of modules means components. The highest-level

component corresponds to the total system. For design this system first following the
10
top down approach to device the problem in modules. In top-down design methods
often result in some form of stepwise refinement after divide the main modules; the
bottom-up approach is followed to designing the most basic or primitive components
to higher-level components. The bottom-up method operations starts from very
bottom.
In this system, the system is main module, because it consists of discrete

components such that each component supports a well-defined abstraction and if a
change to the component has minimal impact on other components. The modules are
highly coupled and coupling is reduced in the system, because the relationships
among elements in different modules are minimized.
 The Genesis of UML
Software engineering has slowly become part of our everyday life. From
washing machines to compact disc player, through cash machines and phones, most of
our daily activities use software, and as time goes by, the more complex and costly
this software becomes.
The demand for sophisticated software greatly increases the constraints

imposed on development teams. Software engineers are facing a world of growing
complexity due to the nature of applications, the distributed and heterogeneous
environments, and the size of programs, the organization of software development
teams, and the end-users ergonomic expectations.
To surmount these difficulties, software engineers will have to learn not only
how to do their job, but also how to explain their work to others, and how to
understand when others work is explained to them. For these reasons, they have (and
will always have) an increasing need for methods.
 Towards the Unified Modeling Language
The unification of object-oriented modeling methods became possible as

experience allowed evaluation of the various concepts proposed by existing methods.
Based on the fact that differences between the various methods were becoming
smaller, and that the method wars did not move object-oriented technology forward
any longer, Jim Rum Baugh and Grady Brooch decided at the end of 1994 to unify
11
their work within a single method: the Unified Method. A year later Ivar Jacobson,
the father of use cases, a very efficient technique for the determination of
requirements, joined them.
Brooch, Rum Baugh and Jacobson adopted four goals:
• To represent complete systems (instead of only the software portion) using

object oriented concepts.
• To establish an explicit coupling between concepts and executable code.
• To take into account the scaling factors that are inherent to complex and
critical systems.
• To creating a modeling language usable by both humans and machines.
The design principles are concerned with providing means to effectively handle
the complexity of the design process. Effectively handling the complexity will not
only reduce the effort needed for design but can also reduce the scope of introducing
errors during design.
The principles are
a. Problem Partitioning.
b. Problem Abstraction
c. Top down/bottom up Approaches
 Partitioning
Here the principle is’ divide and conquer’ overall problem is divided into
smaller pieces and the each pieces will be handled separately. Firstly the socket
program module is done and then database module is done and then the other
modules.
 Abstraction
This is a tool that helps the designer to consider a component at an abstract

level without being worried about the implementation details of the components. This
12
describes the outer behavior of the component. Here the connection between the
computers is tested using the Socket program
 Top down/Bottom up approaches
Top Down Design is basically a decomposition process, which focuses on the

flow of control. The first step is to study the overall aspects of the tasks at hand and to
break it into a number of independent modules. The second step is to break each one
of these modules further into independent sub-modules. The process is repeated one
to obtain modules. In this the project is divided into modules like Study Centers
Enquiry, Application Downloads, Syllabus and Material Downloads etc.
In a bottom-up design one first identifies and investigates parts of design that
are most difficult and necessary designed decision are made the remainder of the
design is tailored to fit around the design already chosen for crucial part. It vaguely
represents a synthesis process explained in previous section.
3.3 Design methodologies:
 SDLC METHDOLOGIES
This document play a vital role in the development of life cycle (SDLC) as it
describes the complete requirement of the system. It means for use by developers and
will be the basic during testing phase. Any changes made to the requirements in the
future will have to go through formal change approval process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model
of Software Development and Enhancement. This model was not the first model to
discuss iterative development, but it was the first model to explain why the iteration
models.
As originally envisioned, the iterations were typically 6 months to 2 years long.

Each phase starts with a design goal and ends with a client reviewing the progress
thus far. Analysis and engineering efforts are applied at each phase of the project,
with an eye toward the end goal of the project.
13
 The steps for Spiral Model can be generalized as follows:

• The new system requirements are defined in as much details as possible.
This usually involves interviewing a number of users representing all the
external or internal users and other aspects of the existing system.
• A preliminary design is created for the new system.
• A first prototype of the new system is constructed from the preliminary

design. This is usually a scaled-down system, and represents an
approximation of the characteristics of the final product.
• A second prototype is evolved by a fourfold procedure:
1. Evaluating the first prototype in terms of its strengths, weakness,

and risks.
2. Defining the requirements of the second prototype.
3. Planning an designing the second prototype.
4. Constructing and testing the second prototype.
• At the customer option, the entire project can be aborted if the risk is
deemed too great. Risk factors might involved development cost overruns,
operating-cost miscalculation, or any other factor that could, in the
customer’s judgment, result in a less-than-satisfactory final product.
• The existing prototype is evaluated in the same manner as was the

previous prototype, and if necessary, another prototype is developed from
it according to the fourfold procedure outlined above.
• The preceding steps are iterated until the customer is satisfied that the
refined prototype represents the final product desired.
• The final system is constructed, based on the refined prototype.
14
The following diagram shows how a spiral model acts like:
Fig 3.3.1-Spiral Model
 Study Of The System
In the flexibility of the uses the interface has been developed a graphics
concept in mind, associated through a browser interface. The GUI’S at the top level
have been categorized as
1. Administrative user interface
2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is
practically, part of the organizational activities and which needs proper authentication
for the data collection. The interfaces help the administrations with all the
15
transactional states like Data insertion, Data deletion and Data updating along with
the extensive data search capabilities.
3.4 Dataflow diagram:

A data-flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system. DFDs can also be used for the visualization of data
processing (structured design).On a DFD, data items flow from an external data
source or an internal data store to an internal data store or an external data sink, via an
internal process. A DFD provides no information about the timing or ordering of
processes, or about whether processes will operate in sequence or i n parallel. Data
items flow from an external data source or an internal data store to an internal data
store or an external data sink, via an internal process.
It is therefore quite different from a flowchart, which shows the flow of
control through an algorithm, allowing a reader to determine what operations will be
performed, in what order, and under what circumstances, but not what kinds of data
will be input to and output from the system, nor where the data will come from and go
to, nor where the data will be stored (all of which are shown on a DFD).
List of notations in DFD diagrams
S.NO SYMBOL NAME SYMBOL DESCRIPTION
This notation is used to represent

1 Function
the functions in the process
This notation represents the file

2 File/Database or database that are used in the
process
This rectangle is used to

3 Input/output represent the input given or
output we get in DFD diagrams
16
This notation is used to represent

4 Flow the flow or direction of the
process.
Project E-R diagram:

Nam Mothers
e Name
DOB
User id Fathers
Birth Name
Birth
Place
Passwo Registration
rd Addre
ss Death
Conform Place
Death
PW Va Sex Date
lid Addr
User ess
Name Death
Va
Login Registratio
Passwo lid
n User id
rd
Passwo Married/Unmarr
Va rd ied
lid
Head of
Family
Ration card
Addre User id
Application/Upda
ss
ting
Passwo
Family rd
Members
Va
Nam lid Mothers
e
Name
Addre PAN card Fathers
ss Registration/ Name
Updating
User id
Passwo
rd
Nam Va
e lid Mothers
Name
Com
Fathers
Address PASS Port
Registration/ Name
17
Updating User id
Passwo
Permanent
rd
Address Sex
E-R Diagram of System.
Description
The entity-relationship(ER) data model allows us to describe the data involved

in real-world enterprise in terms of objects and their relationships, and is widely used
to develop an initial database design.
The ER model is important for its role in database design. It provides useful
concepts that allows changing the detailed and informal description of what users
wanta precise and formal description that can be implemented in a DBMS. Within the
overall design process, the ER model is used in a phase called Conceptual database .
List of notations in E-R diagrams
SYMBOL
SYMBOL DESCRIPTION
NAME
This notation represents the

entities of the ER diagram.
Rectangle
The entity is thing or real
world object

Ellipse attributes of the entity i.e.the
characteristics of entities

Diamond relationship between two
entities
18
The line represents the link of

Line attributes to entities to
relationships
Table 4.3 ER Notations
 Entities
• Birth Registration
• Death Registration
• Ration card Application/Updating
• PAN card Application/Updating
• PASS Port Application/Updating
 Attributes
• Name
• DOB
• Fathers Name
• Mothers Name
• Birth Place
• Address
• Sex
• User Name
• Password
• Death Place
• Death Date
• Address
• Married/Unmarried
• Communication Address
• Permanent Address
• Head of The Family
• Family Members.
UML Diagrams:
19
UML stands for Unified Modeling language. A modeling language is a

language whose vocabulary and rules focus on the conceptual and physical
representation of a system. A diagram is a graphical representation of a set of
elements. Diagrams are used to view building blocks.UML diagrams are used to
visualize, specify, construct and document software architecture.
List of notations in UML diagrams
SYMBOL
NAME SYMBOL DESCRIPTION
Classes represent a collection of

Class
similar entities grouped together.
Association represents a static
Association
relationship between classes.
Aggregation is a form of
Aggregation association. It aggregates several
classes into single class.
Actors are the users of the system
Actor and other external entity that
Actor
react with the system.

A use case is a interaction
Use Case between the system and the
external environment.
Relation It is used for additional process
(Uses) communication.
Communicati It is the communication between

on various use cases.
It represents the state of a
State process. Each state goes through
various flows.
It represents the initial state of the
Initial State
object.
It represents the final state of the

Final State
object.
20
It represents the various control

Control Flow
flow between the states.
It represents the decision making
Decision Box
process from a constraint.
Components represent the

Component
Component physical components used in the
system.
Deployment diagrams use the
Node
Node nodes for representing physical

modules, which is a collection of
components.
A circle in DFD represents a state
Data
or process which has been
Process/State
triggered due to some event or
action.
External It represent any external entity
Entity such as keyboard, sensors etc

which are used in the system.
It epresent any communication
Transition
that occurs between the
Object Object lifelines represents the

processes.
Lifeline vertical dimension that objects

communicates.
It represents the messages
Message
exchanged.
Table 4.2 UML Symbols
21
Project UML Diagram:
Request for Register
Giving Authentication
New User Government

Existed user
CITIZEN Database
Entering the ID Filling the Particulars
Viewing the details
Providing the Social Security

number(ID)
Explanation:
Citizen is approach for the registration of citizenship; He may enter the proper
particulars in the form along with User-id and password. Once the Birth registration
form is successfully created then immediately he can get the User-id and Password.
By this user-id and password He can register their remaining applications. If the User
is a member then he may directly enters into form and update/modified his details and
finally it stores in the database.
Class Diagram:
Description
• A class diagram shows a set of classes, interfaces and collaborations and their
relationships.
• Class diagram are the most common diagrams found in modeling object
oriented systems.
• Class diagrams are used to illustrate the static design view of a system.
• Class diagrams that include active classes are used to address the static
process view of a system.
Project Class Diagram:
22
BirthRegistration
DeathRegistration
Date of Birth
Given Names
Sex
Family Name(Surname)
name of Childrens(If any)
Sex
Name of the Father
Date of Death
Name of the Mother
Date of Birth
Permanent Address
Age at date of Death
Place of Birth
Place of death(In Hospital,Locality with fulladdress
Usual residence of Diecese
Register for Birth Date()
Usual occupation during working profile
Was the deceased retired at date of death
Was the deceased a pensioner at date of death?
Place of birth
Never married
Rationcard Separated but not divorced
Name of Applicant Widow/Widower
Father's Name Second marriage(Place of marriege)
Present Address in full Children of Deceased (if applicable)
permanent Address Father of Deceased
Occupation/Designation Mother of Deceased
Name of Employer/Department Certification by Informant
Details of Femily Member(Adult …Minor…) Name of informant
Electrol Roll No./Census No. Relationship to deceased
L.P.G. Consumer. Name of witness
register for Death()

Getting the Certificate()
PANcardDetails/Updating
Full Name (Full expanded name : initials are not permitted)
Name you would like printed on the card
Father's Name
SocialSecurityNumber
Residential Address
Communication address name
Tel. No........................... Mailing Address
Sex Citizenship
Status of the Applicant(individual,Firm. Sex
Date of Birth / Incorporation / Agreement / Partnership Race/Ethnic Description
Registration Number (In case of Firms, Companies etc.) Date of Birth
Whether citizen of India ? Place of Birth
Are you a salaried employee(Govt or Private sector) Mothers name at her birth
Full name, address of the Representative Assessee Mothers Social Security Number
Fathers name
Fathers Social Security number
PassportApplication/Uadating
Name of applicant
In case of change of name
Sex
Date of Birth
Place of Birth : Village / Town
Father/Legal Guardian's Full Name
Mother’s Full Name
If married, Full Name of wife/husband
If divorced/widow/widower
Current Residential Address
Permanent Address with PIN code
Details of latest held/existing Ordinary / Diplomatic / Official passport(s)
Passport Office File No : ………/ Passport(s) No..………
Date and Place of Issue : …………………………/ Date of Expiry ……
In case passport was applied for and not issued, please give File No. & Date ……
Has your passport(s) ever been lost / damaged (if so attach FIR and give details)……
If you have returned to India on Emergency Certificate (EC)
EC No., date and place of issue & attach seizure memo in original …
Place & Country from where deported / repatriated and reason thereof : …
Educational Qualifications……………
Visible Distinguishing Mark, if any…………
Are you a citizen of India by : (B)irth/(D)escent/(R)egistration/(N)aturalisation; ……
“Emigration Check Not Required” status? Yes/No …………………
In case of minors (applicant below the age of 18),fathers : ...........,Mother..........
Particulars of person to be intimated in the event of death or accident. Name,Address.Phone
Verification()
Issueing the Passport()
Sequence diagram:
Sequence diagram are an easy and intuitive way of describing the behavior of
a system by viewing the interaction between the system and its environment. A
Sequence diagram shows an interaction arranged in a time sequence. A sequence
diagram has two dimensions: vertical dimension represents time; the horizontal
Dimension represents different objects. The vertical line is called is the object’s life
line. The lifeline represents the object’s existence during the interaction.
23
Project Sequence diagram.
Birth Death Rationcard PASSPORT PANCARD Data Base

: Citizen
Registration Registration reg/updating Regi/Updating Reg/Updating
Req for Birth reg

Sending request to the DataBase
Response from the DataBase
Responce to citizen
Submitting the details to Birth DB
Storing the Citizen details
Req for Death Registration

sending request to the DataBase
Responce from the DataBase

Responce to Informant
Submitting the details to death DB

Storing in the details
Req for Rationcard/Updating details

Sending req to the DataBase
Responce from the DB

Responce to Citizen
Submitting the details to the Rationcard DB

Storing in to the DB
Request for the Passport reg/Updating
Sending req to the DataBase
Responce to the Request

Responce to the citizen
Submitting the details to PASSPORT DB

Storing the details to DB
Req for the PANCARD Reg/Updating

Req from PANcard DB
Responce from DB
Responce to the citizen
Submitting the details to the PANCARD DB

Storing in to the DB
Collaboration diagram:
24
The collaboration diagram represents a collaboration, which is a set of objects

related in a particular context, and interaction, which is a set of messages exchanged
among the objects within the collaboration to achieve a designed outcome.
Project Collaboration diagram:
Birth
Registration Death
Registration
7: Req for Death Registration

4: Responce to citizen 11: Submitting the details to death DB
1: Req for Birth reg

5: Submitting the details to Birth DB 10: Responce to Informant
25: Req for the PANCARD Reg/Updating
29: Submitting the details to the PANCARD DB PANCARD
16: Responce to Citizen
Rationcard 2: Sending request to the DataBase Reg/Updating
6: Storing the Citizen details
reg/updating
28: Responce to 8:
thesending
9: Responce citizen
from the DataBase
request to the DataBase
13: Req for Rationcard/Updating details 12: Storing in the details
3: Response from the DataBase
17: Submitting the details to the Rationcard DB
: Citizen
14: Sending req to the DataBase

22: Responce to the citizen
18: Storing in to the DB 27: Responce from DB
26: Req from PANcard DB
19: Request for the Passport reg/Updating 30: Storing in to the DB
23: Submitting the15:
details to PASSPORT
Responce DB
from the DB
20: Sending req to the DataBase

24: Storing the details to DB
PASSPORT
Regi/Updating Data
Base
21: Responce to the Request
Data Base tables:
In my project there are five tables i.e like Birth registration, Death registration,
ration card registration/Updating, PAN card registration/Updating, PASSPORT
Registration/Updating.
 Birth Registration Table:
In birth registration table consists of fields like date of birth, sex,

fathers name, mother’s name, and permanent address, place of birth, hospital
address, religion, user id, password and Birth-id. Birth id will automatically
generates after successful completion of registration.
Project Table:
Birth table:
25
* DCLGEN TABLE(MAT039.BIRTHINF) *
* LIBRARY(MAT039.HARI.PROJECT.DCLGEN(BDCLGEN)) *
* LANGUAGE(COBOL) *
* QUOTE *
* LABEL(YES) *
* INDVAR(YES) *
* ... IS THE DCLGEN COMMAND THAT MADE THE FOLLOWING

STATEMENTS *
EXEC SQL DECLARE MAT039.BIRTHINF TABLE
( DOB DATE NOT NULL,
SEX CHAR(1) NOT NULL,
FATHERS_NAME CHAR(20) NOT NULL,
MOTHERS_NAME CHAR(20) NOT NULL,
PERMENT_ADDR VARCHAR(30) NOT NULL,
PLACE_OF_BIRTH CHAR(15),
HOSPITAL_ADDR VARCHAR(30),
PLACE_OF_BIRTH CHAR(15),
HOSPITAL_ADDR VARCHAR(30),
INF_NAME CHAR(15),
RELIGION CHAR(10) NOT NULL,
USER_ID VARCHAR(15) NOT NULL,
26
PASSWORD VARCHAR(15) NOT NULL,
BIRTH_ID INTEGER NOT NULL ) END-EXEC.
 Death Registration Table:
In death registration table consists of fields like Name of deceased,

date of death, date of birth, sex, age at death, fathers name, mother’s name,
and permanent address, place of birth, hospital address, religion, user id,
password and death-id. Death id will automatically generates after successful
completion of registration.
******************************************************************
* DCLGEN TABLE(MAT039.DEATHINF) *
* LIBRARY(MAT039.HARI.PROJECT.DCLGEN(DDCLGEN)) *
* LANGUAGE(COBOL) *
* QUOTE *
* LABEL(YES) *
* INDVAR(YES) *

STATEMENTS *
******************************************************************
EXEC SQL DECLARE MAT039.DEATHINF TABLE
( NAME_OF_DECEASED CHAR(20) NOT NULL,
DOD DATE NOT NULL,
DOB DATE NOT NULL,
AGE_AT_DEATH INTEGER NOT NULL,
27
PLACE_OF_DEATH CHAR(20) NOT NULL,
PLACE_OF_BIRTH CHAR(20) NOT NULL,
DECSED_FATHER_NAME CHAR(20) NOT NULL,
NAME_OF_INFORMANT CHAR(20) NOT NULL,
DEATH_ID INTEGER NOT NULL,
USER_ID (15) NOT NULL,
PASSWORD VARCHAR (15) NOT NULL
) END-EXEC.
Ration card table:
In ration card registration/Updating table consists of fields like Name

of applicant, communication address, family members details, date of birth,
sex, fathers name, mother’s name, and permanent address, place of birth,
religion, user id, password and ration-id. Ration card-id will automatically
generate after successful completion of registration.
******************************************************************
* DCLGEN TABLE(MAT039.RATIONINF) *
* LIBRARY(MAT039.HARI.PROJECT.DCLGEN(RDCLGEN)) *
* LANGUAGE(COBOL) *
* QUOTE *
* LABEL(YES) *
* INDVAR(YES) *

STATEMENTS *
28
******************************************************************
EXEC SQL DECLARE MAT039.RATIONINF TABLE
( NAME_OF_APPLICANT CHAR(20) NOT NULL,
RECENT_ADDR VARCHAR(30) NOT NULL,
PERMANT_ADDR VARCHAR(30) NOT NULL,
NAME_OF_FATHER CHAR(20) NOT NULL,
NAME_OF_MOTHER CHAR(20) NOT NULL,
OCCUPATION CHAR(15) NOT NULL,
FAMILY_DETAILS VARCHAR(40),
RATION_ID INTEGER NOT NULL,
PASSWORD VARCHAR(15) NOT NULL
) END-EXEC.
 Pan card information table:
In PAN card registration/Updating table consists of fields like Name of applicant,

communication address, family members details, date of birth, sex, fathers name,
mother’s name, and permanent address, place of birth, religion, user id, password and
PAN card-id. PAN card-id will automatically generates after successful completion of
registration.
******************************************************************
* DCLGEN TABLE(MAT039.PANINF) *
* LIBRARY(MAT039.HARI.PROJECT.DCLGEN(PNDCLGEN)) *
* LANGUAGE(COBOL) *
* QUOTE *
29
* LABEL(YES) *
* INDVAR(YES) *

STATEMENTS *
******************************************************************
EXEC SQL DECLARE MAT039.PANINF TABLE
COMM_ADDR VARCHAR(30) NOT NULL,
DOB DATE NOT NULL,
PAN_ID INTEGER NOT NULL,
PASSWORD VARCHAR(15) NOT NULL
) END-EXEC.
 PASSPORT table:
In PASSPORT registration/Updating table consists of fields like Name of

applicant, communication address, family members details, date of birth, sex,
fathers name, mother’s name, and permanent address, place of birth, religion,
user id, password and PASSPORT-id. PASSPORT-id will automatically generates
after successful completion of registration.
******************************************************************
* DCLGEN TABLE(MAT039.PASSINF) *
30
* LIBRARY(MAT039.HARI.PROJECT.DCLGEN(PSDCLGEN)) *
* LANGUAGE(COBOL) *
* QUOTE *
* LABEL(YES) *
* INDVAR(YES) *

STATEMENTS *
******************************************************************
EXEC SQL DECLARE MAT039.PASSINF TABLE
COMM_ADDRESS VARCHAR(30) NOT NULL,
MARITAL_STATUS CHAR(10) NOT NULL,
O_E_PASS_NUMBER INTEGER,
PLACE_OF_ISSUE CHAR(15),
PLACE_OF_ISSUE CHAR(15),
DATE_OF_EXPIRE DATE,
PASSPORT_ID INTEGER NOT NULL,
USER_ID CHAR(15) NOT NULL,
PASSWORD CHAR(15) NOT NULL
) END-EXEC.
31
32

Project Record

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Project Record

Transféré par

Droits d'auteur :

Formats disponibles

Citizenship information management system

The objective of this project is to create a mainframe environment based

The main modules are:

3. Ration card Registration.

4. PAN card Registration.

1.4 Introduction to modules:

1.4.1 Birth registration:

The advantage for this type of system is

1.4.3 Ration card application/Updating:

Electricity bill, Telephone bill.

1.4.4 PAN Card application/Updating:

1.4.5 Passport application:

1.5 Feasibility Study:

a. Feasibility study is made on the system being developed to analyze whether

Estimate Investment and Reward on the Project

In project planning, the investment on a certain project has to be revealed. This

Outline Technical Needs

software development is nearly impossible. Within the realms of the budget,

The citizenship information management system would be the base which

2.2 Existing System

In today’s trend of Citizenship Information system there is not any integrated

2.3 Proposed System

2.4 Advantages of Proposed System

The advantage for this type of system is

2.4 Software and Hardware Requirement Specifications:

1. The hardware requirements : IBM PC & Compatibles , TN3270-

Mainframe environment with Internet

2. The Operating System : Mainframe ZOS/390

3. The Database to be used : DB2 and VSAM.

4. Programming Language : JCL,COBOL.

5. Online Transaction protocol : Customer Information communication

6. Special software : TSO/ISPF, IBM UTILITIES

• A sequence diagram is an integration diagram that emphasizes the timing

3.1.4 Collaboration Diagram

Collaboration diagrams belong to a group of UML diagrams called Interaction

• Instance: An instance of a class shows a sample configuration of an object.

3.1.5 Activity Diagram

• Object is a concrete manifestation of an abstraction; an entity with a well

of a class. Objects may be involved in the flow of control associated with an

3.2 Design Principles:

In design, the most important quality criteria are simplicity and

Before implementation of the component, abstract is very useful to consider a

The system is a collection of modules means components. The highest-level

In this system, the system is main module, because it consists of discrete

 The Genesis of UML

The demand for sophisticated software greatly increases the constraints

 Towards the Unified Modeling Language

The unification of object-oriented modeling methods became possible as

Brooch, Rum Baugh and Jacobson adopted four goals:

• To represent complete systems (instead of only the software portion) using

• To establish an explicit coupling between concepts and executable code.

• To creating a modeling language usable by both humans and machines.

The principles are

c. Top down/bottom up Approaches

This is a tool that helps the designer to consider a component at an abstract

 Top down/Bottom up approaches

Top Down Design is basically a decomposition process, which focuses on the

3.3 Design methodologies:

As originally envisioned, the iterations were typically 6 months to 2 years long.

 The steps for Spiral Model can be generalized as follows:

• A preliminary design is created for the new system.

• A first prototype of the new system is constructed from the preliminary

• A second prototype is evolved by a fourfold procedure: