CSE-308

Submitted by
1005101, 1005102,
1005103, 1005104,
1005119.
TRAVELERS DIARY
Group 5
CSE B
2
Page 1 of 107

Table of Contents
1. overview of Project ___________________________________________________________________________ 3
1.1 Introduction _____________________________________________________________________________ 3
1.2Project overview __________________________________________________________________________ 3
1.3 Goals of the project _______________________________________________________________________ 4
1.4 Report overview __________________________________________________________________________ 4
2. Existing system study _________________________________________________________________________ 5
2.1 Introduction _____________________________________________________________________________ 5
2.2 System analysis __________________________________________________________________________ 5
2.3 Problem analysis _________________________________________________________________________ 6
3. scope definition _____________________________________________________________________________ 7
3.1 What scopes will be covered: _______________________________________________________________ 7
3.2 What scopes will be negotiated & Why: ______________________________________________________ 10
4. Requirement & Feasibility analysis _____________________________________________________________ 11
4.1 Requirement analysis ____________________________________________________________________ 11
4.2 Feasibility analysis _______________________________________________________________________ 11
4.2.1 Operational analysis _________________________________________________________________ 11
4.2.2 Technical feasibility _________________________________________________________________ 12
4.2.3 Cultural analysis ____________________________________________________________________ 12
5.Proposed system design ______________________________________________________________________ 14
5.1 Introduction ____________________________________________________________________________ 14
5.2 Use case diagram _______________________________________________________________________ 14
5.3 Data flow diagram_______________________________________________________________________ 36
5.4 System design __________________________________________________________________________ 41
5.4.1 Class diagram & collaboration diagrams _________________________________________________ 41
5.5 Process design __________________________________________________________________________ 52
5.5.1 Sequence & state chart diagrams ______________________________________________________ 52
5.5.2 Activity diagram ____________________________________________________________________ 61
6. Database design ____________________________________________________________________________ 63
6.1 Introduction ____________________________________________________________________________ 63
6.2 ERD & its brief description _________________________________________________________________ 63
6.3 Database schema _______________________________________________________________________ 67
6.4 Triggers & procedure _____________________________________________________________________ 76
Page 2 of 107

7. Input & output design _______________________________________________________________________ 78
7.1 Input & output design ____________________________________________________________________ 78
8. Project phase & activities_____________________________________________________________________ 94
8.1 Introduction ____________________________________________________________________________ 94
8.2 Work schedule & project time analysis _______________________________________________________ 95
8.2.1 Activity timeline ____________________________________________________________________ 95
8.2.2 Activity network ____________________________________________________________________ 96
8.2.3 Pert chart _________________________________________________________________________ 97
8.3 Cost-benefit analysis _____________________________________________________________________ 98
8.3.1 Cost analysis _______________________________________________________________________ 98
8.3.2 Benefit analysis ____________________________________________________________________ 100
8.4 Risk analysis & management (during implementation) _________________________________________ 101
8.4.1 RISK IDENTIFICATION (During Implementation) __________________________________________ 101
8.4.2 Risk analysis & management (during maintenance) _______________________________________ 104
References__________________________________________________________________________________ 107




Page 3 of 107

1. OVERVIEW OF PROJECT


1.1 INTRODUCTION

This is a tourism based system. This will be under the tourism
board of a country. Agencies will register to this system with
proper terms and conditions and buy license for a certain period of
time from the board. The tourists are the user of this system. By
creating a profile the user can have access to this system and will
get all the necessary information about the whole countrys
tourism scenario.


1.2 PROJECT OVERVIEW

In this project a user will have profile and have the opportunity to
share photo, give rating about any agency or guide, maintain his
own profile.

The agencies will be licensed by the board and get opportunity to
provide their service to the users.

Board will have a control over the agencies and can enrich the
system with updating information about places of the country.


Page 4 of 107



1.3 GOALS OF THE PROJECT

- Creating a platform for the tourists to share experience
- Uploading photo to show any places beauty
- Maintain a rating for guide and agency to make decision easier
for another tourist
- Make countrys tourism more popular among the people
- Control the agencies by a board to keep track of the service of
the agencies
- Make agencies more interested to develop their service to the
tourist.


