Software Requirement Specification (SRS)

fullfattruckMobile - Wireless

Dec 10, 2013 (3 years and 8 months ago)

86 views

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

1

Rajiv, Salman, Dinesh & Abiral


Group B


Software Requirement Specification (SRS)


Project:

Online Shopping Management System
(Confectionary)




TEAM RESPECT

2
9
th

April, 2013

Revision 1.00


Team Members

Student ID

Rajiv Shrestha

30095888

Salman Salim

30100343

Dinesh Maharjan

30096218

AbiralBharijoo

30105969


Author: RSDA

Date: 29
th

April
,

2013

Version:
1.0

Status: Regular



Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

2

Rajiv, Salman, Dinesh & Abiral


Group B


Table of Contents


1. Introduction

................................
................................
...............................

4

1.1 Purpose of this document

................................
................................
................................
.............

4

1.2 Audience Stakeholders

................................
................................
................................
.................

4

1.2.1 End users

................................
................................
................................
................................

5

1.2.2 Client

................................
................................
................................
................................
......

5

1.3 Team Members Detail

................................
................................
................................
...................

6

1.4 Target Audience

................................
................................
................................
............................

7

1.5 Scope of this Document

................................
................................
................................
................

7

1.5.1 Document Scope

................................
................................
................................
....................

7

1.5.2 Product Scope

................................
................................
................................
........................

8

1.6 Definitions and Acronyms

................................
................................
................................
.............

9

2. General Overview (Salman)

................................
................................
........

9

2.1 User Characteristics

................................
................................
................................
......................

9

2.1.
1 User Interface requirements

................................
................................
................................
..

9

2.1.2 Product style Requirements

................................
................................
................................
.

10

2.1.3 Ease of Use

................................
................................
................................
...........................

10

2.1.4 Ease of Learning

................................
................................
................................
...................

11

2.1.5 User View of Products

................................
................................
................................
..........

11

2.2 Operation and Maintenance

................................
................................
................................
.......

12

2.3 Evaluating Project Success

................................
................................
................................
..........

13

2.4 Data Requirements Overview

................................
................................
................................
.....

13

3. Specific Requirements (Dinesh and Abiral)

................................
...............

14

3.1 External Interface Requirements

................................
................................
................................

14

3.1.1 User Interface
................................
................................
................................
.......................

14

3.1.2 Hardware Interface

................................
................................
................................
..............

14

3.1.3 Software Interface

................................
................................
................................
...............

14

3.1.4 Customer Interface

................................
................................
................................
..............

15

3.1.5 Administrative Interface

................................
................................
................................
......

16

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

3

Rajiv, Salman, Dinesh & Abiral


Group B

Figure 2:

................................
................................
................................
................................
............

16

3.2 Functional Req
uirements

................................
................................
................................
............

16

3.2.1 Automatically Load stocks

................................
................................
................................
...

16

3.2.2 Verify Users

................................
................................
................................
..........................

17

3.2.3 Allow users to sign up

................................
................................
................................
..........

18

3.2.4 Provide product listings

................................
................................
................................
.......

19

3.2.5 Provide help functions

................................
................................
................................
.........

19

3.2.6 Provide Contact Information

................................
................................
...............................

20

3.2.7 Process Orders

................................
................................
................................
.....................

20

3.2.8 Payment Method

................................
................................
................................
.................

21

3.2.9 Security System

................................
................................
................................
....................

22

3.3 Database Requirements

................................
................................
................................
..............

22

3.3.1 Entity
-
Relationship Diagram

................................
................................
................................

22

3.3.2 Database Schema

................................
................................
................................
.................

24

3.4
Performance Requirements

................................
................................
................................
........

26

3.4.1 Security

................................
................................
................................
................................

26

3.4.2 Availability Reliability

................................
................................
................................
...........

26

3.5 Quality Requirements and Maintainability

................................
................................
.................

27

5. Project Budget

................................
................................
.........................

28

5.1 Initial Fixed Cost (Start up Cost)

................................
................................
................................
..

28

5.2 Project Staffing Costs

................................
................................
................................
..................

29

Figure 5:

................................
................................
................................
................................
............

29

5.3 Annual Recurring Costs

................................
................................
................................
...............

29

5.3 Expected Financial Benefits

................................
................................
................................
........

29

5.4

NPV Analysis

................................
................................
................................
..........................

30

6. References (Rajiv)

................................
................................
....................

32

7. Sig
n Off

................................
................................
................................
....

32






Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

4

Rajiv, Salman, Dinesh & Abiral


Group B


1.
Introduction

