Credential Verifier And Civil Registry

Credential Verifier And Civil Registry is a web application that will helpful to the students as well as to the candidates who are usually apply online and Upload their documents or certificates for each applications.
Just using Credential Verifier And Civil Registry Application user can create their profiles and manage their documents easily. After that users will not need to upload their documents for each new application. They can just give their unique User Id and document ID to be verify for applications or recruitments.
This application also will be help full to organizations to publish their application forms for exams or recruitments and can verify documents of students or candidates easily by using ID of applicant.
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. This also acts as a consultancy agency to assist the public.

QuickSolve Technologies is built with the experienced IT Professionals to give the best services to their clients. Our clients are from different fields like financial, Manufacturing industries, Marketing firms, Constructions etc. We are always ready to give solutions to your problems.
Our Process
QuickSolve Technologies applies the well pre planned ways to develop the applications. We always focus in depth in our client's requirement and then start to develop application. Our development process applies like following manners..

' Analyzing the problem
' Market research
' Gathering requirements for the proposed business solution
' Devising a plan or design for the software-based solution
' Implementation (coding) of the software
' Testing the software
' Deployment
' Maintenance
Our industry experience, combined with the expert trainers are an ideal platform for students who are looking to get exposure to IT industry. Project Training for freshers is provided by experts of the respective fields. A project training certificate is provided at the end of the training. We even hire people after this training or help them get a suitable job in the ever growing IT industry.
Technologies
We provide development trainings in different languages and technologies.
' PHP
' JAVA
' ASP.NET
' VB.NET
' Joomla
' Android

Key Features
Along with project training we provide some extra key features like..
' Career Development
' Team Work Development
' Technical Enhancement
' Industry Based Learning
' Improvement Of Research & Development Skills
Services That We Provide
QuickSolve Technology provides the best services at any development platform with not compromising with quality. We follow a systematic process to accommodate the customers' requirements in the most efficient manner.

' Software Development
' Mobile Applications
' Web Design & Development

LIST OF FIGURES
Figure No Figure Name Page No.
6.1.1 Sequence Diagram 19
6.1.2 E-R Diagram 21
6.1.3 Context Diagram(level 0) 22
6.1.4 Flow diagramof login process(level1)
6.1.5 Flow diagram of maintain database(level 2)
6.1.6 Flow diagram of report generated(level 3)


LIST OF TABLES
Table No. Table Name Page No.
1 MemberRegRequestMaster 41
2 Login 42
3 MemberMaster 42
4 SecurityQuestion 42
5 UserTypeMaster 43
6 CityMaster 43
7 DocumentTypeMaster 43
8 DocumentDetail 44
9 OrgRegReq 44
10 OrgMemberDetail 44
11 OrgTypeMaster 45
12 AddmissionDeclaration 45
13 AddmissionReqDetail 45
14 AttachmentDetail 46
15 OnlineExamReqDetail 46
16 OnlineExamDeclaration 46
17 AddmissionResult 47
18 ResultDetail 47
19 ExamResult 47
20 PassportLicenseReq 48
21 ReqStatusMaster 48
22 ReqStatusDetail 48
23 ReqCancelHeader 49

No Abbreviations Name Abbreviations Description
1 PHP Hypertext Pre-processing Language
2 SQL Structured Query Language
3 IDE Integrated Development Environment
4 HTML Hyper Text Markup Language
5 CSS Cascaded Style Sheet
6 SDK Software Development Kit

TABLE OF CONTENTS

ACKNOWLEDGEMENT I
ABSTRACT Ii
COMPANY PROFILE Iii
LIST OF FIGURES V
LIST OF TABLES Vi
ABBREVIATIONS vii
1. INTRODUCATION 1
1.1 PROJECT SUMMARY 1
1.2 PROJECT PURPOSE 2
1.3PROJECT SCOP 2
1.4 OBJECTIVE 2
2. PROJECT MANAGEMENT 6
2.1 PROJECT PLANNING 6
2.1.1 PROJECT DEVELOPMENT APPROACH 6
2.1.2 PROJECT PLAN 6
2.1.3 MILESTONES AND DELIVERABLE 6
2.1.4 ROLES AND RESPONSIBILITY 6
2.1.5 GROUP DEPENDENCIES 7
2.2 PROJECT SCHEDULING 8
2.2.1 BASIC PRINCIPLE 8
2.2.2 WORK BREAKDOWN STRUCTURE 8
2.2.3 GANT CHART 8
2.3RISK MANAG EMENT 9
2.3.1 RISK IDENTIFICATION 9
2.3.2 RISK ANALYSIS 9
2.3.3 RISK PLANNING 9

3. SYSTEM REQUIREMENT 11
3.1 USER CHARACTERISTICS 11
3.2 HARDWARE AND SOFTWARE REQUIREMENT 11
3.3 CONSTRAINTS 11
3.3.1 REGULATORY POLICIES 11
3.3.2 INTERFACES OF OTHER APPLICATION 11
3.3.3 PARALLEL OPERATIONS 11
3.3.4 HIGHER ORDER LANGUAGE REQUIREMENT 11
3.3.5 RELIABILITY REQUIREMENT 12
3.3.6 CRITICALITY OF THE APPLICATION 12
3.3.7 SAFETY AND SECURITY CONSIDERATIONS 12
3.4 ASSUMPTION AND DEPENDENCIES 13
3.4.1 ASSUMPTION 13
3.4.2 DEPENDENCIES 13
3.5 TECHNOLOGY AND LITERATURE REVIEW 13
4. SYSTEM ANALYSIS 15
4.1 STUDY CURRENT SYSTEM 15
4.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM 15
4.3 REQUIREMENT OF THE NEW SYSTEM 15
4.3.1 REQUIREMENT ENGG.PROJECT' 15
4.3.2 REQUIREMENT ANALYSIS PROCESS 15
4.4 PROCESS MODEL 16
4.5 FEASIBILITY STUDY 17
4.5.1 TECHNICAL FEASIBILITY 17
4.5.2 OPERATIONAL FEASIBILITY 17
4.5.3 ECONOMICAL FEASIBILITY 17
4.5.4 SCHEDULING FEASIBILITY 17
4.6 FETURES OF THE NEW SYSTEM 18
5. SYSTEM DESIGN 19
5.1 SEQUENCE DIAGRAM 19
5.2 E-R DIAGRAM 20
5.3 DATA FLOW DIAGRAM 21
5.4 DATA DICTIONARY 32
6.IMPLEMENTATION PLANNING 40
6.1 IMPLEMENTATION ENVIRONMENT 52
6.2 CODING STANDARD 43
6.3 SCREEN SHOTS 51
7. TESTING 67
7.1 TESTING PLAN 68
7.2 TESTING STRATEGY 70
7.3 TESTING METHOD 71
7.4 TEST CASE 73
8 LIMITATION & FUTURE ENHANCEMENT 74
8.1 LIMITATIONS 74
8.2 ENHANCEMENT 74
9. CONCLUSION 75
10. REFERENCES 76

CHAPTER 1
INTRODUCTION
1.1 Project Summary:
The main purpose of our website Credential Verifier and Civil Registry is that it helps the people Sfor register or applies for their document online. 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. This also acts as a consultancy agency to assist the public. The main purpose of the web site is to reduce the effort by the candidate and save his time and avoid unwanted rushes at the government offices and assure a smooth working schedule at government offices.
By using this website user can create their own profile and manage their document easily & securely. User will not need to upload their document for each new application.
1. Candidate can register to the admin for register it contain all legal residents with the following details:
First name, Last Name , date of birth, sex, nationality, occupation , photo id ,residential physical address.
2. If it is fraud then admin can cancel their registration and if this is verify than admin gives them unique id. Co-ordination and data sharing across registration. generation of unique identifier linking individual records across registration.
3. After approval candidate can upload their valid documents into this website.
4. After the upload documents at once person should not need to upload their documents for each application.
5. If any user want an application for any type of online examination and recruitment than he can give their documents using this website.
EXAMPLE:
SBI Bank is registered and authenticated user in this application so that it can publish forms for recruitments. Now all the valid candidates or students who are registered in this website can apply to SBI bank from the application form. They will no need to upload their documents for this application process. They will just mention their unique ID in the application form. Now for further verification process SBI Bank will authorized to verify documents of each applicant's. And SBI bank can continue further process for recruitments by using this web application.

