System Design Document

3.1. Introduction

3.1.1 Purpose

The purpose of this design specification is to provide a pictorial representation of the

proposed website through various diagrams.. It shows how the system flows, and how the overall
system works on the web application.

Its target is to help the developers design the system by helping them to picture the scenario and
develop the intended system. It will present the reader with various diagrams such as UML
diagrams and ER diagram.

3.1.2 Initial Assumption:

 In Site user context, the website is accessed by e-mail and password

 Admin users can change the contents of the site.
 An administrative system can only be accessed by authorized users by logging in with
given username and password.

3.1.3 Normal Flow:

The siteuser creates an account if it has not been registered to Yatra webiste. Siteuser Sign up by
providing personal details and fill up the form given. Upon submission of the form, the site user
is driected to his/her respective profile.

After creation of profile, user can sign in and out of the system. The user must use email and
password for that. In using the website, the user can add friends by entering name or keywords in
search button. The site user can also see different trips and lists, get information from it. The user
can later add that place to his./her trip list(bookmarl) to visit the place. After visit of the place,
the user can add that place to his/her visited list. The user can update status , upload photos and
comment on friends status as well comment on friends photos. The updates of user interatction
will be listed in the homepage of the user. It will list the updates of site user and his/her friend
circles.

3.2 Intended Audiences (Reading Suggestions)

This document illustrates the design of the system represented by UML diagrams. It is presented
to developer to develop the system. The document presents Use case diagram, Activity diagram,
Data design by the means of ER diagram, Activity diagram, Sequence diagram and State
Transition diagram. The diagrams give the detail design of the system. In response to the
document the system can be developed thoroughly.

3.3 System Models

Scenario

Use Case diagram is used to represent the scenario of the system. The system is divided into 3
distinct modules so as to make easier to represent the system. The modules are;

a. Site user Module (Create Profile, User Interaction )

b. Authentication Module (Form validation, user login, admin login)
c. Admin Module (Admin Panel)
Use Case

Create Profile
3.4 Class Diagram

Class Diagram is used to model the architecture of the system. It illustrates objects and classes
and relationships between them. It represents the static structure of the system. The textual
analysis of gathered requirements specified in SRS was carried out to model the class diagram.

3.4.1. Textual analysis

The objects, classes and their relationships is identified as follows;

Noun

Yatra Website

Site User

Admin

Guides

Trip list

Verb

Sign In

Maintain Guides

Maintain Siteusers

Add user

Maintain users

Sign Out
On the basis of the textual analysis carried out above following classes, objects, methods and
relationships are identified.

Classes

Activity

Comments

Friend

Guide

Guide_comment

Guide_gallery

Images

Photos

Photo_comments

Siteusers

Triplist

Users

wallpost
Objects

Objects of User

a. Site users
b. Admin users

Attributes

Attributes of activity

a. Id
b. Dt
c. User_id
d. Type
e. Type_id

Attributes of comments

a. C_id
b. Comment_from
c. S_id
d. comment

Attributes of friend

a. friend_id
b. request_from
c. request_to
d. status

Attributes of guide

a. id
b. name
c. description
d. address
 e. image

Attributes of guide_comment

a. id
b. guide_id
c. comment
d. user

Attributes of guide_gallery

a. id
b. guide_id
c. image
d. caption

Attributes of images

a. id
b. name

Attributes of photos

a. id
b. name
c. user_id

Attributes of photo_comment

a. id
b. photo_id
c. comment
d. comment_from
e. comment_to
Attributes of siteusers

a. id
b. firstname
c. lastname
d. password
e. email
f. gender
g. month
h. day
i. year
j. stud
k. profession
l. profilepic

Attributes of triplist

a. trip_id
b. guide_id
c. name
d. description
e. address
f. image
g. status
h. user_id

Attributes of users

a. id
b. username
c. password
Attributes of wallpost

a. s_id
b. user_id
c. to
d. status

