Dehradun at a Glance

UTTARAKHAND ROADWAYS

Developed byAyush Kumar

M.C.A. IV Semester

Under the Guidance ofMrs. DIVYA NEGI

Graphic Era University566/6 Bell Road Clementown, Dehradun (Uttarakhand)

Project Report On

CERTIFICATE

This is to certify that the work embodied in the

project report entitled “UTTARAKHAND ROADWAYS” is own

account of work carried out by Ayush Kumar Student of

M.C.A. IV Semester Graphic Era University Dehradun. To the

best of my knowledge this work has not been submitted

elsewhere for the award of any other degree.

Mr. Sushil

Chandra Dimri

( HOD MCA Department)

Dehradun at a Glance1

ACKNOWLEDGEMENT

Before going into thick of things I would like to

add a few heartfelt words for the people who were part of this

project in numerous ways. A large number of teachers,

students and computer lovers have made valuable suggestions

which have been incorporated in this work. It is not possible to

acknowledge all of them individually. I take this opportunity to

express my profound gratitude and ineptness to them.

I am gratefully thankful to Mrs.DIVYA NEGI , and

Mr .BREAJESH DHYANI for their kind cooperation, excellent

suggestions, moral support and guidance.

The love, affection and encouragement that I got from

my family members is unforgettable, they are my strength, my

support and my pride. How can I ever thank to my dearest

Family Members for always cheering up and spicing up my life.

It’s a time to depart and I am flooded with

nostalgic memories of spent with my friends.

I express my thanks to the Faculty member of MCA

Department for their day to day helps.

At least we thank and praise the Almighty for his constant

blessing and grace through every step of our life.


Ayush Kumar

PREFACE

This website is for every person who wants to get

information related to uttarakhand roadways. I have tried to

present this website in such a way that it will ease the person

looking for uttarakhand roadways related information like

timing of buses ,arrival time, departure time etc. user doesn’t

need to waste a lot time in searching these information to go

roadways station,the information is just a click away from him.

A project succeeds only when it meets the need of

the people who use it, when it performs flawlessly over a long

period of time, when it is easy to modify and even easier to

use.

I have tried my best to meet all the requirements and

need of this system. If you have any comment or suggestion

that can help to improve the software please send it to me.

[email protected]


TABLE OF CONTENTS

Contents at a Glance

Introduction

Objective . . . . . . . . . . . . . . . . . . . . . . . Modules ………………………….

Feasibility Study

Feasibility Study……………………. Types of Feasibility Study…………….

Requirement Analysis

Functional Requirements . . . . . . . . . . . . . . . . . . . User Requirements . . . . . . . . . . . . . . . . . .

Correctness


Performance

User Friendly

Maintenance

Hardware requirements. . . . . . . . . . . . . . . . . .

Software Requirements. . . . . . . . . . . . . . . . . .

Visual Studio 2008

IIS Server

My sql

Justification and need of the system. . . . . . . . . . . . . . . . . . .

Advantages of the System

Software Design

System Design . . . . . . . . . . . . . . . . . . .

DFD

E-R Diagram

User Interface. . . . . . . . . . . . . . . . . . .

Database Design…………………..

Testing

Unit Testing . . . . . . . . . . . . . . . . . . .

System Testing. . . . . . . . . . . . . . . . . . .

Integration Testing…………………..

Maintenance

Future Scope of the System

Conclusion

Bibliography


Introduction

This documentation discusses over various design decisions made and the

way they are implemented in the prescribed solution. It will give a quick glance

to the developers solving their problem of “what to design?” All the major

diagrams including the system architecture, data flow diagrams, entity

relationship diagram has been discussed here. Seeing the Entity Relationship

diagram we can say that how the database tables are attached to each other. The

whole system architecture is described in this documentation part. It has been

tried to cover all of the major modules and corresponding subroutines.

This website is for every person who wants to get information related to

Dehradun like colleges, picnic spots ,schools etc. user doesn’t need to waste a

lot time in searching these information on the internet ,the information is just a

