Grocery System Requirements Analysis

Only available on StudyMode
  • Topic: Supermarket, Unified Modeling Language, User
  • Pages : 24 (4406 words )
  • Download(s) : 212
  • Published : December 24, 2012
Open Document
Text Preview
Software Requirements Specification

For

Organic Grocery Software System

Table of Contents

Table of Contents

1.Introduction1

1.1Intended audience1
1.2Brief Specification and Project Scope1
1.3Own Assumptions1-2

2.System Features3

2.1Nonfunctional and Functional Requirements3-6

Appendix A: Analysis Models7
3.Class Diagram
3.1 Noun Identification………………………………………………………………………….7 3.2. Responsibility Driven Design8-9
3.3. First Cut Class Diagram and Class Diagram (attributes and methods)……… 10-11 3.4 Class Descriptions12-13
4. Object Diagram14
5.Sequence Diagram15
6.Collaboration and Communication Diagram16
7.State Diagram……………………………………………………………………………….17 8.Activity Diagram……………………………………………………………………………18 9.UseCase Diagram………………………………………………………………………….19

Appendix B: Group Work Division20

Introduction

1 Intended Audience

The system is to set up an “Organic Grocery Software System”. The different types of users that this document is intended for are:

• Grocery manager/assistants
• Grocery Customer
• Grocery Customers
• Grocery Drivers

2 Brief Specification and Project Scope

The general Objectives of the software for the users are:

Grocery Managers/ Assistants:
- Manage customer records
- Manage orders
- Allocate deliveries

Grocery Customer
- Order groceries
- Make payments (person/internet)

Grocery Drivers
- Obtain daily deliveries
- Download route plans.

This is just an outline of what will need to be implemented into the software; however at a later stage in the specification, our own assumptions have been incorporated into this specification, which will benefit the usability of the system

1.3 Our own Assumptions

As this was a brief specification, we had developed ideas which would work with the system, based on what has been proposed to us.

Below is a list of the additional aspects which will be implemented into the system:

For Managers/ Assistants:

As there is a requirement for the managers/assistants to allocate orders and deliveries, it is efficient to implement a time to which they can start processing the information, to be provided for the next working day, 5pm will be the cutoff point to which then they will start collecting and gathering the information.

The Managers / Assistants will have their own user name and password to login onto the system. This is because the system needs to be secure as there are personal details about customers and their accounts. So to avoid unauthorised people accessing the system, login’s are required.

The Managers / Assistant create a summary of each order for the driver. The summary should include: • When the customer ordered their groceries
• Delivery date
• Delivery time
• And status of the order (if paid or not)
• Have a delivery id
• Status of the delivery –pending, cancelled, delivered etc Customers:

The payment over the internet needs to be secure, therefore there needs to be able to be a verification procedure put into place for customers, i.e. when a customer registers their details (if a new customer) there will be a condition to: • Login using a personalised username and password.

• The next time they log in (starting with the customers username and password) it will direct them to the verification procedure. Thus would be beneficial to prevent hackers.

When the customer wants to add an item it adds it into their individual grocery cart. This is the replication of a shopping basket as if the customer is physically in the shop. There will be a grocery cart item which will hold details about each individual product that the customer adds into the grocery cart. The product will hold details about the customer’s order, the list of items, description, weight and total weight of products. This will appear to show the...
tracking img