This document is for the confectionary industry website designed with this
document. This planning brief aims to outline the
requirements that are used as
guidelines to build a website that highlights the chocolate store and its features. It
will serve as a one stop knowledge resource containing general information and
relevant forms as well as contact details for people looking

for information about the
website.

1.1
Purpose

of this document

This document is about Everest Sweets, which is a confectionary site developed as a
class project for use within Australia. The website is designed to serve as a one stop
shop for all
confectionary needs. It will provide all related items that a person can
find in a brick and mortar store. Also, it is built on the simple ease of use model and
therefore helps in the customer selecting their desired products with ease and not
having to ph
ysically leave the comfort of their homes.

The business model allows one to peruse the website at leisure and allows the
culmination of several different vendors and confectionary products at one exclusive
location from which people can securely and comfor
table shop with the knowledge
of secure transaction processing and expedited delivery. Special monthly promotions
will highlight different brands as well as how to get around and where the best deals
are on ongoing events in any given month. This will incr
ease customer flow and
generate revenue for the business.


1.2
Audience
Stakeholders




Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

5

Rajiv, Salman, Dinesh & Abiral


Group B

1.2.1
End users

The target audience for this website is mostly adults both male and female,
aged between 18
-
60 belonging to a middle class to upper middle class
demogr
aphic. These people are looking to shop from the comfort of their
homes and are interested in viewing a broad selection of confectionary at a
single online destination. Also, people looking for information about the
various brands offered by the site as we
ll as the different selections and
niches catered to by Everest Sweets (diabetic chocolate, dark chocolate etc,)
as well different ‘fun’ statistics about the target demographic that visit the
site and potential future customers.

1.2.2
Client

The Client se
rver system is one in which the database of the company’s
information including login passwords and other details resides on a main
server and from there, shared with all the required users of a network.
Everest will benefit from using Microsoft SQL for th
eir Client Server design.

The site will be designed to have multi
-
tier accessibility which allows
handicapped people and people with disabilities to be able to navigate to key
pages and glean information the same way as a normal user, using the help
of big
ger more eligible text (with the ability to magnify page settings if
required using custom scripting) This is important because a lot of people
who might be potential shoppers, buying online or not going to a physical
store may be doing so because they are

not able to visit a brick and mortar
location due to some handicap or disability, so the cost and time required to
implement such measures will be recouped in terms of accessibility to
potential clients but not overly done so to alienate the key demograph
ic.





Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

6

Rajiv, Salman, Dinesh & Abiral


Group B

1.3
Team Members Detail



Name

Role

ID

Phone

Email

Raj
iv Shreshta

Group Leader

30095888

04
30802041

Ragv_shrae15@hot
mail.c
om

Dinesh Maharjan

Web Developer

30096218

0414910116

D.Maharajan@gmail.com

Abiral
Bharijoo

Programmer/Tester

30097829

0466576876

abiralized@e
mail.com

Salman Salim

Documentation

30100343

0415780016

salmansaleem@gmail.co
m

Position

Responsibility

Group Leader:

Raj
iv Shreshta

Rajiv is the Group Leader
and along with ensuring all the deliverables from all
members of the team are on time, he has to double check the proper
working of the project and any errors or glitches in the paperwork and/or
software.

Web Developer:

Dinesh Maharjan


Dinesh is helping

to develop and write the AJAX and XML code for the
website and to ensure it is in proper running condition and all webpages are
current and ensuring load times.

Programmer/Tes
ter:

Abiral
Bharijoo

The Programmer/Tester in this project will help convert req
uirements of the
project into source code and will also help to alpha and beta test the website
before making it live.

Documentation
:

Salman Salim

Keeping track of the documentation submitted with the project and to
ensure all deliverables and milestones

as well as definitions and project
information is relevant and properly listed in the Report to be submitted with
the project.

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

7

Rajiv, Salman, Dinesh & Abiral


Group B


1.4 Target Audience

The target audience for the website is anyone who has the need to purchase
confectionary and choose from
the widest variety of chocolates available on a
website that provides quick delivery along with other value add services like gift
wrapping and express post. Also, because the site is designed to be user friendly, the
navigation will be designed so as to q
uickly process the transaction and check out
while simultaneously offering some other confectionary options just before check
out.

Also key is the navigation, which will be essentially catered towards the target
audience maintaining relevance thorough out
the webpage

s as well as similarity in
terms of design and theme. There will be a link to the homepage in every page as
well as easy access to direct webpage’s by
labelling

them based on the action in an
easy to remember way. Also, clicking on the logo on
any page will take the user to
the homepage and will allow them to skip using the back button to get to the
homepage. This description is mentioned to facilitate the access of a larger and
broader target audience catering to a demographic as listed above f
rom young to old
but focusing mostly on the young tech savvy customers as well as parents and
individuals who would like to place chocolate orders for special events and holidays
as well as gift packages.