1.2 Purpose:
' This document will fully describe all the functional and non functional requirements, design constraints, and other factors necessary to provide a complete and comprehensive description of the requirements for the Credential Verifier And Civil Registry.. It also describes requirements should be used by the developer to implement the system.
' The main purpose of our website Credential Verifier and Civil Registry is that it helps the people for register or applies for their document online. 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.
' The main purpose of the web site is to reduce the effort by the candidate and save his time and avoid unwanted rushes at the government offices and assure a smooth working schedule at government offices.
1.3 Scope:
' Project has a big scope to do. Just using Credential Verifier And Civil Registry Application user can create their profiles and manage their documents easily.
' This application also will be help full to organizations to publish their application forms for exams or recruitments and can verify documents of students or candidates easily by using ID of applicant.
' We can apply for Passport and License using this. Our documents regarding Passport are verified by agents who are registered. And they give notification in this site. So we don't have to go their office again and again.
' So using this we can apply for different application and manage our document eaily and securely. We can search for any document & company detail which are register in our website.
1.4 Objectives:
The main objectives of this system are as below:
' User Requests Verification
If any visitor wants to be user of this website then he/she will have to make request to the admin with one identity proof. Then admin will verify and accept or reject request after that registration will be possible.

' Documents Management
Candidate can register and then they provide their unique id and unique profile using this profile they submit their document online then we divide their document as per the category wise. This module help to manage the documents.
' Applications Process
Application process includes the process regarding any applications as following:
' Admission Process
' Exams Application
' Passports Application
' License application
' Recruitments Process
Any organization who are registered they can recruit people for their organization through this web site.
' Reminders
Register person also take reminder and new update for new recruitment of any company which are register in our website and also new update about online exams etc.
' Searching
We can search for any document & company detail which are register in our website.
1.5 Technology and Literature Review:
1.5.1 Front End Tool
PHP
' PHP is a powerful tool for making dynamic and interactive Web pages.
' PHP is the widely-used, free, and efficient alternative to competitors such as Microsoft's ASP.
' In our PHP tutorial you will learn about PHP, and how to execute scripts on your server.
' The full form of PHP is 'Hypertext preprocessor'. Its original name was 'Personal Home Page'.
' Rasmus Lerdorf software engineer, Apache team member is the creator and original driving force behind PHP. The first part of PHP was developed for his personal use in late 1994.
' PHP is server-side scripting language, which can be embedded in HTML or used as a standalone.
' PHP doesn't do anything about what a page looks and sounds like. In fact, most of what PHP does is invisible to the end user.
' Someone looking at a PHP page will not necessarily be able to tell that it was not written purely in HTML, because usually the result of PHP is HTML.
' PHP is an official module of Apache HTTP server.
' PHP is fully cross-platform, meaning it runs native on several flavors of Unix, as well as windows and now on Mac OS X.

' Advantages of PHP

' Cost: PHP costs you nothing. It is open source software and doesn't need to purchase it development.

' Ease of use: PHP is easy to learn, compared to the others. A lot of Ready-made PHP scripts are freely available in market so, you can use them in your project or get some help from them.

' HTML 'Support: PHP is embedded within HTML; In other words, PHP pages are ordinary HTML pages that escape into PHP mode only when necessary. When a client requests this page, the web server preprocessor it. This means it goes through the page from top to bottom, looking for sections of PHP, which it will try to resolve.

' Cross-platform compatibility: PHP and MySQL run native on every popular flavor of UNIX and windows. A huge percentage of the world's HTTP servers run on one of the classes operating system.

' PHP is compatible with the three leading Web servers: Apache HTTP server for UNIX and windows, Microsoft internet information server, and Netscape enterprise server. It also wo with several lesser-known servers, including Alex Blits' fhttpd, Microsoft's Personal Web-server AOL server and Omnicentrix's application server.

' Stability: the word stable means two different things in this context:
' The server doesn't need to be rebooted often
' The software doesn't change radically and incompatible from release to release.
To our advantage, both of these apply to both MySQL and PHP.
' Speed: PHP is pleasingly zippy in its execution, especially when compiled as and Apache module on the UNIX side. Although it takes a slight performance hit by being interpreted ratio than compiled, this is far outweighed by the benefits PHP drives from its status as a web server module.
1.5.2 Back End Tool
MySQL :
' MySQL is a database server
' MySQL is ideal for both small and large applications
' MySQL supports standard SQL
' MySQL compiles on a number of platforms
' MySQL is free to download and use
' MySQL is the database of choice for a vast majority of Web developers who use PHP because of its efficiency and ease of use.
' MySQL is free and runs on multiple platforms, and its documentation is superb.
' The data in MySQL is stored in database objects called tables.
' A table is a collection of related data entries and it consists of columns and rows.
' Databases are useful when storing information categorically. A company may have a database with the following tables: "Employees", "Products", "Customers" and "Orders".
' Tools and Technologies

' IDE Tool: Macromedia Dreamweaver
' Application Architecture: Web Base
' Application Server: Apache (WAMP)
' Application Browser: Mozilla Firefox
' Coding Architecture: Three-Tier
' Scripting: HTML, CSS, JavaScript
' Code-behind Language: PHP (Hypertext Pre-processing Language)
' System Design Tools: VISIO
' Database: MySQL
' Platform: MS Windows 7

CHAPTER 2
PROJECT MANAGEMENT

2.1 PROJECT PLANNING
Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Time Scheduling feasibility for adding new modules and debugging old running system.
' Technical Feasibility
' Operation Feasibility
' Time Scheduling feasibility

2.1.1 Project Development approch:
Operational Feasibility is depended on the User who will be using this site once its ready. The site is made as simple as it can meet the operational feasibility. Any Proposed Project can be Beneficial only if it satisfied the Users Requirement.
Following are the points to describe the Operational Feasibility of the System:
' The web site has been design such it is not Resource intensive.
' The web site can be developed without much over head on minimal system configuration.
' Both user and customer can interact with System where they can easily act the functionality as per their role.
2.1.2 Project Plan :
Project Planning is an aspect of Project Management that focuses a lot on Project Integration. The project plan reflects the current status of all project activities and is used to monitor and control the project.
The Project Planning tasks ensure that various elements of the Project are coordinated and therefore guide the project execution.
Project Planning helps in.
' Facilitating communication
' Monitoring/measuring the project progress, and
' Provides overall documentation of assumptions/planning decisions
The Project Planning Phases can be broadly classified as follows:
' Development of the Project Plan
' Execution of the Project Plan
' Change Control and Corrective Actions

2.1.3 Roles And Responsibility :
' We are three persons involved in this project. For any software development there is always human organization structures. Our team structure is Democratic Decentralized, so there is no permanent leader in our team.
' We take decisions regarding our project's problems discussing with each other. It has been found that this project would require a large amount of communication sociability.
' There is no particular role has been defined between us. We have take responsibilities according to situation occur during the development of this project. System Analysis , Design, these all task have been completed by us.
2.1.3 Group Depenencies :

2.2 Project Scheduling:
Following the software engineering standard as specified for Web Engineering, we are using Incremental Model for the development of the Credential verifier And Civil Registry system. This process model is explained in brief below.
2.2.1 Basic Principle:
Scheduling the project task is an important project planning activity. It involves deciding which tasks would be taken up when based on the planned duration of required tests and collection of resources to complete those tasks projected completion date is calculated.
A Process Model for software engineering is chosen based on nature of the project and application, the methods and tools to be used and the controls that are required. The process model used in our project is 'Incremental Model'.

2.2.2 Work Breakdown Structure :
' Incremental LifeCycleModel :
Incremental model is an evolution of waterfall model. The product is designed, implemented, integrated and tested as a series of incremental builds. It is a popular model software evolution used many commercial software companies and system vendor. Incremental software development model may be applicable to projects where requirements are well defined, but realization may be delayed.

Advantages:

' Generates working software quickly and early during the software life cycle.
' More flexible - less costly to change scope and requirements.
' Easier to test and debug during a smaller iteration.
' Easier to manage risk because risky pieces are identified and handled during its iteration.
Disadvantages:
' Each phase of an iteration is rigid and do not overlap each other.
' Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle.

Justification:
' Requirements not completely clear
' Project development team is not experienced
' Likely to provide regular presentation at regular intervals of time
' Feedback from the project guide may cause improvement in the basic model
' Even if the model doesn't succeed we will gain experienced

2.3 Risk Management:
The Following is the Risk Management study report, which is under taken for the requirement traceability tools.
2.3.1 Risk Identification:
Risk identification is the first stage of risk management. It is concerned with discovering possible risks to the project. Risk identification may be carried out as a team process. To help the process, a checklist of different types of risk may be used. There are at least six types of risk that can arise:
' Technology risks: Risks that derive from the software or hardware technologies that are used to develop the system.
' People risks: Risks those are associated with the people in the development team.
' Organizational risks: Risks that derive from the organizational environment where the software is being developed.
' Tools risks: Risks that derive from CASE tools and other support software used to develop the system.
' Estimation risks: Risks that derive from the management estimates of the system characteristics and the resources required to build the system.
When we finished the risk identification process, following list of risks could occur which could affect the product, the process and the business.

2.3.2 Risk Analysis :
Risk Probability Effects
Organizational financial problems force reductions in the project budget. Low Catastrophic
Key staffs are ill at critical times in the project. Moderate Serious
Software components which should be reused contain defects which limit their functionality. Moderate Serious
Changes to requirements which require major design rework are proposed Moderate Serious
The organization is reconstructed so that different management are responsible for the project High Serious
The database cannot process as many transactions per second as expected Moderate Serious
The time required to develop the software is underestimated. High Serious
Customers fail to understand the impact of requirements changes. Moderate Tolerable
Required training of staff is not available Moderate Tolerable
The rate of defect repair is underestimated Moderate Tolerable
The size of the software is underestimated High Tolerable

2.3.3 Risk Planning:
The risk planning process considers each of the key risks that have been identified and identifies strategies to manage the risk. The different strategies fall into three categories:
' Avoidance strategies: Following these strategies means that the probability that the risk will arise will be reduced. Risk avoidance strategy is the strategy with defective components.
' Minimization strategies: Following these strategies means that the impact of the risk will be reduced. Example of risk minimization strategy is that for staff illness.
' Consistency plans: Following these strategies means that we were prepared for the worst and had a strategy in place to deal with it. An example of a contingency strategy is the strategy for organizational problems.

CHAPTER 3
SYSTEM REQUIREMENT STUDY
3.1 User Characteristics:
The intended users can be classified into three categories:
' Admin
' Organization
' User

' Admin

If any visitor wants to be user of this website then he/she will have to make request to the admin with one identity proof. Then admin will verify and accept or reject request after that registration will be possible.
Candidate can register and then they provide their unique id and unique profile using this profile they submit their document online then we divide their document as per the category wise. This module helps to manage the documents securely and easily.

' Organization

Different type of organization may be registered here for their application. Application process includes the process regarding any applications as following:
' Admission Process
' Exams Application
' Passports Application
' License application
' User

He can view the whole website detail like contact us, inquiry, serching after login. He can manage their document easily and very safely.He can apply for any application who are registered in this site. They can show the all notification , send by the organization.

3.2 Hardware and Software Requirement:
3.2.1 Hardware Requirements:
' Processor : Pentium IV or any Intel processor.
' RAM : 512 MB or more
' Hard Disk : 40 GB on system drive or more
' Monitor : Color Monitor
' Mouse : Mouse or compatible pointing device
' Keyboard : Any keyboard
3.2.2 Software Requirements:
' Server Side
' Macromedia Dreamweaver
' Apache (WAMP[window server for PHP])
' Microsoft SQL server 2008
' Microsoft Windows XP/ windows 7/windows vista

' Client Side
' Browser
' Microsoft Windows XP/ windows 7/windows vista

3.3 Constraints:
There are some constrains defined for the system as described below.
3.3.1 Regulatory Policies:
' The project must be completed within eight months.
' The system design must be user friendly.
' All the information about admin and users must be well managed.
3.3.2 Interface Of Other Application
The system should provide an interface that is available to the user through any of the browser. E.g. IE, a Mozilla etc Server module does have a user interface with administrator Database module does not have a user interface.

3.3.3 Parallel Operation
The various interfaces to communications such as local network protocols:
' FDDI- Fiber distributed data interface
' Ethernet/IEEE 802.3
' Token ring/IEEE 802.5

3.3.5 Reliability Requirements:
The main reliability requirement is the validation used. Without proper validation the system does not allow to enter that value into the database. For example, in the user id, the user cannot enter any dummy value, the validation checks that whether there is only 10 digit mobile number or not also any null value is not allowed in place of compulsory fields.
3.3.6 Criticality of the Application
' The application performs critical in case of more no of user.
' Hardware limitations.
' Database constraints.
3.3.7 Safety & security consideration
Without logging in, a user cannot access other facilities of the application. For Safety of user authentication we use session. When a user logs-off his session is destroyed so other user cannot access his/her data from the same system. All the data transfer over internet is use HTTP protocol
3.4 Asssumpition And Dependencies
3.4.1 Assumptions:
' Administrator is present all the time.
' Administrator handles the database and the user privileges.
' The Navigation menu is easy to navigate.
' The user should be capable of providing login name and password.
' Every user regularly uses the system.
' The server used for data storing is always secured.
3.4.2 Dependency:
' Every new user is registered by administrator for accessing the system.
' All the users of the system are given user privileges according to their post in the company.
' All the normal user of system will be assigned a specific set of privileges. According to these privileges each and every user will be allowed to access to predefined set of features.
' The privileges that are assigned to each user will be decided by the administrator.

CHAPTER 4
SYSTEM ANALYSIS
4.1 Study Current System
If any person want to apply for any application than they have to go for the office and their they face much difficulties. They have to go the government office again & again to verify and for approval of their documents.

4.2 Problem And Weakness Of Current System
' It takes too much time to verify.
' It is difficult for person to handle such situations.
' Difficult to manage hard copies of documents.
' User interaction becomes difficult.

4.3 Requirement Of The New System
The main purpose of our website Credential Verifier and Civil Registry is that it helps the people for register or applies for their document online. 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. This also acts as a consultancy agency to assist the public. The main purpose of the web site is to reduce the effort by the candidate and save his time and avoid unwanted rushes at the government offices and assure a smooth working schedule at government offices.
By using this website user can create their own profile and manage their document easily & securely. User will not need to upload their document for each new application.
4.3.1 Requirement Analysis Process
The main purpose of our website Credential Verifier and Civil Registry is that it helps the people for register or applies for their document online. 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. This also acts as a consultancy agency to assist the public. The main purpose of the web site is to reduce the effort by the candidate and save his time and avoid unwanted rushes at the government offices and assure a smooth working schedule at government offices.
By using this website user can create their own profile and manage their document easily & securely. User will not need to upload their document for each new application.
1. Candidate can register to the admin for register it contain all legal residents with the following details:
First name, Last Name , date of birth, sex, nationality, occupation , photo id ,residential physical address.
2. If it is fraud then admin can cancel their registration and if this is verify than admin gives them unique id. Co-ordination and data sharing across registration. generation of unique identifier linking individual records across registration.
3. After approval candidate can upload their valid documents into this website.
4. After the upload documents at once person should not need to upload their documents for each application.
5. If any user want an application for any type of online examination and recruitment than he can give their documents using this website.

4.4 Process Model
' Incremental LifeCycleModel :
Incremental model is an evolution of waterfall model. The product is designed, implemented, integrated and tested as a series of incremental builds. It is a popular model software evolution used many commercial software companies and system vendor. Incremental software development model may be applicable to projects where requirements are well defined, but realization may be delayed.


Fig :4.2.1 Incremental LifeCycle Module
Advantages:

' Generates working software quickly and early during the software life cycle.
' More flexible - less costly to change scope and requirements.
' Easier to test and debug during a smaller iteration.
' Easier to manage risk because risky pieces are identified and handled during its iteration.
Disadvantages:
' Each phase of an iteration is rigid and do not overlap each other.
' Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle.
Justification:
' Requirements not completely clear
' Project development team is not experienced
' Likely to provide regular presentation at regular intervals of time
' Feedback from the project guide may cause improvement in the basic model
' Even if the model doesn't succeed we will gain experienced
4.5 Feasibility Study
Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Time Scheduling feasibility for adding new modules and debugging old running system.
' Technical Feasibility
' Operation Feasibility
' Time Scheduling feasibility
4.5.1 Technical Feasibility
Technical feasibility includes whether the technology is available in the market for development and its availability. The assessment of technical feasibility must be based on an outline design of system requirements in terms of input, output, files, programs and procedures.
This can be qualified in terms of volumes of data, trends, frequency of updating, cycles of activity etc, in order to give an introduction of technical system. Considering our project it is technical feasible.
The system offers greater levels of user friendliness combined with greater processing speed. Therefore, the cost of maintenance can be reduced. Since processing speed is very high and the work is reduced in the maintenance point of view management convince that the project is operationally feasible.
4.5.2 Operational Feasibility
Operational Feasibility is depended on the User who will be using this site once its ready. The site is made as simple as it can meet the operational feasibility. Any Proposed Project can be Beneficial only if it satisfied the Users Requirement.
Following are the points to describe the Operational Feasibility of the System:
' The web site has been design such it is not Resource intensive.
' The web site can be developed without much over head on minimal system configuration.
' Both user and customer can interact with System where they can easily act the functionality as per their role.

4.5.3 Economical Feasibility
' Here cost-benefit analysis of system is done here. The entire cost schedules to the system i.e. direct and indirect costs are calculated and it is checked to see whether it is affordable or not. This checks the economic feasibility. Our system will need software's like Macromedia Dreamweaver. This software is easily available and will be affordable to use for developing the system.
' So our system will be completed in required time and will be completed with affordable amount of money. So the system will be economically feasible given the conditions and functionality completed in given amount of time.

4.5.4 Scheduling Feasibility
Time scheduling type of Feasibility includes a measure of how reasonable the projected with respect to time aspect, when Developing web site. it is difficult to measure such things as software Complexity, quality and to estimate the amount of effort it will take to complete project.
Time duration was 4 Months. Analysis and Designing were also crucial phases because of different combinations of reports, to manage all the information of daily coverage on a single page. It was also a crucial task to manage huge amount of Database.

4.6 Fetures Of The New System
' physical person is registered in the population register right from his birth, and all future documents are issued on the basis of PIN assigned to him from birth.
' Physical person may be identified at any moment.
' Automatization of the registration process.
' Reduction of the number of mistakes due to human factor.

CHAPTER 5
SYSTEM DESIGN
5.1 Sequence Diagram

5.1 Sequence Diagram


Expansion : Sequence Diagram

5.2 E-R Diagram

5.2 E-R Diagram '
5.3 Data Flow Diagram

5.3.1 Context Diagram (LEVEL 0)

5.3.2 Flow Diagram Of Login Process (LEVEL 1)


5.3.3 Expansion Of Login Process (LEVEL 1)


5.3.4 Second Diagram of Expansion Member (LEVEL 1)


5.3.5 Second Diagram of Expansion Organization (LEVEL 1)


5.3.6 Flow Diagram Of Maintain Database (LEVEL 2)


5.3.7 Flow Diagram Of Exam Process (LEVEL 2)


5.3.8 Flow Diagram Of Admission Process (LEVEL 2)


5.3.9 Flow Diagram Of Passport Or License Process (LEVEL 2)


5.3.10 Flow Diagram Of Report Generated (LEVEL 3)

5.4 Data Dictionary :
A data dictionary is a catalog a repository of the elements in a system. As the name suggested, these elements center around data and the way they are structured to meet user requirements and organization needs. In a data dictionary you will find a list of all the elements composing the data flowing through a system. The major elements are data flow, data stores and processes. The data dictionary stores details and descriptions of these elements.
If analysts want to know how many characters are in a data item, by what other names it is referenced in the system, of where it is used in the system, they should be able to fine the answers in a property developed data dictionary.

1. MemberRegReqMaster Table

Table name : MemberRegRequestMaster
Description: This table is useful for store new requested member.
Field Constrains DataType Description
RequestId Primary key Number(1) Request Id of user
Name Not null Varchar(20) Name of user
Gender Not null Varchar(6) Gender of user
ParentName Not null Varchar(20) Parent name of user
Address Not null Varchar(200) address of user
PhotoPath Not null Varchar(100) Photo path of user
IdentityDocpath Not null Varchar(100) Docpath of users identity
ResidentialProofCopypath Not null Varchar(100) Residencial proof of user
ParentVoterIdpath Not null Varchar(10) User's parents voterId
Descreption Not null Varchar(200) Description of user
CityId Foreign key Number(10) City Id of user
PinCode Not null Number(7) Pincode of user's city
EmailId Not null Varchar(30) Emailed of user
Username Not null Varchar(20) Unique username
DateofReq Not null Date Date of request

2. Login Table
Table name: Login
Description: This table is useful for store login information.
Field Constrains DataType Description
Username Primary key Varchar(20) User name
Password Not null Numeric(10) Password of user
SecurityQuestionId Foreign key Varchar(10) Security question Id
SecurityAns Not null Numeric(20) Security answer
UserTypeId Foreign key Numeri(10) Id of user
Is_approved Not null Numeric(11) Approved Or Not
3. SecurityQuestion Table
Table name: SecurityQuestion
Description: This table is useful for store information about securityQuestion which are fill by register member.
Field Constrains DataType Description
SecurityQuestionId Primary key Numeric(10) Securityquestion identification no.
SecurityQuestion Not null Varchar(10) Securityquestion list
4. UserTypeMaster Table
Table name: UserTypeMaster
Description: This table is useful for store information about different type of user table for example admin, organization info etc.

Field Constrains DataType Description
UserTypeId Primary key Numeric(10) Id of user
UserTypeName Not null Varchar(20) Name of user
5. CityMaster Table
Table name: CityMaster
Description: This table is useful for store information about city information of register member.
Field Constrains DataType Description
CityId Primary key Numeric(10) cityId of user
CityName Not null Varchar(20) City name of user
6. member_documents
Table name: member_documents
Description: This table is useful for store document information of register member.
Field Constrains DataType Description
Document_Id Primary key Numeric(10) Document id of user
User_type_id Foreign key Numeric(10) Member id of user
Username Not null Varchar(20) Username of member
Document_title Foreign key Varchar(30) Document name of user
Document_path Not null Varchar(100) Path of the Document
7. OrgRegReq Table
Type name: This table is useful for store information about new register organization.
Field Constrains DataType Description
OrgRegReqId Primary key Numeric(10) Organization request id
OrgName Not null Varchar(20) Organization name
Address Not null Varchar(100) Address of organization
RegLicensepath Not null Varchar(100) Registerlicense path of organization
CityId Foreign key Numeric(10) City id of organization
Pincode Not null Numeric(7) Pincode of city of organization
ContactPersonName Not null Varchar(20) Contact name of person of org.
EmailId Not null Varchar(20) Email id of organization
ContactNumber Not null Numeric(10) Contact number of organization
Username Not null Varchar(10) Username Of The Organization
OrgTypeId Primary key Numeric(10) Organization type id

