sample report-7th and 8th.pdf

CHAPTER-1 INTRODUCTION

1

Travel Sharing And Habit Tracking Introduction

SITG(IT) 1

1.1 PROJECT DETAIL

Our Greatest asset is share the vehicle and match habit among Crowd.!! This software we are developing for implicit solution client who is introducing their

daily travelling site in market.The company is taking a challenging step by introducing completely new concept sharing vehicle and match habit in market. The Introduction of the Software Requirement Specification(SRS) provides an overview of the entire SRS with purpose, scope, definition, acronyms, abbreviations, references and overview of SRS. The aim of this document is to gather and analyze and give in

depth insight of the complete Travel Sharing and Habit Tracking Software System by defining the problem statement in detail. Think about your own life and transportation facility With the proposed solution, website helps to users as in following ways:

Here are some features like Admin which manage all users account and activate

and deactivate function,

Also manages the time of transport.

User Can registered first in this website, and then he/she can visit the site and choose routes also share and post vehicle.

User can also match the habit with other user .

Whenever there is any delay in vehicle and if he/she is part of that vehicle then there will be SMS alert to that user.

User who gets the information about the status of the vehicle

So in this manner user will have facility to save the time.

Even system will provide suggestions about other service providers when particular service is cancelled so user doesnt have to spend much time on finding the information

This system will save cost in terms of fuel and other too.User can give comment and rating.

Can payment using cash and paypal.

1.2 PROJECT PURPOSE The purpose of this SRS document is to provide a detailed overview of our software

product, its parameters and goals. This document describes the project's target


2

audience and its user interface, hardware and software requirements.It defines how our client, team and audience see the product and its functionality. Nonetheless, it

helps any designer and developer to assist in software delivery lifecycle (SDLC) processes.

The Travel sharing and habit tracking web application is used to share vehicle,save expensese and to meet great pepole .It will match the habits of users.This SRS aims to provide the detail description on the client requirements for travel sharing and habit tracking application. With the proposed solution, website helps to users as in following ways:

Register for free. Create their profile and manage it.

Can share vehicle with other.

Can make comments and also rate the vehicle.

Can post vehicle.

Connecting people who are going from same route.

1.3 PROJECT SCOPE

Travel sharing is an online sharing site, searching, posting and sharing website. It provides all these features to its customers for free, thereby decreasing the cost spent on

them largely.User can post and share vehicle and do payment according to routes,it will also provide detail of different vehicle and their timing.User can get discount by registering in limited time period. Admin will manage the whole front and back end of the application.

1.3.1 PROJECT FEATURES The Web Asset Management has following features.

Asset Procurement on arrival of Assets.

Asset check-in.

Assignment of Asset to user here user is the employee of the organization

Registration of complaints regarding Assets.

Asset Check-out.

The system provides login facility to the users.

The system allows the members to manage the assets 24 hours a day and all the through the year.


3

The system lets the administrative staff to check which members have Assets and

who have registered complaint for their asset and which complaints are sorted out.

The system allows the administrator to procure assets, check-out assets to employees, check-in the complaints from users, sends the assets for repairing.

1.4 PROJECT OBJECTIVES The main objectives of this system are as below:- Travel Sharing is considered as big and enhance the business of private travelling agents.This system is capable for maintaining details of different vehicle,their timing and give also route information.The central idea of this website is to gather people,enjoy the company,save expense and cooperate each other.

1.5 TECHNOLOGY AND LITERATURE REVIEW

1.5.1 Technology Review What is PHP? PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML.

Instead of lots of commands to output HTML (as seen in C or Perl), PHP pages contain HTML with embedded code that does "something". The PHP code is enclosed in special start and end processing instructions that allow you to jump into and out of "PHP mode."

What distinguishes PHP from something like client-side JavaScript is that the code is executed on the server, generating HTML which is then sent to the client. The client

would receive the results of running that script, but would not know what the underlying code was. One can even configure ones web server to process all your HTML files with PHP, and then there's really no way that users can tell what the code was.The best things in using PHP are that it is extremely simple for a newcomer, but offers many advanced features for a professional programmer as well.


4

What can PHP do? Anything. PHP is mainly focused on server-side scripting, so you can do anything any

other CGI program can do, such as collect form data, generate dynamic page content, or send and receive cookies. But PHP can do much more. There are three main areas where PHP scripts are used.

Server-side scripting. This is the most traditional and main target field for PHP. You

need three things to make this work. The PHP parser (CGI or server module), a web server and a web browser. You need to run the web server, with a connected PHP installation. You can access the PHP program output with a web browser, viewing the

PHP page through the server. All these can run on your home machine if you are just experimenting with PHP programming. See the installation instructions section for more information.

Command line scripting. You can make a PHP script to run it without any server or browser. You only need the PHP parser to use it this way. This type of usage is ideal for scripts regularly executed using cron (on *nix or Linux) or Task Scheduler (on Windows). These scripts can also be used for simple text processing tasks. See the section about Command line usage of PHP for more information.

Writing desktop applications. PHP is probably not the very best language to create a desktop application with a graphical user interface, but if you know PHP very well,

and would like to use some advanced PHP features in your client-side applications you can also use PHP-GTK to write such programs. You also have the ability to write

cross-platform applications this way. PHP-GTK is an extension to PHP, not available in the main distribution. If you are interested in PHP-GTK, visit its own website.

PHP can be used on all major operating systems, including Linux, many Unix variants (including HP-UX, Solaris and OpenBSD), Microsoft Windows, Mac OS X, RISC OS, and probably others. PHP has also support for most of the web servers today. This includes Apache, IIS, and many others. And this includes any web server that can utilize the FastCGI PHP binary, like lighttpd and nginx. PHP works as either a module, or as a