Relationships

Siteusers comment on wallpost, comments

Siteusers update wallpost

Siteusers updates activity

Siteusers send reuest to friend

Siteusers comment on photo, photo_comment

Siteusers upload photos on photo

Siteusers maintain triplist

Users maintain guides

Users maintain siteusers

Methods
Class Diagram

Regarding the above textual analysis following class diagram is modelled.

Fig: Class Diagram

Data model (Extended Entity Relationship diagram)

Data model represents the design of the database of the system. Extended Entity Relationship (EER) diagram is used to show data
design. Following is the EER diagram of the system.
Activity Diagram

Activity diagram helps to properly represent the system design. The system is divided into 3
Modules. The activity diagrams of such modules are presented to represent the system
 Test Document

4.1. Introduction

4.1.1. Purpose

This document is prepared after the system is developed. This document illustrates range of test
activities performed. The test activities ensure the system is free from errors and bugs. It is
necessary activity for the validation and verification of the system. The test activity is divided
into following portions;

a. Test Plan

b. Test Cases

c. Test Log

4.1.2. Intended Audiences and Reading Suggestions

The document is prepared after the system is completely validated and verified. It is prepared by
System Tester and presented to Analyst, Designer and Developer for the validation and
verification of the system. The intended audiences should observe the test plan carried out, test
cases of individual test and test log or result of such tests performed. The Test Plan has the list of
test activity. Test Cases are the description of individual test performed with details of how it is
performed with acquired results. Test Log has the results of the test activities mentioned in Test
Plan.
 Test Cases Objective
1 To check whether the email and password match with the email and password saved
Test Case 1
Objective in the database
To checkof site users.the email and password match with the email and
whether
2 To check if the new password in the text field matches with confirm new password or
password saved in the database of site users.
not.
Test Data Database email and password
3 To check whether password changes or not after clicking Update button.
Expected
4
Test Result System will grant access to the user account after match of email
To check whether the photos are displayed on My photos section if photos are
inserted.and password.
Actual
5 Test ResultTo check
System grants
whether access.
photo upload shows in both home page and photos page after
Conclusion Successfully done.
uploading a photo.
6 To check whether comment are shown after entering comment on a photo.
7 To conform whether comments are stored in the DB after entering a comment on a
Test Case 2
Objective photo To check if the new password in the text field matches with confirm
8 To test if site users status is stored in the database after clicking update button
9 To checknew password
whether or not.
updated status shows in both home page and user profile page.
Test10Data To checkSite users icon
if delete Password
deletes specific status of the user.
Expected
11 Test Result
To checkThewhether
password should match
comments the confirmed
are deleted from the password
photo comment given by the
Actual Test Result Password matches with the confirmed password.
specific user only.
Conclusion
12 Successfully
To test whether result done.
displays in search page after entering keywords.
13 To test whether the search results from search page redirects to specific links or not.
14 To test whether “friend request sent” displays or not after sending add friend request
Test Case 3
Objective to the specific
To checkuser whether
or not. password changes or not after clicking Update
15 To test whether the friends are connected to eachother by accepting the friend
button.
request.
Test Data Site users Password
16 To test whether guides are shown if the admin user adds new guides in the admin
Expected Test Result The password should be updated
Actual Test Resultpanel. Password updates
17
Conclusion To test whether guidesdone.
Successfully are deleted or not if the user deletes guides from admin panel.
18 To test whether the pagination links works or not in the guides page.
19 To test whether add to trip list inserts guides to the trop list or not.
20 To test whether trip list update shows in homepage after adding guide to the trip list
or not.

Test Case 4
Objective To check whether the photos are displayed on My photos section if
photos are inserted.
Test Data Site users photos
Expected Test Result The photos related ot the site user should be displayed
Actual Test Result Photos are displayed related to the site user
Conclusion Successfully done.