1.5 Scope of this Document




1.5.1 Document Scope

This scope of this document is to emphasize and to examine the benefits of
the creation of a robust website for Everest Sweets, a company that provides
online confectionary services for individuals, with focus on the younger
demographic. This report draws

attention to the main benefits that the new
website can bring to the company, increasing the profit and consolidating the
Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

8

Rajiv, Salman, Dinesh & Abiral


Group B

company as the niche market trail blazer in Australia, providing services form
the very beginning, such as the search for chocolate b
rands from
international retailers, to gift wrapping and shipping services.

The online retail market in Australia has experienced tremendous growth.
This growth is due to many factor, but mostly because of the facilitation of
services for the consumer sitt
ing at home, for whom it has become very easy
to click and shop conveniently and efficiently. Also, the enhanced reliability
of the delivery process is a big contributor to the growth of the online retail
market, with more individuals and businesses recog
nising the benefits of
online sales, the uptake of online retail services has soared over the past five
years.


1.5.2 Product Scope

The basis of the propped system is to be a website for confectionary products
that is linked to a database which will monit
or all the items listed within the
store. This database will be hosted online and will be the backend for the
website, and the interface for all the search, record keeping and transactional
interactions.

The website will be based on two tier access. One
secure access will be for
the employees and administrator, who can log in to view stock reports, sales
invoices, billing and record related details. The second secure access will be
the customer’s login screen which allows a customer to securely shop and
s
tore cart details which may be retrieved later and used to link to customer
loyalty programs later on and current billing details. The administrator will
also have access to create users and give them privileges and usage rights
that are linked to their re
al world position and need to know requirements.


Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

9

Rajiv, Salman, Dinesh & Abiral


Group B

1.6 Definitions and Acronyms

The Following Acronyms have been used is this report.



IEEE (Institute of Electrical and Electronics Engineers)



SPMP (Software Project Management Plan)



UOB (University of
Ballarat)



IIBIT (International Institute of Business And Information Technology)



SRS (Software Requirement Specification)



RFP (Request for Proposal)



MySQL (My Structured Query Language)



SDD (Software Document Design)

2.
General Overview

(Salman)



2.1
User

Characteristics

2.1.1
User Interface requirements

The website will be designed to cater to its broader user base which includes
shoppers young and old. It will include (but not be limited to) making sure the
content quality and information is relevant and

consistent. The service and
maintenance of the website will also be important including no broken links,
and minimal hosting disruption if any. The design of the website will
incorporate features like feedback, automated reply generation; metric
analytics

through capturing user information to make sure the experience for
the end user can be optimized. FAQ’s and email alerts regarding new arrivals
and changes in policy and information.

The site has an easy navigation system and a user friendly design keepi
ng in
mind the target audience. Also, the site has a member’s area with a java
script based username/password login and authentication feature which
Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

10

Rajiv, Salman, Dinesh & Abiral


Group B

includes information about orders and stock details, and mailing lists as well
as employee logins to access

feedback and update/maintain the site.


2.1.2
Product style Requirements

As per the W3C requirements for universally accessible webpages, the
following standards are recommended to be utilized for the best possible
audience availability.

a)

Website: HTML,
XML and CSS will be mainly utilized to broaden
accessibility on all kinds of systems.

b)

PHP


Hypertext Processing (PHP) will be incorporated to ensure the
layout and formatting of the webpage is controlled and plug ins to
support its functionally are inclu
ded and utilized.

c)

Apache


This will be used as the backend to interface with the PHP
utilized in generating the webpages.

d)

MySQL


This will be the system to manage the storage, retrieval and
archiving of details relevant to the business including custom
er
information, business transaction logs and membership information.


2.1.3
Ease of Use

The interface mentioned above is specifically designed to support the
activities of the end user. For this universal supports of all standard web
browsers like Firefox, Google Chrome or Internet Explorer is supported.
Everest Sweet’s site satisfies the W3C

guidelines for webpage optimization
including ease of navigation and quick load times.

The homepage is the main page people will access as they click on the
website. It is designed to be an entry point for the casual as well as specific
web user who is i
nterested or mildly curious about buying chocolates online
and/or having a gift of confectionary delivered to others. It is designed to be
readily accessible, all the links are neatly grouped together, with navigational
Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

11

Rajiv, Salman, Dinesh & Abiral


Group B

links grouped together and member li
nks as well as information and full
screen images links listed separately. This allows the user to quickly access
the page that they want to browse without having to go through a web of
different redundant clicks.