CGI processor.

PHP also has support for talking to other services using protocols such as LDAP, IMAP,

SNMP, NNTP, POP3, HTTP, COM (on Windows) and countless others. You can also open raw network sockets and interact using any other protocol. PHP has support for the


5

WDDX complex data exchange between virtually all Web programming languages. Talking about interconnection, PHP has support for instantiation of Java objects and using them transparently as PHP objects.

PHP also has useful text processing features, which includes the Perl compatible regular expressions (PCRE), and many extensions and tools to parse and access XML documents. PHP standardizes allof the XML extensions on the solid base of libxml2, and extends the

feature set adding SimpleXML, XMLReader and XMLWriter support.

MySQL OVERVIEW:

MySql MySQL, the most popular Open Source SQL database management system, is developed, distributed, and supported by Oracle Corporation.

Features Of MYSQL: Cross-platform support

Stored procedures

Triggers

Cursors

Updatable Views

True Varchar support

A database is a structured collection of data. It may be anything from a simple

shopping list to a picture gallery or the vast amounts of information in a corporate

network. To add, access, and process data stored in a computer database, you need a database management system such as MySQL Server. Since computers are very good at handling large amounts of data, database management systems play a central role in computing, as standalone utilities, or as parts of other applications.

MySQL is a relational database management system.

A relational database stores data in separate tables rather than putting all the data in one big storeroom. This adds speed and flexibility. The SQL part of MySQL stands for Structured Query Language. SQL is the most common standardized language used to access databases and is defined by the ANSI/ISO SQL Standard. The SQL standard has


6

been evolving since 1986 and several versions exist. In this manual, SQL-92 refers to the standard released in 1992, SQL:1999 refers to the standard released in 1999, and SQL:2003 refers to the current version of the standard. We use the phrase the SQL standard to mean the current version of the SQL Standard at any time.

MySQL software is Open Source.

Open Source means that it is possible for anyone to use and modify the software. Anybody can download the MySQL software from the Internet and use it without paying anything. If you wish, you may study the source code and change it to suit your needs. The MySQL software uses the GPL (GNU General Public License),http://www.fsf.org/licenses/, to define what you may and may not do with the software in different situations. If you feel uncomfortable with the GPL or need to embed MySQL code into a commercial application, you can buy a commercially licensed version from us.

MySQL Server was originally developed to handle large databases much faster than existing solutions and has been successfully used in highly demanding production environments for several years. Although under constant development, MySQL Server today offers a rich and useful set of functions. Its connectivity, speed, and security make MySQL Server highly suited for accessing databases on the Internet.

MySQL Server works in client/server or embedded systems.

The MySQL Database Software is a client/server system that consists of a multi-threaded SQL server that supports different backends, several different client programs and libraries, administrative tools, and a wide range of application programming interfaces (APIs).

We also provide MySQL Server as an embedded multi-threaded library that you can link into your application to get a smaller, faster, easier-to-manage standalone product.

A large amount of contributed MySQL software is available.

It is very likely that your favorite application or language supports the MySQL Database Server.


7

Xampp Overview: XAMPP is a free and open source cross-platform web server solution stack package, consisting mainly of the Apache HTTP Server, MySQL database, and interpreters for scripts written in the PHP and Perl programming languages. Officially, XAMPP's designers intended it for use only as a development tool, to allow website designers and programmers to test their work on their own computers without

any access to the Internet. To make this as easy as possible, many important security features are disabled by default.[2] In practice, however, XAMPP is sometimes used to

actually serve web pages on the World Wide Web. A special tool is provided to password-protect the most important parts of the package.

XAMPP also provides support for creating and manipulating databases in MySQL and SQLite among others.

CHAPTER-2 PROJECT MANAGEMENT

2

Travel Sharing And Habit Tracking Project Management

SITG(IT) 8

2.1 FEASIBILITY STUDY Feasibility is a practical extent to which a project can be performed successfully. To evaluate feasibility, a feasibility study is performed, which determines whether the solution considered to accomplish the requirements is practical and workable in the software or not. Such information as resource availability, cost estimate for software development, benefits of the software to organization, and cost to be incurred on its

maintenance are considered. The objective of the feasibility study is to establish the reasons for developing software that is acceptable to users and adaptable to change. A feasibility study is a short, focused study, which aims to answer a number of questions:

Does the system contribute to the overall objectives of the organization? Can the system be implemented using current technology and within given cost

and schedule constraints?

Can the system be integrated with systems which are already in place?

Operational Feasibility

Technical Feasibility

Scheduling Feasibility

Economic Feasibility

Implementation Feasibility Now each of them is explained briefly, as below.

2.1.1 OPERATIONAL FEASIBILITY STUDY The main purpose of checking Operational Feasibility is to find out whether the system

will be functional after its development and installation or not. The outcomes of the operational feasibility are as follows:

Travel sharing and habit tracking provides all available vehicle published on site.

They can be administered from remote locations like mail,phone.

So, it is supposed to improve working efficiency of its user.

Hence this application is operationally feasible.

2.1.2 TECHNICAL FEASIBILITY The main purpose of checking Technical Feasibility is to examine whether the current technology is sufficient for the development of the system. The outcomes of the technical feasibility are as follows:


SITG(IT) 9

Travel sharing and habit tracking application uses php as programming

platform, Xamp server in front end and My SQL in back end. The application is developed in PHP can be run on any web browser like

Opera, Chrome, Mozilla Firefox, Internet Explorer etc.

For back end we have used My SQL server for data connection. It provides faster response to its users. It is accurate, reliable and easy to use on

WWW.

Further expansion of the system is possible easily.

Hence this application is technically feasible.