click away from him.


User doesn’t wants to waste any time in surfing on the net for getting some

information , what he does is simply chooses the best alternate available, and

this site is prepared by keeping this point in mind . User would get the overview

of Dehradun just from this site and he doesn’t need to look anywhere else for

his requirement.

Objective

The objective of this website is to provide user with refined and centralized

information relating to uttarakhand roadways . The aim is to give a proper

idea about the uttarakhand roadways even to a user who haven’t ever heard

about it.

The main objective of this project is to facilitate the user to avoid their dilemma

and provide the information about Dehradun related to -

Tourism

Transport


Modules of the Software

Home: - This page includes: 1) Contact us: - About the developer of website and their contact

information. 2) Map: - Map of uttarakhand roadways. 3) Transport: it contains submenus:

Railway Bus Station Airport.

5) Tourism: - Information of tourist places.Except above defined menus there are some more hyperlinks on the home page for faster access of frequently accessed pages.


Feasibility Study

The feasibility of a project is determined in order to decide whether or not an

organization should undertake that particular project. There are some obvious,

and some not so obvious, Factors to consider when determining feasibility.

The feasibility study proposes one or more conceptual solutions to the

problem set for the project. The conceptual solutions given an idea of what the

new system will look like. They define what will be done on the computer and

what will remain manual. They also indicate which inputs the systems needed

for the desired outputs.

The most successful system projects are not necessarily the biggest or most

visible in a business but rather those that truly meet user expectations. More

projects fail because of inflated expectation than for any other reason.

During system engineering, however we concentrate our attention on six

primary areas of interests.

Operational feasibility

Timing feasibility

Technical feasibility

Legal feasibility

Organizational feasibility

Economic feasibility


Steps in feasibility analysis

Form a project team and appoint a leader.

Prepare system flowcharts.

Enumerate potential candidate system.

Describe and identify characteristics of candidate systems.

Determine and evaluate performance and cost effectiveness of each

candidate system.

Weight system performance and cost data.

Select the best candidate system.

Prepare and report final project directive to management.

This new proposed system is economically feasible as it does not involve

much financial cost and is very beneficial to the large organization, offices etc

as this system will save the time required for the queries are generate reports.

Accordingly, the proposed system stands out on these constraints to fulfill the

requirements. Economically the proposed system is cost-effective as it makes

use of the minimum available resources (H/W, S/W) and is in tune with the

latest technology. The system is designed at the software and hardware level.

Thus technically keeping the proposed system uses most of the latest tool.


Requirement Analysis

Requirement Analysis is the first phase of software development process.

This phase focuses to understand the problem Requirement Analysis is on

identifying what is need from these systems, not how the system will achieve its

goals. In this phase often at least two parties are involved in Software

Development-a client and a developer. The developer has to develop the system

to satisfy the clients’ needs. The developer and client arrange a meeting and

discuss his/her own views the developer asks the clients for needs. After a

meeting the developer understands what the requirements of the client are.

Before start the development process, the developer analyze, test the

requirements which are given by the clients. According to those requirements

the developer starts development process. Hence the developer needs a user’s

problem.

In the software requirement we are dealing with the requirements of the

proposed system, that’s the capabilities of that system, which is yet to be

developed, should have. The software requirement specification (SRS) is a

document that completely describes what the proposed software should do

without describing how the software will do it. So the basic goal of

Requirement Phase is to produce the SRS, which describes the complete

external behavior of the proposed software.

The basic aim of problem analysis is to obtain the clear understanding of the

needs of the clients and the user, what exactly described from the software, and

what the constraints on the solution are? This involves a meeting of user and

developers. The developer may ask the following questions to users-:


a) Functional Requirements:

In the development process of the software must face the new record should

have a unique registration number.

The software should have the capability that it can be used by the authorized

user following requirements-:

b) User requirements:

The main requirement of the user is that this website should provide him the

information he wants on that topic. The developer can face a number of

requirements of the user. So, the website should have a number of facilities. The

