DESIGN AND DEVELOPMENT PROCESS

FUNDAMENTAL DESIGN CONCEPTS

Although the degree of interest in each concept has varied over the year, each has
stood the test of time. Each provides the software designer with a foundation from which
more sophisticated design methods can be applied. Fundamental design concepts provide the
necessary framework for “getting it right”.

During the design process the software requirements model is transformed into design
models that describe the details of the data structures, system architecture, interface, and
components. Each design product is reviewed for quality before moving to the next phase of
software development.

DESIGN NOTATIONS

Sets of fundamental design concepts are evolved over the past there decades. Design
is defining a model of the new system and continues by converting this model to a new
system. The method is used to convert the model of the proposed system into computer
specification. Data models are converted to a database and processes and flow to user
procedures and computer programs. Design proposes the new system that meets these
requirements. This new system may be built by a fresh or by changing the existing system.
The detailed design starts with three activities, database design, user design and program
design. Database design uses conceptual data model to produce a database design. User
procedure design uses those parts of the DFD outside the automation boundary to design user
procedures.
DATA FLOW DIAGRAM

Dataflow diagram is a representation in which overall description of a system can be

shown in the form of a diagram. The description of the system will start from the source of
the content and with its destination. The diagram can be divided many different stages and
each stage must give information about the system.

Design notation

There are four symbols that are used in the design.

 Entities

External entities represent the sources of data that enter the system or the recipients of
data that leave the system

 Process

Processes represent activities in which data is manipulated by being stored or

retrieved or transformed in some way. A circle represents it. The process will show the data
transformation or change.

 Database

Databases represent storage of data within the system

  Data Flow

A data flow shows a flow of information from its source to its destination. A line
represents a data flow, with arrow heads showing the direction of flow.

Level 0

Login process
Admin Login File

Login details

Intelligent
Tourist System
Level 1

Admin details Login Login details

process
Admin
Login

After login

Intelligent Tourist
System

Manage
Web pages

Tour Agency Tutorial

Information

Stores & retrieves

Tutorials
Level 2

Login Login details

Admin
Process Login

Manage
feedback Feedback
Process

Feedback details

Manage
employee
Article

Employee details

Manage
tutorials Tutorials

Tutorials

Manage web
pages
Article

Tour agency details

ER DIAGRAM
An entity-relationship diagram is a data modeling technique that creates a graphical
representation of the entities, and the relationships between entities, within an information
system. The three main components of an ERD are as follows.

The entity is a person, object, place or event for which data is collected. For example,
if the information system for a business is considered, entities would include not only
customers, but the customer's address, and orders as well. The entity is represented by a
rectangle and labeled with a singular noun.

The relationship is the interaction between the entities. In the example above, the
customer places an order, so the word "places" defines the relationship between that instance
of a customer and the order or orders that they place. A relationship may be represented by a
diamond shape, or more simply, by the line connecting the entities. In either case, verbs are
used to label the relationships.

The cardinality defines the relationship between the entities in terms of numbers. An
entity may be optional: for example, a sales rep could have no customers or could have one or
many customers; or mandatory: for example, there must be at least one product listed in an
order.

There are several different types of cardinality notation; crow's foot notation, used
here, is a common one. In crow's foot notation, a single bar indicates one, a double bar
indicates one and only one (for example, a single instance of a product can only be stored in
one warehouse), a circle indicates zero, and a crow's foot indicates many. The three main
cardinal relationships are: one-to-one, expressed as 1:1; one-to-many, expressed as 1:M; and
many-to-many, expressed as M:N.

The steps involved in creating an ERD are:

 Identify the entities.

 Determine all significant interactions.
 Analyze the nature of the interactions.
 Draw the ERD.
Symbols & their meaning in ERD

Entity

Weak entity is an entity which depends on strong entity attribute’s, it

i does not have attribute of its own

Attribute

Multi valued attribute is an attribute which has more than one values

Derived attribute

Relationship
Uid Pwd

Web pages & gallery

Admin
Manages

Viewed
by

Users

Tutorials
Posts Downloads

Posts

Feedback
Replies
for
DATABASE DESIGN

Data base is designed to manage large bodies of information. The management of data
involves both the definitions of structures for the storage of information. In addition the data
base system must provide for the safety of the information solved, despite system crashes or
due to attempts at unauthorized access. For developing an efficient database they have to
fulfill certain conditions such as controlled redundancy.

 Defining the data

 Inputting the data
 Locating the data
 Accessing the data
 Communicating the data
 Revising the data

Objectives of Data base design

In the data base design several objectives are designed such as

 Ease of use
 Control of data integrity
 Control of redundancy
 Control of security
 Data independence (logical & physical)
 Data storage protection
 System performance
 System functions
 System compatibility

