Final SRS Document

Requirements Specification

For

Lord Buddha’s Travel and Trek Website & CMS

Software Engineering (COMP 401)

January 30, 2012

Version 1.0

Submitted By:-

Anup Chitrakar (47)

Bigyan Shrestha (50)

Kishlay Jha (13)

Pragya Kadariya (16)

Sanjeev Shrestha (39)

Submitted To:-

Dr. Rabindra Bista

Lecturer

Department of Computer Science and Engineering

Kathmandu University

i

Change History

Date Version Description

12 Dec 2011 1.0 Initial Draft

Document Approvals

Name Role Signature

Dr. Rabindra Bista Supervisor

ii

Table of contents

CHAPTER 1 .................................................................................................................................. 1

INTRODUCTION ........................................................................................................................ 1

PURPOSE ........................................................................................................................................ 1 VISION ........................................................................................................................................... 1 PROJECT SCOPE ............................................................................................................................... 1 GLOSSARY ....................................................................................................................................... 1 REFERENCES .................................................................................................................................... 2 OVERVIEW OF DOCUMENT ................................................................................................................. 2

SYSTEM DESCRIPTION ........................................................................................................... 3

OVERVIEW OF THE SYSTEM ................................................................................................................. 3

FUNCTIONAL REQUIREMENTS ............................................................................................ 5

SYSTEM MODELS ...................................................................................................................... 8

CONTEXT DIAGRAM .......................................................................................................................... 8

USE CASE DIAGRAMS ........................................................................................................................ 8 Use case: - LBN Web Server ................................................................................................................................ 8 Use case:- Basic User Activities .......................................................................................................................... 9 Use case: - System .............................................................................................................................................. 10

ENTITY RELATIONSHIP DIAGRAMS ...................................................................................................... 11

DATA DICTIONARY: ......................................................................................................................... 12 user_account: ..................................................................................................................................................... 12 menu .................................................................................................................................................................. 12 article ................................................................................................................................................................. 13 comment ............................................................................................................................................................ 13 template ............................................................................................................................................................. 14 slider ................................................................................................................................................................... 14 news ................................................................................................................................................................... 15 announcement ................................................................................................................................................... 15 event ................................................................................................................................................................... 16 newsletter........................................................................................................................................................... 16

CHAPTER 5 ................................................................................................................................ 17

SYSTEM FEATURES ................................................................................................................ 17

SYSTEM FUNCTIONS / RESPONSIBILITIES .............................................................................................. 17

FUNCTIONAL OBJECTIVES ................................................................................................................. 17

SYSTEM CONSTRAINTS ..................................................................................................................... 18 User Interface Constraints ................................................................................................................................. 18 Hardware Constraints ........................................................................................................................................ 18 Software Constraints .......................................................................................................................................... 18 Database Constraints ......................................................................................................................................... 18 Operational Constraints..................................................................................................................................... 18 Other Constraints ............................................................................................................................................... 18

iii

TECHNICAL REQUIREMENTS (NON FUNCTIONAL) .................................................................................. 19 Performance ....................................................................................................................................................... 19 Security .............................................................................................................................................................. 19 Scalability .......................................................................................................................................................... 19 Maintainability ................................................................................................................................................... 19 Multi lingual Support ......................................................................................................................................... 19

SYSTEM EVOLUTION ............................................................................................................. 20

1

Chapter 1

Introduction

Purpose

The purpose of this document is to present a detailed description of the Lord Buddha’s Travel

and Trek Website & CMS . It will explain the purpose and features of the system, the interfaces

of the system, what the system will do, the constraints under which it must operate and how the

system will react to external stimuli.

SRS document is here to present the requirements of the Users for managing the website

http://www.lbn.com.np. In this Project a Dynamic website is to be created, whose page content

changes according to the interactions made by the Users/Clients. The website is immensely

useful to the tourist who wishes to know about the various exotic travelling spots and experience

the thrill. The reservations to the various Hotels inside the Nation can also be done via this

Website.

The System administrator functions to create update or delete content according to the user

demands.

Vision

To deliver the best of our services to all the aspiring travellers and trekkers from around the

globe.

Project Scope

This project is a Web Content Management System. The scope extends on creating and

