Menu

Chapter 1 INTRODUCTION Project Description “Melanoma Detection” is a desktop application developed for the melanoma cancer detection

March 3, 2019 0 Comment

Chapter 1
INTRODUCTION
Project Description
“Melanoma Detection” is a desktop application developed for the melanoma cancer detection. Melanoma is one of the different type of cancer, it will effect on the skin. The skin cancer Melanoma is referred as Malignant Melanoma. This cancer will be caused by abnormal multiplication of pigment producing cell that give color to the skin. Melanoma detection in the primary stage is curable. The different between melanoma and benign moles is from the initial stage. It is a challenging task for doctors. Computerized Algorithms are being developed for detection. Some methods are designed which can be run through clinics and it can done for non-dermatologist.
Melanoma fatil skin cancer, is wide spreading stronger in this project. In this project, propose a method for melanoma lesion through an implementation of deep-learning system on a computer server equipped with Graphic processing unit(GPU). Clinical images are used to create the proposed project. That could be help dermatologist for the early detection of melanoma. For the project the input clinicall images contain illumination and noise effects that are preprocessed. There after preprocessed images are transferred to a pretrained convolution neural network(CNN). CNN is a member of deeplearning model. The cnn classifier distinguishes between melanoma and belgin cancer as classifier for the already trained by a number of training samples. The result shows that proposed method is more accuracy than it comparing to other method.
There are six modules are there in this application that are Data Preprocessing, Image Enhancement, Masking, Filtering, Creating CNN architecture and Training and Prediction. There are mainly two stages for detection. The two stages are preprocessing stages and CNN architecture. In preprocessing stage
Company Details
Name : FlemingEmbedded and Software solutions
Fleming is a software development and training company. The company engages in software, Embedded Hardware and training solutions. The company transforms the customers business through bringing greater flexibility, faster time to market, technical excellence and lower cost to their door step. Fleming performance outsourcing strategies help the customer’s business grow faster, stronger and achieve sustainable differential advantage against their competition. All are well-trained and motivated talent pool working cohesively to deliver solutions based around a proven global delivery model to clients across the globe.
Companies guarantee uncompromised customer satisfaction through a highly motivated team, which holds direct stake in company’s success. Regardless of industry (Automotive, Aeronautic, Medical, Consumer, Consulting, Training) a wide expertise in Software Development, Product Design, IT training and Support make a partner of choice for challenging projects. Services Software Development provides cost effective and high performance Web/Cloud based application using the latest technologies. Enterprise Applications company help customers to improve the enterprise’s productivity and efficiency by providing business logic support functionality. Mobile Application company Mobile Application development team always focuses on application performance and user satisfaction.
1.2 Contact Details
Fleming Embedded and Software Solutions LLP,
Bank Road, Kaloor, Ernakulum,
Kerala, India. Pin code: 682017,
Tel: +91-484-4045252.

Chapter 2
LITERATURE SURVEY
Existing and proposed system
The existing melanoma cancer detection is done manually done by dermatologist. Used in the melanoma detection is only through an experienced dermatologist. The existing system is time consuming. The problem with all the existing system is with the accuracy of the system.
The proposed system is a desktop application to reduce the complexity of the existing system. The existing system is not applicable in clinic the melanoma detection is only possible through dermatologist. To overcome this problem proposed system can be used. It can be applied through clinic. This system is not a time consuming problem. Without consulting doctor and only with the software detection will done. The result will be accurate.

2.2 Feasibility studyThis desktop application is checked for a technical feasibility. This can be applicable through clinic. So time consuming problem will not be there, this application will help in provide accurate result without time consuming so the customers can easily find their solution.

2.2.1 Technical Feasibility
Melanoma detection is a desktop application is technically feasible because the software Python, Opencv, Keras, and Tencerflow used in this application is open-sources and that are freely available.
2.2.2 Operational feasibility
Operational feasibility will be checked for the users those are using this application. This application will be user friendly.
2.2.3 Economic feasibility
All the used technologies are open source and freely available, the application is economically feasible. The implementation cost will be less because there is no external hardware used.

2.3 Tools and Technologies Used
ThisDesktop application is developed by using Python,OpenCV, Keras and Tencerflow.

2.3.1 Python
Python is a high level interpreted language. Python is designed to be highly readable. Python can be used as a scripting language. It support automatic garbage collection.

2.3.2 OpenCV
OpenCV (Open Source Computer Vision Library) was designed for computational efficiency and with a strong focus on real-time applications. OpenCV has C++, Python and java interfaces and support windows, Linux, Mac OS, iOS and Android.

2.3.3 Keras
Keras is an open source neural network library written in Python. It is capable of running on top of TensorFlow, Microsoft Cognitive Toolkit. It is designed to enable fast experimentation with deep neural networks.

2.3.4Tenserflow
TensorFlow is an open-source software library for dataflow programming across a range of tasks. It is a symbolic math library, and also used for machine learning applications such as neural networks.
2.4 Hardware and Software Requirement
2.4.1 Hardware Requirement
System : Intel i3 processor
Hard Disk : 40GB
Camera : Webcam
Monitor : 15 VGA Color
RAM : 1GB
2.4.2 Software Requirements
Operating system : Windows/ubuntu
Coding Language : Python
IDE : IDLE
Chapter 3
SOFTWARE REQUIREMENT SPECIFICATION
The SRS is a description of a software system to be developed. It lays out requirements of the proposed system. The SRS fully describes what the software will do and how it will be expected to perform. The basic objective of SRS is to specify the important requirements of the proposed system that are gathered during the system analysis. To satisfy the basic goals, an SRS should have some desirable characteristics: correctness, completeness, unambiguous, verifiable, modifiable and traceable, which we have throughout during the process in entirely.

3.1 Introduction
“Melanoma Detection” is a desktop application which is used to detect melanoma cancer. This application will help to reduce the complexity of existing system.

3.1.1 Purpose
This application contains six different modules. That is Data processing, Image Enhancement, Masking, Filtering, Creating CNN architecture and Training and Prediction. Melanoma detection will help the users to easier detection of skin cancer.
3.1.2 Project Scope
Melanoma Detection is aimed detection of cancer. It can be applicable in hospitals or clinic. This application will be very useful to the users and for doctors also. This detection process is not a time consuming process, so it will be a best application for the users.

3.2 Overall Description
3.1 Users
Different users of an system and their requirements are listed below. The Academic Performance Tracker has two different users.

User
USER
MELANOMA DETECTION
DATASET
3.1.1 Product Perspective
Fig 3.1: Product Perspective diagram for Melanoma Detection.

Design and Implementation Constraints
The user can directly perform task. The system is performing the entire task.

User has only few works to done. First user has to load the image and move to different stages
After loading image preprocessing stage has to be done that will be done with the help of OpenCV library. Illumination correction and mask generation and Gaussian filter have to be done.

The second stage is CNN architecture stage here there are levels. Training, Testing with new image and finally detect image is melanoma or not through binary numbers.
3.2.3 Assumption and Dependencies
System is assumed to be up and running whenever required.

The product must have an interface which is simple enough to understand
Functional Requirements
Various functional requirements are involves in this application. This application has different modules each have with similar functionality.
3.2.1 Data Pre-processing
In this stage the dataset is pre-processed. The aim of pre-processing is an improvement of the image data that suppresses unwanted distortions or enhances image features important for further processing.

Image Enhancement
In this module, each melanoma image is normalized. That is after the pre-processing; image is resized and converted into a standard form. So the image needs to be clearer. To do this OpenCV image enhancement or contrast enhancement techniques.

Masking
Each image is processed for background subtraction. That is needed only the essential parts of the image. To do this add a mask layer over the image and detects the melanoma affected regions. The removes the unwanted regions.

Filtering
Filtering is used for noise removal. We use Gaussian filter for denoising and smoothening the image.

Creating CNN architecture and Training
After the image is processed, the image is ready to pass into CNN layers. Here the feature of the images is extracted. The CNN architecture is a five layer architecture. The images are passed through each layers and the deepest features are extracted. After the data is extracted, the system will be trained with these features.

Prediction
Here a new image is tested with the deep learning model. The training and testing image format must be same so at the testing time, newly uploaded image also needs to preprocessed. After the pre-processing is completed, the data is tested against the trained model. The system checks for similar matches and returns a binary output (true or false).

Non-Functional Requirements
3.3.1 Safety Requirements
For making software error free safety requirements are used.
This contains many tests cases, that are unit testing, integration testing.

It is not possible to hack the details.

Chapter 4
SYSTEM DESIGN
4.1 System Perspective
The most creative and challenging face of the system development is System Design. It provides the understanding and procedural details necessary for the logical and physical stages of development. In designing a new system, the system analyst must have clear understanding of the output is to be produced and in what format. Second, input data and master files have to be designed to meet the requirements of the proposed output. The operational phases are handled through program construction and testing.

Design of the system can be defined as a process of applying various techniques and principal for the purpose of defining a device, a process or a system in sufficient detail to permit its physical realization. Thus system design is a solution to “how to” approach to the creation of a new system. This important phase provides the understanding and the procedural details necessary for implementing the system recommended in the feasibility study. The design step provides a data design, architectural design, and a procedural design.

4.2 System Architecture
A system architecture is a conceptual model that defines the structure ,behavior and more views of a system .Architectural Design is a process of decomposing a large complex system into small subsystems. These subsystems are meant for providing some related services.
The Architectural Design is basically a layout or a framework of the system for the subsystem control and communications. The student information will be developed as a web based application.
Architectural Design for Tour Management
Tour Management System
Database
Administrator
Service provider
Customer

Figure 4.1 Architectural Design for Tour Management
There are three layers in the architectural design namely: View Layer, Business Layer and Access Layer.

View Layer: This layer includes the participating administrator, tour operator, service provider and customer.
Business Layer: Business Layer involves the tour packages. It also interacts with the database to perform necessary computations.
Access Layer: Access Layer involves the database and is used to store all the details of computation.

4.3 System Analysis
Analysis involves a detailed study of current system, leading to specification of the system. It is detailed study of various operations performed by a system and their relationships within and outside the system. Specification of what the system is to accomplish based on the user requirements and the functional hierarchy showing the functions to be performed by the system and their relationship with each other are few things to be considered in the system analysis.

4.3.1 ER Diagram
A set of primary component are identified for the E-R Diagram: data object, attributes, relationships and various type indicators. The primary purpose of the E-R Diagram is to represent data object and their relationships. Data object is a represent data objects and their relationships. Data objects: A data objects is a representation of almost any composite information that must be understood by software. Composite information refers to something that has a number of different properties or attributes.

Attributes: Attributes defines the properties of a data object and take on one of three different characteristics. They can be used to (1) name an instance of the data object, (2) describe the instance, or (3) make reference to another instance in another table. In addition, one or more of the attributes must be defined as an identifier that is, the identifier attribute becomes a “key” when we want to find an instance of the data object.

Relationship: Relationships indicate the manner in which data objects are “connected” to one another.

Cardinality: The data model must be capable of representing the number of occurrences objects in a given relationship. Tillman defines the cardinality of an object/relationship pair in the following manner: “Cardinality is the specification of the number of occurrences of one object that can be related to the number of occurrences of another object. Cardinality is usually expressed as simply ‘one’ and ‘many’, two objects can be as:
One-to-One(1:1): An occurrence of object ‘A’ can relate to one and only one occurrence of object ‘B’, and an occurrence of ‘B’ can relate to only one occurrence of ‘A’.

One-to-Many (1:N): One occurrence of object ‘A’ can relate to one or many occurrences of object ‘B’, but an occurrence of ‘B’ can relate to only one occurrence of object ‘A’.

Many-to-Many(M:N): An occurrence of object ‘A’ can relate to one or more occurrence of ‘B’, while an occurrence of ‘B’ can relate to one or more occurrences of ‘A’ .

1
1
Hotel_Details
Fax_no
M
Ownername
Hotelname
nation
hospitals
city
Other_facilities
District
Hoteltype
Special_offer
Hotid
Email
airport
Railway_station
hbookid
Hotel_description
register
checkindate
Hotelbooking
checkoutdate
nation
phone
city
state
email
Address
name
typeofroom
1
cartype
noofdays
todate
carid
name
fromdate
address
Rentacar
Email
phone
M
M
M
1
M
Book_id
regid
status
Children
Select_packages
Adults
Bookingdate
select
M
Booking
Adult
Creditcard
Children
Return_date
Email
To_place
Aid
From_place
Name
Travel date
Allocate
Booking
M
Package
nights
Pkg_type
rate
days
pkgid
specialitiy
place
Pkg_name
M
View
fax
Email
1
Trvid
Trvowner
state
phone
Agencyname
Landmark
Travel post data
features
Post
Pin
status
gender
dob
mobile
telephone
Registration
Nation
state
password
secname
Address
regid
fname
username
usertype
District
Chooseairline
phone
Address
1
photo
Guide
Gdid
Name
Emailid
Hotels
languages
place
Airticket

Figure 4.2 ER-Diagram
4.3.2 Data Flow Diagram
Data flow diagram is graphical tool. It is used to describe and analyze the movements of data throughout a system-manual or automated focus on the data flowing into the system, between processes and in and out of the data stores.

A full description of system actually consists of a set of DFD’s which comprises of various levels. An initial overview model is exploded into more detailed lower level diagrams that show additional features of the system. Further each process can be broken down into more detailed DFD. This occurs repeatedly until sufficient details are described to allow the analyst to allow the analyst to fully understand the portion of the system.

DFD is also known as bubble chart or Data Flow Diagram Graphs. DFD may be used to represent the system at any level abstraction. DFD’s may partition into a level that represents increasing information flows and functional details.

Level 0: DFD Diagram
The level 0 is also called Fundamental System Model or a Context Analysis Design (CAD) represents the entire software elements as a single bubble with input and output indicated by incoming and outgoing arrows. Additional process and information flow paths are represented as 0 level. DFD is partitioned to reveal more details.

RESPONSE
REQUEST
RESPONSE
REQUEST
Tour Management System
SERVICE PROVIDER
CUSTOMER
ADMINISTRATOR
REQUEST
RESPONSE
RESPONSE

Figure 4.3 Level 0 DFD Diagram
Level 1: DFD Diagram
Registration
RESPONSE
REQUEST
RESPONSE
REQUEST
RESPONSE
Verification
Login
Service provider
Registration
Login
Customer
Administrator
Admin Login
Registration details
Registration details
User/pwd
User/pwd

Figure 4.4 Level 1- DFD Diagram
Administrator, Tour operator, Service Provider, Customer can log in their on page using username and password.

LEVEL-2
REQUEST
Service Provider
Login
Post data
Packages details
Reservation
Travel agency
Guide
Travel agency
Hotel
Edit/
Delete
Post data
Edit
/Delete
Post data
Edit/
Delete

REQUEST
Customer
Login
Change password
Modify no.of people
Hotel booking
Modify date of travel
Select packages
Rent a car
Packages details
Hotel booking
Reservation
Registration details

Figure 4.5 Level 2- DFD Diagram
Each module having different sub module. That will getting only after they login their page.

4.4 System Design
The purpose of the design phase is to plan a solution of the problem specified by the requirements document. This phase is the first step in moving from the problem domain to the solution domain. In other words, starting with what is needed; design takes us toward how to satisfy the needs. The design of a system is perhaps the most critical factor affecting the quality of the software; it has a major impact on the later phases, particularly testing and maintenance. The output of the design phase is the design document. This document is similar to a blue print or plan for the solution and is used later during implementation, testing and maintenance.

System design is a solution, “How to approach” to the creation of a new system. The purpose of the design phase is to plan a solution of the problem specified by the requirement document. This phase is a first step in moving from the problem domain to the solution domain. It is also a bridge between requirement specification and the final solution for satisfying the requirement.
The two most important properties that comes designers are efficiency and simplicity. System design includes two sub parts namely: Procedural Design and User Interface Design.

4.5 Database Design
Databases are normally implemented by using a package called a Database Management System (DBMS). Each particular DBMS has somewhat unique characteristics, and so such, general techniques for the design of database are limited. The database table has been designed as follows.
List of Tables
Table 4.1 Registration table
Field Name Data type Constraints Description
Regid Int Primary key User Id
Usertype Varchar Not Null User Type
Username Varchar Not Null User Name
Password Varchar Not Null Password
Fname Varchar Not Null User’s name
Secname Varchar Not Null Second Name
Address Varchar Not Null User’s address
State Varchar Not Null State
District Varchar Not Null District
Nation Varchar Not Null Nation
Pin Int Not Null Pin code
Telephone Varchar Not Null Telephone number
Mobile Varchar Not Null Mobile number
Dob Varchar Not Null Date of birth
Gender Varchar Not Null Gender
Status Bit Not Null Eligibility to login
Table 4.2 Booking table
Field Name Data type Constraints Description
Book_id Numeric Primary key Booking Id
Regid Int Not Null Registration id
Adults Int Not Null Number of adults
Childern Int Not Null Number of children
Booking_det Datetime Not Null Travelling date
Select_package Varchar Not Null Package selection
Status Varchar Not Null Current status
Table 4.3 Hotel details table
Field Name Data type Constraints Description
Hot_id Varchar Not Null Hotel id
Owner_name Varchar Not Null Hotel owner
Hotel_name Varchar Not Null Name of hotel
Hotel_Type Varchar Not Null Type of hotel
Phone Varchar Not Null Conduct number
Fax_no Varchar Not Null Fax number
Email Varchar Not Null Email id
City Varchar Not Null City
District Varchar Not Null District
Nation Varchar Not Null Nation
Hotel_Description Varchar Not Null Description of hotel
Special_Offers Varchar Not Null Special offers
Other_facilities Varchar Not Null Other facilities
Hospitals Varchar Not Null Nearest hospital
Airport Varchar Not Null Nearest airport
Railway_station Varchar Not Null Nearest railway station
Table 4.4 Travel post data table
Field Name Data type Constraints Description
Trvid Int Not Null Identifier
trv_owner Varchar Not Null Travel agency owner
Agency_name Varchar Not Null Name of agency
State Varchar Not Null state where located
Fax Varchar Not Null Fax number
Phone Varchar Not Null Phone number
Landmark Varchar Not Null Land mark
Email Varchar Not Null Email ID of agency
Features Varchar Not Null Special features
Table 4.5 Guide table
Field Name Data type Constraints Description
Gdid Int Primary key Identifier
Emailid Varchar Not Null Mailed of guide
Name Varchar Not Null Guide name
Hotels Varchar Not Null Hotels knowing
Languages Varchar Not Null Languages knowing
Place Varchar Not Null places knowing
Table 4.6 Packages table
Field Name Data type Constraints Description
Pkgid Int Primary key Package id
Package_no Int Not Null Package number
Pkg_name Varchar Not Null Package Name
Place Varchar Not Null Place
Pkg_Type Varchar Not Null Type of package
Speciality Varchar Not Null Speciality
Rate Varchar Not Null Rate of package
Days Int Not Null Days of package
Nights Int Not Null Nights
Table 4.7 Hotel Booking table
Field Name Data type Constraints Description
Hbook_id Int Primary key Identifier
Name Varchar Not Null Name
Address Varchar Not Null Address
Phone Varchar Not Null Phone number
Email Varchar Not Null Mail id
City Varchar Not Null City where hotel
Nation Varchar Not Null Nation name
Type_of_room Int Not Null Room types
Check_in_date Varchar Not Null Date of checkin
Check_out_date Varchar Not Null Date of check out
Nights_to_stay Varchar Not Null How many nigts
Table 4.8 Airticket table
Field Name Data type Constraints Description
Aid Int Primary key Identifier
Name Varchar Not Null Customer Name
Address Varchar Not Null Address
Email Varchar Not Null Mail id
From_place Varchar Not Null Beginning place
To_place Varchar Not Null Departure place
Phone Int Not Null Phone number
Choose_Airlines Varchar Not Null Selecting airline
Travel_date Date Not Null Date of travelling
Return_date Date Not Null Return date
Adult Int Not null Number of adults
Children Int Not null Number of children
Credit_card Int Not null Creditcard number
Table 4.9 Rent car table
Field Name Data type Constraints Description
Carid Int Primary key Identifier
Name Varchar Not Null Customer Name
Address Varchar Not Null Address
Nation Varchar Not Null Nation
Phone Varchar Not Null Conduct number
Email Varchar Not Null Email id
Car_type Int Not Null Type of car
No_of_days Varchar Not Null Number of days
from_date Date Not Null Date of travelling
to_date Date Not Null Return date
Discribe_requirement Int Not null Discribe_requirement
Chapter 5
IMPLEMENTATION AND USER INTERFACE
5.1 Introduction
Implementation is the stage in the project where theoretical design I turned into a working system. The implementation phase constructs, installs and operates the new system. The most crucial stage in achieving a new successful system is that it will work effectively and efficiently. There are several activities involved while implementing new project. They are
End user training
End user education
Training on the application software
System design
Parallel run and to new system
Post implementation review
The Implementation process of the project is easier. While implementation the initial values to the amount of the amount of each item should be specified. The interface and the working of the model is user friendly. A user with basic computer knowledge can use the system.

5.2 User Interface Design
User Interface Design is the design of the websites, Computers, Appliances, Machines, Mobile communication devices and software application with the focus on the user’s experience and interactions. The goal of user interface design is to make the user’s interaction as simple and efficient as possible, in terms of accomplishing user goals-What is often called user-centered design. Good user interface design facilitates finishing the task at hand without drawing unnecessary attention to itself. Graphic design may be utilized to support its usability. The design process must balance technical functionality and visual elements to create a system that is not only operational but also usable and adaptable to changing user needs.

Home page of Tour Management System

Figure: 5.1 Home page
It is the home page for Tour Management System. It contains options to login and registration for customer and employees.
Registration Page

Figure: 5.2 Registration Page
Registration page for new customers.

Administrator Login Page

Figure: 5.3 Administrator Login Page
Administrator Login page for Administrator.

Administrator Home page

Figure: 5.4 Administrator Home Page
Only Administrator can use this page.

Customer Home Page

Figure: 5.5 Customer Home Page
Registered customer can use this page. They will get different services.

Service Provider Home Page

Figure: 5.6 Service Provider Page
Only registered service provider can use this page. They can edit the service.

Chapter 6
TESTING
6.1 Introduction
The Testing process focuses on the logical intervals of the software ensuring that all the statements have been tested and on functional interval is conducting test to uncover errors and ensure that defined input will produce actual results that agree with the required results. Program level testing, modules level testing integrated and carried out. The first test of software is to see whether it produces correct outputs. Testing is executing program to check logical changes made in it and with the intention finding errors and correcting all detected errors and correcting all detected errors. A good test case is one that has a high probability of finding an undiscovered error. The following testing methods were used to ensure correctness and reliability of examination results.

6.2 Type of Testing
6.2.1 Unit Testing
Each module was tested separately to ensure the correctness of each module. This type of test enables the developers to know if there are any faults in the functionality of any module
6.2.2 Integration Testing
Integration testing is a systematic testing for constructing the program structure which at the same time conducting test to uncovered errors associated with interfacing the objective of these testing is to take unit tested modules and build a program structure that has been dictated by design. After connecting all the sub modules into whole module the connection s between the modules are correctly being established. The back end and front end are working as whole module and the data entered in the front end submitted where successfully entered into the database
6.2.3 Validation Testing
Validation testing is mainly done to confirm that each values of different fields all fall in their type and also check whether any field is left without entering any value.

If any field left empty then message appears specifying enter the data.

Some fields can be left blank
If any field must be filled by any character in place of integer or vice versa then a message appears specifying enter the data in current format
6.2.4 White Box Testing
White Box focuses on the program control structure. Test cases are divided to ensure that all statements in the program have executed at least once during, testing and that all logical conditions implying that this test is typically applied to small program components. The system has been tested by providing variety of input to ensure that all the statements are executed at least once and that too in the expected manner. While Box testing is the test case design method that that uses the control structure of the procedural design to derive test cases. While Box Testing methods were used to check whether the loops executed properly, different methods were applied at the boundaries and the execution was examined to be perfect. All typical conditions were tried and the correct results were obtained.

6.2.5 Black Box Testing
Black Box Testing focuses on the functional requirements of the software; it enables to derive sets of input conditions that fully exercise all functional requirements for a program. Black Box Testing tends to find out errors in data structure or external database access, performance errors and initialization errors. While testing the system by using test data, errors were found and corrected. Thus the series of test were performed for the proposed system before the system was ready for implantation.

6.3 Test cases
Table 6.3.1 Test case for User login
SL No. Test description Test case data Expected output Remarks
1 Selecting UserType Click on cancel Registration form should be displayed. SUCCESSFUL
2 If the user name and password does not match Username, password Alert user that “invalid username or password” SUCCESSFUL
3 If the user name and password matched Username, password Extract it from the database table. Display the home page. SUCCESSFUL
4 If all the fields entered properly and the user clicks SUBMIT button All fields in the form Alert the user that “Login is successful” SUCCESSFUL
Table 6.3.2 Test case for data will be entered by Admin
SL No. Test description Test case data Expected output Remarks
1 After loading main form Click on main menu service provider details,tour operator details,view packages approve packagesGuidedetails,reservationdetails,change password. Particular pages are displayed based on the menu items selected. SUCCESSFUL
2 After loading form Click on home Confirmation are asked and exist from the administrator main. SUCCESSFUL
Table 6.3.3 Test case for Customer main form
SL No. Test description Test case data Expected output Remarks
1. After loading main form Click on main menu rent a car, view packages,airticketbooking or modify the data of travel,reservationdetails,edit number of people or change password. Particular pages are displayed based on the menu items selected. SUCCESSFUL
2. After loading form Click on home Confirmation are asked and exist from the customer main page to Home page. SUCCESSFUL
Table 6.3.4 Test case for service provider main Form
SL No. Test description Test case data Expected output Remarks
1. After loading form Click on menus hotel,travel agencies or Guide or home. Sub menu should be displayed. SUCCESSFUL
2 After clicking on sub menu Click on menu post hotel data or edit/delete posted hotels or post travel agency data or edit/delete posted trvel agency data or post guide data or edit/delete posted guide. Particular pages are displayed based on the menu items selected. SUCCESSFUL
3 After loading the form Click on home Confirmation are asked and exist from the main page to Home page. SUCCESSFUL
Table 6.3.5 Unit Test case for Customer Form
SL No. Test description Test case data Expected output Remarks
1 Typing letters in the field of numbers On key press Error message should be displayed SUCCESSFUL
2. Typingnumbers in the field of alphabets On key press Error message should be displayed SUCCESSFUL
3. Not entering the data in the required field. Click On submit button Error message should be displayed SUCCESSFUL
4. After loading the form Click On list box item Selected item value should be displayed SUCCESSFUL
5 After loading the form Click On reset button All the field are cleared SUCCESSFUL
6 Entering all the field’s value Click on submit button New record should be inserted in the database. SUCCESSFUL
7 Editing record field values Click on edit button Selected record field value should be updated SUCCESSFUL
8 Selecting the record Click on edit button Selected record deleted from the database SUCCESSFUL
9 Entering /not entering the details Click on back button Form should be closed and goes back in main page. SUCCESSFUL
Table 6.3.6Unit Test case for service provider Form
SL No. Test description Test case data Expected output Remarks
1 Typing letters in the field of numbers On key press Error message should be displayed SUCCESSFUL
2. Typing numbers in the field of alphabets On key press Error message should be displayed SUCCESSFUL
3. Not entering the data in the required field. Click On submit button Error message should be displayed SUCCESSFUL
4. Entering all the field values Click On reset button record should be cleared SUCCESSFUL
5 Entering all the field values Click On reset button Record should be cleared SUCCESSFUL
6 Entering /not entering the details Click on back button Form should be closed and goes back to the main page SUCCESSFUL
7 Editing record field values Click on edit button Selected record field value should be updated SUCCESSFUL
8 Selecting the record Click on delete button Selected record deleted from the database SUCCESSFUL
Chapter 7
CONCLUSION
The system has been developed and is found working effectively. The developed system is flexible and changes can be made easy as and when required. We tried to make the system maximum user friendly. Security is the main consideration in this project. The system is protected from any unauthorized access by giving user name and password during log in process. All the necessary validations are carried out in this project, so that any kind of users can make use of this software and necessary messages makes them conscious of the error they have made.

Chapter 8
FUTURE ENHANCEMENT
The scope of the project is enormous. Also in the vast developing environment like the tour management, more and more scope for development still exists. This project can make use of still more complicated and more complex design logics to produce a new and better one in any other working environment.

The project can be implemented on intranet in future. Project can be updated in near future as and when requirement for the same arises, as it is very flexible in terms of expansion. With the proposed software of database Space Manager ready and fully functional the client is now able to manage and hence run the entire work in a much better, accurate and error free manner.

Chapter 9
BIBLIOGRAPHY
Books Referred:
C# and ASP.NET Project
Beginning ASP.NET 4.5.1 in C# and VB
Professional C# 5.0 and .NET 4.5.1 (WROX)Website Referred:
https://www.tutorialspoint.com/csharp
https://msdn.microsoft.com/en-us/library/341zb1z3(v=vs.90).aspx

Build Your Own ASP.NET Website Using C# And VB.NET, Chapter 1 – Introduction to .NET and ASP.NET


https://webproject.scottgu.com/CSharp/HelloWorld/HelloWorld.aspx