user may require the followings-

(i) Correctness:

Correctness is the degree to which the website performs its required need.

The extent to which the website satisfies its specifications and fulfills the User’s

mission and objectives.

(ii) Performance:

The website must perform required action. All the requirements of the

website directly related to its performance. The performance of the website is

measured on the basis of response time taken to display the record of the

Author. In the Performance, the website must be able to “process all the

operations quickly”. So the performance is measured by throughput, efficiency,

response time and the processing speed.

(iii) User Friendly:

The developed website must be user friendly by which the user can search its

requirement easily. If the software provides a good interface then it is said to be

user friendly.


The Base of this website developed by using the ASP. Net as a user interface

and the background using MS Access. The website can be used easily and user

can use it without more knowledge about the computer. The website provides

integrated and consistent information.

c) Performance Requirements:

a) Maintainability

b) Less time consuming

c) The system should utilize time effectively.

d)Portability

e) Reliability

The system should be capable enough to maintain the level of

performance.

d) Hardware and Software Requirements: For developing the website software and hardware requirements are as follows:

Hardware Requirement:

Processor Pentium 4

1 GB RAM

20 GB Hard disk

Software Requirement:

TECHNOLOGIES

HTML

PHP

MY SQL Server : database


Internet Information Server

Development Tool:

WAMP SERVER

Database:

MY SQL .

Platform:

Microsoft Windows 7 Operating System.

METHODOLOGIES Object Oriented Approach.

Centralized Database.

Supported Browser: Internet Explorer, Mozilla Firefox , google chrome.

Client side requirements:

To use this website following are the basic client side requirements:

Internet Connection

Web Browser

HOW WEB APPLICATIONS WORK?

Web applications use client/server architecture. The Web application resides on a server and responds to requests from multiple clients over the Internet, as shown in Figure


Fig. ASP.NET Web application architecture

On the client side, the Web application is hosted by a browser. The application’s user interface takes the form of Hypertext Markup Language (HTML) pages that are interpreted and displayed by the client’s browser.

On the server side, the Web application runs under Microsoft Internet Information Services (IIS). IIS manages the application, passes requests from clients to the application, and returns the application’s responses to the client. These requests and responses are passed across the Internet using Hypertext Transport Protocol (HTTP). A protocol is a set of rules that describe how two or more items communicate over a medium, such as the Internet. Figure 1-2 shows how the client and server interact over the Internet.

Fig. Client/server interaction in a Web application

The Web application composes responses to requests from resources found on the server. These resources include the executable code running on the server


(what we traditionally think of as the “application” in Microsoft Windows programming), Web forms, HTML pages, image files, and other media that make up the content of the application.

Web applications are much like traditional Web sites, except that the content presented to the user is actually composed dynamically by executable, rather than being served from a static page stored on the server. Figure above shows how a Web application composes the HTML returned to a user.

Fig An ASP.NET Web application response from server resources


The executable portion of the Web application enables you to do many things that you can’t do with a static Web site, such as:

Collect information from the user and store that information on the server Perform tasks for the user such as placing an order for a product,

performing complex calculations, or retrieving information from a database

Identify a specific user and present an interface that is customized for that user

Present content that is highly volatile, such as inventory, pending order, and shipment information.

This is only a partial list. Basically, you can do anything with a Web application that you can imagine doing with any client/server application. What makes a Web application special is that the client/server interaction takes place over the Internet.


Software Requirement Specification

The SRS document basically contains the requirements in an informal form. It is the origin of most software is in the need of a client, who either wants to automate an existing manual system or desires a new software system. The important purpose of developing an SRS is helping the clients understand their own needs. Requirements have to be visualized and created. In order to satisfy the client which is the basic quality objective of software development, the client has to be made aware of the potentials and aided in visualizing and conceptualizing the needs and the requirements of his organization. In this we tested uttarakhand roadways website according to its workability, impact on the user, ability to meet the user needs, and the effective use of the available resources. Basically we have to justify the following major questions:

What shall be the solution available? The solution is to user requirement is the website that will fulfill the basic information needs of user, so providing him easy access can be the very good solution.

What will the proposed system will achieve? Through proposed system we will be able to provide user with the refined and collected info and also with few clicks. And user will not have to go here and there for Data. Below are the characteristics of a good SRS document:

Concise : The SRS document should be concise and at the same time unambiguous, consistent, and complete.

Structured: The SRS document should be well-structured. A well-structured document is easy to understand and modify.

Black box view : It should only specify what the system should do and refrain from stating how to do. It should view the system to be developed as a black box, and should specify the externally visible behavior of the system.


Conceptual integrity : The SRS document should exhibit conceptual integrity so that the reader can easily understand the contents.

Justification and need of System

This website is for every person who wants to get information related to

uttarakhand roadways. I have tried to present this website in such a way

that it will ease the person looking for Dehradun related information like

timing of buses ,arrival time, departure time etc. user doesn’t need

to waste a lot time in searching these information on the internet ,the

information is just a click away from him.

None of the existing website contains information in such a refined way as

this will produce. User want faster and easy access way to his required data and

this site will cater both the needs.

An Approach to System development

The basic approach used in System Design is PHASED DEVELOPMENT

PROCESS. The development process consists of many phases, each phase

ending in a defined output. The phases are performed in the order specified by

the processes model. This ensures that the cost of the problem is lower than it

would have been by taking the whole problem together. The approach used in

System Design is Object Oriented Approach.


Object oriented Design Approach Object oriented design is a relatively new technique. In this technique various objects that occur in the problem domain and the solution domain are first identified and different relationships that exist among these objects are identified. The object structure is further refined to obtain the detailed design. The OOD approach has several benefits such as lower development time and effort and better maintainability of the product.


Recognition of Need

Feasibility Study

Analysis

Design

Implementation

Post Implementation

Maintenance

System Development Process

Introduction


The Data flow diagrams and various processing logic techniques show

how, where, and when data are used or changed in an information system, but

these techniques do not show the definition, structure, and relationships within

the data.

System design is a solution of “how to” approach to the creation of the

proposed system. It facilitates and provides the procedural detail necessary for

implementation of the system recommended in the Initial study and Feasibility

study. Emphasis is given on translating the requirements into design

specification. System design is a highly creative process. This System design

process is also referred as data modelling. The most common format used for

data modelling is entity-relationship (E-R) diagramming. Data modelling using

the E-R notation explains the characteristics and structure of data independent

of how the data may be stored in computer memories.

The design of the system is essentially a blueprint or a plan for the

solution for the system. Here we consider a system to be a set of components

with clearly defined behavior that interacts with each other in a fixed defined

manner to produce some behavior or services for its environment. A component

of a system can be considered a system with its own components. In a software

system a component is a software module

Data Flow Diagram Level 0 DFD


Level 2 DFD


USER UTTARAKHAND ROADWAYS

INFORMATION ABOUT UTTARAKHAND ROADWAYS

USERREQUEST

SEARCHING FOR REQUEST

E-TICKET

PHOTO GALLARY

ENQUERY

FACILITY

MANUAL

ADMINISTRATER

TIME TABLE

GENERAL ENQUERY

Level 1 DFD


USERREQUEST

SEARCHING FOR REQUEST

ADMINISTRATER

TIME TABLE GENERAL

ENQUERY

Tables


Database:-MS AccessDB Name : Dun

School Table:

SName(Text) Address(text) Contact(number)

Established(number)

Sams sams A

4 FMCA F

5 5 F

Medical College:

CName(text)

Course(text) Address(text)

Website Contact(number)

One MCA 5

Two MCA 5 B

three MCA 5 B


Engg. College:

SId(Number)

SName(text)

Course(text) Address(text)

Website Contact(number)

1 One MCA 5

2 Two MCA 5 B

3 Three MCA 5 B


Testing Phase