2.1.4
Ease of Learning

The website has a
simple design to ensure that the user base that can access
it is the broadest possible. Therefore, the site will be designed using simple
HTML 5.0 based on a CSS template modelling other chocolate stores in the
country but heavily modified to be completely

relevant to Everest’s
requirement. The login feature will be based on JavaScript version 1.8.5 and
parts of the website used to illustrate pictures will be designed on Ajax (using
the .NET 3.5 version of the toolkit) so as to offer real
-
time updates. Java
Script
has been selected due to its ease of coding as well as its universal availability
and moderate security on different systems as mentioned on the W3C spec
sheet for the language. Ajax is incorporated to ensure real time relevancy to
the site with reg
ards to products available and special daily and monthly
offers as well as new arrivals.


2.1.5
User View of Products

The use of big images and enticing angles coupled with optimized browsing
and quick loading features will capture the mouth
-
watering elem
ent of
shopping for chocolate in person and therefore allow the customer to feel
more at ease with their entire shopping experience.




Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

12

Rajiv, Salman, Dinesh & Abiral


Group B

2.2
Operation and Maintenance



The website will be hosted on GoDaddy.com and the relevant uptime log will also be
avai
lable upon request. The user specifics will be determined based on the service
provider and their hosting plan and provided details. The hosting site will be
responsible for the uptime and hosting for the site and any downtime that may
occur will be depend
ent on the web service provider. Also, the two tier access to the
website will comprise of administrator access which will also allow access to website
employees and similarly the second access type will be for the customers who login
to the website after
a simple email registration process that requires their email and
a chosen password. No other type of access will be allowed to maintain website
security.

Physical security for the website, although not a through requirement will be limited
by the physica
l access to the server where the site is hosted. Any hazards related to
the elements (fire, rain) or theft are the responsibility of the service provider and
care has to be made that a geographically diverse host provider is chosen that also
provides data
redundancy. Similarly, the responsibility of the backup of the website
and updated database and maintenance is up to the administrator of the website
every 24 hours so as to prevent significant loss of data in the event of hardware
failure or software corr
uption. Also a soft SQL backup will be required after any
significant update or after order updating so that the database remains as close to
current as possible and does not get significantly impacted if there is a system crash.
The website has to be upd
ated to allow real time visibility of stock and therefore
needs a dedicated resource so as to keep the website current. Any holidays and
special events need to be incorporated into the daily operation of the website
therefore a dedicated plan is required f
or the day to day functionality of the website.



Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

13

Rajiv, Salman, Dinesh & Abiral


Group B

2.3
Evaluating Project Success


Success of the company’s operations will be key in guiding the business development
aspect of Everest Sweets as well as changing policy and revising ways of maximizing
user ‘stickiness’ and recurring revenue growth. In order to do this effectively, a
cumul
ative analysis of customer feedback, word on the street and profit and loss
assessment shall be tracked on a regular (weekly/monthly/yearly) basis to see how
the company is perceived in the market, by the end consumer as well as the revenue
coming in and p
rofits available to the business.

A very crucial aspect of business analysis is employing a third party consulting firm to
take into account all of the above mentioned metrics and then generating a chart of
what policies the company needs to further adapt

and which operations it needs to
drop to move forward and grow even more successful. The consulting firm also takes
into account such values as share price (if the company is publically traded), its
corporate image, the competitor scenario, avenues of gro
wth and many other
technical tools to present a snap shot of the company’s performance relative to its
industry.

In our case, as this is a class project, we will use Google Analytics


a free service, for
the above mentioned. Also, if the website is pursu
ed further, the data and analysis
gathered will be used to focus on listening to the end consumer, the most important
aspect of the business, and a long term strategy to generate the most success and
tweak any inefficiency out of the company’s daily operat
ion model will be
implemented.


2.4
Data Requirements Overview

The data requirements for the website include pricing for the inventory as well as
images of the merchandise and headers and footers as well as corresponding images
with Everest Sweet formatti
ng. The logo as well as relevant information about each
Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

14

Rajiv, Salman, Dinesh & Abiral


Group B

product including details about brands, shipping times and availability in stock will all
be considered data for the website.

Also, the database storing product inventory, pricing, membership details
, login logs
and shipping invoices will also be updated and reviewed as part of the data
requirement policy which is to govern all external and internal data available on the
website.


3.
Specific Requirements

(Dinesh and Abiral)



3.1
External Interface
Requirement
s

3.1.1
User Interface

The Everest Sweets will have amazing user interface in web browsing .user
can browse fro
m any part of the world easily
as it uses firebox and Google
chrome the late
st web browser. W
e also intend to expand in mobile
technol
ogies so that user can browse in mobile device easily and
comfortably.