managing the overall web content efficiently. There are tools allocated to the System

Administrators to achieve this goal. The sole purpose is to create a CMS that is both efficient and

user friendly.

Glossary

Term Defination

Website A place on World Wide Web

Actors Client/Customer/System

Use case A diagram in which actors interacts with

system

LBN Lord’s Buddha’s Nepal

HTML Hypertext mark up language

2

CSS Cascading Style Sheet

Hacking Unauthorized use of other account

Prototype A simple model to show How the System shall

work

Troubleshoot To fix the problem

Constraints Conditions required

Plug-ins is a set of software components that adds

specific abilities to software application.

Logger System To maintain the log/record of data

References

This is a complete list of all documents referenced elsewhere in this document.

1. Systems Analysis and Design in a Changing World , Satzinger, Burd, Jackson, 3rd edition.

2. The Object Oriented Approach Concepts, System Development and Modeling with UML,

Satzinger, Orvik, 2nd edition.

Overview of Document

The next chapter, the Overall Description section, of this document gives an overview of

the functionality of the product. It describes the informal requirements and is used to establish a

context for the technical requirements specification in the next chapter.

The third chapter, Requirements Specification section, of this document is written

primarily for the developers and describes in technical terms the details of the functionality of

the product. Both sections of the document describe the same software product in its entirety, but

are intended for different audiences and thus use different language.

The fourth chapter, System model depicts various popular system models used to show

the functional requirements of the system.

The fifth chapter gives the overview of the functionalities provided by the system. The

Last Chapter, System evolution outlines the necessary upgrades that will be maintained in the

future versions of the program.

http://en.wikipedia.org/wiki/Software_component

http://en.wikipedia.org/wiki/Software_application

3

Chapter 2

System Description

Overview of the System

This Website is explicitly designed for both the internal and external tourist who wishes to relish

the exotic beauty of Nepal.

It has the following Components and provides detailed information about the following things:-

i) Home: - It provides brief description about the Vision of Website along with a short

Overview on the major Places Attraction, Recommended tour destinations, highlights,

Event Calendar and an efficient Search box to provide the Users with quicker results.

ii) About Us:- This Page Provides the User with the basic incentives of the Organization &

The Team whose Consolidated efforts have brought up this Work.

iii) Services:- It explains about the Various amenities provided by the Organization.

a. Trekking

b. Tour

c. LBN Specials

d. Ticketing

e. Pleasure

f. Adventure

g. Expeditions

h. Rental

i. Visa

j. Art and Crafts

k. Shopping

iv) About Nepal: - This provides a short glance the demographic figure and the Life Style of

our nation.

a. A quick glance.

b. Some facts about Nepal.

c. Subdivisions of Nepal

i. Eastern Region.

ii. Western Region.

iii. Mid-Western Region.

iv. Far-Western Region

4

d. History

i. Ancient period.

ii. Medieval period.

iii. Modern period.

iv. Rules of Monarchy.

e. People

i. Himalayan people.

ii. Hilly people.

iii. Terai people.

f. Economy

i. Per capita Income.

ii. GDP.

iii. Government Budget

g. Art and Culture

i. Festival.

ii. Music

iii. Languages

iv. Museums

h. Inter/National Carries

i. Photo Gallery.

v) Reservation:- Online Reservation Form is available which helps us to know about yours

interests and Present you with best choices.

vi) Contact us:- The Postal address, street address has been posted here which enables you to

be in direct touch with us. Any query, suggestion, Positive criticism can be sent to us via

the feedback form.

5

Chapter 3

Functional Requirements

Given below are the functional requirements of the dynamic website http://lbn.com.np

1. Mainly 2 end should be designed: FRONT-END and BACK-END.

The website viewers should not have access to the BACK-END i.e. BACK-END

must be under only administrative control.

Administrator of the website should have privileges of inserting, updating and delete

the contents to be displayed in the FRONT-END.

2. The website must provide the facility of displaying images at the index page of the.

Slideshow image gallery on the index page of the website should be customizable

by the administrator.

The system should provide the facility to the administrator of selecting images to be

displayed on so called slider.

First image on the slider should be selected by the administrator.