1.4 REPORT OVERVIEW
- Scope definition of the project
- Use case diagrams
- Class diagrams
- Collaboration diagrams
- State chart diagrams
- Activity diagrams
- Timeline analysis
- Cost benefit analysis
- Risk analysis
Page 5 of 107

2. EXISTING SYSTEM STUDY


2.1 INTRODUCTION

In this section we will discuss about the existing systems in the
field of tourism in our country. Also the problems with these
systems are noted and we try to give a possible solutions to this
problems thorough our project.


2.2 SYSTEM ANALYSIS

Bangladesh tourism board web site
Not so up to date
Not user friendly
Old-fashioned
Provides very few information
No way to get feedback from the travelers
Agencies' own websites
Costly tour packages
Traveler can not plan his plan
Include a single place in every package
.

Page 6 of 107


2.3 PROBLEM ANALYSIS


Our improvised solution to these problems are




Page 7 of 107

3. SCOPE DEFINITION


3.1 WHAT SCOPES WILL BE COVERED:

The actors and subsystems of our project are:

ACTORS
Anonymous use
Member user
Agency
Board

SUBSYSTEMS
User profile
- sharing option as writing reviews & uploading photos
- maintaining a simple profile and update own info
- opportunity to give rating to agency and guide according to
their service

Log in/Sign up
o Add info
Review
Give rating
o Share photo


Page 8 of 107


Agency profile
- Information update ability to any place thorough board
confirmation
- Renew membership by giving required data and apply for
renewal to the board.
- Express companies service through promotional activity
- Give additional info about own contact and service

Web link
Contact
Location
Guide
Trip plan
Discount
Regular
Transport

Board controlling
- Update various information about any place
- Control agencies by keeping track of their service and user
rating
- Manage user profile database

Page 9 of 107



Information update
- Add new info to any place
- Remove unnecessary information about any place
- Update info according to the agency

Sites
History(category)
Festivals
Special attraction
Gallery
Weather
Guide
(contact , ranking)
Emergency helpline
Police
Hospital
Transport
(schedule, cost)
Railway
Roadway
Airway
Waterway
Page 10 of 107

Accommodation
(location , contact)
Hotel
Cottage
Food


3.2 WHAT SCOPES WILL BE NEGOTIATED & WHY:

Online money transaction:

1. The ATM system is not available everywhere in the country.
2. Online banking and mobile internet system is not familiar with
people in the rural areas.
3. Worldwide usable credit card management is not provided by
all the agencies/hotels/restaurants.

Guide registration:

The guides are basically not so up-to-date technology user. So
most of the time they dont know the procedure of using internet or
making registration through sms.

Agency monitoring:

As any agency is a licensed member of the management system, any
complain against it by a users review or individuals personal
experience it is not possible to take immediate steps of penalty
against the agencies. It will be a lengthy process with checking the
license agreement and violation law.
Page 11 of 107

4. REQUIREMENT & FEASIBILITY ANALYSIS


4.1 REQUIREMENT ANALYSIS

Some portions of this project doable as the required resources are
available, and the rest of the parts aren't worthy taking the risk.
Sharing platform for tourists will give a great feedback.
Traveling will be easier than never before.



4.2 FEASIBILITY ANALYSIS

4.2.1 Operational analysis

In the existing system following problem were found:
o Not user friendly
o Lack of information
o Lack of interaction
o No platform for sharing
Our system successfully deals with this problems.

Page 12 of 107


4.2.2 Technical feasibility

The proposed technology is quite realistic as it is mature enough to
easily apply to the problems.
For implementation of the system we will use
i. PHP for server side scripting
ii. MySQL for Database management
iii. JavaScript for client side scripting
iv. Java for PC and mobile based software implementation
v. HTML/CSS for web designing
vi. And expert engineers will deal with these


4.2.3 Cultural analysis

Management supports because:
Increase end user number
Controlling the agencies will be easier

Page 13 of 107