3.1.2
Hardware Interface

Since our project is web based there is no direct connection to hardware
interfaces except modem connection and printer connection which can be
indirect con
nection.

3.1.3
Software Interface

The following software interfaces are required for Everest
Sweets
:

Web Browser
:

It display the WebPages at the end users computer which Interprets HTML
and CSS code.

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

15

Rajiv, Salman, Dinesh & Abiral


Group B

HTML:

It is one of the marku
p

language
s

to give look and feel of the website.

JSP
:

It is the Server
-
side scripting
language

tha
t

interfaces

between HTML and
MySQL.

MySQL
:

A relational
database management system

used to store the data

3.1.4

Customer

Interface

The diagram below shows the site ma
p for the custo
mer interface
:

see
appendix 1 for story board
.



Figure 1:

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

16

Rajiv, Salman, Dinesh & Abiral


Group B

3.1.5 Administrative Interface

Below fig shows the site map of the administrative interface which will only
be accessible to administrator and separated from the main customer
interface.



Figure 2
:

3.2
Functional Requirements

3.2.1
Automatically Load stocks

Description
:

One of the major functional requirements of Everest
confectionary website is its ability to automatically scan load the stock sheets
into the database.

Criticality
:

Since there would be too much information and critical data
on the sheets and it is a known fact that the information on the sheet would
be changing all the time it would be a tiresome and prone to error if manually
handled. If the website co
uld not automatically upload all the stock sheets
into database and user had to do it manually then error would be major
issues on the database. Beside error, time consumption for doing so will be
Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

17

Rajiv, Salman, Dinesh & Abiral


Group B

immense. Efficiency of the website because of Automatically

Load stocks
increases.

Technical issues
:

Creating an algorithm to read the Microsoft Excel files when
the stock sheet changes after each updates or modifications could be a major
technical issue.

Risks
:

There are few risks involved in this function. One
of the major one
could be the Stock sheets could change and cause the system to incorrectly
read them. Another might be Stock sheets may not be available.

Dependencies
:

None

Priority
:

This Functional Requirement is considered to fall on the range of
high p
riority
.


3.2.2
Verify Users

Description
:

Another important functional requirement of Everest
confectionary website is its ability to identify and verify its users.

Criticality
:
If a registered customer of Everest confectionary has to provide all
of their
details each time they try to login or purchase the product then it’s a
tiresome as well as not logical. So it is very important that once a user gets
registered in the website they should be able to login my just providing the
password every other time.

T
echnical issues
:

Forgetting password is the most common problems of
clients so there should be a standard and well recognised process to reset,
change and verify the passwords.

Risks
:

Few risks are involved with this function. One of the major risk that
co
uld be a failure of the database, in this case all the authentication process
would be a failure hence none or all non
-
registered clients can access the
site. Fake order could be a issues for the website.

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

18

Rajiv, Salman, Dinesh & Abiral


Group B

Dependencies
:
This function highly depends upon the

up to date user
database.

Priority
:
This Functional Requirement is considered to fall on t
he range of

very
high priority.


3.2.3
Allow users to sign up

Description
:
Among the other important functional requirement of Everest
confectionary website, its
ability to allow the new users to sign up is a big
catch.

Criticality
:
Any ecommerce website sells the products or services to their
clients. So it is must that the site should be able to earn new clients all the
t
ime and be able to retain the older ones.
For increa
sing the e
-
bu
sines
s
of
Everest
Sweets

they should allow the new customer to sign up so that
customers can explore and purchase the products. This is one of the
marketing
strategies

of Everest confectionary to gain its popularity.

Technical issues
:
There might me numerous people who might just create a
denial of service (DOS) for the website. So a strong process needs to be put in
practice that ensures that the client actually exists in real world. There also
should be a process that would allow t
he clients to change or update their
personal information.

Risks
:
Fake user could

sigh in as a part of a client
and may create
mayhem

in
the website such as DOS and spamming.

Dependencies
:
None

Priority
:
This Functional Requirement is considered to fall on

th
e range of
very high priority
.


Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

19

Rajiv, Salman, Dinesh & Abiral


Group B

3.2.4
Provide product listings

Description
:
Another impo
rtant functional requirement of
Everest
Sweets

website is its product listing ability.

Criticality
:
Clients of Everest confectionary should be able to browse
all the

ranges of products
, their prices and other facts related with the products. All
the clients would definitely try to browse all the products or search some
specified product in the website. It is very crucial that all the clients should be
able to browse a
ll the products offered in the website.

Technical issues
:
Products must be categorised in some way.

Risks
:

Risks such as Products entered into wrong category and listing, take
makes it could be search. Product database fails and no products are listed

Dep
endencies
:
This function requires that the product listing in the database
has to be up to date. Non existing products should be removed instantly and
the new products should be added immediately

Priority
:
This Functional Requirement is considered to f
all
on the critical
priority
.


3.2.5 Provide help functions

Description
:
Clients are often confuse with the meaning, images and content
of the pages so Everest confectionary website has an additional accessible
help on all the pages.

Criticality
:
Everest confe
ctionary website should be able to guide its clients
for easily accessible for help page. Confusion with the meaning , images
prices and other component of website could lead to the loss of clients. Help
functionality aids the website to retain their custo
mers.

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

20

Rajiv, Salman, Dinesh & Abiral


Group B

Technical issues
:
Information provided in the help should always be up to
date. This is the section where client or even other team members would rely
upon so all the information provided needs to be exact and up to date.

Risks
:
Help functions rely o
nly on the possible questions that customers
might ask or need to guide, however there is always a risk that some unique
queries or problems not covered in the help function.

Dependencies
:
None

Priority
:
This Functional Requirement falls in the range of m
e
dium.


3.2.6 Provide Contact Information

Description
:
Everest confectionary website provides the detail contact
information of organisation

Criticality
:
It is a crucial feature of the website to provide the clients with the
detail contact information of
organisation. All the postal address, email
address, telephone numbers, fax numbers should be provided so that
customers can choose their convenient medium for communicating with the
organisation for different purposes.

Technical issues
:
All the contact in
formation needs to be up to date.

Risks
:
If wrong or out
-
dated i
nformation provided, customers
might confuse
or mislead
.

Dependencies
:
None

Priority
:
This Functional Requir
ement falls in the critical
.


3.2.7 Process Orders

Description
:
Another important
function of

Everest confectionary website is
the ability for processing the customer orders.

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

21

Rajiv, Salman, Dinesh & Abiral


Group B

Criticality
:
The system must be able to process customer orders. The
payment system will make use of current offline business processes (which is
currently preferr
ed by client), but may provide online payment functionality
(which can be disabled).

Technical issues
:
Implementing security certificates to guarantee security.
Customers and team both parties should rely on some process that
guarantee the security and pri
vacy of the orders.

Risks
:

The order may not go through even though customer submitted it.
System may not calculate order correctly.

Dependencies
:
Requires up to date product
listings, verification of users
,
security .

Priority
:
This Functional Requirement

falls in th
e medium range of priority.


3.2.8 Payment Method

Description
:
Another important function of

Everest confectionary website is
the range of payment methods that are available for the ease of customers.

Criticality
:
It is an important factor for
clients to provide a range of payment
options so that the clients can pay their purchase according to their
feasibility. Everest confectionary website provides the payment options such
as PayPal, master card, credit card and debit card options for the paym
ent.

Technical issues
:
Implementing security certificates to guarantee security.
Process secures enough to secure the transactions. Encryption techniques are
must for the transaction process.

Risks
:
If the process are not secure enough then loss of money.

Process
should be reliable for all the transaction from both parties.

Dependencies
:
None


Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

22

Rajiv, Salman, Dinesh & Abiral


Group B

Priority
:
This Functional Requirement falls in the c
ritical range of priority.


3.2.9 Security System

Description
:
The system will be made secure from outside attac
ks and
unauthorised access
.

Criticality
:
As this product is going to be accessible on the Internet, it is
important that it has security in place to make it harder for hackers, viruses,
‘malware’ etc. to access or damage important areas of the website

Tech
nical issues
:
If someone (or something) is able to alter the prices of the
products, site design etc. then this is likely to be detrimental to the image of
the business. Security needs to be put in lace without adversely affecting the
sites useability too
much.

Risks
:
Unauthorised access or modification to the website.

Dependencies
:
None
.

Priority
:
This Functional Requirement falls in
the high range of priority.




3.3
Database Requirements




3.
3.1
Entity
-
Relationship Diagram

An Entity
-
Relationship (ER) diagram for the database component of the
solution is shown
below
there

are 6 tables
:
product entity,
category entity,
cart entity, orders entity,

customer entity and order detail entity. Primary key
is underlined and bold.

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

23

Rajiv, Salman, Dinesh & Abiral


Group B
























ORDER_PRODUCT

Fk

fk

Product id

Order id


Quantity

Gst

total

PRODUCTS

pk

Product id


Product name

Product detail

Product category

Product price

Feature

image

ORDERS

Pk

Order id




fk

Order date

Product

Status

Customer id

CATEGORY

pk

Category id


Category name

detail