Caption to the each image in the slider should be modifiable by the administrator.

Logo of the company should be displayed over the image slider on the left hand

side.

3. The main navigation menu should be on the top right hand side of the image slider.

The navigation menu must be multi-level drop down menu.

Administrator must have privileges to add, update and delete items in the menu list.

Administrator must have some facility to re-order menu items.

4. The website must contain the Highlights section.

Highlight section must display the major highlights and the news/information

provided by the administrator.

Tabbed-panel could be used to for the highlight section.

Administrator can add, update and delete the major highlights.

Recently added highlights must be displayed at the top.

5. Search option should be included in the website.

The website viewers must have facility to search various information that are

available within the website.

http://lbn.com.np/

6

6. The website must have an Event Calender section.

This section must keep record of the list of events on particular date that should be

noticeable to the website viewers.

Administrator may add, update, delete event related contents.

Must display details when the highlighted event that has been clicked by the viewers.

7. Newsletter Signup section must be included.

Website viewers can subscribe to the company through this.

A signup form should be displayed for this purpose.

The viewer must provide his/her Name and E-mail address.

E-mail must be sent to the corresponding email address provided by the viewer along

with a thank you message in e-mail.

This feature is useful when the administrator wants to communicate to the client via

email.

8. The website must have a Places of attraction section.

This section must display the Attractive Tourist Destinations in Nepal.

This is one of the most important features of this website because it gives a brief and

quick overview of where the viewers would like to visit in Nepal.

The administrator of this website must be able to add, update and delete contents

regarding the attractive destinations.

This section must include an image, a short description, and should be slide

enabled(auto/manual).

9. Photo Gallery should also be included in the website.

The gallery should have album / category where the administrator can have different

photos relating to different locations, events, etc. (just like in facebook).

It must be user-friendly. The performance or speed with which the gallery loads must

be fast enough.

The images inside the album must pop-out with large size image when clicked in the

thumbnail.

10. Most importantly, Contact Us section should be included in the website.

This feature enables the user or viewer to send message directly to the administrator if

he/she has any queries.

This section should provide a simple yet attractive interface which can be used easily

by the viewers.

7

This section consists of name, email and message components. It should also have a

viewable send e-mail button.

The contact us must be located in the contact us section which is denoted by a

telegram-icon.

The e-mail must go to [email protected].

11. Article section should be included in the website.

This is where the articles of the website get loaded.

This section must have options to have more than one page under the same menu or

sub menu to define the character limitation by the administrator for any page (i.e.

Pagination feature).

The CMS must support inline articles.

12. More Importantly RESERVATION FORM must be made available.

For the purpose of online reservation and booking this section must be included.

The booking form must be validated before submitting.

The details of the filled form should be emailed to the administrator so that the

administrator could contact the client for follow-up.

13. The website must include other additional features such as:

Popup Windows: The popup windows (from both places of attraction and highlights

sections) more attractive and utilize all available space around it.

Thank you notes: A good popup window saying 'Thank you!' with a LBN logo after

they submit (in updates/newsletter section) and feedback (in contact us section). The

note and icon should be editable by administrator

Facebook Like Box must be included for follow up.

https://mail.google.com/mail/h/1bg65mlcujmtq/?&v=b&cs=wh&[email protected]

8

Chapter 4

System Models

Context Diagram

Context diagrams use data flow diagramming (DFD) notation to illustrate the scope of a problem

and the source, sinks of data and control that flows into and out of a system.

Use Case Diagrams

Use case: - LBN Web Server

Brief Description:-

The User Connects to the

Web Server and access the

various pages.

Respond Queries Subscribe

Manage CMS View

Information

Process

membership

Request membership Employee Customer/User

Web System

9

Use case:- Basic User Activities

Brief Description: - The User Looks for the various resources of information available.

Step-By-Step Description:-

1) The User Opens the Website in a compatible browser.

2) He looks at the various images.

3) Takes an Overall tour of the Website.

4) Takes a glimpse at the various services and amenities provided.

5) If interested Subscribes to the news and makes Reservations.

6) Queries about a particular thing in the Search box.

10

Use case: - System

Brief Description: - The task that System has to Perform.

Step-By-Step Description:-

