You are on page 1of 4


Roll no-01111502712
1. Introduction

The Software Requirements Specification is designed to
document and describe the agreement between the customer and the
developer regarding the specification of the software product
requested. This Software Requirements Specification aims to describe
the Functionality, External Interfaces, Attributes and Design
Constraints imposed on Implementation of the software system
described throughout the rest of the document. Throughout the
description of the software system, the language and terminology used
should unambiguous and consistent throughout the document.
Handling customer issues online might seem like a simple incremental
addition to traditional call centers and retail stores.
1.1 Purpose
Digital customer care (“e-care”) responds to customer demand
for easily accessible hardly multichannel interactions. The advent of
digital channels has changed the way consumers communicate and
search for product and service information. Digital channels have
already become the preferred source for product and service
information. Nearly 65% of social media users go digital when seeking
customer ratings, 62% do so for customer reviews, and half routinely
visit company websites. These figures exceed call centre use (47%),
e-mail(45%), or live chats(30%).
1.2 Scope
Increasingly, consumers themselves are responding to customer
queries and customer service. Two different levels of this peer-to-peer
(P2P) consumer interaction exist. One focuses on as hoc interactions
via forums, blogs, and social networks. Various communities where
consumers can crowd-source their questions and where highly
engaged brand promoters are recognized and rewarded.

Definitions and Acronyms


A unique identifier assigned to different customers
A person that is a user of the product
The items present in the store of the company

with the consumer attempting to use an online self service channel.1 Product Perspective As stated by the customer. Overall Description To adapt digital customer care. this acts as hardware interface.1. It might start out digitally. If the consumer can offer partial but not resolution.2 System Interface All the data input received by the system will be mapped to the respective file and a collection will be analyzed by different levels of employees in the organization.5 Software Interface . the consumer service journey across different channels first needs to be mapped to gain insights into the road blocks preventing uptake among the customer base. 2. Software Requirement Specification The information related to customer’s purchase that is logged The person who operates the software product.1.3 User Interface The user interface will be defined by the company’s website. he or she may resort to asking an online forum for help. 2.4 Hardware Interface The cloud storage facilities provided to the company helps in easier storage of customer data. there are no hardware or software requirements beyond these including. the consumer is then likely to contact a call centre for assistance. 2. 2.1. If the consumer cannot resolve the issue via that channel.1. A separate column “Product Support and Customer Care” will help the customer to review their product and submit their grievances if required. The journey itself can only begin if customers are already aware of their channel options and know how to use these to find answers to their questions. The storage involves web servers & load storage.Item Shopping Cart SRS Transaction User An individual entity in the inventory An object that lists a customer’s selected items. where an agent works with the customer to completely resolve the problem. 2. 2. but not limited to. their applied promotions and gives them a option to check out. memory or specific software packages that need to be utilized nor software packages that need not be utilized.1.

email address (no restrictions).2 Product Functions • Anyone is able to add one or more products to the shopping cart. 2. • A customer has a username (unique across all users).1. A user that is not logged in as a customer is given a chance to log in. Details of its use are involved . password (no restrictions). • Allow any customer to become a member. Company and price • The inventory also keep track of the stock/quantity of each product • Maintain records for many customers • A customer can be either a member or non-member.1. and navigate the browser to the address of this DCC website. • Only one promotion code may be used per purchase • The promotion is a fixed percentage discount that is to be applied to an entire order. • The shopping cart does allow multiple copies of any product. • Each product has its own stop-order status – either on or off. • Checkout is only available to logged-in customers. 2.1.) • Anyone may sign up for a customer account.8 Site Adaptations We have assumed that all of the computer systems in the present with the customers are in proper working condition and that the user is capable of operating these system's basic functions including but not limited to being able to power on the system. 2. and postal address (unverified. • Collect a 16-digit credit card number from the customer • Log/record the transaction • Allow manager to specify a stop-order for a purchase. Jacqual & message programming interface applications (MPI) are different Hadoop applications programme interfaces used by the company. • Member customers may enter a promotion code.6 Memory constraints High speed intel servers have been used for processing the queries of different customers present in the database. 2. • The discount is specified by the manager at the time of the promotion’s creation or most recent update/edit. thereby resolving the faster access memory availability.Various data analytics tools such as Pig. Eventually the memory constraint is handled. Hive.7 Operations • Maintain data associated with the inventory (a collection of products) • A product has a Name. login and open either Internet Explorer or Mozilla Firefox.

• Any user cannot edit their account information. A strong password is a password that meets a number of conditions that are set in place so that user's passwords cannot be easily guessed by an the following feature.4 Constraints The database may store passwords in plain text and there doesn't need to be a password recovery feature nor lockout after numerous invalid login attempts. • The manager account’s username and password maybe hard coded.5 Assumption and Dependencies We have assumed that the DCC will be running on a properly working web server and database system with an Internet connection that allows this system to perform all communications with clients. • Notify manager when an item to be reordered • When the quantity of items falls below a threshold. these rules include ensuring that the password contains a sufficient number of characters and contains not only lowercase letters but also capitals. and in some cases. the system may not work correctly in cases when security is a concern. 2. . from and within simple websites. 2. • The manager cannot be a customer.3 User Characteristics The typical DCC user is simply anyone that has access to the Internet and a web browser in the product department. Assumptions: • There is no need for anyone to be able to order more than a single copy of a book (or any item) in a single transaction. numbers. As such. These cases include those listed above in addition to lack of an encrypted connection when sending credit card information and forcing users to use “strong” passwords. symbols. Generally. the manager is notified that the item. 2. keyboard and mouse and is capable of browsing to. It is assumed that the user is familiar enough with a computer to operate the browser.