End user feeling about new system:
user friendly interface to meet their urges for information about
tour spot
share their experience as they wish
user get privacy control
With the present existing system, the end users find it hard to
collect reliable and detailed information about their travelling
spots and the tourism board has to manage agencies in a manual
way. The agencies also find it hard to advertise their services as
there is no common platform for travelers.
In this proposed system, getting information will be easier and
they can also share their views. As the new system will be
easier to use , advertise and manage , the end users and
managers can easily adapt to the change.

Page 14 of 107

5. PROPOSED SYSTEM DESIGN

5.1 INTRODUCTION

In this section we will discuss about the detail design process of
this system with important diagrams.

5.2 USE CASE DIAGRAM

Use-case Glossary
Use-case Diagram
Use-case Narrative with
Tabular form
Documentation

Actor glossary

Actor
Short-
key
Activity scope
Tourism
Board
BRD a)managing user profiles
b)managing agency profiles
c)updating information
Tourist TST a)searching
b)uploading photos
c)writing review
d)giving rating
Agency AGN a)updating information
b)promoting services


Page 15 of 107

USER PROFILE SYSTEM
Use-case Glossary:
Use-
Case
ID
Name Description Participant
actors
And Roles
1.1 Sign Up /
Login
Signing Up
& Logging
in to an
account
TST signs
up and logs
into
account
1.2 Searching Searching
for any
place
TST
searches
places
1.3 Selecting
Place
Selecting
place
according
to choice
TST selects
the place
1.4 Review Sharing
experience
and rating
services of
the place
selected in
1.3
TST writes
about the
place
and rates
services
1.5 Uploading
Photos
Uploading
photos
TST
uploads
photos


Page 16 of 107

Use-Case Diagram:



uc Primary Use Cases
User Profi l e Management
Login/signup
TST
The System Boundary shows the
logical interface between TST
and the user profile
management system.
searching
selecting place
review
rating
sharing experience
upload photos
extend
extend
Page 17 of 107

Use-Case Narrative:
The System features how the users can use their profile and what
options they will get.

1.1 Log in/ Sign up
Typical course of event
General people can create a profile in this system easily
only by providing an email id.
They can login into this system using that id and enjoy all the
features from his/her profile.

1.1
Use-Case
name
Define route and price
Use-Case
ID
1.1
Priority High
Primary
Business
Actor
Tourist/User(TST)
External
Receiver
Actor
Board(BRD)
Description
The user creates a new account by signing
up providing an email id.Later he/she can
log into that account using that email id.
Trigger By TST

Actor: TST, BRD

Page 18 of 107

Documentation:
Conclusion: concludes when a request to create an account is
made.
Post-condition: confirm the user about the creation of his/her
account and make the user logged in.
Implementation-issues: GUI will be provided in the webpage for
the user to fill up the form as well as maintain a database for user
accounts.

1.2 Categorized Searching System
Typical course of event

In the search system, a user can see a drop down list of the
following category:
Display map:
Displaying a places map location via google map facility according
to the name a user entered.
Historical listing:
Showing a list of whole countrys historical/traditional spots
according to users entry.
Geological sorting:
Providing the user a list according to hill tracks / sea beach sorting.

Page 19 of 107


1.2
Use-Case
name
Define route and price
Use-Case ID 1.2
Priority High
Primary
Business Actor
Tourist/User(TST)
Description The user searches for the desired
place in a category based search
engine. The categories will make the
searching easier.
Trigger By TST

Actor: TST
Documentation:
Conclusion: concludes when an entry of the search is made.
Post-condition: supply information about the item/place that user
was searching for.
Implementation issues: GUI will be provided in the webpage for
the user to look at various issues related to that searched item.

Page 20 of 107




1.3 Selecting places

Typical course of event
user selects a place after searching with suitable choice
1.3


Actor: TST

Use-Case name Define route and price
Use-Case ID 1.3
Priority High
Primary
Business Actor
Tourist/User(TST)
Description After the user gets a satisfying result
from the search, he/she selects the
place
Trigger By TST
Page 21 of 107



Review
Typical course of event

