SOFTWARE DESIGN DOCUMENT

BISY3002: INFORMATION SYSTEMS PROJECT 1(CAPSTONE)

Student name Student ID

KAPIL KARKI 200652

BISHWA RAJ PANDEY

DIKSHANTA BANJARA

ALINA SHRESTHA

BANDANA DEVKOTA
1. Executive Summary.........................................................................................................................2
2. Introduction.....................................................................................................................................3
2.1. Project Overview....................................................................................................................3
Aim..................................................................................................................................................3
Objectives........................................................................................................................................3
Why this project?............................................................................................................................3
2.2. Purpose of the Software Design Document...........................................................................4
2.3. Reading Recommendations...................................................................................................4
3. Conceptual model...........................................................................................................................4
3.1. Technologies used.................................................................................................................4
3.2. System overview....................................................................................................................6
Login and Registration.....................................................................................................................6
Search Product................................................................................................................................6
Product Catalogue and Cart.............................................................................................................6
Payment System and Transaction Handling....................................................................................6
Communication...............................................................................................................................7
Content Management.....................................................................................................................7
3.3. Architectural Pattern.............................................................................................................7
4. Design Viewpoints.............................................................................................................................8
4.1. Logical Viewpoint.......................................................................................................................8
4.2. Information Viewpoint...............................................................................................................9
4.3. Interface Viewpoint.................................................................................................................10
4.3.1. Interface Design Aspects...................................................................................................11
4.3.3. Site Map............................................................................................................................14
4.3.4. User Interfaces..................................................................................................................15
4.4. Interaction Viewpoint..............................................................................................................32
5. Traceability Matrix.........................................................................................................................33
 1. Executive Summary

Launching an e-commerce website with a social media feature is the purpose of this project, which is
mostly focused on Tourism industry in Nepal. In this website people can book the flights, hotels and
they can make friends, communicate with each other and travel together. This website is created as
the response to the COVID-19 pandemic, where travel and tourism is the mostly affected sectors,
with hotels closing, flights are on the ground, and travel restrictions implemented in all over the
world. A software design documentation is like a map which guides each team member to track the
project from the start to the last lines of code. So, before writing any code to establish an SDD we
must plan our complete system architecture. This allows to detect potential challenges and the
obstacles that might come in the way while developing the software. It is crucial that all the team
members understand the parts of software and how that are designed. This documentation helps in
collaboration with the team members as everyone needs to work together and build up their
respective parts of the software. This document describes the overall software architecture and
detailed design of CWNN website and how it can be operated through the graphical documentation
of the software design for the project. This document features overall class diagram, sequence
diagram, block diagram as well as traceability matrix which is related to the project, and it also
demonstrate many components of the product and provide a detailed explanation of the user
interface.

2. Introduction  

2.1. Project overview

  
Aim
  
The aim of our website is to connect of people of Nepal with all people from all over the world and
the main aim of our project is to let know the whole world about our beautiful country. Let them
know about culture of Nepal, the people, and our languages. The secondary aim of this project is to
promote tourism of Nepal. The name of our website that we give name to our website is Connect
win Nature of Nepal (CWNN).
 
Objectives
  
For the project we have and for the object we have used the SMART approach which suggests that
we make any objectives to be specific, measurable, achievable, realistic and time bond (Dysart,
2019). Keeping those in mind we have following as the objectives of our project. 
1. The finalization of project charter should be done with the approval of other team
members.  
2. PHP and SRC document should be done by 20 th of November 2022. 
3. SDD documentation should be done by 28 th of November with the showcase of it.  

Importance of the Project

  
The idea for the social media solely for the proposes of promoting the culture, people and places of
our country came into our mind for by thinking how small people in this world knows about our
country. People relate our country with any other countries such as India or China, but they never
know we are country of our own with our own legislation and judicial systems. Then our idea of
CWNN started with not just promoting our stuff or selling our things on the ecommerce platform.
What we want to do is connect our people with other people and then when people learn from each
other in their own then they will not be in confusion and know the truth about our about our past
and all the historical things that we are in part of, this part can be done by connecting with people
from our country and by booking the place , hotels and guides from our website they can come to
our country and visit meet people with selected package for the travel part and for meeting of
people they can interact with anyone inside or outside of our websites.  

Purpose
 
The purpose of this documented report is to showcase the process of taking the imagination in your
head to the figures that all the clients, shareholders and other team members in that project. 

Structure
 
In the structure of this document, it starts with executive summary then introduction of the
document and project then we give information about conceptual model, design viewpoint and
traceability matrix.

3. Conceptual model:

3.1 Technologies used:

Balsamiq
In this project we have used balsamiq for prototyping and wireframing as it is one of the most
popular programs and very easy to use and it is available free. You can portray the sketch of your
website digitally with the help of balsamiq

The specific reasons for using balsamiq can be.

1. Easy to learn, easy to pick up and implement for marketing associates without much design
experience.
2. The drag and drop features are very user-friendly in order to create mock-ups in a short
span of time.
 3. Balsamiq is quick. we can put an idea down in the tool very fast and not have to focus too