Testing is the major quality control measure used during software development. The aim of the testing process is to identify all defects existing in the software product. Thus its basic aim is to detect the errors in the software. Testing a program consists of subjecting the program to a set of test inputs and observing if the program behaves as expected. If the program fails to behave as expected, then conditions under which failure occurs are noted for later debugging and correction.

A software product goes through three levels of testing: Unit Testing Integration Testing System Testing

Unit Testing: The starting point of testing is Unit Testing. It includes the testing of different units (or modules) of a system in isolation. Each module is tested separately which is often performed by the coder himself simultaneously along with the coding of the module. The purpose behind Unit Testing:

During this phase each module is unit tested to determine the correct working of all the individual modules.

It involves testing each module in isolation as this is the most efficient way to debug the errors identified at this stage.

Another reason behind testing a module in isolation is that the other modules, with which this module has to be interfaced, may not be ready.

Integration Testing : The primary objective of integration testing is to test the module interfaces in order to ensure that :-

There are no errors in the parameter passing. When one module invokes another module


Integration of different modules is undertaken once they have been coded and unit tested. The modules are integrated in a planned manner. However the different modules making up a software product are almost never integrated in one shot.

It is normally carried out incrementally over a number of steps. During each integration step, the partially integrated system is

tested and a set of previously planned modules are added to it.

System Testing :

System tests are designed to validate a fully developed system that it meets its requirements. System testing usually consists of three different kinds of testing activities :

Alpha Testing : It is the system testing performed by the development team.

Beta testing: It is the system testing performed by a friendly set of customers.

Acceptance testing: It is the system testing performed by the customer himself after the product delivery to determine whether to accept or reject the delivered product.

System testing is usually carried out in a planned manner according to the system test plan document. The system test plan identifies all testing related activities that must be performed, specifies the schedule of testing, and allocates resources. It also lists all the test cases and the expected outputs for each test case.


Maintenance

The maintenance of a software product requires much more effort than the effort necessary to develop the product itself. This phase involves the following three kinds of activities:-

(1) Correcting errors that were not discovered during the product development phase. This is called Corrective Testing.

(2) Improving the implementation of the system and enhancing the functionalities of the system according to the customer’s requirements. This is called Perfective Maintenance.

(3) Porting the software to work in a new environment. For example, porting may be required to get the software to work on a new computer platform or with a new operating system. This is known as Adaptive Testing.

Thus, maintenance involves understanding the existing software( code and related documents), understanding the effects of change, making the changes – to both the code and the documents – testing the new parts ( changes ), and retesting the old pan that were not changed.

Hence, we can say that maintenance is one form of change or software rework that typically is done after the software development is completed and the software has been deployed.


Future Scope of the System

The website is easy to operate, it doesn’t require one to be familiar with computer, one having a bit knowledge of computer can be befitted by the site as well. Since all the information is just a click away from user so the project can be implemented as a website. The limitation of our website is that it can provide us information related to Dehradun only. The future scope of the project is as follows:-

This project can be implemented as a website to cater the need of users

related to basic information about Dehradun. In future it can be extended to a portal also to serve people in a better way.


Conclusion

The computer provides a great accuracy, speed and increasing volume of data

which accelerate the work of that department .Computer is a central element in

an organization, despite the fact that the computer is nothing more than a tool

for processing data, but its real role is to provide information for decision and

for planning and controlling operation.

In present world , life is going very fast and everybody want a good

and correct information is very short time and we are also moving towards

twenty first century all of us wants some new in the coming century, for this we

had developed this software program for easily handling. So our aim to develop

a proposed system which solved this problem and save the time and gives good

facility. Our goal is to develop a computerized system which can hide the

difficulties in current system. We tried our best to develop this software

package which solves the problems or difficulties of the current system.


Wrox Professional: C# 2008

Microsoft Press: MCTS

APress -ASP.Net

www.w3schools.org

www.euttaranchal.com

www.dehradun.nic.in

www.dooneducation.com/schools

www.mytripindia.com/Uttaranchal


Dehradun at a Glance

Documents

Transcript of Dehradun at a Glance