Test Case 5
Objective To check whether photo upload shows in both home page and
photos page after uploading a photo.
Test Data Site users photo
Expected Test Result The photo should be displayed in home page and photos page of
respective site user
Actual Test Result The photo is displayed.
Conclusion Successfully done.

Test Case 6
Objective To check whether comment are shown after entering comment on a
photo.
Test Data Photo comment
Expected Test Result The comment should be shown for the respective photo
Actual Test Result The comment is shown for the respective photo
Conclusion Successfully done.
Test Case 7
Objective To conform whether comments are stored in the DB after entering a
comment on a photo
Test Data Photo comment
Expected Test Result The comment should be stored in the database of photo_comment
Actual Test Result The comment is inserted in photo_comment
Conclusion Successfully done.

Test Case 8
Objective To test if site users status is stored in the database after clicking
update button
Test Data Wall post status
Expected Test Result The status should be stored in the DB under wallpost.
Actual Test Result The status is inserted in the DB.
Conclusion Successfully done.

Test Case 9
Objective To check whether updated status shows in both home page and user
profile page.
Test Data Wallpost Status
Expected Test Result The updated status should be displayed on home page and profile
page
Actual Test Result The updated status is displayed in both home and profile page of the
respective site user.
Conclusion Successfully done.
Test Case 10
Objective To check if delete icon deletes specific status of the user.
Test Data Wallpost status
Expected Test Result The updated status should be deleted from the database and not
displayed in the result.
Actual Test Result The updated status is deleted form the DB and not shown in the site.
Conclusion Successfully done.

Test Case 11
Objective To check whether comments are deleted from the photo comment
given by the specific user only.
Test Data Photo comment
Expected Test Result Photo comment should be deleted from the DB
Actual Test Result Photo comment is removed from the DB
Conclusion Successfully done.

Test Case 12
Objective To test whether result displays in search page after entering
keywords.
Test Data Site user and guides
Expected Test Result The result should display site users or guides or both
Actual Test Result The result is displayed.
Conclusion Successfully done.
Test Case 13
Objective To test whether the search results from search page redirects to
specific links or not.
Test Data Site users and guides
Expected Test Result The links should redirect to user profiles or guides
Actual Test Result The links redirects
Conclusion Successfully done.

Test Case 14
Objective To test whether “friend request sent” displays or not after sending
add friend request to the specific user or not.
Test Data Friend
Expected Test Result The friend request message should show after clicking add request
Actual Test Result The message is displayed
Conclusion Successfully done.

Test Case 15
Objective To test whether the friends are connected to each other by accepting
the friend request.
Test Data friend
Expected Test Result The friends are set on both friends list after the request is accepted
Actual Test Result The friends are connected to each other.
Conclusion Successfully done.
Test Case 16
Objective To test whether guides are shown if the admin user adds new guides
in the admin panel
Test Data guides
Expected Test Result New guides data inserted should be shown in admin panel and
guides section
Actual Test Result Guide is inserted and shown
Conclusion Successfully done.

Test Case 17
Objective To test whether guides are deleted or not if the user deletes guides
from admin panel.
Test Data guides
Expected Test Result The selected guide should be deleted from DB
Actual Test Result The selected\ guide is deleted.
Conclusion Successfully done.

Test Case 18
Objective To test whether the pagination links works or not in the guides page.
Test Data Guides pagination
Expected Test Result The pagination links should redirect to prev and next pages
Actual Test Result Pagination link works.
Conclusion Successfully done.
Test Case 19
Objective To test whether add to trip list inserts guides to the trip list or not.
Test Data Site users Password
Expected Test Result The guides should be inserted in the trip list
Actual Test Result The guide is inserted in the trip list
Conclusion Successfully done.

Test Case 20
Objective To test whether trip list update shows in homepage after adding
guide to the trip list or not.
Test Data Trip list
Expected Test Result The update should be shown in home page
Actual Test Result The update is shown in home page.
Conclusion Successfully done.