much on detail.

Notepad++
We use notepad++ for source code editing because of following reasons:

1. We can open multiple files opened at once in a tab view

2. An important feature is the autosave of information, no need to manually save the file.
3. The code syntax is highlighted when the file is saved with a specific file format, making it
easy to edit the code.

Mysql Database
We will be using Mysql for database management. The reasons we are using Mysql are:

1. Backup and restore functions are really good so if anything goes wrong on client-server it is
easy to restore our data.
2. Compatible with almost all types of programming languages, like C#, Java, and PHP, which
provides flexibility to deploy databases for different applications
3. High performance-MySQL provides very high performance in terms of data mining . A huge
amount of data can be easily extracted in couple of seconds.

phpMyAdmin
It is free software tool written in php. It is intended to handle the administration of MySql over the
web. It is a fully-features database management tool. The reasons why we are going to choose
phpMyAdmin for the backend of the website are;

1. We can run custom SQL commands directly inside the tool.

2. We can create, edit and delete databases whenever we want.
3. It can manage the user accounts with their permission
4. And so much more

3.2 System overview:

Our website offers a unique set of features that makes the website different from others. They are:
Login and registration:
Users are allowed to register and login into the website through a very secure system while the
admin and agencies have their own login portal.

Searching for destinations

Users can search for their desired destinations and choose the best package through the search bar.
And also by scrolling through our news feeds as it offers the user posts of various destinations.

Knowing people
As a social media website, we offer our users to get closer to the people of Nepal and know their
lifestyle. Promoting Nepal while fulfilling their desires. Users can add people who are on website and
follow them.

Communication
Users can communicate through the chat option available on the website or can directly email while
the website will use emails to provide the newest deals, offers, and invoices. Users also can submit
feedback. Users can communicate to people they may know with comments and chat options
available.

Payment
The website uses a very effective and secure gateway for payment handling as all the transactions
will be online. Bookings and reservation fees are charged for different packages chosen. Using social
media is completely free.

Content on website
Admin is in charge of content management. The admin can modify/remove or add the ads from the
website. Admin can remove users for violating guidelines.

3.3 Architecture Pattern:

Our website is based on MVC architecture patterns. It has three logical components.
 Figure 1: Architectural Pattern for CWNN

 Model:
The model defines the data contained in the site. If the data in model is changed the model
notifies the view or controller. Places, flight details and price details are some examples of
model in our project.

 View:
The view is the interface part of the system. This is how our website is presented to our
guests. It receives the data from model and displayed as requested. Just like if a customer
must book a flight the system will show the price details, place details and stay. The model
transfers the data to view, and guests can see it.

 Controller:
This is the brain of the architecture. It contains the logic that updates model and view upon
requests from the user.
As discussed about the flight booking, user chooses option to book a flight (model) all the
necessary logic is performed by controller after this the booked flight is shown to the users
(view).
 4. Design viewpoints

4.1. Logical Viewpoints

This part of the assignment gives a brief outline of the logical view of the system design. This gives a
description of the logical structure of the CWNN. Logical viewpoint is the distribution of functions as
per the hierarchy of logical sections.

To describe logical viewpoints briefly we will be using class diagram and their relationship with each
other.

Figure: Class Diagram

4.2. Information Viewpoint

The entity Diagram shown below gives the knowledge on CWNN are interdependent on each other
in a fluid state i.e., when the payment is happening. The diagram shows the entity ‘Order’ is based
on the existence of entities such as customer, product, and admin. It also shows how the user can
control all the other entities.

The series of information is uploaded to the database and described thoroughly. Thus, the given ER
diagram gives out brief information on CWNN and how it works.

Fig: Entity Relationship Diagram

4.4. Interaction Viewpoint

The figure below gives a brief idea of the sequence diagram and how the communication between
the customer, admin, and agent works. First thing first the customer will request to be logged into
the system which is accepted by the admin. After briefly visiting the site customer will inquire with
the admin about the pricing of the package which is further discussed with the travel agent. After
that, the pricing details are passed onto the customer. Later, the customer sends the payment
details to the admin and the admin accepts the payment detail.

The admin will also then modify the database according to the update in the site availability of the
booking.
Traceability Matrix
A document called the Requirement Traceability Matrix (RTM) links user requirements to test cases
(Tufail et al., 2017). At the conclusion of the software development life cycle, it contains all
requirements put forth by the client and requirement traceability in a formal statement.
Requirement Traceability Matrix's major goal is to confirm that all specifications are verified through
test cases in order to ensure that no function is overlooked while performing software testing.
References
Tufail, H., Masood, M. F., Zeb, B., Azam, F., & Anwar, M. W. (2017). A systematic review of
requirement traceability techniques and tools. 2017 2nd International Conference on System
Reliability and Safety (ICSRS), 450–454. https://doi.org/10.1109/ICSRS.2017.8272863