For achieving the above mentioned criteria’s one has to make use of various features
that are available with the RDBMS by enforcing integrity constrains, one can ensure data
integrity and reduce data inconsistency to a great extent. Database is designed meeting all the
above requirements.
TABLE STRUCTURE

Table name : login

Primary key : uid

Field Type Description

uid Int(10) Id of the user
Pwd varchar(50) Password of the user

Table description

Login table is used for storing user details

Table name : feedback

Primary key : fid Foreign key : uid

Field Type Description

Uid bigint(8) ID of the user
Name varchar(20) Name of the user
Email varchar(20) Email ID of user
Sub varchar(50) Subject of feedback
Message varchar(100) Feedback given by the user
Fid Varchar(20) Feedback ID

Table description

Feedback table is used for storing feedback offered by the users

Table name : photo

Primary key : pid

Field Type Description

pid bigint(8) Photo ID
caption varchar(500) Name of the photo
location varchar(25) Location of the photo
Table description

Photo table is used for storing photos taken during tour agency functions and
important events.

Table name : brochures

Primary key : bid

Field Type Description

bid bigint(8) Brochures ID
caption varchar(25) Name of the tutorial
location varchar(25) Location of the tutorial
cat varchar(25) Category of the tutorial

Table description

Brochures table is used for storing tour brochures and tips for best tour experience

Table name : article

Primary key : arid

Field Type Description

arid bigint(8) Article ID
title varchar(50) Title of article
content varchar(70) Content
metatag varchar(70) Meta tag
metadesc varchar(70) Description of an article

Table description

Articles table is used for maintaining articles posted in the website. This table can be
managed only by the administrator.
DESCRIPTION OF MODULES

The project maintains the following modules:

 Login module
 Tour agency module

 Employee information module

 Fee module
 Brochure Upload & Download module
 Feedback module

Login module

It is used for logging in the Intelligent Tourist System. Only the administrator has
rights to login and access he site. Once the admin logins, admin get privileges to modify the
information in web pages. Tutorials can be posted by admin, which can be used by the
passengers.

Tour agency module

Tour agency information is maintained by the administrator through this module.

When the use visits website, it is possible to view the tour agency information like rules and
regulations of the tour agency, gallery, facilities available in tour agency etc.

Employee information module

Admin maintains employee details through this module. Employee details can be
added as well as updated through manage employee information page. Customers cma view
the employee details in order to contact them for tour package.

Fee module

Fee details of tour agency are maintained through this module. Admin can access this
module for managing the fee brochure details.
Brochure Upload & Download module

Tutorials and brochures can be uploaded through this module where passengers can
be able to download the brochures uploaded by admin.

Feedback module

Customers will be able to post their feedback enquiries through this module. Those
feedbacks will be sent automatically to administrator. Admin will be able to view and
respond to the feedback.

INPUT DESIGN

Input design is a part of overall system design. The main objective during the input
design is as given below:

 To produce a cost-effective method of input.

 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.

Input Stages

The main input stages can be listed as below:

 Data recording
 Data transcription
 Data conversion
 Data verification
 Data control
 Data transmission
 Data validation
 Data correction

Input Media

Keeping in view the above description of the input types and input media, it can be
said that most of the inputs are of the form of internal and interactive. As Input data is to be
directly keyed in by the user, the keyboard can be considered to be the most suitable input
device.

Major inputs of the proposed project will be

 Admin enter his or her user id and password.

 Admin requests the tour package details for tutorial management.
 Passenger requests the tutorial details.
 Passenger requests the gallery details.
 Passenger clicks and navigates through map.

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the results of
processing to users. They are also used to provide a permanent copy of the results for later
consultation. The various types of outputs in general are:

 External Outputs whose destination is outside the organization.

 Internal Outputs whose destination is within organization and they are the User’s
main interface with the computer.
 Operational outputs whose use is purely within the computer department.
 Interface outputs involve the user who communicates directly with the system.

Output Definition

The outputs should be defined in terms of the following points:

 Type of the output

 Content of the output
 Format of the output
 Location of the output
 Frequency of the output
 Volume of the output
 Sequence of the output

Output screens of the project are

  Login screen
 Tour agency Admin home page
 Tutorial screen
 Employee screen
 Gallery screen
 Tour admission procedures, rules & regulations rules screen
 Feedback screen
 Fee details screen
 Location tracking screen
 Brochure Download screen

DEVELOPMENT APPROACH

Analysis for mining web pages using a link analysis and entension was designed and
developed based on the Waterfall Model. This model particularly expresses the interaction
between subsequent phases. Testing software is not an activity, which strictly follows the
implementation phase. In each phase of the software development process, we have to
compare the results obtained against that which is required. In all phases quality has to be
assessed and controlled.
 The waterfall model is a sequential design process, used in software development
processes, in which progress is seen as flowing steadily downwards (like a waterfall) through
the phases of conception, initiation, analysis, design, construction, testing,
production/implementation and maintenance.