1) The System updates the information available at various pages.

2) It adds / deletes the Service as per the availability.

3) It manages the tour packages and the reservations.

It responds to the various queries of the customers.

11

Entity Relationship Diagrams

Fig:- Entity Relationship Diagram of Website

12

Data Dictionary:

user_account: (The entity user_account will be used for storing the information about a particular user.)

Attribute

Name

Attribute

Type

Attribute

Size

Optional Notes

username VARCHAR 50 No Username should be unique for

each user. This attribute is the

primary key and should not be null.

password VARCHAR 50 No Password should not be null.

email_address VARCHAR 50 No Email Address should be unique for

each user and should not be null.

menu:

(The entity menu will be used for storing the information about a particular menu for the

navigation between different pages.)

Attribute

Name

Attribute

Type

Attribute

Size

Optional Notes

Id INT 11 No This is the primary key and is

incremented automatically. This

should not be null.

Title VARCHAR 100 No The attribute title should be unique

and should not be null.

url_name VARCHAR 200 No The attribute url_name should be

unique and should not be null.

parent_id INT 11 Yes -

Level INT 11 Yes -

page_layout INT 11 Yes -

Link VARCHAR 100 Yes -

description TEXT - Yes -

Icon VARCHAR 200 Yes -

front_page TINYINT 1 No This should not be null.

13

article:

(The entity article will be used for storing the information about a particular article linked to a

particular entity menu by the attribute menu_id.)

Attribute

Name

Attribute

Type

Attribute

Size

Optional Notes



should not be null.

Title VARCHAR 100 No The attribute title should be unique


Body TEXT - Yes -

display_order INT 11 Yes -

menu_id INT 11 Yes -

Author VARCHAR 100 Yes -

published_date DATE - Yes -

last_modified DATE - Yes -

comment:

(The entity comment will be used for storing the information about a particular comment linked

to a particular entity article by the attribute article_id.)

Attribute

Name

Attribute

Type

Attribute

Size

Optional Notes



should not be null.

article_id INT 11 No This should not be null.

Author VARCHAR 200 No This should not be null.

Email VARCHAR 200 No This should not be null.

Body TEXT 11 No This should not be null.

comment_date DATETIME 100 No This should not be null.

14

template:

(The entity template will be used for storing the information about a particular page layout i.e.

template of the web page.)

Attribute

Name

Attribute

Type

Attribute

Size

Optional Notes



should not be null.

Name VARCHAR 100 No The attribute title should be unique


position1 VARCHAR 100 Yes -






slider:

(The entity slider will be used for storing the information about a particular slider image for the

web page.)

Attribute

Name

Attribute

Type

Attribute

Size

Optional Notes



should not be null.

Title VARCHAR 200 Yes -

Path TEXT - Yes -

Target TEXT - Yes -

description TEXT - Yes -

front_image INT 11 No This should not be null

15

news:

(The entity news will be used for storing the information about a particular news item.)

Attribute

Name

Attribute

Type

Attribute

Size

Optional Notes



should not be null.


news_date DATE - Yes -

content TEXT - Yes -

Image LONGBLOB - Yes -

announcement:

(The entity announcement will be used for storing the information about a particular

announcement.)

Attribute

Name

Attribute

Type

Attribute

Size

Optional Notes



should not be null.


Content TEXT - Yes -

Image LONGBLOB - Yes -

16

event:

(The entity event will be used for storing the information about a particular event.)

Attribute

Name

Attribute

Type

Attribute

Size

Optional Notes



should not be null.


Content TEXT - Yes -

event_date DATE - Yes -

newsletter:

(The entity newsletter will be used for storing the information about a particular newsletter

subscription.)

Attribute

Name

Attribute

Type

Attribute

Size

Optional Notes



should not be null.

Name VARCHAR 100 Yes -

Email VARCHAR 100 Yes This should be unique for each

subscription.

subscribe_date DATE - Yes -

17

Chapter 5

System Features

System Functions / Responsibilities

1. Develop and manage a user registration and login system for the web site.

2. To provide a Quick glance about the nation. i.e history, people, economy, art and culture,

3. Listing the various Services available for the tourists. i.e trekking, tours, adventure,