CART

pk

Cart id






fk

Product id

Item

Price

Quantity

Session id

Customer id

CUSTOMER

pk

Customer id


Name

Country

State

City

Phone

Email

Username

password

ORDER DETAIL

pk

Detail id




fk

Shipping name

Address

Phone no

Customer id



Figure 3
:



M


M


M


1

M


1

M


1

1

1

1

1

1

1

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

24

Rajiv, Salman, Dinesh & Abiral


Group B


3.3.2 Database Schema


TABLE NAME:

FIELD:

TYPE:

DESCRIPTION:

P
roduct

Product id

Number

Primary Key


Product name

Text(30)



Product
category

Text(30)



Product price

Text(30)



Product feature

Text(20)



Product image



CUSTOMER

CustomerID

Number

Primary Key


First Name

Text(30)



Last name

Text(30)



Country

Text(40)



Phone

Text(15)



State

Text(15)



Mobile

Text(15)



Fax

Text(15)



Email

Text(50)



Password

Password










ORDER

OrderID

Number

Primary Key


CustomerID

Number

References
CUSTOMER(CustomerID)


Order date

Date/Time



Product name

Text (20)



Product price

Text(10)


Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

25

Rajiv, Salman, Dinesh & Abiral


Group B

TABLE NAME:

FIELD:

TYPE:

DESCRIPTION:


Quantity

number



Status

Text(10)


ORDER DETAILS

Detail iD

Number

Primary key


Shipping name

Text (20)



Shipping
address

Text(20)



Shipping phone
no

Int



Customer id


Foreign key of customer

CART

cartID

Number

Primary Key


Product id

number



Item

Text(50)



Price

Float



Quantity

Number



Session id

Number


CATEGORY

CategoryID

Number

Primary Key


CategoryName

Text(20)



Category detail

Text(20)






ADMINISTRATORS

Username

Text(12)

Primary Key


Password

Text(20)







Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

26

Rajiv, Salman, Dinesh & Abiral


Group B

3.4
Performance
R
equirements




3.4.1
Security

The website is designed to avoid and be able to protect sensitive user and
business information therefore the following security issues will be
addressed:

Encryption of Sensitive user Data:

The website employs AES encryption to
store sensitive user information as well as payment details and billing
information.

Data Redundancy:

The website also has incorporated a backup solution to
ensure data is not lost in the case of a server crash or ha
rd disk failure.

Denial of Service, Malware and Virus Protection:

As the site is hosted on
GoDaddy.com, their websites uses sufficient firewalls between the user and
the data to prevent any file execution on the end server as well as protect
from hacking
attacks and attempts at unauthorized intrusion.

Authentication:

The login and password protocol will be implemented as well
as resources like encryption and offline storage for safe keeping of these
details.

Error Correction and Handling:

Website glitche
s, server errors, missing or
dead links and other website runtime errors will cause a default display of
error message that does not allow user access to file directory or system
information.

3.4.2
Availability

Reliability

The network and communication st
ructure adapted by any company,
especially ones that are web based can make or break them. Therefore it’s
important to setup a network that is optimized to provide the broadest range
of availability and usage within the budget the company has set out for s
uch
an infrastructure. The uptime based on GoDaddy.com’s statistics is 99.9%,

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

27

Rajiv, Salman, Dinesh & Abiral


Group B



3.5
Quality Requirement
s

and Maintainability


The browser compatibility will include latest specs upto Firefox 4.0.13,
Google Chrome 19.0.1084.23 (Platform version: 2046.30.0)

and Internet
Explorer version 9.0.2. as well as older versions of the browsers up to three
iterations prior.

The connection speeds at which the website will be optimized for will include
anything over 56k (baseline) going up

to any higher speeds that are

available.
The optimal user experience recommended on the website will be 128kb to
ensure much wider compatibly.

The screen resolution supported will be 800X600 in 24bit Colo
u
r but will also
include inverse colour features for colour
-
blind and handicappe
d (as per the
W3C specifications).

The website will be tested to work on Windows 8 and below up

to Windows
XP as well as Android 4.04 (Ice cream sandwich) and below to Android 2.01.
Mac OS 10.6 will be supported all the way down to Mac OS 8.

Mobile compa
tibility will be tested using iPhone 3GS and blackberry bold
9000 and above browser revisions (4 and 6 respectively) as well as framing
and view ability on Safari 5.5 and 4.0.

As the site is small in size and is uploaded as a class project, the
maintenan
c
e

of the site will not be pursued further than the duration of the course. If in
the future the website is deemed suitable to be launched as an actual
business, it shall be maintained by a dedicated resource i.e. an employee of
Everest Sweets on a daily ba
sis.


Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

