A PROJECT REPORT ON
E-CHALLAN SYSTEM Submitted in Partial Fulfillment Fulfillment of the Requirement for the Degree of Bachelor of Engineering In
INFORMATION TECHNOLOGY 2009-2013 Submitted to RAJIV GANDHI PROUDYOG PROUDYOGIKI IKI VISHWAVIDYALAYA
BHOPAL (M.P.) Submitted by Nidhi Pundhir 0905IT091033
Under the guidance of Prof. Pradeep Yadav DEPARTMENT OF INFORMATION TECHNOLOGY
INSTITUTE OF INFORMATION TECHNOLOGY AND MANAGEMENT
Contents 1. Introduction to the project. 2. Tools and Platform 3. System Analysis 4. Need. 5. System requirement. 5.1 Technical Feasibility 5.2 Economical Feasibility 5.3 Operational Feasibility 6. Software requirement specification 7. Description of the Front end 8. Description of the Back end 9. System Requirements 10. Testing 11. Form Layouts 12. Data Dictionary 13. DFD & E-R Diagram 14. Future enhancement 15. Bibliography
Abstract
AbstractE-challan an e-challan is an electronic format of the challan. The term challan is generally used in Asia. It means a receipt for payment or delivery. An e-challan can also be defined as a specific format used for depositing/remitting the contribution/statutory payment at bank/ treasury. An example would be the challan issued by the traffic police for violation. This challan would then have to be paid directly by cash or at an e-seva center or by any other payment mode as specified on the challan. The government of Andhra Pradesh has established a new challan system called e-challans. They have also established a website where one can check if their vehicle has any traffic offences registered against it. One can also find the offence description, fine amount, user charges, and the total fine amount. In the context of traffic violations by citizens, Hyderabad Traffic Police had introduced the system of echallan. E-challan is a non contact enforcement system to curb violations and implement stricter traffic discipline among the traffic commuters. We are generating e-challans with photo evidence only. There are two types of e- challan which are being generated. One is with Surveillance Cameras, which automatically takes the violation photos which will be printed on the challan it self. Second one is with Digital Cameras; the cops will take snap shots of the violations on the field. These photos will be stored for record purposes. The development of software for tagging all violation photos to the e-challans is under process. At present
we have kept record of all the e-challan and violation information for all vehicles. You can check the e-challan status on our website. We are going to soon upload all violation photos on our web portal; the software for it is still under development.
NEED
The E-Challan System the following general challenges that are created when multiple services respond to a single site:
The need to work with large numbers of services and people; It provides the better flexibility Today E-Challan system is very useful for improve to the traffic discipline. Inter-service coordination problems;
Inter-dependencies of decisions and actions taken by multiple services. We are targeting those cliques who work in an organization Police etc. More precisely we will target to those who works on the Pc’s. All sorts of services will be just at a click away. The whole project will be bifurcated in user module and an administrator module.
Feasibility study
Technical Feasibility
In technical feasibility, we study all technical issues regarding the proposed system. It is mainly concerned with the specifications of the equipments and the software, this successfully satisfies the end-user’s requirement. The technical needs of the system may vary accordingly but include:
The feasibility to produce outputs in a given time
Response time under certain conditions.
Ability to process a certain volume of the transaction at a particular speed. Facility to communicate data.
Economical Feasibility
Economic feasibility is the most frequently used technique for evaluating the effectiveness of the proposed system. More commonly known as cost/benefit analysis, the procedure is to determine the benefits and savings that are Expected from the proposed system and compare them with the costs. If the benefits outweigh cost, a decision is taken to design and implement the system otherwise further justification of the alternative in the proposed system will have to be made if it is to have chance of being approved. Classification of Costs & Benefits: The various cost expected to incur & benefit expected to realize are given below.
Direct of Indirect Costs
Fixed and Variable Costs
Operational Feasibility
Proposed projects are beneficial only if they can be turned into information system that will meet the operating requirements for which they are designed and developed. It is mainly related to human organizational and political aspects. People are resistant to change and computers have Been known to facilitate change. Findings of operational feasibility analysis can be summarized as given below: Since the audiences are million of native who use it for information retrieval. So their will be many who will be benefited with this project End users are always welcome to have the technical support on the site.
Software Requirement Specification
SRS It is important that requirements be traceable through the design and test process, because a project’s very success is dependent upon requirements that are complete, accurate, and measurable. The sort war requirement specification (SRS) is very important part of the software building process, which describes the actual user level requirement from technical point of view i.e. what the user exactly wants? Or for what purpose we are making every thing. The objective of preparing the software requirement specification is to represent the requirements of the software in such a manner that ultimately leads to successful software implementation. The document is organized in the following structure:
INTRODUCTION: The introduction section describes the goals and objective the software under going development in context of the computer based system. It mainly deals with the software scope.
INFORMATION DESCRIPTION: This section of the SRS provides a detailed of the problem that the software must solve. FUNCTIONAL DESCRIPTION: It includes the process specification of each function, design constraints, and performance characteristics.
BEHAVIORAL DESCRIPTION: This section of the SRS describes the behavior of the software will exhibit.
Description of the Front End
Microsoft Visual Studio 2010 In computing, Microsoft Visual Studio is an integrated development environment (IDE) form Microsoft. It can be used to develop console and graphical user used to develop console and graphical user interface applications along with windows forms applications, web sites, web applications, and web services in both native code together with managed code for all platforms supported by Microsoft windows, Windows mobile, Windows CE, .NET framework, .NET compact framework and Microsoft silver light. Visual studio includes a code editor supporting intelligence as well as code refactoring. The integrated debugger works both as a source-level debugger and a machine-level debugger. Other built-in tools include a forms designer for building GUI applications, web designer, class designers and database schema designer. It accepts plug-ins that enhance the functionality at almost every level-including adding support for source-control systems (like subversions and visual source safe) and adding new toolsets like editors and visual designers for domainspecific languages or toolsets for other aspects of the software development life cycle (like the team foundation server client: Team explorer). Visual studio supports different programming languages by means of language services, which allow the code editor and debugger to support (to varying degrees) nearly any
programming, provide a language-specific service exits. Built-in languages include C/C++ (via Visual C++), VB.NET(via Visual Basic .NET), C# (via Visual C#), and F#(as of Visual Studio 2010). Support for other languages such as M, Python, and ruby among others is available via language-specific versions of Visual Studio also exist which provide more limited language services to the user: Microsoft Visual Basic, Visual J# , Visual C# , and Visual C++.
Microsoft .NET Framework The Microsoft .Net Framework is a software framework that can be installed on computers running Microsoft Windows operating systems. It includes a large library of coded solutions to common programming problems and a virtual machine that manages the execution of programs a virtual machine that manages the execution of programs written specifically for the framework. Notably, the .NET Framework supports multiple programming languages in a manner that allows language interoperability, whereby each language can stylize code written in other languages; in particular, the aforementioned .NET library is available to all the programming language that .NET facilitates. The .NET Framework is a Microsoft offering and is intended to be used by most new applications created for the Windows platform.
The framework’s Base class Library provides a large range of features including user interface, data access, database connectivity, cryptography, application development, numeric algorithms, and network communications. The class library is used by programmers, who combine it with their own code to produce applications. Programs written for the .NET Framework execute in a software environment that manages the program’s runtime requirements. Also part of the .NET Framework, this runtime environment is known as the Common Language Runtime (CLR). The CLR provides the appearance of and application virtual machine so that specific CPU that will execute the program. The CLR also provides other important services such as security, memory management, and exception handling. The class library and the CLR together constitute the .NET Framework.
Description of Back End
Microsoft Sql Server 2005 Microsoft SQL Server is a relational model database server produced by Microsoft. Its primary query language is T-SQL and ANSI SQL. SQL Server 2005 (codenamed Yukon), released in October 2005, is the successor to SQL Server 2000. It included native support for managing XML data, in addition to relational data. For this purpose, it defined an xml data type that could be used either as data type in database columns or as literals in queries. Xml columns can be associated with XSD schemas; XML data being stored is verified against the schema. XML is converted to an internal binary data type before being stored in the database. Specialized indexing methods were made available for XML data. XML data is queried using Query; CLR integration was the main features managed code these are those code which are being executed by CLR (common language Runtime). SQL server 2005 added some extensions to the T-sql. In addition it also defines a new extension to query, called XML DML that allows query-based modifications to XML data. SQL Server 2005 also allows a database server to be exposed over web services using TDS packets encapsulated within SOAP (protocol) requests. When the data is accessed over web services, results are returned as XML. For relational data, T-SQL has been augmented with error handling features (try/catch) and support for recursive queries
(common Table Expressions). SQL server 2005 has also been enhanced with new indexing algorithms and better error recovery systems. Data pages are check summed for better error resiliency, and optimistic concurrency support has been added for better performance. Permissions and access control have been made more granular and the query processor handles concurrent execution of queries in a more efficient way. Partitions on tables and indexes are supported natively, so scaling out a database onto a duster is easier. SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET Framework.
System RequirementHardware Requirement:
The hardware requirement specification for this project is described below: PROCESSOR
: Pentium IV, Core I3
RAM & HARD DISK : 512 MB RAM and 4.3 GB HARD DISK MONITOR
: SVGA COLOR MONITOR
Software Requirement:
The software requirement specification for this project is as follows: VISUAL STUDIO 2010 SQL SERVER 2008 Operating System: Windows XP, Windows 7
TestingSoftware testing is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test, with respect to the context in which it is intended to operate. Software Testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. Software Testing can also be stated as the process of validating and verifying that a software program/application/product: 1.meets the business and technical requirements that guided its design and development; 2.works as expected; and 3.Can be implemented with the same characteristics. Software Testing, depending on the testing method employed can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. As such, the methodology of the test is governed by the Software Development methodology adopted. Different software development models will focus the test effort at different points in the development process. In a more traditional model,
Most of the test effort occurs after the requirements have been defined and the coding process has been completed. Newer development models, such as Agile or XP, often employ test driven development and place an increased portion of the testing up front in the development process, in the hands of the developer.
Testing methodsThe box approach Software testing methods are traditionally divided into black box testing and white box testing. These two approaches are used to describe the point of view that a test engineer takes when designing test cases.
Black box testing Black box testing treats the software as a "black box" — without any knowledge of internal implementation. Black box testing methods include: equivalence partitioning, analysis, all, fuzz testing, model-based testing, traceability matrix, exploratory testing and specification-based testing.
Specification-based testing: Specification-based testing aims to test the functionality of software according to the applicable requirements. Thus, the tester inputs data into, and only sees the output from, the test object. This level of testing usually requires thorough test cases to be provided to the tester, who then can simply verify that for a given input, the output value (or behavior), either "is" or "is not" the same as the expected value specified in the test case. Specification-based testing is necessary, but it is insufficient to guard against certain risks.
Advantages and disadvantages: The black box tester has no "bonds" with the code, and a tester's perception is very simple: a code must have bugs. Using the principle, "Ask and you shall receive," black box testers find bugs where programmers do not. But, on the other hand, black box testing has been said to be "like a walk in a dark labyrinth without a flashlight," because the tester doesn't know how the software being tested was actually constructed. As a result, there are situations when (1) a tester writes many test cases to check something that could have been tested by only one test case, and/or (2) some parts of the back-end are not tested at all. Therefore, black box testing has the advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of "blind exploring," on the other.
White box testing White box testing is when the tester has access to the internal data structures and algorithms including the code that implement these.
Types of white box testing The following types of white box testing exist:
API testing (application programming interface) Testing of the application using Public and Private APIs Code coverage - creating tests to satisfy some criteria of code coverage (e.g., the test designer can create tests to cause all statements in the program to be executed at least once) Fault injection methods - improving the coverage of a test by introducing faults to test code paths Mutation testing methods Static testing - White box testing includes all static testing.
Form Layouts
DATA DICTIONARY
1. ADMIN DATABASE TABLE Field Name
Description
Data Type
First Name
This field contains the first name of the admin
TEXT
Last Name
This field contains the last name of the admin
TEXT
User Name
Admin User_Id
Varchar(50)
Password
Admin Password
Varchar(50)
Gender
This field contains the gender of the admin
TEXT
Date of Joining
Date of Joining of the Admin
Varchar(50)
Date of Birth
Date of joining of the Admin
Varchar(50)
Address
Address of the Admin
Varchar(Max)
Contact
Contact No.
Numeric(0,18)
Email
Email Id
Varchar(50)
2. MANAGER DATABASE TABLE Field Name
Description
Data Type
Id
This field contains Id of the Managers
First Name
This field contains the first name of the Mangers
TEXT
Last Name
This field contains the last name of the Managers
TEXT
User Name
Managers User_ID
Varchar(50)
Password
Mangers Password
Varchar(50)
Gender
This field contains the gender of the Manager
TEXT
Category
This field contains the category to the user
TEXT
Date of Joining
Date of Joining of the Manager
Varchar(50)
Date of Birth
Date of joining of the Manager
Varchar(50)
Address
Address of the Manager
Varchar(Max)
Contact
Contact No.
Numeric(0,18)
Email
Email Id
Varchar(50)
Status
Working/Not Working
Varchar(50)
3. EMPLOYEE DATABASE TABLE Field Name
Description
Data Type
Id
This field contains Id of the Employees
First Name
This field contains the first name of the Employee
TEXT
Last Name
This field contains the last name of the Employee
TEXT
User Name
Employee User_ID
Varchar(50)
Password
Employee Password
Varchar(50)
Gender
This field contains the gender of the Employee
TEXT
Category
This field contains the category to the user
TEXT
Date of Joining
Date of Joining of the Employee
Varchar(50)
Date of Birth
Date of joining of the Employee
Varchar(50)
Address
Address of the Employee
Varchar(Max)
Contact
Contact No.
Numeric(0,18)
Email
Email Id
Varchar(50)
Status
Working/Not Working
Varchar(50)
4. CASHIER DATABASE TABLE Field Name
Description
Data Type
Id
This field contains Id of the Cashiers
First Name
This field contains the first name of the Cashier
TEXT
Last Name
This field contains the last name of the Cashier
TEXT
User Name
Cashier User_ID
Varchar(50)
Password
Cashier Password
Varchar(50)
Gender
This field contains the gender of the Cashier
TEXT
Category
This field contains the category to the user
TEXT
Date of Joining
Date of Joining of the Cashier
Varchar(50)
Date of Birth
Date of joining of the Cashier
Varchar(50)
Address
Address of the Cashier
Varchar(Max)
Contact
Contact No.
Numeric(0,18)
Email
Email Id
Varchar(50)
Status
Working/Not Working
Varchar(50)
5. RTO DATABASE TABLE Field Name
Description
Data Type
Vehicle Registration No.
This field contains Registration No. of the Vehicles
Varchar(50)
Owner Name
This field contains the Owner name of the Vehicle
Varchar(50)
Father Name/Husband Name
This field contains the Father name/Husband Name of the Owner
Varchar(50)
Address
Address of the Vehicle Owner
Varchar(Max)
Vehicle Type
Type of the Vehicle(Vehicle Company Name)
Varchar(50)
Vehicle Color
This field contains the Vehicle Color
Varchar(50)
6. AUTO INCRIMENT TABLE Field Name
Description
Data Type
ID
100
Varchar(50)
EC_NO
1000
Varchar(50)
7. CHALLAN DETAILS TABLE Field Name
Description
Data Type
EC_NO
This field contains Registration No. of the Vehicles
Varchar(50)
Vehicle Registration No.
This field contains Registration No. of the Vehicles
Varchar(50)
Owner Name
This field contains the Owner name of the Vehicle
Varchar(50)
Father Name/Husband Name
This field contains the Father name/Husband Name of the Owner
Varchar(50)
Address
Address of the Vehicle Owner
Varchar(Max)
Vehicle Type
Type of the Vehicle(Vehicle Company Name)
Varchar(50)
Vehicle Color
This field contains Color of the Vehicle
Varchar(50)
D.O.V.
Date of Violation
Varchar(50)
T.O.V.
Time of Violation
Varchar(50)
P.O.V.
Place of Violation
Varchar(50)
Offence
Offence Description
Varchar(50)
Fine
Fine Amount
Varchar(50)
Status
Pending/Paid
Varchar(50)
8. PLACE DETAILS TABLE Field Name
Description
Data Type
Place
This field contains the Place of the City
Varchar(50)
E-R Diagram
Employee
First Name Username Cashier
Manager
Last Name Password
E-id
Locked
Employees
Address
Contact
Add
Check list
Manager Check list
Admin
Search
Employee Check list
Cashier User Name
Password
E-R Diagram-1
First Name Username Last Name Password
E-id
Employees
Address
Generate Challans Contact
Add
Employee
Manager
Updates Cashier
User Name
Password Paid Challans
E-R Diagram-2
Future Enhancement
We can enhance this service by giving the to the web server phone.
The victim will have no need to call he will only ring the server and actions will be taken.
In it will the server will check the challan status on the internet and will provide the germane service to the person.
The project “E-Challan System” is much more flexible and can withstand any future developments. Any module can be extended as well as information can also be included into it according to future requirements.
The customized package “E-Challan System” fulfills all the requirements as stated in the objectives, but scope of improvement is a part of life and it is inevitable for survival and this is no exception to this package. Modular extension can be done easily.