The travelers can review in two ways:
Sharing Experience in public
The travelers can share their views about any particular place,
agency, restaurant or guide service after their
traveling experience.
Rating
There will be a rating corner for each service for every places.
A user can rate that service as his/her wish. That rating will
be publicly visible.

1.4

Actor: TST ,BRD

Use-Case name Define route and price
Use-Case ID 1.4
Priority High
Primary
Business Actor
Tourist/User(TST)
Description The user visits the page of the
desired place/spot and then writes
about that place from past
experience. He/she can also rate the
services around that place provided
by Agencies or guides.
Trigger By TST
Page 22 of 107

Documentation:
Conclusion: concludes when a user shares his/her experience, give
suggestions.
Post-condition: Notify the board about suggestions.
Implementation-issues: GUI will be provided in the webpage to
share ideas and views.

Uploading photos
Travelers can upload photos if they want to share their tour
experience with other people.
1.5





Actor: TST

Use-
Case
name
Define route and price
Use-
Case ID
1.5
Priority Medium
Primary
Busines
s Actor
Tourist/User(TST)
Descrip
tion
The users share their traveling
experience uploading the tour photos
Trigger By TST
Page 23 of 107

Documentation:
Conclusion: concludes when a user upload photos.
Post-condition: add photos in the gallery.
Implementation-issues: GUI will be provided in the webpage for
uploading.

Agency Profile System



Use-
Case
ID
Name Description Participant actors
And Roles
2.1 Agency
informatio
n Update
Updating information about
agencies own services
AGN updates their own
information
2.2 Promotion
al Activity
Advertising
activities,offers,packages,services
AGN does the promotions


2.3 Request
Account
Renewal
Requesting extension of valid time
period
AGN requests for the
extension
Page 24 of 107


Use-Case Diagram



Use-Case Narrative:

This system features how the agencies can manage their profile. It
includes:
Agency Information update
Typical course of event

The agency can update their own information in their profile as
follows:

uc Primary Use Cases
Agency profi l e
info update
AGN
The System Boundary shows
the logical interface between
AGN and the agency profile
promotional activity
BRD
guide update
update contact
request time period
renewal
provide offers
upload photos
extend
extend
extend
extend
Page 25 of 107


Guide info:
The agency will register local guides in this database on their own.
Then they can provide the guide detail and contact info
for that guide. Using these information,
people can access guides.

Location & contact info:
Detail contact information agency and location of their associated
sites/resorts.
Website link:
Agency will give its own website link with all detailed service.
2.1



Actor: AGN

Use-Case
name
Define route and price
Use-Case ID 2.1
Priority High
Primary
Business
Actor
Agency(AGN)
Description Updating information about
agencies own services
Trigger By AGN
Page 26 of 107



Promotional activity
Agencies can advertise about their service publicly

Typical course of event

Offers:
Agencies can promote their trip plan and schedule, special
packages, discount offer
for a particular situation.
Photo gallery:
They can have their own photo gallery to attract tourists.
2.2


Actor: AGN

Use-Case
name
Define route and price
Use-Case ID 2.2
Priority High
Primary
Business
Actor
Agency(AGN)
Description Advertising activities, offers,
packages, services
Trigger By AGN
Page 27 of 107


Request Time Renewal of Membership:
The agency have got the option to request the board to renew
their time period
followed some official processes.

2.3
















Actor: AGN

Use-
Case
name
Define route and price
Use-
Case ID
2.3
Priority High
Primary
Business
Actor
Agency(AGN)
External
Receiver
Actor
Board(BRD)
Descript
ion
Requesting extension of valid time
period
Trigger By AGN
Page 28 of 107



Board Controlling System

Use-Case Diagram:



uc Primary Use Cases
Board Control l i ng
agency management
BRD
The System Boundary shows
the logical interface between
AGN, BRD and the agency
profile management system,
user profile management
system.
user management
AGN
add agency
remove agency
membership renewal
extend
extend
extend
Page 29 of 107



Use-Case Narrative:
Agency Management
The board will have the control over agency accounts and several
operations can be performed over the accounts:
3.1

Typical course of event