8. orgdocuments
Table name: orgdocuments
Description: This table is useful for store document information of register organization.
Field Constrains DataType Description
document_Id Primary key Numeric(10) Document id of user
User_type_id Foreign key Numeric(10) Member id of user
User_id Not null Varchar(20) Username of member
Document_title Foreign key Varchar(30) Document name of user
Document_path Not null Varchar(100) Path of the Document
9.OrgMemberDetail Table
Table name: OrgMemberDetail
Description: This table is useful for orgmemberdetail.
Field Constrains DataType Description
OrgMemberId Primary key Numeric(10) Organization member id
OrgRegReqId Foreign key Numeric(10) Org register request id
UserName Foreign key Varchar(20) User name of org.
10. OrgTypeMaster Table
Table name: orgtypemaster
Description: This table is useful for different type of org detail.
Field Constrains DataType Description
OrgTypeId Primary key Numeric(10) Organization type id
OrgTypeName Not null Varchar(20) Org type name
11. AdmissionDeclaration Table
Table name: AdmissionDeclaration
Description: This table is useful for store admission detail.
Field Constrains DataType Description
AdmissionProcId Primary key Numeric(10) Admission process id
OrgMemberId Foreign key Numeric(10) Organizationmember id
Subject Not null Varchar(10) Subject of admission
Formpath Not null Varchar(100) Form path of admission
Description Not null Varchar(2000 admission detail
LastDateOfSubmission Not null Date Last date of submission
DateOfUpload Not null Date Date of upload forms

12. AdmissionReqDetail Table
Table name: AdmissionRequestDetail
Description: This table is useful for store information about new admission request.

Field Constrains DataType Description
MemberId Primary key varchar(10) Member id
AdmissionProcessId Primary key Numeric(10) Admission process id
DateofApplication Not null Date Date of admission
ApplicationFormpath Not null Varchar(100) Path of form
AttachmentId Foreign key Numeric(10) Attachmentid of admission form
13.AttachmentDetail Table
Table name:AttachmentDetail
Description:This table is useful for store attachment information.
Field Constrains DataType Description
AttachmentId Primary key Numeric(10) id of documents
MemberId Primary key varchar(10) Member id
Document_Id Primary key Numeric(10) Document id
DateOfAttachment Not null Date Date of attachment
14.OnlineExamReqDetail Table
Table name: OnlineExamReqDetail
Description: This table is use to store new online exam detail.

Field Constrains DataType Description
MemberId Primary key Varchar(10) Member id of online exam
ExamId Primary key Numeric(20) Email id of member
DateOfExamForm Not null Date Date of exam forms
LastDateOfSubmission Not null Date Last date of submission
AttachmentId Foreign key Numeric(10) Attachment id of document
Description Not null Varchar(200) online exam detail

15.OnlineExamDeclaration Table
Table name:OnlineExamDeclaration
Description:This table is use to store online exam detail.

Field Constrains DataType Description
ExamId Primary key Numeric(10) exam id of member
OrgId Foreign key Numeric(10) Organization id
LastDate Not null Date Last date of exam
UploadDate Not null Date Upload date of document
Formpath Not null Varchar(100) Form path of exam
Description Not null Varchar(200) Description of online exam
16.AdmissionResult Table
Table name: AdmissionResult
Description: This Table is use to store Admission detail.
Field Constrains DataType Description
ResultId Primary key Numeric(10) Result id of member
AdmissionProcessId Foreign key Numeric(10) Id of member
DateOfResult Not null Date Date of result
Description Not null Varchar(200) Description of admission result

17.ResultDetail Table
Table name: ResultDetail
Description: This table is use to store Result detail.
Field Constrains DataType Description
ResultId Primary key Numeric(10) Result id
Username Primary key Varchar(30) Username forMember

18.ExamResult Table
Table name:ExamResult
Description:This table is use to store examresult detail.

Field Constrains DataType Description
ResultId Primary key Numeric(10) Result id
ExamId Foreign key Numeric(10) Exam id
DateOfResult Not null Date Date of result
Descreption Not null Varchar(200) Description of exam result

19.PassportLicense Req Table
Table name:PassportLicense Req
Description:This table is use to store new passport/license request.

Field Constrains DataType Description
PassportLicensReqId Primary key Numeric(10) Passport license request id
MemberId Foreign key Varchar (10) Member id
AttachmentId Foreign key Numeric(10) Attachment id
ReqType Not null Varchar(20) Request type of member
OrgMemberId Foreign key Numeric(10) Organization member id
DateOfReq
Description Not null
Not null date
Varchar(200) Date of request
passport license request detail
20.ReqStatusMaster Table
Table name: ReqStatusMaster
Description: This table is use for store new reqstatus master detail.

Field Constrains DataType Description
StatusId Primary key Numeric status id of member
StatusName Not null Varchar Status name
21.ReqStatusDetail Tabe
Table name: ReuestStatusDetail
Description: This table is use to store Request status detail.
Field Constrains DataType Description
PassportLicenseReqId Primary key Number Passport license request id
StatusId Primary key Number Status id
DateOfStatus Not null Number Date of status
Description Not null Varchar request status detail
22.Reminder
Tablename:Reminder
Description: This table is use to remind Request detail.
Field Constrains DataType Description
Reminderid Primary key Numeric(10) Reminder Id
Username Primary key Varchar(20) Username for the member
Dateofreminder Not null Date Date Of Reminder
Subject Not null Varchar(100) Subject
Description Not Null Varchar(200) Description about reminder

CHAPTER 6
IMPLEMENTATION PLANNING
6.1 Implementation Environment
The Project was a result of a single consensus .The team was having one member. The team structure depends on the management style of the organization, the number of people in the team, their skill levels and the problem difficulty. Uniform GUI Design
' SOLServer R2 Management Studio name and authentication required for
normal/network base access.
' Internet support
6.1.1 Implementation Planning
Implementation phase requires precise planning and monitoring mechanism in order to ensure schedule and completeness. We developed the software in various sub phases in Implementation Phase.
6.1.2 Database Implementation
This phase involved creation of database table and specifying relationships among them in SQL server 2008
6.1.3 Core Class Implementation
First we decided to implement the core system classes which will facilitate the further implementation. In this class we developed the database connection codes, data adapter codes, data reader codes,data binding codes,grid view display codes, insert, update, delete codes, Modal pop up viewer codes.
6.1.4 User Components Implementation
Motive behind this separate phase is to focus on the Reusability. In these phase we have tried to developed reusable user interface components.
6.1.5 Module Implementation
This Subsystem involves various administration specific services like giving rights to admin and users, Creating Users,managing assets and Database Management.

6.2 CODING STANDARDS
6.2.1 Purpose Of Coding Standards And Best Practices
Best practices are a set of informal rules that the software development community has learned over time to improve the quality of applications and simplify their maintenance. They can be broken into many levels based on the coding language, the platform, the target environment and so forth. Using bestpractices for a given situation greatly reduces the probability of introducing errors into your applications, regardless of which softwaredevelopment model is being used to create that application.
There are coding standards that originated from the intensive study of industry experts who analyzed how bugs were generated when code was written and correlated these bugs to specific coding practices. They took these correlations between bugs and coding practices and came up with a set of rules that when used prevented coding errors from occurring. These standard practices offer incredible value to software development organizations because they are pre-packaged automated error prevention practices; they close the feedback loop between a bug and what must be done to prevent that bug from recurring.
Best practices gives you a way to analyze your source code so that certain rules and patterns can be detected automatically and that the knowledge obtained through previous years of experience by industry experts is implemented in an appropriate way.
6.2.2 Naming Convention And Standards
The terms Pascal Casing and Camel Casing are used throughout this document.
PASCAL CASING:-First character of all words are Upper Case and other characters are lower case.
Example: BackColor
CAMEL CASING: - First character of all words, except the first word is Upper Case and other characters are lower case.
Example: backColor
1. User Pascal Casing for Class names
public class HelloWorld
{
... }
2. Use Camel Casing for method names
void sayHello(string name)
{
...
}
3. Use Camel Casing for variable names
int totalCount=0;
4. Use the prefix 'I' with Camel casing for interface (Example: IEntity).
5. Use Meaningful, descriptive words to name variables. Do not use
Abbreviations.
Good:
string address
int salary
Not Good:
stringaddr
intsal
6. Do not use single character variable name like i, n, s etc. use name like index, temp.
7. One exception in this case would be variables used for iterations in loops:
for (int i=0; i<count; i++)
{
}
8. If the variable is used only as a counter for iteration and is not used anywhere else in the loop, may people still like to use a single char variable (i) instead of inventing a different suitable name.
9. All member variables must be prefixed with underscore (_) so that they can be identified from other local variables.
10. Do not use variable names that resemble keywords.
11. Prefix boolean variables, properties and methods with 'is' or similar prefixes.
Example: private bool _isFinished
12. File name should match with class name.
6.2.3 Sample Coding
FOR REGISTRATION:
<?php
session_start();
include("Templates\ClassFile.php");
include("Templates\connect.php");
$Reqid=0;
//$obj=new Register();
global $msg;
$msg="";
if (isset($_POST["Submit"]))
{
if ($_POST["Submit"]=="Next" && isset($_POST["Submit"]))
{
$Reqid=$_POST["Reqid"];
$Mname=$_POST["Mname"];
$Gen=$_POST["Gen"];

$Pname=$_POST["Pname"];
$Ads=$_POST["Ads"];
//$Photopath=$_POST["Photopath"];
//$Docpath=$_POST["Docpath"];
//$Respath=$_POST["Respath"];
// $Pvoterpath=$_POST["Pvoterpath"];
//$Des=$_POST["Des"];
$Cid=$_POST["s1"];
$Pcode=$_POST["Pcode"];
$Eid=$_POST["Eid"];
$Reqdate=$_POST["Reqdate"];
$Uname=$_POST["Uname"];

//$Uname=$_POST["Uname"];
// $Pass=$_POST["Pass"];
// $Cpass=$_POST["Cpass"];
// $Secque=$_POST["Secque"];
// $Secans=$_POST["Secans"];
//$Utype=$_POST["Utype"];


if ($Reqid=="" || $Mname=="" || $Gen=="" || $Pname=="" || $Ads=="" || $Cid=="" || $Pcode=="" || $Eid=="" || $Reqdate=="" || $Uname=="" )
{
$msg="All Fields Are Necessary..";
}


else
{

$_SESSION["Reqid"]= $Reqid;
$_SESSION["Mname"]= $Mname;
$_SESSION["Gen"]= $Gen;
$_SESSION["Pname"]= $Pname;
$_SESSION["Ads"]= $Ads;
//$_SESSION["Photopath"]= $Photopath;
//$_SESSION["Docpath"]= $Docpath;
//$_SESSION["Respath"]= $Respath;
//$_SESSION["Pvoterpath"]= $Pvoterpath;
//$_SESSION["Des"]= $Des;
$_SESSION["Cid"]= $Cid;
$_SESSION["Pcode"]= $Pcode;
$_SESSION["Eid"]= $Eid;
$_SESSION["Reqdate"]= $Reqdate;
$_SESSION["Uname"]= $Uname;


header("Location: reg1.php");
}

}
}
?>
<?php
getNextId();

$today = date("Y-m-d");
?>


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><!-- InstanceBegin template="Templates/myTemplate.dwt" codeOutsideHTMLIsLocked="false" -->
<head>
<title>Credential Verifier</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<link href="Templates/style.css" rel="stylesheet" type="text/css" />
<meta name="keywords" content="free templates, Business Website, Free CSS Template, CSS, HTML" />
<meta name="description" content="Business Template is a free css template provided by templatemo.com" />
<link href="Templates/templatemo_style.css" rel="stylesheet" type="text/css" />
<link href="Templates/css/jquery.ennui.contentslider.css" rel="stylesheet" type="text/css" media="screen,projection" />

<script language="javascript" type="text/javascript">
function clearText(field)
{
if (field.defaultValue == field.value) field.value = '';
else if (field.value == '') field.value = field.defaultValue;
}
</script>
</head>
<body>
<div id="topPan">
<a href="http://www.free-css.com/"><img src="Templates/cube%20logo.png" title="Credential Verifier & Civil Registry" alt="Civil Registry" width="300" height="30" border="0"/></a>
<ul>
<li><a href="index.php"><img src="Templates/images/h1.jpg" /> </a></li>
<li><a href="Services.html"><img src="Admin/images/srvs.jpg" /></a></li>
<li><a href="mainreg.php"><img src="Admin/images/reg.jpg" /></a></li>
<li><a href="contact.html/"><img src="Admin/images/cntus.gif" /></a></li>
<li><a href="Templates/feedback.html/"><img src="Admin/images/fedbk.gif" /></a></li>
</ul>
</div>


<div id="tempatemo_content_wrapper">

<div id="templatemo_content">

<div class="recent_projects">

<div class="project_slideshow">

<div id="one" class="contentslider">
<div class="cs_wrapper">
<div class="cs_slider">

<div class="cs_article">
<a href="#">
<img src="Templates/images/admission23.jpg" alt="Screenshot 1" />
</a>
</div><!-- End cs_article -->

<div class="cs_article">
<a href="#">
<img src="Templates/images/online%20examy.jpg" alt="Screenshot 2" />
</a>
</div><!-- End cs_article -->

<div class="cs_article">
<a href="#">
<img src="Templates/images/admission.jpg" alt="Screenshot 3" />
</a>
</div><!-- End cs_article -->

<div class="cs_article">
<a href="#">
<img src="Templates/images/images%20license.jpg" alt="Screenshot 4" />
</a>
</div><!-- End cs_article -->

</div><!-- End cs_slider -->
</div><!-- End cs_wrapper -->
</div><!-- End contentslider -->
<!-- Site JavaScript -->
<script type="text/javascript"
src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>
<script type="text/javascript" src="Templates/js/jquery.easing.1.3.js"></script>
<script type="text/javascript" src="Templates/js/jquery.ennui.contentslider.js"></script>
<script type="text/javascript">
$(function() {
$('#one').ContentSlider({
width : '530px',
height : '200px',
speed : 800,
/* easing : 'easeInOutExpo' */
/* easing : 'easeOutQuad' */
easing : 'easeInOutBack'
});
});
</script>
<script src="Templates/js/jquery.chili-2.2.js" type="text/javascript"></script>
<script src="Templates/js/chili/recipes.js" type="text/javascript"></script>


</div>

</div>
<div id="bodyPan">
<div id="leftPan">
<div id="leftmemberPan">
<!-- InstanceBeginEditable name="login" -->

<h2>Login</h2>

<form name="login" id="login" method="post">
<label>Username</label>
<input name="Uname" type="text" id="Uname" />
<label class="passwordpadding">Password</label>
<input name="Pass" type="password" class="fieldpadding" id="Pass" />
<label>
<input name="Submit" type="submit" class="contentslider" value="login" />
</label>
<div id="leftPango">
<p class="textposition"><a href="http://www.free-css.com/">Register now</a></p>
<input type="submit" class="gobutton" value="Go" />
</div>
</form>
<!-- InstanceEndEditable -->

</div>
<div id="headerPan">
<div id="headerPanleft">
<!-- InstanceBeginEditable name="p1" -->
<div id="ourblog">


<h2>Our blog</h2>
<p>Desktop publishing</p>
<a href="http://www.free-css.com/">&nbsp;</a> </div>
<div id="possib">

<h2>possibilities</h2>
<p>Desktop publishing</p>
<a href="http://www.free-css.com/">&nbsp;</a> </div>
<div id="solution">

<h2>Solutions</h2>
<p>Desktop publishing</p>
<a href="http://www.free-css.com/">&nbsp;</a> </div>
<!-- InstanceEndEditable -->
</div>
</div>
<div id="rightPan">
<div id="rightbodyPan"><!-- InstanceBeginEditable name="head" -->
<div id="registrationform">
<form id="form1" name="form1" method="post" >
<table width="449" border="3">
<tr>
<th height="0" scope="col"><div style="font-size: 16px">
<div align="left"><span style="font-weight: bold">Personal Info</span> </div>
</div></th>
</tr>
<tr>
<td width="147"><span style="font-family: &quot;Times New Roman&quot;, Times, serif; font-size: 14px">RequestId</span></td>
<td width="162"><input name="Reqid" type="text" size="30" value="<?php echo $Reqid; ?>"/>
<?php
function getNextId()
{
$qry = mysql_query("Select max(RequestId) from memberregreqmaster");
$res=mysql_fetch_row($qry);
if($res) {
global $Reqid;
$Reqid=$res[0]+1;

}else
{
echo mysql_error();
}


}
getNextId();
?></td>
</tr>
<tr>
<td width=147><span style="font-family: &quot;Times New Roman&quot;, Times, serif; font-size: 14px">Member Name</span></td>
<td><input type="text" name="Mname" /></td>
</tr>
<tr>
<td><span style="font-family: &quot;Times New Roman&quot;, Times, serif; font-size: 14px">Gender</span></td>
<td> <p>
<label>Male
<input type="radio" name="Gen" value="Male" />
</label>
<br />
<label>Female
<input type="radio" name="Gen" value="Female" />
</label>
<br />
</p></td>
</tr>
<tr>
<td><span style="font-family: &quot;Times New Roman&quot;, Times, serif; font-size: 14px">ParentName</span></td>
<td><input type="text" name="Pname" /></td>
</tr>
<tr>
<td><span style="font-family: &quot;Times New Roman&quot;, Times, serif; font-size: 14px">Address</span></td>
<td><textarea name="Ads"></textarea></td>
</tr>
<tr>
<td><span style="font-family: &quot;Times New Roman&quot;, Times, serif; font-size: 14px">CityId</span></td>
<td><select name="s1">
<?php
$qry=mysql_query("Select * from CityMaster");

while($obj=mysql_fetch_object($qry))
{
echo "<option value=".$obj->CityId.">".$obj->CityName ."</option>";
}
?>
</select></td>
</tr>
<tr>
<td width="143"><span style="font-family: &quot;Times New Roman&quot;, Times, serif; font-size: 14px">PinCode</span></td>
<td width="89"><input type="text" name="Pcode" /></td>
</tr>
<tr>
<td><span style="font-family: &quot;Times New Roman&quot;, Times, serif; font-size: 14px">Email Id</span> </td>
<td><input type="text" name="Eid" /></td>
</tr>
<tr>
<td><span style="font-family: &quot;Times New Roman&quot;, Times, serif; font-size: 14px">DateofReq</span></td>
<td><input type="text" name="Reqdate" value="<?php echo $today; ?>" /></td>
</tr>
<tr>
<td>User Name </td>
<td><input type="text" name="Uname" /></td>
</tr>

<tr>
<td colspan="4"><?php echo $msg; ?></td>
</tr>

<tr>
<td colspan="4"><input name="Submit" type="submit" id="Submit" value="Next" /> <input name="Submit" type="submit" id="Submit" value="Cancel" /></td>
</tr>
</table>
</form>
</div>

<!-- InstanceEndEditable -->
</div>
</div>
</div>

</div>
</body>
<!-- InstanceEnd --></html>
FOR CONNECTION:
<?php
$cn = mysql_connect("Localhost","root","");
if ($cn)
{

$db = mysql_select_db("credentialverifier");
if($db) { } else { echo "Error in connecting"; }
}
else
{
echo "Error";
}

?>
CLASS FILE:
<?php
include("connect.php");
class EventMgt
{
function getId($qry)
{
$res= mysql_query($qry);
if ($res)
{
@$val=mysql_result($res,0);
}
else
{
$val="";
}

return $val;
}

function insert($qry)
{
$res=mysql_query($qry);
if($res)
{
return"1";
}
else
{
return"0";
}
}

function showdata($qry1)
{

echo '<hr><b>mysql_result($qry)</b><hr>';
$qry=mysql_query($qry1);

while($rows = mysql_fetch_row($qry))
{
$cnt= count($rows);
for($i=0;$i<$cnt;$i++)
echo $rows[$i]." ";
}
echo "<br>";
}}?>
6.3 Screen Shots
Home:

The Main Page Of Credential Verifier And Civil Registry.


Cendidate can login with correct Username and Password.

Member Registration:

Cendidate fill the personal Details for registration.


Cendidate should give the verification information.

Candidate give the Login Information for Login into site.
Member Information:

Conformation Details of the registration.

Admin Side:

Admin Approve or Reject the Member.

Admin approve the Candidate successfully.

Details Of Approve , Reject and Pending candidate.

Member side

Display the member information at member home page.
Document Submit:

Member can submit the Document here.

Exam Details:

Member can view the Exam details.

Member can apply for the Exam.


Attach document for the Application.


Give the conformation for the exam application.
Organization Side :

Organization can register here.


Organization give the Login information.
Organistation Information:


Details of Exam, Admission And Passport:

Organization can view the member of application.


How many members were apply in this exam.

Organization publish the Exam Details.

Passport License

Organization view the Passport Request.


Organization give the response for the request.
Result :

Organization can add the result of particular application.

Organization add the result of particular application.


CHAPTER 7
TESTING
TESTING
Testing is a process of executing a program with the intent of finding an error. If testing is conducted successfully, it will uncover the error in the software.
Secondly, testing demonstrates that software functions appear to be working according to specification and that performance requirements appear to have been met. In additional, data collected as testing is conducted provides a good indication of software reliability and some indication of software quality as whole.
But there is one thing that testing cannot do: Testing cannot show the absence of defects, it can only show that software errors are present.
There are several objectives which are as follows:
' Testing is a process of executing a program with the intent of finding an error.
' A good test case is one that has a probability of finding an as undiscovered error.
' A successful test is one that uncovers an as yet undiscovered error.
Testing Principle
Following are the testing principles which are used:
' All tests should be traceable to customer requirement.
' Tests should be planned long before testing begins.
' Testing should be in small and progress toward testing in the large.
' Exhaustive testing is not possible.
' To be most effective testing should be conduct by independent third party.

7.1 Testing Plan
The aim of the testing process is to identify all defects existing in software Product. However for most practical systems, even after satisfactorily carrying out the testing phase, it is not possible to guarantee that the software is error free. This is because of the fact that the input data domain of most software products is very large. It is not practical to test the software exhaustively with respect to each value that the input data may assume. Even with this practical limitation of the testing process, the importance of testing should not be underestimated. It must be remembered that testing does expose.
Functional Testing
The testing technique that is going to be used in the project is black box testing. In black box testing the expected inputs to the system are applied and only the outputs are checked.
The working or the other parameters of the functionality are not reviewed or tested on the black box testing technique. There is a specific set of inputs for each and every module which is applied and for each set of inputs the result or the output is verified and if found as per the system working this testing is termed or result is declared as pass.
If the set of inputs that are provided to each module are not giving the outputs as per the expected results from the module then the result of that testing is to be declare failed.
Moreover the bottom up integration of the modules is applied herein so that each module can be verified at the initial stage and if it is found that the independent module is perfectly alright, only then it is going to be integrated with other related modules otherwise the module is checked for flaws and then if it satisfies all the specific requirements of the module, is integrated to other related modules to form and incorporate a system.
In the black-box testing approach, test cases are designed using only the functional specification of the software, i.e. without any knowledge of the internal structure of the software. For this reason, black-box testing is known as functional testing.
Equivalence Class Partitioning
In this approach, the domain of input values to a program is partitioned into a set of equivalence classes. This partitioning is done such that the behavior of the program is similar for every input data belonging to the same equivalence class. The main idea behind defining the equivalence classes is that testing the code with any one value belonging to an equivalence class is as good as testing the software with any other value belonging to that equivalence class. Equivalence classes for software can be designed by examining the input data and output data.
Boundary Value Analysis
A type of programming error frequently occurs at the boundaries of different equivalence classes of inputs. The reason behind such errors might purely be due to psychological factors. Programmers often fail to see the special processing required by the input values that lie at the boundary of the different equivalence classes. For example, programmers may improperly use < instead of <=, or conversely <= for <. Boundary value analysis leads to selection of test cases at the boundaries of the different equivalence classes.
Structural Testing
In the white-box testing approach, designing test cases requires thorough knowledge about the internal structure of software, and therefore the white-box testing is called structural testing.

Fig:-7.1 Testing Process.
7.2 Testing Strategy
The black box testing is going to be used for the project. The entire module is going to be checked for the specific inputs and the output is going to be checked. We are going to test the modules individually and thereafter if found to be working as per the expectations they are going to be integrated with other successfully tested modules and then on integrated.
At last all the modules are integrated and thereafter it is checked on a broader basis and all the requirements which are specified are checked for each integrated system modules. If all the functionalities are successfully satisfied than the entire integrated system is found to be working perfectly alright.
The integration is going to be in a bottom up manner where in each individual modules are going to be checked for the first time initially. Later on as and when other modules are developed and are in a working condition than they are integrated and the entire system is going to be generated. As mentioned before these entire system will finally be tested as per the requirements specified by the customer if any flaws are seen they are immediately required to be solved. In short the entire system should be working as per the requirements with no unexpected results.
7.3 Testing Methods
Involveexecution and implementation of the software with test data and examining the outputs of the software and its operational behavior to check that it is performing as required.

7.3.1 Statistical Testing
Used to test the program's performance and reliability and to check how it works under operational conditions. Tests are designed to reflect the actual user inputs and their frequency.
The stages involved in the static analysis are follows.
' Control flow analysis
' Unreachable code
' Unconditional branches into loops
' Data use analysis
' Variable used before initialization
' Variables declared but never used
' Variables assigned twice but never used between assignments
' Possible array bound violations
' Declared variables
' Interface analysis
' Parameter type mismatches
' Parameter number mismatches
' Non-usage of the results of functions
' Uncalled functions and procedures
' Storage management faults
' Unassigned pointers
7.3.2 Defect Testing
Intended to find inconsistencies between a program and its specification.These inconsistencies are usually due to program faults or defects.
' We have tested our functions of component to check the specification of our components.
' We selected input set to test the components like in query process we gave the different kinds of inputs to examine their output.
' We test software with sequences that have only a single value.
' We used different sequences of different sizes in different tests.
' Derived tests so that the first, middle and last elements of the sequence and accessed to reveal the problems at partition boundaries.

7.4 TEST CASES
7.4.1 Purpose
The purpose of this application is to reduce overhead in paper work and all the records are maintained such that the user as well as administrator can easily segment them into desired properties so it is easy for any novice user to have access to the application.
Another purpose is to make record of papers in database so it can be referred in future.
7.4.2 Required Input and Expected Result
TEST CASES
TABLE 7.1 LOGIN
TEST CASE ID: TC_Login_01 NAME: Login
TESTING STRATAGY: Black Box and White Box Testing
PURPOSE: Checking the authenticity of the user.
INPUT: Username, password
TEST DATA: tb_username, tb_password
EXPECTED O/P: If username and password are correct then user is allowed to enter in to the system and if not then he/she is again asked to enter the username and password
UNBEHAVIOURABLE O/P: N.A.
STEPS:
1. After user enters user name and password it is going to be verified with database and allows user to access system if both matches correctly

TABLE 7.2 USER RIGHTS
TEST CASE ID: TC_Login_02 NAME: User Rights
TESTING STRATAGY: Black Box and White Box Testing
PURPOSE: Checking the authenticity of the user.
INPUT: Username, password
TEST DATA: tb_username, tb_password
EXPECTED O/P: User privileges are allocated according to user group.
UNBEHAVIOURABLE O/P: N.A.
STEPS:
1. After user enters user name and password it is going to be verified with database
2. It matches user name and password and get his user privileges
3. As per assigned privileges relevant action will be enabled
TABLE 7.3 INSERTIONS
TEST CASE ID:TC_AV_03 NAME: Insertion of new asset/employee/vendor/complaints regarding assets
TESTING STRATAGY: Black Box and White Box Testing
PURPOSE: Whenever any Administrator wants to add any information about assets/ add new employee/ add new vendor/ register a complaint regarding assets it can be done using save.
INPUT: Data to be saved i.e. new Assets/ employee/ vendor or complaint.
TEST DATA: Save button
EXPECTED O/P: Data to be stored in database
UNBEHAVIOURABLE O/P: N.A
STEPS :
1. Whenever user selects save button the data he inserted in the textbox should be saved in the database.

TABLE 7.4 AUTOMATIC UPDATE
TEST CASE ID:TC_AV_04 NAME: Automatic Update Asset/Employee/Vendor Master
TESTING STRATAGY: Black Box and White Box Testing
PURPOSE: Whenever any Administrator/user wants change his/her information and selected previous information should be placed automatically in relevant textbox
INPUT: Selection of Asset/Employee/Vendor for updating
TEST DATA: Respective Id of Vendor/Employee/Assets is passed
EXPECTED O/P: Existing name of the selected item
UNBEHAVIOURABLE O/P: Exception Occurs: no output will be displayed
STEPS :
1. Whenever user selects Assets/Employee/Vendor then their respective Ids are passed.
2. And from database, then from already placed data its new data should be stored in some variable then all the information is placed in relevant textbox.
3. Updated category is then reviewed.

TABLE 7.5 DELETE
TEST CASE ID:TC_AV_05 NAME: Delete Asset/Vendor/employee/complaint
TESTING STRATAGY: Black Box and White Box Testing
PURPOSE: Whenever any Administrator/user wants to delete existing Asset/Employee/Vendor/or complaints when they are resolved then selected previous information should be placed automatically in relevant textbox to delete them.
INPUT: Selection of Asset/Vendor/Employee/ Complaint for deletion.
TEST DATA: Id of therespective Asset/vendor/employee/complaint.
EXPECTED O/P: Respective data which is selected will b deleted.
UNBEHAVIOURABLE O/P: N.A.
STEPS :
1. Whenever user selects an Asset/Employee/Vendor/Complaint then its Id is passed.
2. And from the Id, information of the Asset/Employee/Vendor/Complaint is selected and delete operation is performed.
3. Existing data is then reviewed.

CHAPTER 8
LIMITATION & FUTURE ENHANCEMENT
8.1 Limitation
' It takes too much time to verify.
' It is difficult for person to handle such situations.
' Difficult to manage hard copies of documents.
' User Interaction becomes difficult.
8.2 Enhancement
' There is relatively little cost involved in collecting data for voter registration because the key information has already been collected and compiled for the civil registry. To a large extent, another government agency simply assumes the costs in place of the electoral administration. Costs are quite high but the share borne by the election management authority is small;
' As with a continuous list, the information in a civil registry normally is updated regularly, making it possible to produce a current voters' list on short notice;
' Again as with a continuous list, the costs of maintaining a civil registry are spread across years;
' Governments that use a civil registry typically place a very high priority on ensuring that it provides reliable, up-to-date information. Voters' lists produced from such registries score well on the three performance criteria of currency, accuracy and completeness;
' Because civil registries are used for a variety of administrative purposes, citizens are generally given a short time frame for reporting changes to their personal information. As a result, while any ongoing registry system has a delay in integrating changes, it tends to be rather short for civil registries. And these systems perform well on the criterion of currency;
' Because the civil registry is updated regularly, it allows significant lead time for confirming the accuracy of the information
' All citizens are usually required to be listed in the civil registry, and not being listed has been described as equivalent to social death. A citizen not in the registry may not have access to a wide variety of social services, such as employment or unemployment benefits, health care support, and education. For this reason, civil registry systems tend to perform very well on the criterion of completeness; and


CHAPTER 9
CONCLUSION
Credential Verifier And Civil Registry is a web application that will helpful to the students as well as to the candidates who are usually apply online and Upload their documents or certificates for each applications. Just using Credential Verifier And Civil Registry Application user can create their profiles and manage their documents easily. After that users will not need to upload their documents for each new application. They can just give their unique User Id and document ID to be verified for applications or recruitments. This application also will be help full to organizations to publish their application forms for exams or recruitments and can verify documents of students or candidates easily by using ID of applicant. 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.


CHAPTER 10
REFERENCES

Refered Books :

' Object Oriented Anaysis And Design And Uml(OOAD) 'Author: RAMBAUG
Publication: Pearson
' Software Engineering(SE) ' Author: PRESSMAN

Web Sites :

' http://www.wikipedia.org/wiki/Civilregistry

' http://www.kashipara.com/project/projectphp.php

' http://www.bestprojectidea.com/civilregistry

Source: Essay UK - http://www.essay.uk.com/free-essays/information-technology/credential-verifier-civil-registry.php



About this resource

This Information Technology essay was submitted to us by a student in order to help you with your studies.


Search our content:


  • Download this page
  • Print this page
  • Search again

  • Word count:

    This page has approximately words.


    Share:


    Cite:

    If you use part of this page in your own work, you need to provide a citation, as follows:

    Essay UK, Credential Verifier And Civil Registry. Available from: <https://www.essay.uk.com/free-essays/information-technology/credential-verifier-civil-registry.php> [06-06-20].


    More information:

    If you are the original author of this content and no longer wish to have it published on our website then please click on the link below to request removal: