Grocery System Requirements Analysis

Software Requirements Specification

For

Organic Grocery Software System

Table of Contents

Table of Contents

1. Introduction 1

1.1 Intended audience 1 1.2 Brief Specification and Project Scope 1 1.3 Own Assumptions 1-2

2. System Features 3

2.1 Nonfunctional and Functional Requirements 3-6

Appendix A: Analysis Models 7
3. Class Diagram
3.1 Noun Identification………………………………………………………………………….7
3.2. Responsibility Driven Design 8-9
3.3. First Cut Class Diagram and Class Diagram (attributes and methods)……… 10-11
3.4 Class Descriptions 12-13
4. Object Diagram 14
5.Sequence Diagram 15
6.Collaboration and Communication Diagram 16
7.State Diagram……………………………………………………………………………….17
8.Activity Diagram……………………………………………………………………………18
9.UseCase Diagram………………………………………………………………………….19

Appendix B: Group Work Division 20

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