Add agency:
New agency account can be added after verification maintaining
the terms of agreement.
Actor: BRD
Documentation:
Conclusion: concludes when a request to get membership is made.
Post-condition: Inform the agency about the membership giving
membership access password.
Use-Case
name
Define route and price
Use-Case ID 3.1
Priority High
Primary
Business
Actor
Board(BRD)
External
Receiver
Actor
Agency(AGN)
Description Modifying Agency account status
Trigger By BRD
Page 30 of 107

Implementation-issues: GUI will be provided to gather required
info about that agency

Remove agency:
Agency account can be removed after expire date.

Actor: BRD

Documentation:
Conclusion: concludes when board send notification to an agency
about its time period removal.
Post-condition: make the agencys membership status invalid.
Implementation-issues: System preserves membership status.

Time period renew:
The allotted time period can be extended for an account.

Actor: BRD, AGN

Documentation:
Conclusion: concludes when agency send notification to board
about its time period renewal.
Post-condition: update the agencys membership status.
Implementation-issues: System preserves membership status.


Page 31 of 107

User Management
The board can also control any user account. If anything is wrong
with the user profile, the Board can remove that account.

3.2

Actor: BRD
Documentation:
Conclusion: concludes when board delete a users account.
Post-condition: update the user membership database.
Implementation-issues: System preserves membership status.

Use-Case
name
Define route and price
Use-Case ID 3.2
Priority Medium
Primary
Business Actor
Board(BRD)
External
Receiver Actor
Tourist/User(TST)
Description Modifying User account status
Trigger By BRD
Page 32 of 107

Information update system


uc Primary Use Cases
Informati on update
add info
AGN
The System Boundary shows
the logical interface between
AGN,BRD and the information
update system
remove info
BRD
update info
Use-
Case ID
Name Description Participant actors
And Roles
4.1 Add Info Adding new places with new
information
BRD creates a new
interface for a new
place
4.2 Update
Info
Updating information of
already existing places
BRD updates necessary
information
4.3 Remove
Info
Removing any unnecessary
information or interface
BRD does the work
Page 33 of 107

Use-Case Narrative:

The Board and Agencies can update information about following
categories and user can view this information from his/her profile:


Add info :
4.1


Use-Case
name
Define route and price
Use-Case ID 4.1
Priority High
Primary
Business Actor
Board(BRD)
External
Receiver Actor
Tourist/User(TST)
Description Adding new places with new
information
Trigger By BRD
Page 34 of 107


Typical course of event
Weather status: showing climate situation and weather
forecast for particular areas.
Emergency helpline: police, hospital and fire services contact
no & location list
Festivals: traditional festival occurrence in the spot will be
mentioned.
History : it will describe the history of any spot and mention
places for travelers
Food: display list of special foods(if any) available in the site
Transport : ways of going the site will be presented before
user as
1. Highways
2. Water ways
3. Railway
4. Airway

Accommodation : provide a list of available accommodation
facilities as
1. Hotels
2. Resorts
3. Govt. rest houses
Actor: BRD, AGN
Documentation:
Conclusion: concludes when a piece of information is updated.
Post-condition: make sure that uploaded information are available
to every related actors.
Implementation-issues: All the information are maintained by the
system.

Page 35 of 107


4.2 Update info:

Actor: BRD,AGN

4.3 Remove Info













Actor: BRD,AGN
Use-Case name Define route and price
Use-Case ID 4.2
Priority High
Primary
Business Actor
Board(BRD)
External
Receiver Actor
Tourist/User(TST)
Description Updating information of already existing
places
Trigger By BRD
Use-Case
name
Define route and price
Use-Case ID 4.3
Priority High
Primary
Business Actor
Board(BRD)
External
Receiver Actor
Tourist/User(TST)
Description Removing any unnecessary
information or interface
Trigger By BRD
Page 36 of 107

5.3 DATA FLOW DIAGRAM

User profile management:

Fig: data flow diagram for user profile
Page 37 of 107

FISHBONE DIAGRAM

Fig: fish bone diagram for user profile system
Agency profile management:

Fig: data flow diagram for agency profile
Page 38 of 107