expeditions, Art and Crafts, rental and many more.

4. To scan for the various Tourist attraction in the nation.

5. Provision for the Reservation.

6. Develop a simple and efficient search feature to find topics and information on specific

properties.

Functional Objectives

1. The system shall provide a user message board, allowing users to remain updated with the

current news.

2. The System shall provide the brief Information about the distinct Trekking Spots,

pleasure/leisure’s, Shopping, adventures and many other exotic things.

3. The system shall provide the ability for users to post topics on specific Subjects, allowing

users to request information on certain aspects.

4. The system shall provide the ability for users to register and login before they are allowed

to interact with the social networking aspect of the web site.

18

System Constraints

System Constraints restrict options of design, behavior, appearance or operation. They become

requirements due to factors outside the normal problem domain. System Constraints describe

how the product operates inside various circumstances. This section specifies design constraints

imposed by other standards, hardware limitations, communication interface limitations, etc.

There are a number of attributes of software that can serve as requirements.

User Interface Constraints

Using this system is fairly simple and intuitive. A user familiar with basic browser navigation

skills should be able to understand all functionality provided by the system.

Hardware Constraints

The system should work on most home desktop and laptop computers.

Software Constraints

The system is designed to run on Firefox, Internet Explorer, Chrome, Opera and Other Similar

Browsers. There are some issues currently associated with various JavaScript plug-ins in the

program. Some compatibility issues are also inherent while using the Internet Explorer for

browsing.

Database Constraints

The space given to the database is very limited in size. The data fetched from database may also

take some time because of various checks while querying the results. This results in slow

retrieval of records. Some images are also stored in the database which in turn results in database

fragmentation.

Operational Constraints

The system is limited by its operating server in terms of the maximum number of users it can

support at a given time

Other Constraints None.

19

Technical Requirements (Non functional)

Performance

It is a fast and efficient Website, which loads quickly with reasonable internet Speed. The

images, reservation form-fill up pages, feedback forms also loads instantly.

Security

The Server on which this Website resides will have its own security to prevent unauthorized

write/delete access. There is no restriction on read access. The updating of the Pages is restricted

Only to the admin.

Scalability

There is no provision for the User to Sign-up into the System. Hence, to sent the Feedbacks or to

request any Query or to mark the Reservation any number of Users can do it Simultaneously.

Maintainability

The maintenance of the System is purely mechanical. i.e., the developers go and troubleshoot the

problems.

Multi lingual Support

Only English language is supported currently. We hope to incorporate some other languages in

our future release.

20

Chapter 6

System Evolution

We started this project after the confirmation of prototype by the client. Then we slowly clanged

onto building the individual/smaller components. After testing each of them, we integrate them

as a whole. The product was basically built keeping in mind the genuine requirement of the

Client and the level of comfort it should provide to its Customers.

As the Scope for improvement never stops, there are a lot of dimensions to be further

incorporated in the further release. With the rapid advancement in technology and the demand of

time the requirement goes on changing. Hence the Product was designed as an Open System so

that new requirements could be easily included without affecting its other components’.

Some of the features of further release are listed below:-

1) Multiple menus can select the same data article.

2) Two or more articles can be linked to the same menu.

3) Better performance resulting from use of updated and optimized javascript.

4) Better security enhancements to prevent hacking of the site.

5) Including features such as Google Analytics and Paypal.

6) Making plug-in installable.

7) Flexible CSS designs can be used with user-configurable options.

8) Making a resource downloads menu for allowing the clients to download necessary

resources.

9) Making the website search engine optimized for better search results.

10) A user logger system to keep track of all the updates done within the system.

21

Index

A

Actors, 5

advancement, 20

C

comfort, 20

Constraints, 3, 6, 18

F

Functional, 3, 9, 17

Functional Requirements, 3, 9

H

Hacking, 6

HTML, 5

L

LBN, 3, 5, 7, 11, 12

Logger System, 6

N

Non functional, 19

O

Online Journal, 19

P

Prototype, 6

S

Security, 3, 19

System Functions, 3, 17

T

Technical Requirements, 3, 19

U

Use case, 5, 12, 13, 14

W

Web Publishing System, 5

Website, 5

Documents

Final SRS Document