Software Requirement Specification for Carnival Ice Cream

Erica Jayasundera (2016MIS013)

Member A , Member B

February 5, 2019

1|Page
 The Purpose of the Product
1.1 The user problem or background to the project effort
Carnival Ice Cream Pvt Ltd. has been enlisted by UCSCMIS2016 to rewrite their existing
semi manual system. The existing system includes out-of-date technology and has become
increasingly difficult to maintain. In addition, there are several issues and bugs remaining in
the current product that cause difficulties and inconveniences to the users. Domain
modeling and presentation issues have also come to the foreground and require a
reworking of the system to be more accurate and useful.

1.2 Goals of the product

The goal is to provide a clear, efficient, and accurate way for ecommerce on internet more to
larger customer base. To provide online services to order, book, and payment process for the
ease of customers.

Functional Requirements
E commerce site will provide a number of functions; each is listed below.
1. Maintain data associated with the inventory (a collection of Ice creams and other

recipes

2. A product has a price, top ups -catalog

3. The inventory also keeps track of the stock/quantity of each product

4. Maintain records for many customers

5. A customer can be either a member or nonmember.

6. A customer has a username (unique across all users), password (no restrictions),

email

2|Page
7. address (no restrictions)

8. Anyone may sign up for a customer account.

9. Allow any customer to become a member.

10. Show a listing of available ice creams

11. Allow customers and managers to log in and out of the system.

12. Users (both customers and the manager) will be logged out if inactive for 30

minutes.
13. Shopping cart

14. Anyone is able to add one or more orders to the shopping cart.

15. The shopping cart does not need to allow multiple copies of any orders

16. Checkout
17. Checkout is only available to logged in customers. A user that is not logged in as

a customer is given a chance to log in.

18. Member customers may enter a promotion code.

19. Only one promotion code may be used per purchase

20. The promotion is a fixed percentage discount that is to be applied to an entire

order.

21. The discount is specified by the manager at the time of the promotion’s creation

or most recent update/edit.

22. Collect a 16-digit credit card number from the customer

23. Log/record the transaction

24. Allow manager to specify a stop order for an order

25. Each order has its own stop -order status either on or off. Details of its use are
involved in the following feature.

3|Page
Non-functional Requirements
. Separate user levels
. Audit compliant
. PCI DSS compliant
. GRPS Compliant
. Hashing of passwords
. Secure payments
. Captcha for each order confirmation
. Dual Authentication for user registration
. CMS -=PKI
.

Technologies used
Responsive CMS -Joomla with XAMPP(Apache Web Server) on Google Site with Paypal
Sandbox Payment system. Uses SMS gateway to verify the users of the orders.

. Buyer Oriented marketplace architecture

4|Page