Fig: fish bone diagram for agency profile system

Board controlling:

Fig: data flow diagram for board controlling system
Page 39 of 107


Fig: fish bone diagram for board controlling
Information update:

Fig: data flow diagram for information update


Page 40 of 107



Fig: fish bone diagram for information update

Page 41 of 107



5.4 SYSTEM DESIGN

5.4.1 Class diagram & collaboration diagrams

User profile system
Use-cases
Log in/sign up
Review
Search

Login/Signup




Page 42 of 107




SEARCHING


Page 43 of 107


REVIEW


Page 44 of 107



Page 45 of 107

Agency profile system
Use case
Membership renewal
Promotional activity
RENEWAL REQUEST


Page 46 of 107

PROMTIONAL ACTIVITY


Page 47 of 107



Page 48 of 107

Board controlling system

Use case
Agency management
User management
AGENCY MANAGEMENT


Page 49 of 107


USER MANAGEMENT


Page 50 of 107


INFORMATION UPDATE

Page 51 of 107




Page 52 of 107

5.5 PROCESS DESIGN

5.5.1 Sequence & state chart diagrams

User Profile Management
Use Case:
Sign Up/Login


4
Page 53 of 107


Search


5
6
Page 54 of 107



Review


9
Page 55 of 107

Agency Profile Management
Use Case:
Agency Info update





11
12
Page 56 of 107

Promotional Activities







13
14
Page 57 of 107

Agency Membership Renewal



15
16
Page 58 of 107

Board Management
Use Case:
User Management

Agency Management

18
19
Page 59 of 107



20
Page 60 of 107

Information Update
Use Case:

Info Update [agency]

Info Update [board]


22
23
Page 61 of 107


5.5.2 Activity diagram

User Profile Management

Agency Management


25
26
Page 62 of 107


Board Management



27
Page 63 of 107


6. DATABASE DESIGN

6.1 INTRODUCTION

This section will provide the database design along with ERD and
schema.

6.2 ERD & ITS BRIEF DESCRIPTION

ENTITY RELATIONSHIP DIAGRAM




Page 64 of 107

ATTRIBUTES




Page 65 of 107

Page 66 of 107







Page 67 of 107

6.3 DATABASE SCHEMA


















FOOD
Info_id NUMBER(10)
Place_id NUMBER(10)

Restaurant address VARCHAR2(30)
Special dish VARCHAR2(30)
PLACE
Id NUMBER(10)
Name VARCHAR2(30)
Category VARCHAR2(30)
Location VARCHAR2(500)
History VARCHAR2(500)(500)
LATITUDE NUMBER(3, 10)
LONGITUDE NUMBER(3, 10)
Special Recognition VARCHAR2(500)
Page 68 of 107













Accomodation
Id NUMBER(10)
Info_id NUMBER(10)
Place_id NUMBER(10)
Name VARCHAR2(30)
Type VARCHAR2(30)
Location VARCHAR2(500)
Photo VARCHAR2(500)
Transport
Distance NUMBER(10)
Info_id NUMBER(10)
Air way BOOLEAN
Rail way BOOLEAN
Bus way BOOLEAN
Water way BOOLEAN
Page 69 of 107






Weather
Place name VARCHAR2(10) (FK)
Info_id NUMBER(10)
Place_id NUMBER(10)
Forecast BOOLEAN
Link VARCHAR2(500)









Info
Id NUMBER(10)
Place id NUMBER(10)
Emergency
Location VARCHAR2(50)
Info_id NUMBER(10)
Place_id NUMBER(10)
Contact info NUMBER(10)
Type VARCHAR2(30)
Page 70 of 107










BOARD
Country VARCHAR2(30)
Web link VARCHAR2(500)
Renewal
Request no NUMBER(10)
Membership date DATE
Start date DATE
End date DATE
Agency id NUMBER(10) (FK)


Festival
Name VARCHAR2(20)
Info_id NUMBER(10)
Place_id NUMBER(10)
History VARCHAR2(500)
Photo VARCHAR2(500)
Start date DATE
End date DATE
Page 71 of 107

















