INTRODUCTION
1
1.1 SCOPE
2
1.2 OVER VIEW
3
2. SYSTEM ANALYSIS
The system analysis can be defined as the processes involved in the analysis of
the requirements, designing and developing a computer based system. It includes
both preliminary and detailed stage. During preliminary analysis, takes a quick look
at what is wanted and whether its cost and benefits justify the perceived want.
Detailed analysis includes an in depth look at what is wanted and contain more
reduced cost and benefit studies.
Many cities in India have already implemented a video surveillance system for
traffic management. However, this has been done before recent developments in mega
pixel IP cameras and video analytics, so it would be pertinent to discuss the impact of
these two developments and their implications for enforcement of traffic rules.
4
2.1.1 LIMITATIONS OF EXISTING SYSTEM
5
2.2.1 Advantages of Proposed System
Vehicular traffic is one of the most important social and economic issues faced
today resulting in congestion.
A smart transport system which will provide real time information about
the traffic by p2p is the need of the hour.
The existing smart transport systems demand a need for the construction of
expensive infrastructures or a change in the road structure.
A simple solution to traffic congestion is to gain knowledge about
the traffic congested routes.
6
2.3 Feasibility Study
7
2.3.3 Operational Feasibility
Pentium 4 Processor.
3GB Free Disk Space(Minimum).
512 MB RAM(Minimum).
3GB Free Disk Space(Minimum).
8
3. SYSTEM DESIGN
3.1 Input design
Input is considered as the process of keying in data into the system, which will be
converted to system format. People from different categories over the world use a web
application. So the input designs given in the application should be really flexible and faster to
use and are important for the success of the application. The easy to use hyperlinks of the
application help in navigating between different pages of the web application in a faster way.
The user need not enter the user ID in the corresponding field since the system identifies
the logged user and gets the user ID default. Also, the current date can be inserted by default. Sub
lists for a particular item can be displayed accordingly. All these provide a better way to handle
the input functions of the system.
Input design is a part of overall system design, which requires very careful attention. If
data going into the system is correct, then the processing and output will magnify these errors.
Thus the designer has a number of clear objects in the different stages of input design
9
3.2 Output Design
The success or failure of a software system is decided by the integrity and correctness
of the output that is produced by the system. One of the main objective behind the automation
of business systems itself is the fast and prompt generation of reports and information in a
short time period with correctness. Prompt and reliable reports are considered to be the
lifeline of every business today. At the same time wrong reports can shatter the business itself
and create huge and irreparable losses for the business. So the output/reports generated by the
system are of paramount importance.
At the beginning of the output design various types of outputs such as external,
internal, operational, and interactive and turnaround are defined. Then the format, content,
location, frequency, volume and sequence of the outputs are specified. The content of the
output must be defined in detail. The system analysis has two specific objectives at this stage.
10
3.3 CODE DESIGN
Register
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
11
Login
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data;
using System.Data.SqlClient;
}
protected void Button1_Click(object sender, EventArgs e)
{
SqlCommand cmd21=new SqlCommand();
cmd21.CommandText="select * from login_table where username='"+txt_user.Text+"' and
password='"+txt_password.Text+"'";
DataTable dt=db.getdata(cmd21);
if(dt.Rows.Count>0)
{
int id=Convert.ToInt32(dt.Rows[0][0]);
string type=dt.Rows[0][3].ToString();
if(type=="Admin")
{
Session["Ui"]=id;
Response.Redirect("Admin_home.aspx");
}
if(type=="user")
{
Session["Ui"]=id;
Response.Redirect("user_home.aspx");
}
if(type=="service")
{
Session["Ui"]=id;
Response.Redirect("service_home.aspx");
}
}
else
{
Response.Write("<script>alert('invalid id')</script>");
}
}
}
12
3.4.DATA BASE DESIGN
Normalization Techniques:
Transitive Dependency
If two non-key attributes depends on each other as well as on the primary key then they are
said to be transitively dependent. the above normalization principles where applied to decompose
the data in multiple tables there by making the data to be maintained in a consistent state
13
4. SYSTEM TESTING
4.1 TESTING
System testing is actually a series of different tests whose primary purpose is to fully exercise
the computer-based system. Although each test has a different purpose, all work to verify that
all system elements have been properly integrated and perform allocated functions.
Testing is the final verification and validation activity within the organization itself.
Testing is done to achieve the following goals: to test the quality of the product, to find and
eliminate any residual errors from previous stages, to validate the software as a solution to the
original problem, to demonstrate the presence of all specified functionality in the product, to
estimate the operational reliability of the system. During testing the major activities are
concentrated on the examination and modification of the source code.
14
4.2 TEST TYPES
Unit testing focuses verification efforts on the smallest unit of software design, the
module. This is also known as module testing. The modules are tested separately. These
testing are carried out during programming stage itself. In this testing step, each module is
found to be working satisfactory as regards to the expected outputs from the module.
interfaces; all the modules are combined and tested as a whole. when conducting this sort of
tests, the analyst may devise test data; the collection of data that analyst used when providing
system accuracy. Another source of test data is the user.
Text Field: The text field can contain only the number of characters lesser than or equal to its
size. The text fields are alphanumeric in some tables and alphabetic in other tables. Incorrect
entry always flashes an error message.
Numeric Field: The numeric fields can contain only numbers 0 to 9.An entry of any character
flashes an error messages.
Output testing
After performing the validation testing, the next step is output testing of the
proposed system, since no system could be useful if it does not produce the required output in
the specific format. The output generated by the system under considerations is tested by
asking the users about the format required by them.
15
White box testing
In white box testing knowing the internal working of the product, tests can be
conducted to ensure that internal operations are performed according to specification and all
internal components have been adequately exercised. In white box testing logical path
through the software are tested by providing test cases that exercise specific sets of conditions
and loops.
Using white-box testing software developer can derive test case that
Guarantee that all independent paths within a module have been exercised at least once.
Exercise all loops at their boundaries and within their operational bound.
At every stage of project development I have tested the logics of the program by
supplying the invalid inputs and generating the respective error messages. All the loops and
conditional statements are tested to the boundary conditions and validated properly.
This is a software testing in which the test are doesnt know the internal working of
the item being tested. For example in black box test, on software design the tester only knows
the input and the expected outputs. He doesnt know how the program drives the output. He
doesnt even imaging as to how, the coding is done. He need know only the specification.
1. The test is unbiased because the designer and tester are independent of each other.
3. The test is done from the point of view of the user, not the designer.
16
The disadvantages of these testing approaches are
1. The test can be redundant if the software designer has already run a test case.
2. The test can be difficult to design.
3. Testing every possible input stream is unrealistic.
Acceptance Testing
User Acceptance of a system is the key factor for the success of any system .The
system under consideration is tested for user acceptance by constantly keeping in
touch with the prospective system users at the time of developing and making of
hardware management software system.
17
5. SYSTEM IMPLEMENTATION AND
MAINTENANCE
System implementation is the final phase, i.e., putting the utility into action.
Implementation is the state in the project where theoretical design turned into working
system. The most crucial stage is achieving a new successful system and giving confidence in
new system that it will work efficiently and effectively. The system is implemented only after
thorough checking is done. It involves careful planning, investigation of the current system
and constraints on implementation, design of methods achieve.
Implementation is the stage of the project where the theoretical design is turn into a
working system. The implementation stage is a system project in its own right. It involves
careful planning, investigation of the current system and constraints on implementation,
design of methods to achieve the change over and the evolution method. Once the planning
has been completed the major effort is to ensure that the programs in the system are working
properly. At the same time concentrate on training user staff.
Implementation phase is an important one in which the source code put into the
operation. Before implementing the software, careful documentation is necessary.
Implementation should provide with well defined software requirements, design
specifications. The major milestone for project implementation is successful integration of
software components in the functioning system. During the implementation the configuration
management and quality assurance of requirements design specification and source code are
performed.
18
SYSTEM MAINTENANCE
In this project, the maintenance is carried over by the administrator. Since he is the
key persons to develop this project they know clearly about the project coding structure. So,
they will change the coding whenever required. Regarding the project maintenance, the
changes will occur then and there according to the conditions.
19
6. SCOPE FOR FUTURE ENHANCEMENT
20
7. CONCLUSION
This system has been developed and is found working effectively. The
developed system is flexible and changes can made easily as and when required. We
tried to make the system maximum user friendly. Services is the main considerations
in the project. The system is protected from any unauthorized access by giving user
name and password during login process. All the necessary validations are carried
out in this project, so that any kind of user can use this software and necessary
messages make them conscious of the error they have made.
The project developed using c#.net & Android. It is based on the requirements
specification of the user and analysis of existing system with flexibility for future
enhancement. Since the system is developed in modules, future enhancement is very
easy.
21
8. BIBLIOGRAPHY
Teachers
Students
Internet
Friends
22
9. APPENDIX
9.1 DATA FLOW DIAGRAM
A data flow is route, which enables packets of data to travel from one point to
another. Data may flow from a processor and from data store or process. An
arrow line depicts the flow, with arrow head pointing in the direction of the
flow.
A data store is a repository of data that is to be stored for use by one or more
processes. It may be as simple as buffer or queue or sophisticated as
relational database. They should have clear names. If a process merely uses
the content of store and does not alter it, the arrow head goes only from the
store to the process. If a process alters the details in the store then a double-
headed arrow is used.
23
LEVEL 0
24
25
26
27
9.2 Entity Relationship Diagram
= Entity.
= Attribute
= Relation
= Connection
28
ER DIAGRAM
29
9.3 TABLE DESIGN
Login Page
Registration Table
30
Admin_serviceregtable
Complaint Table
Column Name Data type Description
31
Congestion Table
Column Name Data type Description
32
Location_table
Column Name Data type Description
Over Speed_table
Column Name Data type Description
33
Post awareness_table
Column Name Data type Description
34
Traffic Light Register_table
Column Name Data type Description
35
9.4 FORM DESIGN
LOGIN
36
POST AWARENESS
37
NEAR ACCIDENT
38
SERVICE REGISTER
39