Software Engineering Project: Coles System Design and Implementation

This Software Engineering project provides a comprehensive analysis of the Coles system. The project begins by outlining the functional requirements, such as customer and scheme detail storage, customer registration, purchase handling by staff, and tracking customer spending for rewards. It then details the non-functional requirements, including 24/7 system availability, data protection, scalability, and system reliability. The project includes use case modeling, a sequence diagram illustrating system interactions, and a data flow diagram depicting data movement. A detailed data dictionary defines the attributes and datatypes for customers, schemes, products, checkouts, staff, purchases, and registrations. An ER diagram visually represents the database structure, and the project concludes with a bibliography of relevant sources.

Running head: SOFTWARE ENGINEERING
Software Engineering
Name of the Student:
Name of the University:
Author Note

1
SOFTWARE ENGINEERING
Table of Contents
Functional requirements..................................................................................................................2
Non-functional requirements...........................................................................................................2
Use Case modelling.........................................................................................................................3
Sequence Diagram...........................................................................................................................4
Data Flow Diagram..........................................................................................................................5
Data Dictionary................................................................................................................................5
ER diagram......................................................................................................................................8
Bibliography....................................................................................................................................9

2
SOFTWARE ENGINEERING
Functional requirements
The main functional requirements of the system are:
 The system should be able to store the details of the customers. Additionally, the scheme
details are also required to be stored in the system. The registration of the customer of the
customer should also be recorded.
 The staffs of the Coles organization should be able to handle the purchase made by the
customers. The details of the purchases made by the customers are to be stored in the
system. In addition to this the products that the customers are purchasing should be stored
in the system.
 The total spending details are also required to be tracked by the system and the customers
are to be awarded based on their yearly expenditure. Hence, the system should be able to
provide the total expenditure of the customers.
Non-functional requirements
The non-functional requirements of the Coles organization are provided below:
 The system should be made available 24x7 so that the customers and the staffs of the
Coles Organization does not face any kind of difficulties. They would always be able to
access the system in their time of need.
 The system should be able to provide protection of data as huge amount of data for both
the company and the customers are stored in the system and this data can be
compromised at any cost.

3
SOFTWARE ENGINEERING
 The system should be scalable as the data for the system would be growing with the
growth in the size of the organization and the organization would be able maintain the
record for a considerable amount of time.
 The system should be reliable and should be fault proof. The system would be consisting
of all the main procedures of the system and hence reliability is an important factor for
the company.
Use Case modelling

4
SOFTWARE ENGINEERING
Sequence Diagram

5
SOFTWARE ENGINEERING
Data Flow Diagram
Data Dictionary
Customer
Attribute Datatype Size NULL/NOT
NULL
Key
CIN Short text 10 NOT NULL Primary Key

6
SOFTWARE ENGINEERING
Name Short text 10 NOT NULL
Address Long Text 255 NOT NULL
TelephoneNumbe
r
Number 10 NOT NULL
Scheme
Attribute Datatype Size NULL/NOT
NULL
Key
SchemeID Short text 10 NOT NULL Primary Key
Name Short text 10 NOT NULL
Description Long Text 255 NOT NULL
Product
Attribute Datatype Size NULL/NOT
NULL
Key
ProductID Short text 10 NOT NULL Primary Key
ProductName Short text 10 NOT NULL
price Currency NOT NULL
Checkout Staff
Attribute Datatype Size NULL/NOT Key

7
SOFTWARE ENGINEERING
NULL
StaffID Short text 10 NOT NULL Primary Key
StaffName Short text 10 NOT NULL
StaffContact Long Text 255 NOT NULL
Purchase
Attribute Datatype Size NULL/NOT
NULL
Key
PurchaseID Short text 10 NOT NULL Primary Key
CIN Short text 10 NOT NULL Foreign Key
ProductID Short text 10 NOT NULL Foreign Key
Quantity Number 10 NOT NULL
PurchaseDate Date NOT NULL
StaffID Short text 10 NOT NULL Foreign Key
Registration
Attribute Datatype Size NULL/NOT
NULL
Key
RegistrationID Short text 10 NOT NULL Primary Key
CIN Short text 10 NOT NULL Foreign Key
SchemeID Short text 10 NOT NULL Foreign Key
RegistrationDate Date NOT NULL

8
SOFTWARE ENGINEERING
ER diagram

9
SOFTWARE ENGINEERING
Bibliography
[1] Gaedke, U., Tirok, K. and Petzoldt, T. Pragmatic Rules for Databases. , 2015.
[2] Gil de la Fuente, A., Grace Armitage, E., Otero, A., Barbas, C. and Godzien, J.
Differentiating signals to make biological sense–A guide through databases for MS‐based non‐
targeted metabolomics. Electrophoresis, 38(18), pp.2242-2256. , 2017.