User
Id NUMBER(10)
Name VARCHAR2(30)
Mail id VARCHAR2(30)
Password VARCHAR2(30)
Country VARCHAR2(30)
Age NUMBER(3)
Contact VARCHAR2(30)

Updted info
edited TEXT VARCHAR2(500)
edited_id NUMBER(10)
agency_id NUMBER(10)
Page 72 of 107

















Description
Site name VARCHAR2(30)

Address VARCHAR2(500)
Rating NUMBER(2)
Contact VARCHAR2(500)
Service VARCHAR2(500)
Guide
Id NUMBER(10)
Name VARCHAR2(30)
Address VARCHAR2(30)
Rating NUMBER(2)
Service VARCHAR2(200)
Contact VARCHAR2(30)
Page 73 of 107


















Agency
Id NUMBER(10)
Name VARCHAR2(30)
Password VARCHAR2(30)
Covering area VARCHAR2(30)
Validity status BOOLEAN
Web link VARCHAR2(500)
Rating NUMBER(2)
Contact VARCHAR2(30)
Board country VARCHAR2(30) (FK)
Promotion
Adv no NUMBER(10)
Offer VARCHAR2(500)
Adv time DATE
Agency id NUMBER(10) (FK)
Page 74 of 107


















Gallery
Id NUMBER(10)
Info id NUMBER(10)
Title VARCHAR2(30)
Uploading date DATE
Description VARCHAR2(500)
Photo VARCHAR2(500)
User id NUMBER(10) (FK)
Place name VARCHAR2(30)
Gives opinion
User id NUMBER(10)
Place id NUMBER(10)
Opinion VARCHAR2(500)
Search
User id NUMBER(10)
Place id NUMBER(10)
Page 75 of 107











View map
User id NUMBER(10)
Place id NUMBER(10)

Manages
User id NUMBER(10)
Board COUNTRY VARCHAR2(30)
Page 76 of 107


6.4 TRIGGERS & PROCEDURE

Trigger
APPLY CHANGES

AUTOMATED CHANGES



Page 77 of 107

Procedure (publish promotion)

Procedure (Save list of photo)





Page 78 of 107

7. INPUT & OUTPUT DESIGN
7.1 INPUT & OUTPUT DESIGN




Page 79 of 107

Anonymous user

Page 80 of 107


Page 81 of 107

Member interface


Page 82 of 107


Page 83 of 107


Page 84 of 107


Page 85 of 107


Page 86 of 107


Page 87 of 107


Page 88 of 107


Page 89 of 107



Page 90 of 107


Agency interface

Page 91 of 107


Page 92 of 107

Board interface

Page 93 of 107




Page 94 of 107

8. PROJECT PHASE & ACTIVITIES
8.1 INTRODUCTION

This section provides a detail assumption and analysis of project
time period , duration , cost, risk and benefit of this system.
Page 95 of 107

8.2 Work schedule & project time analysis

8.2.1 Activity timeline

Tasks Task
number
Dependency Milestone Estimated
working day
Analyze the current
system
T1 6
Planning T2 T1 M1 10
Discovering
problems
T3 T2 M2 4
Identify business
requirement
T4 5
Analyze system
requirement
T5 T2,T4 M4 6
Design system
architecture
T6 T3 M3 10
Interface design T7 T5 M5 8
Database design T8 T5 M5 15
Design application
logic
T9 T6,T7,T8 M6 20
Installing hardware T10 T5 M5 8
Software
development
T11 T9,T10 M7 12
Page 96 of 107


8.2.2 Activity network

The blue line represents the activity network of the project.






Page 97 of 107

8.2.3 Pert chart



Page 98 of 107


8.3 COST-BENEFIT ANALYSIS

8.3.1 Cost analysis

Preliminary Expenses




Yearly Expenses


Page 99 of 107

Revenue from registration


Revenue from advertisement


Page 100 of 107

Projected Cash Flow



8.3.2 Benefit analysis
Tangible & intangible benefit
Tangible benefit:

1. Increased revenue
2. Membership fee

Intangible benefit:

1. Highlighting the tourist spot
2. Representing cultural & tradition
3. Improvement in travel agency sector



Page 101 of 107


8.4 RISK ANALYSIS & MANAGEMENT (DURING IMPLEMENTATION)

8.4.1 RISK IDENTIFICATION (During Implementation)
There can be some risks involved with the project during the
implementation and
They are as follows:
1. Technological risks:
With the existing technological support,the progress of the project may
be hampered
regularly.For example,the server may not contain the whole website,or
the database
may not process as many transactions per second as expected.If the
software components are
reused from another project,there can be defects which will limit their
functionality.
2.Manpower risks:
If the budget is not that high,enough skilled manpower cannot be
recruited as required,which will lead the project to a
schedule problem.
3.Disciplinary risks involved with organisation:
Change in the structure of the organisation can confuse people
involved with it and that can lead to an ambiguous situation.

Page 102 of 107


4.Requirement risks:
The proposed system will require a major change in the design.The
impact may not be visible to the customers.
5.Estimation risks:
There may be some underestimation in the timeline analysis,rate of
defect repair and the size of software.

Risk Analysis:

Risk Probability Effects
Sudden reduction in budget due to
organisational problem
low Catastrophic
Skilled staffs leaving project because of
financial issue
moderate catastrophic
Key staff ill at critical situation moderate serious
Software malfunction at critical situation moderate catastrophic
Sudden changes to requirement that
require major design rework
moderate serious
Restruction of the organisation bringing
in a different management
high serious
Database isn't capable of handling
enough transactions
high serious
Underestimation of time analysis moderate serious
Required training for technical staffs not
available
high tolerable
Rate of defect repair in underestimated low tolerable
Size of the software is underestimated high serious
Page 103 of 107


Risk Planning:
Risk Strategy
Organisational financial
problem
Have to prepare a brief statement for senior
management showing the necessity of the project
and how much hamper will be held due to reduction
of budget
Skilled staffs problem Convince them the impact of the project and giving
them as much advantage as possible
Staff illness Re organise teams and backup the works
Defective components Replace potentially defective components
Requirement changes Derive traceability info to assess requirement change
impact,maximise info hiding in the design
Organisational
restructuring
Prepare a statement which states all the necessary
information about the project
Underestimated
development time
Investigate how to minimise the time as possible
Database performance Investiagte all the probabilities to increase the
performance of the database or buy a new one





Page 104 of 107


8.4.2 Risk analysis & management (during maintenance)

1.Technological risks:
Technological issues may occur during the maintenance of the
project such as there may be an overflow in the server or the database
may not handle too much transactions.

2.Manpower involved risks:
Skilled and key staffs may leave the project team for personal
problem.Finding proper substitute sooner will be hard.
3.Organisational risks:
There can be changes in the management committee and the
organisation may not realise all the components of the project.
4.Requirement risks:
Customers can complain consequently which may lead to a major
change in the design.
Page 105 of 107

Risk Analysis:

Risk Probability Effects
Sudden reduction in budget due to
organisational problem
low Catastrophic
Skilled staffs leaving project because of
financial issue
moderate catastrophic
Key staff ill at critical situation moderate serious
Software malfunction at critical situation moderate catastrophic
Sudden changes to requirement that
require major design rework
moderate serious
Restruction of the organisation bringing in
a different management
high serious
Database isn't capable of handling enough
transactions
high serious
Underestimation of time analysis moderate serious
Required training for technical staffs not
available
high tolerable
Rate of defect repair in underestimated low tolerable
Size of the software is underestimated high serious
Page 106 of 107


Risk planning:


Risk Strategy
Staff handling problems Encouraging staffs to co operate and give them space
at times
Defective components Replace potentially defective components
Requirement changes Derive traceability info to assess requirement change
impact,maximise info hiding in the design
Organisational
restructuring
Prepare a statement which states all the necessary
information about the project
Underestimated
development time
Investigate how to minimise the time as possible
Lack of response from
people
Find all the ways of branding the project and the
impact of it to the target group
Page 107 of 107


REFERENCES


Diagram Designed by :

Enterprise architecture
GUI design studio professional