2.1.3 TIME SCHEDULE FEASIBILITY A project will fail if it takes too long to be completed before it is useful. Typically this means estimating how long the system will take to develop, and if it can be completed in a given time period using some methods like payback period. Given our technical

expertise, are the project deadlines reasonable? Some projects are initiated with specific deadlines. You need to determine whether the deadlines are mandatory or desirable.

2.1.4 ECONOMICAL FEASIBILITY Economic analysis could also be referred to as cost/benefit analysis. It is the most

frequently used method for evaluating the effectiveness of a new system. In economic analysis the procedure is to determine the benefits and savings that are expected from a

candidate system and compare them with costs..If the expected benefits equal or exceed costs, the system can be judged to be economically feasible. Economic analysis is used for evaluating the effectiveness of the proposed system.

The economic feasibility will review the expected costs to see if they are in-line

with the projected budget or if the project has an acceptable return on investment. At this point, the projected costs will only be a rough estimate. A rough estimate of the project schedule is required to determine if it would be feasible to complete the systems project within a required timeframe. The required timeframe would need to be set by the organization.

2.1.5 IMPLEMENTATION FEASIBILITY The main purpose of checking Operational Feasibility is to find out whether the system will be functional after its development and installation or not. The outcomes of the

operational feasibility are as follows:


SITG(IT) 10

Service Provider website helps the user for getting information about new available Service product quickly by presenting the data in proper format online. Graphical

representation of data helps the user in taking proper decision in time.

So, it is supposed to improve the working efficiency of user.

So, this application is operationally feasible.

2.2 PROJECT PLANNING 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

Monitoring/measuring the project progress, and Facilitating communication

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.2.1 PROJECT DEVELOPMENT APPROACH AND JUSTIFICATION

Agile Software Development Agility refers to the quality of being agile. Internet software industry and Mobile and

wireless application development industry are looking for a very good approach of software development. Conventional software development methods have completely closed the requirements process before analysis and design process. As this approach is not always feasible and compatible with all others projects. In contrast to the conventional approaches, agile methods allow developers to make late changes in the requirement specification document. The focus of the Agile software development as

given by Agile Software Development Manifesto is presented in the following:

Individuals and interactions over processes and tools

Working software over comprehensive documentation.


SITG(IT) 11

Customer collaboration over contract negotiation

Responding to change over following a plan 1) There is vital importance of communication between the individual who are in development team, since development centers are located at different places. The necessity of interaction between Individuals over different tools and different versions

and processes is very vital. 1 2) The only objective of software development team is to continuously deliver the working software for the customers. New releases must be produced for frequent intervals.

3) The relationship between developers and the stakeholders is most important as the pace and the size of the project grows. Agile methods are using in maintaining good relationship with clients.

4) The development team should be well-informed and authorized to consider the possible adjustments and enhancements emerging during the development process.

Fig 2.1 Agile Lifecycle Agile methods Agile methods are designed to produce the first delivery in weeks, to achieve and early win and rapid feedback. These methods invent simple answers so that change can be less. These also improve design issues and quality as they are based on iteratively incremental

method.

What makes a method an Agile? When the process are: a) Incremental: Small releases with rapid iterations b) Cooperative: Customer and developer relationships


SITG(IT) 12

c) Straight: The method which is easy to learn and modify with documentation d) Adaptive: Able to embrace changes instantly

Different Agile Software Development methods 1) Extreme programming 2) Scrum 3) Feature driven development

Extreme programming The life cycle of Extreme programming consists of five phases

a) Exploration b) Planning c) Iteration on releases d) Product ionizing e) Maintenance f) Death

Extreme programming is a light weight software methodology for a small to medium sized teams developing software in the rapidly changing requirements situation. XP

matches the behavior of successful programmers in the wild

Tests

Refactoring

Evolutionary delivery

Incremental planning

Less overhead

Scrum

The term SCRUM originally derives from a strategy in the game of rugby where it

denotes getting an out of play ball back into the game with teamwork. Scrum

concentrates on how the team members should function in order to produce the system flexibly in a constantly changing environment. Scrum is extremely simple model used by different software companies from long time, which works with existing engineering practices and is scalable and work with common sense which is to say it is very easy.

Scrum process includes three phases 1. Pre-game

2. Development

3. Post-game


SITG(IT) 13

1. Pre-game phase includes two sub-phases Planning and Architecture design

Planning phase: includes the development of the required system. A Backlog list is created, which contains all the requirements that are known at that moment. In every iteration the Back log list is updated by scrum team to gain commitment for the next iteration.

Architecture phase: In this phase an abstract view of the model is designed by viewing Backlog list.

2. The Development phase:

This phase takes care of the different variable like time frame, quality, requirements, recourses, technologies and tools. Sprints are the iterative cycles where functionality is

developed or enhanced to produce new increments. Each Sprint includes the traditional phases of software engineering.

Requirement

2 Analyses

Designs

Evolution and delivery

3. The Post-game phase close to release.

Roles in Scrum

SCRUM master

Product owner

Scrum Team

Customer

Feature Driven Development FDD is agile approach for software development systems. It provides enough structure for large items, emphasis on quality and working software, delivers frequent, tangible

results.

Five phases of FDD

Develop a overall model

Build a features list

Plan by feature

Design by feature


SITG(IT) 14

Build by feature

Conclusions As we came to know that traditional software development approaches are more mechanistic which concentrate more on Processes, tools, contracts and plans. In contrast to traditional methods, agile methods keep emphasis on interaction, working software, embracing change at any moment of the project, customer relationships. The method can be agile if it is:

Incremental

Cooperative

Straightforward

Agile view is more people centric rather than plan-centric.

Agile methods are not defined by a small set of principles, practices and techniques. It creates a strategic capability which has capability of responding to change, capability to

balance the structure and flexibility, capability of innovation and creations through development team and uncertainty.

Scrum

FDD (Feature driven development) DSDM (Dynamic systems development method)

2.2.2 PROJECT PLAN Project planning is basically concerned with identifying and measuring activities, milestones and deliverables produced by project. Thus in this section I cover following:- Estimating some basic attributes of the project a) Duration: How long will it take to complete the development? The project that we have taken contains functionalities which are very complex for an undergraduate. We need to do a detailed research of what combination of technologies would be best for the project, get acclimatized to them, do the rest of the planning and go ahead with the work. Hence the duration of the Project can be roughly estimated to 10 months.

b) Efforts: How much efforts would be required? Since it is a two people group and as it is a very hazy picture ahead of how to go about the project, figuring that out and considering the pros and cons would take up a lot of effort in itself. Thus efforts can be estimated to 3 hours of weekdays work for 10 months


SITG(IT) 15

2.2.3 MILESTONES AND DELIVERABLES Management needs information. As software is intangible, this information can only be

provided as documents that describe the state of the software being developed. Without this information, it is impossible to judge progress and cost estimates and schedules cannot be updated. When planning a project series of milestones are established.

Table 2.1 Travel Sharing And Habit Tracking Milestones

Sr. No Activities Date

1 Study of available system 20/07/2013

2 Prior tools study 27/07/2013

3 Project Synopsis 1/08/2013

4 Requirement Gathering 8/8/2013

5 Analysis Iteration-1 22/08/2013

6 Analysis Iteration-2 16/09/2013

7 Prototype 28/09/2013

8 Data Dictionary 15/10/2013

9 UML Diagrams 2/11/2013

10 Designing 12/01/2014

11 Coding 5/02/2014

Roles And Responsibilities The team members are responsible for all documentation to be developed and for all work

to be done. I am grateful to my team member for her dedication in our project development; without her it would be tough for me to even take up this project. For better development of a project, internal and external helped me.


SITG(IT) 16

2.2.4 GROUP DEPENDENCIES As I have described there are two members in my team including me, so there has is

group dependency. Team structure is as follows

Fig-2.2 Group Dependencies

2.3 PROJECT SCHEDULING Scheduling of a software project does not differ greatly from scheduling of any multitask engineering effort. Therefore, generalized project scheduling tools and techniques can be applied with little modification to software projects. Project scheduling consists of identifying the tasks needed to complete the project, determine the dependency among different tasks, plan the starting and ending dates for various tasks and determine the chain of tasks that determine the duration of the project. In Project scheduling we decide the order in which to do the tasks.

Table 2.3 Project Scheduling

Task No. Task Name Starting Ending 1 Domain Understanding August September

2 Analysis September December

3 Learning Process August January

4 Design December March

5 Coding December April

6 Coding and Testing December April


SITG(IT) 17

7 Limitation & Future

Enhancement

March April

8 Conclusion March April

9 Documentation March April

10 Final Documentation March April

CHAPTER-3 SYSTEM REQUIREMENT STUDY

3

Travel Sharing And Habit Tracking System Requirement Study

SITG(IT) 18

3.1 STUDY OF CURRENT SYSTEM Current System is web-based Application on PHP. My SQL is used as back end to

store and perform operations on database. The current system named Travel sharing and habit tracking is a site in which user share their routes and discuss their own travelling

problem to their colleagues and also communicate people of surrounded area who are coming from same route.

Travel sharing and habit tracking website will be providing right information at right

time to all related users and not stuffing users with information. This website is way for doing the team work about passing the right information to only those people for whom this information is useful. This website will give the alerts in form of push notifications

so there I no need for constant internet connection and it is really useful and reduces the panic of person.

Travel sharing and habit tracking website will save complete time for searching and also

finding the best match for travel time and expense sharing.This system will save cost in terms of fuel too.This system will match the profile likings and habit and based on that pure information can be provided so this is completely business intelligence based which can make the process fast as well.

3.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM

This application finds all possible match but still if information is being provided is depended on the information entered so if information entered wrongly it will provide wrong information.This system can find best match but further communication for

sharing the vehicle and other things user has to communicate with other users by himself so this system will not provide the way to make the sharing possible 100%.This

application is compatible with web based so user must be web literate.This website is based on assumption then user know how to use website and also how to find information and create profile.

3.3 USER CHARACTERISTICS

Each System has various types of users.Some have all the permissions to the access all the system features while some others has a subset of all the permissions.In this system the Users roles and permissions need to be specified very specifically and each role must

be given only that set of permissions which their role is defined for.


SITG(IT) 19

Administrator Admin is user who manages user account, general contents of site,can receive suggestions from public, has power to edit, delete, activate, deactivate any user or any content, can make general notification, can manage database, view all the payment processed through site.For this task admin must have Internet knowledge.

User(Transpoter) User can post vehicle and add route, registration features, create profile and manage it, contact admin, have quick links, provide suggestions, make comments

and rating, see routes and other features.

User(Traveller) User can share vehicle and search route,view Gallery or photos of different vehicle and share them,create their account and manage their profile,if any delay

then send push notification,give comment and rating.

3.4 HARDWARE AND SOFTWARE REQUIREMENTS Hardware Requirement

Pentium 4 processor & above.

Any operating system

Minimum 512 MB RAM

Minimum 512 MB Hard Disk Space

Any Monitor

Software Requirement

Any operating system

XAMP/WAMP server

PHP- Front End

My SQL- Back End Macromedia Dreamweaver

Adobe Photoshop

Rapid Php


SITG(IT) 20

3.5 CONSTRAINTS 3.5.1. REGULATORY POLICIES

As all the documents are confidential they will be only available to me only. Documents will be uploaded by the Administrator only.

3.5.2 INTERFACES TO OTHER APPLICATIONS

This system is a web application and can be used in day to day life for sharing and posting vehicle website,so that it can be accessed anywhere.

3.5.3. PARALLEL OPERATIONS At a time users can access the System for same functions. It means any user can post or share vehicle at a time. Travel sharing and habit tracking has different modules. Admin module is used for keeping records of Vehicle Categories, Post vehicle,Share vehicle, users and route information. It will manage all

users. It also manages the successfully Posting vehicle by transpoter.It also manage user and transaction. The data would then be stored to a database.

Since all of the modules work simultaneously, it requires concurrent updating of database. This problem can thus be solved by effective use of database management system. Use of transaction remove this problem and would also ensure updating & deletion of the database.

3.5.4. HIGHER ORDER LANGUAGE REQUIREMENTS The project required XAMPP, that is a free and open source cross-platform web server solution stack package, consisting mainly of the Apache HTTP Server, MySQL database, and interpreters for scripts written in the PHP and Perl programming

languages.XAMPP also provides support for creating and manipulating databases in MySQL and SQLite among others. 3.5.5. RELIABILITY REQUIREMENTS The main reliability requirement is validation of entered data. Without proper

validation the system does not allow to enter that value in the database. For example in email id the user cannot enter any dummy value, the validation checks that weather

there is @ or . symbol. Also any null value is not allowed in place of compulsory fields. The system also uses transaction features such as whenever the transaction is not fully completed (i.e. due to power failure) it is roll backed. Only complete transaction allows successful updating of data to the data store.


SITG(IT) 21

3.5.6 SAFETY AND SECURITY CONSIDERATION Without proper authentication unauthorized users will be unable to alter the database.

For e.g.: without administrator password no one will be able to create or delete the workspace once allocated and user will be unable to updating of records. Unauthorized access, revelation, or destruction of data can violate individual privacy. Corruption of business data can result in significant and potentially catastrophic losses

to companies.

In this software, security threats are at user level as well as on data level.

1. User Level Security:- Only authorized user can able to access this S/W. No one can able to access this S/W without knowing username and password. 2. Data Level Security:- Data level security provided in back end. This S/W is run on SQL server express edition as back end tool. Administrator, merchant, customer has all rights to insert,

update, delete any data and everything is shown to them.

3.6 ASSUMPTIONS AND DEPENDENCIES Assumptions:

Administrator is present all the time. Administrator handles the database and the user privileges. 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.

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 REQUIREMENT OF PROPOSED

SYSTEM

4

Travel Sharing And Habit Tracking Requirement Of Proposed System

SITG(IT) 22

4.1 Main Module of the System There are four main module of the system mainly Login, Insert, Update and Delete.

4.1.1 INTRODUCTION The Travel sharing and habit tracking web application is used to share vehicle,save expensese and to meet great pepole .It will match the habits of users.This SRS aims to provide the detail description on the client requirements for travel sharing and habit

tracking application.

4.1.2 FUNCTIONALITY OF TRAVEL SHARING

Register for free. Create their profile and manage it.

Can share vehicle with other.


User Can registered first in this website, and then he/she can visit the site and choose routes also share and post vehicle.

Can make comments and also rate the vehicle.

Can post vehicle.

Connecting people who are going from same route.

This system will save cost in terms of fuel and other too.

4.1.3 REQUIREMENT OF TRAVEL SHARING There are so many websites in market which can provide you route information and also timing information about different trains, buses and flights, etc.So,it will not support public transport but private only and he/she wanted solution for sharing vehicles going from same route.Through this website user share their routes and discuss their own traveling problem to their colleagues and also communicate people of surrounded area who are coming from same route.

4.1.4 MAJOR COMPONENTS OF TRAVEL SHARING There are three major components in web asset management:

Posting

Sharing

Searching


SITG(IT) 23

4.1.5 DESCRIPTIVE DATA

Administrator: Admin is user who manages user account, general contents of site,can receive suggestions from public, has power to edit, delete, activate, deactivate any user or any content, can make general notification, can manage database, view all the payment processed through site.For this task admin must have Internet knowledge.

Users: o Transpoter: User can post vehicle and add route, registration features,

create profile and manage it, contact admin, provide suggestions, make comments and rating, see routes and other features.

o Traveller : User can share vehicle and search route,view Gallery or photos of different vehicle and share it,create their account and manage their profile,if any delay then send push notification,give comment and rating.

4.1.6 CONNECTING FEATURE AND ATTRIBUTES

Poster

Poster can post vehicle.

Poster cant share all information with other user until he/she registered or login.

Traveller

User can Share vehicle. User can search a vehicle,but after resgistering Through this people can connect each other,discuss problems of travelling with

each other,and enjoy company as well.

4.1.7 USABILITY OF TRAVEL SHARING Any user wish to be perfect in there daily management schedule like office timing, safety and security and want to be a regular in their day to day schedule.Through this

site user can post and share vehicle and also search vehicle by entering their place and timing information.If he/she is convinent to their searched route and vehicle then they can go,and enjoy the company with them.Use can save money and save fuel.


SITG(IT) 24

4.1.8 AREAS WHERE TRAVEL SHARING IS USED???

The web based application is mainly used in a private transportation. This project in real life will be useful to people like Students and also helpful to Handicapped Person. Normal people who do job and doing up down on daily based .People who like to share the vacation with other people .People who like to share time and cost too.

4.1.9 FUTURE OF TRAVEL SHARING In future we will develop the android and iphone app for this

We will set auto alerts for that as well

We will make site more scalable as well.

In future we will add advertisement module in the application

4.2 MODULE DESCRIPTION Login

To access the application the users have to login first.

According to the username and password of the user their rights(privileges) are provided.

User can visit all pages but cant access any page without registering/login

Insert:

In insert the user can first fill registration form and can choose the status.

After login user can fill all the form which is conveninent for them.

Update: Any details which are needed to be changed after it is registered or inserted are

altered using update.

Delete: Any details you want to remove from database is removed by using delete.

4.3 FEATURES OF NEW SYSTEM Here are some features like Admin which manage all users account and activate and deactivate function,


User Can registered first in this website, and then he/she can visit the site and


SITG(IT) 25

choose routes also share and post vehicle.

User can also match the habit with other user .

User who gets the information about the status of the vehicle

So in this manner user will have facility to save the time.

This system will save cost in terms of fuel and other too.User can give comment and rating.

Manual work will be reduced.

CHAPTER-5 SYSTEM DESIGN

5

Travel Sharing And Habit Tracking System Design

SITG(IT) 26

5.1 SYSTEM ARCHITECTURE DESIGN 5.1.1 USE CASE DIGRAM

The Use case diagram is used to define the core elements and processes that makeup a system. The key elements are termed as "actors" and the processes are called "use cases." The Use case diagram shows which actors interact with each use case.

Table: 5.1 Symbols for Use-Case diagram

UseCase: Use cases describe what a system does, not how it does it. A use case contains multiple

scenarios, each of which

describes a specific flow of events through the usecase.

Actor : An actor is a person, organization, or external

system that plays a role in one

or more interactions with the

system.

The relationship indicates that

the behavior of the extension use case may be inserted in the extended use case under some conditions.

Include is a Directed Relationship between two use cases, implying that the behavior of the included use case is inserted into the

behavior of the including use case.


SITG(IT) 27

5.1.1 (a) Use-Case Diagram for Admin


SITG(IT) 28

5.1.1 (b) Use-Case Diagram for Traveller and Transpoter


SITG(IT) 29

R 1 N

R N N

R 1 1

5.1.2 ER DIAGRAM:

Symbols used in E-R diagram:

Rectangles, which represent entity sets.

Ellipses, which represent attributes.

Diamonds, which represent relationship sets.

Lines, which link attributes to entity sets and entity sets to relationship sets.

Weak Entity,is an entity that must defined by a foreign key relationship with another entity as it

cannot be uniquely identified by its own attributes alone.

Many to many relationship

Many to many relationship

One to one relationship

Multivalued Attribute ,it can have more than one value.

Derived Attribute,is based on another attribute .

Weak Enity


SITG(IT) 30

5.1.2 ER-Diagram


SITG(IT) 31

5.1.3 SYSTEM ACTIVITY DIAGRAM Activity diagrams are normally used for business process modelling, for modeling the

logic captured by a single use case or usage scenario, or for modeling the detailed logic of business rule.

Table: 5.2 Symbols for Activity diagram

Symbol Name Symbol

Decision

Control Flow

Final State

Initial State

State

Action State

Fork Line

Join Line


SITG(IT) 32

Fig: 5.1.3(a) Activity Diagram of Admin


SITG(IT) 33

Fig: 5.1.3(b) Activity Diagram of Client


SITG(IT) 34

5.1.4 DATA FLOW DIAGRAM A data flow diagram (DFD) shows the functional relationship of values computed by a system, including input values, output values, and internal data stores. A data flow diagram is a graph showing flow of data values from their sources in objects through process that transform them to their destinations in other objects. A data flow doesnt show control information, such as the time at which the process is executed or decision

among the alternative data paths.

Symbols used in DFD:

Symbol name Description Process: People, procedure or devices that use or produce data. The physical component

is not defined.

External entity: An external entity such as an employee, team leader, and HR person are essentially physical entities external to the software system which interact with

the system by inputting data to the system or by consuming the data produced by the system.

Data Flow: A data flow symbol represents the data flow occurring between two processes

or between, an external entity and a process in the direction of the data flow arrow.

Data store: A data store represents a logical file. The direction of data flow arrow shows

whether data is being read from or written into a data store.


SITG(IT) 35

Fig: 5.1.4.1 Data Flow At context Level for main System


SITG(IT) 36

Fig: 5.1.4.2 Data Flow Level-1 for Admin


SITG(IT) 37

Fig: 5.1.4.3 Data Flow Level-1 for Transpoter


SITG(IT) 38

Fig: 5.1.4.4 Data Flow Level-1 for Traveller


SITG(IT) 39

5.1.5 SEQUENCE DIAGRAM It illustrates how objects interact with each other. It emphasizes time ordering of messages it can model simple sequential flows, branching, iteration, recursion and concurrency.

Table: 5.3 Symbols for Sequence diagram

Symbol Name Symbol

Object

Life Line

Active

Message

Object


SITG(IT) 40

5.1.5.1 Sequence Diagram for Transpoter


SITG(IT) 41

5.1.5.2 Sequence Diagram for Traveller


SITG(IT) 42

5.2 DATA DICTIONARY

5.2.1) Sign-Up: It contains initial login details for all kind of user.

5.2.2) Vehicle Category :This table is use for Selecting vehicle type.

Field Name DataType Null Constraints Description U_id Int(5) No Primary_key Auto Increment of User

identification number email_id Varchar(20) No Unique_key This will be used for

Emailid for particular type of user.

Password Varchar(20) No -- For Authentication Purpose.

Forgot_pass Varchar(20) No -- Registration_date Date No -- User registration Date

Registration_gender Varchar(20) No -- Identify male/female Registration_address Varchar(20) No -- User Address Security_questn Varchar(20) No -- Select question Security_answer Varchar(20) No -- Stores Answer of selected

question Phn_no Longint(10) Yes -- Contact purpose

Field Name Data Type Null Constraints Description

U_id Int(5) No Foreign_key Auto Increment of User identification number

Veh_type Varchar(20) No -- It selects the type of vehicle

Veh_no Varchar(20) No -- Identify veh no Veh_pic Blob Yes -- Display image of vehicle

Model_no Varchar(15) Yes Unique_key Define model No of vehicle

Veh_id int(10) No Primary_key AutoIncrment of vehicle id


SITG(IT) 43

5.2.3) Vehicle Sub_Category :It select Sub Category of vehicle

5.2.4) Upload Vehicle : This Table is used for posting a vehicle .

5.2.5) Share Vehicle : User Can Share Vehicle with other User

Field Name Data Type Null Constraints Description U_id Int(5) No Foreign_key Auto Increment of User

identification number Veh_Sub_id int(10) No Primary_key Identify unique id of

Sub_vehicle Veh_sub_type Varchar(20) No -- Choose vehicle Sub_type Veh_sub_pic Blob Yes Unique_key Display image

Sub_Model_no Varchar(15) Yes Unique_key Define model_no Veh_id int(10) No foreign_key AutoIncrment of vehicle

id


identification number Veh_id int(10) No Foreign_key AutoIncrment of vehicle

id Post_id bigint(10) No Primary_key Identification No. of

Upload vehicle Route Varchar(20) No -- Define Route Vacant seats(no. of person)

Int(5) Yes -- Remaining no.of seats


identification number Share_id Bigint(10) No Primary_key Identification No. of Share

vehicle


SITG(IT) 44

5.2.6) Requirement : User can suggest their ideas.

5.2.7) Search :User can search vehicle and Route and other details.

5.2.8) Route : Select and add Route From Source to Destination


identification number U_requirement varchar(25) No -- Give Suggestion Veh_id int(10) No Foreign_key AutoIncrment of vehicle id

Field Name Data Type Null Constraints Description search_id Int(5) No primary_key Unique no. for searching u_id Varchar(10) No Foreign_key Auto Increment of User

identification number veh_id bigint(10) No foreign_key AutoIncrment of vehicle

id Registration_gender Varchar(20) No -- Identify male/female Route Varchar(20) No -- Define route


identification number veh_id int(10) No Foreign_key AutoIncrment of vehicle

id

Route_id Int(5) No Primary_key Identify the route pickup_place Varchar(20) No -- Define source drop_place Varchar(20) No -- Define destination Distance Varchar(10) No -- Give distance in km. Charge Varchar(10) No -- Define routecharge


SITG(IT) 45

5.2.9) Payment: It is used for payment of transportation.

5.2.10) Album/Gallery : It is used for create gallery.

Field Name Data Type Null Constraints Description album_id Int(5) No primary_key Unique album no. of

photo

veh_id int(10) No Foreign_key AutoIncrment of vehicle id

u_id int(5) No Primary_key Auto Increment of User identification number

5.2.11) Sub_Album : It is used to create sub album



id

Veh_Sub_id longint(5) No Foreign_key Identify unique id of Sub_vehicle

Sub_album_id int(5) No Primary_key Unique identification no. for Sub_album



id

pay_id longint(5) No Primary_key Unique id for Payment Cash/cheque longint(20) No -- Cash/Paypal Distance Varchar(10) No -- Give distance in km. Charge Varchar(10) No -- Define route charge


SITG(IT) 46

5.2.12) Rating : This table give Rating for particular Vehicle



id

Rating_id longint(5) No Primary_key Particular Vehicle rating id

Rating int(6) No -- Give rating

5.2.13) Comment/Review : This table give Review/Comment for particular Vehicle.



id

Comm_id longint(5) No Primary_key Uniquely identify no.for Comment

hide_id longint(5) null -- Uniqueid for Hiding comment

Like_id longint(5) null -- likeid for liking comment Comment Varchar(10) null -- User give

comment/Rating

5.2.14) GPS System : This table is used for identify vehicle or route info. through GPS.

Field Name Data Type Null Constraints Description Map_id longiInt(10) No primary_key Map_id U_id int(10) No Foreign_key Auto Incrementof User identification

number Distance longint(5) Yes -- Give Distance in kilometer Source varchar(20) No -- Destination varchar(20) No --


SITG(IT) 47

5.2.15) Time Duration:It is used to view timing info.of particular user vehicle.

Field Name Data Type Null Constraints Description veh_id longiInt(10) No foreign_key AutoIncrment of vehicle id U_id int(10) No Foreign_key Auto Increment of User

identification number User_arrival_time Timestamp no -- Define arrival time

User_departure_time Timestamp No -- Define droping time

Route_id Int(5) No Foreign_key Identify the route

5.2.16) Alert : Its provide push notification.

5.2.17) Cancel : Its used for cancel of vehicle.

Field Name Data Type Null Constraints Description alert_id longiInt(10) No primary_key Uniquely identification of

alert id U_id int(5) No Foreign_key Auto Increment of User

identification number Veh_id int(10) No F_key AutoIncrment of vehicle id Status varchar(20) No -- It shows active/inactive

Status

Field Name Data Type Null Constraints Description cancel_id Int(5) No primary_key It defines cancellation id for

vehicle U_id int(5) No Foreign_key Auto Increment of User

identification number Veh_id longint(10) No F_key AutoIncrment of vehicle id Reason varchar(20) Yes -- Reason for cancellation Cancellation_Date Date No -- Cancel Date


SITG(IT) 48

5.2.18) Settings : It sets all privacy settings.

5.2.19) FAQ : It provides frequently asked questions information.

Field Name Data Type Null Constraints Description FAQ_id Bigint(8) No primary_key Auto increment FAQ -id Questions Varchar(255) No -- Define Frequently asked

questions Answers Varchar(255) No -- Define answers of the

questn

Field Name Data Type Null Constraints Description

Set_id Int(5) No primary_key Setting id U_id int(5) No Foreign_key Auto Increment of User

identification number Alert-status(on/off) varchar(10) Yes -- Active/inactive GPS-status varchar(10) Yes -- Active/inactive


SITG(IT) 49

5.3 SNAP SHOTS

Home Page: URL : http://localhost/treepreservation/travel%20sharing%20final/index.php


SITG(IT) 50

Register Page

URL: http://localhost/treepreservation/travel%20sharing%20final/register.php


SITG(IT) 51

Login PAGE

URL: http://localhost/treepreservation/travel%20sharing%20final/login.php


SITG(IT) 52

After Login Home Page

URL: http://localhost/treepreservation/travel%20sharing%20final/index.php


SITG(IT) 53

Transport page:select category of vehicle

URL: http://localhost/treepreservation/travel%20sharing%20final/transport.php


SITG(IT) 54

Fill form For 4wheeler

URL: http://localhost/treepreservation/travel%20sharing%20final/4wheeler.php


SITG(IT) 55

Gallery URL: http://localhost/treepreservation/travel%20sharing%20final/gallery.php

Vehicle information by clicking:photo URL: http://localhost/treepreservation/travel%20sharing%20final/gallery_result.php?veh_id=1


SITG(IT) 56

Search Route: URL: http://localhost/treepreservation/travel%20sharing%20final/route.php


SITG(IT) 57

Forgot Password:

URL: http://localhost/treepreservation/travel%20sharing%20final/login.php


SITG(IT) 58

By clicking forgot link new page..look like this: URL: http://localhost/treepreservation/travel%20sharing%20final/forgotview.php

Update Password: URL: http://localhost/treepreservation/travel%20sharing%20final/update.php


SITG(IT) 59

Contact us form:

URL: http://localhost/treepreservation/travel%20sharing%20final/contact.php


SITG(IT) 60

Admin Login

URL: http://localhost/treepreservation/admin/alogin.php


SITG(IT) 61

Admin Home Page URL: http://localhost/treepreservation/admin/menu.php#


SITG(IT) 62

Manage user

URL:http://localhost/treepreservation/admin/a_manageuser.php

URL: http://localhost/treepreservation/admin/a_managetransport.php

CHAPTER-6 IMPLEMENTATION PLANNING

6

Travel Sharing And Habit Tracking Implementation Planning

SITG(IT) 63

6.1 IMPLEMENTA TION ENVIRONMENT The project is a result of an individual effort. The structure depends on the management style of the organization, the number of people in the team is 3, their skill levels and the problem difficulty.

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 MYSQL. 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.

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 software development 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


SITG(IT) 64

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.

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


SITG(IT) 65

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


SITG(IT) 66

LOGOUT

LOGIN


SITG(IT) 67

echo "Welcome";

echo "&nbsp";

echo "&nbsp"; echo $row['user_name'] ; echo "&nbsp"; echo "&nbsp";

} } ?>

TravelSharing

Save money,Enjoy Company

Home

Transport

Route

Gallery

Contact


SITG(IT) 68

Settings

You Can SELECT Your interested Vehicle


SITG(IT) 69

You Can POST Your Vehicle

You can SEARCH in which Vehicle you want to travel


SITG(IT) 70

Home Transport Route Gallery Contact Settings Designed By:Binal Suthar , Gopi Patel , Poonam Patel

CHAPTER-7 TESTING

7

Travel Sharing And Habit Tracking Testing

SITG(IT) 71

7 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


SITG(IT) 72

many defects existing in a Software product. Thus testing provides a practical way of reducing defects in a System and increasing the users confidence in a developed system.

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.


SITG(IT) 73

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


SITG(IT) 74

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

Involve execution 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 programs 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


SITG(IT) 75

Non-usage of the results of functions

Uncalled functions and procedures

Storage management faults

Unassigned pointers

Pointer arithmetic

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.

CHAPTER-8 LIMITATION & FUTURE EXPANSION

8

Travel Sharing And Habit Tracking Limitation & Future Expansion

SITG(IT) 76

8.1 LIMITATION This website will be depended on the user provided information so if user will provide wrong information then it will be counted wrong

This website also provide the best match for sharing the route vehicles and after

matching the things user has to communicate for best deal

This website is based on assumption then user knows how to use website and also

how to find information and create profile

This website is scalabale up to 100000 user initially

This website is only 80% AJAX based

8.2 FUTURE EXTENSIONS In future we will develop the android and iphone app for this

We will set auto alerts for that as well

We will make site more scalable as well.

In future we will add advertisement module in the application.

CHAPTER-9 CONCLUSTION & REFERENCE

9

Travel Sharing And Habit Tracking Conclusion

SITG(IT) 77

9.1 CONCLUSION

This website is way for doing the team work about passing the right information

to only those people for whom this information is useful

This website will provide the alerts in form of push notifications so there I no need for constant internet connection and it is really useful and reduces the panic of person.

This website is not for checking the routes and all but passing information and we

will make sure that this website will have backward compatibility so can run on different android platforms

This website is initially free on Android Market so large number of users can get benefits from it.

9.2 REFERENCES

http://www.tripadvisor.in/

http://www.kayak.co.in/flights

http://en.wikipedia.org/wiki/Kayak.com

http://www.orbitz.com/

https://www.facebook.com/

http://www.chapman-freeborn.com/en/private_jet_features http://www.edrawsoft.com/entity-relationship-diagrams.php (April, 2004) http://creately.com/blog/diagrams/er-diagrams-tutorial/

Fundamental Of Software Engineering By RAJIV MALL(18th May 2009) Software Engineering : A practitioners Approach Ed.7 (January 2010) Php Reference:Beginner Of Intermediate Php5 By Mario Lurig (26April 2010)