28

Rajiv, Salman, Dinesh & Abiral


Group B

5.
Project Budget


The project budget is a detailed estimate of all the costs required to complete
project tasks. It is much more detailed than the high
-
level budget developed in the
Initiate Stage. The typical budget specifies costs for staff
labour
, materials
procurement, ongoing operating costs and other direct costs such as travel or
training.

The detailed budget provides the project sponsor with a best estimate of
how much the project will cost. The detail budget helps manage expectations
and
gives the project sponsor information to develop

a cost/benefit for the project
(Boards of Regents, 2007).

Note: This project is a student project, and as such there will not be any substantial
costs associated with it for either the project team or th
e client.


5.1
Initial Fixed Cost (Start up Cost)

Hardware

Amount


Server

x

1


Router

x


1


Switch

x


1



Total Hardware Costs

65
0

150

75


8
75

Software



Windows 7 OS


Microsoft Word Package (1 Year)



Total Software Costs

00.00

125
.00


125.00

Grand Total

$
1000
.00


Figure 4
:

Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

29

Rajiv, Salman, Dinesh & Abiral


Group B


5.2
Project Staffing Costs



Rajiv

Salman

Dinesh

Abiral

Total

Rate per hour

40

40

40

40

1
6
0

Expected hours per week

10

10

10

10

40

Expected duration (weeks)

26

26

26

26

104

Total hours

260

260

260

260

1040

Total cost

$
10,400

$10,400

$10,400

$10,400

$41,6
00

Figure 5:

5.3 Annual Recurring Costs


Hardware

Amount

Server Maintenance

25
0
.00

Upgraded ADSL speed ($19

per month)

228.00

Domain N
ame
regeneration

costs

45.00

Total Costs

$
473.00


Figure 6
:


5.3
Expected Financial
Benefits


Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

30

Rajiv, Salman, Dinesh & Abiral


Group B

The system will attract an extra
twenty

custom
ers per month, who each spend $4
0
per month on
normal
.

The system will
maintain

three

customers per
month, who
each spend $4
0 per month on
normal
.

The ease of use of the new system will mean
that the
active

customer base of 6
0 cust
omers will now spend an extra $2
0 per
month.


New customers per month

2
0


Retained customers

3

12

Expected
purchases per month


4
0

Total benefit from new and retained customers


$48
0




Existing customer base


6
0

Expected additional purchases


2
0

Total benefit from existing customers


$1,2
00




Total gain in revenue


$1,68
0



Figure 7
:

5.4


NPV Analysis


Net Present Value (NPV) analysis is the process of taking a current, and projecting
the future net income from
the

investment. The calculation includes the

price
received for market Everest Sweets
on the income side of the equation, and feed
costs, facilit
y expenses, genetic premiums, etc. on the expense side to arrive at the
net value, then converting these future earnings into present
-
day dollars. Future
Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

31

Rajiv, Salman, Dinesh & Abiral


Group B

dollars are converted to present
-
day value because a dollar today is worth more
than the same dollar t
omorrow. This concept is known as discounting

(Penton
Media, 2013).

This calculation only considers the cash flow, and therefore excludes depreciation
.
The NPV analysis shows a 5 year period, but the expected gains and losses may
continue for a greater
period.


Year

0

1

2

3

4

5

Increase in revenue

150
00

150
00

150
00

150
00

150
00

150
00

less Expenses






Initial fixed costs

1000






Project staffing costs

4
16
00






Server maintenance

250

250

250

250

250

250

Upgraded ADSL

228

228

228

228

228

228

Domain name costs

4
5

4
5

4
5

4
5

4
5

4
5

Total costs

43123

473

473

473

473

473

Net cash flow


$
15,473


$
15,473

$
15,473

$
15,473

$
15,473








Payback Period:

1.5






Net Present Value*

$43,088



*Discount Rate:

10%



Figure 8
:



Software Requirement Specification (SRS)


ITECH 3602
-
7602 Project

32

Rajiv, Salman, Dinesh & Abiral


Group B

6.
References

(Rajiv)


Boards of Regents. (2007). Project Management Advisor. Retrieved on 29
th

April,
2013. From.
http://www.pma.doit.wisc.edu/plan/2
-
4/what.html

Penton Media. (2013). What is Net Present Value. Ret
rieved on 29
th

April, 2013.
From.
http://nationalhogfarmer.com/genetics
-
reproduction/evaluation
-
selection/0109
-
npv
-
anaylsis
-
process


7
. Sign
Off



Name

Signature

Date

Rajiv Shrestha



Dinesh Maharjan



Salman Saleem



Abiral Bharijoo