MN507 Software Engineering Report: System Requirements Analysis

This software engineering report details the analysis and design of a system for the Coles organization. It begins by outlining the functional and non-functional requirements, including scalability, availability, and usability. The report then presents use case modeling, sequence diagrams, and data flow diagrams to illustrate the system's processes. A comprehensive data dictionary and an entity-relationship (ER) diagram are also included to define the system's data structure. The report concludes with a bibliography of relevant sources, providing a complete overview of the software engineering principles applied to the system's design. The report covers aspects of system requirements, design, and modelling for the Coles organization, as per the MN507 Software Engineering course, and it also follows the assessment guidelines provided in the assignment brief.

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...........................................................................................................3
Use Case modelling.........................................................................................................................4
Sequence Diagram...........................................................................................................................5
Data Flow Diagram..........................................................................................................................6
Data Dictionary................................................................................................................................6
ER diagram......................................................................................................................................9
Bibliography..................................................................................................................................10

2
SOFTWARE ENGINEERING
Functional requirements
The functional requirements of the system to be developed for the Coles Organization
are:
 The system should be able to provide the details of the product and the also provide a
brief description of the products available in the system. The Products are access by the
product names.
 In addition to the details of the products the purchase of the products. Each of the
purchases made by the customer would be stored in the system with the PurchaseID. The
details would also include the CID providing the details of the customer and the SID is
used for the details of the staffs that would be handling the purchase. Additional details
such as PurchaseDate and Quantity is also recorded for a particular purchase.
 The details of the customers are also stored in the system with the CID being used for the
details of the customers as a reference. The customer name, the address of the customer
and the telephone number of the customers are also stored in the system. The details of
the customers are stored in the system during the registration and the selection of scheme
for the customers.
 The scheme details are also stored in the system with the name of the scheme and the
description of the scheme is also stored in the system.
 Additionally, the details of the staffs are also stored in the system which are referred by
the SID which is a unique Identification for the staffs.
 The system also provides the report for the customers who are eligible for the gifts for the
purchases that they have made throughout the year.

3
SOFTWARE ENGINEERING
Non-functional requirements
The non-functional requirements of the system that is being developed for the Coles
Organization are described below:
 Scalability: Scalability is very important for the system which is being developed, the
system should be able to store a huge amount of the data as the organization is a growing
one and would be having a high range of data to be stored in the system and this would
increase infinitely and hence, there is need for the scalability of the system.
 Availability: The system is made available to the staffs and the customers in the system
on 24x7 basis as the business of the organization should not stop and the customers
would be able access the system on a 24x7 basis, hence, the requirement of the criteria of
availability of the system.
 Usability: The system design should be very useful and optimal for the users. The users
should be able to have an attractive interface and the navigation and menu features in the
system would be developed in the system with great efficiency. The system should be
convenient to use for the customers and the staffs.
 Reliability: The system should be reliable enough so that there not much error and the
system should not be unresponsive. Hence, the reliability of a system is very important
factor and data stored in the system should be protected efficiently.
 Maintainability: The maintenance process of the system and cost of maintenance for the
system should be minimal and the maintenance of the system should be hassle free for
the organization. Hence, maintainability of the Coles system is very important.

4
SOFTWARE ENGINEERING
Use Case modelling
Figure 1: Use Case Diagram for the Coles organization
Source: (created by author)

5
SOFTWARE ENGINEERING
Sequence Diagram
Figure 2: Sequence Diagram for the Coles organization
Source: (created by author)

6
SOFTWARE ENGINEERING
Data Flow Diagram
Figure 3: Data Flow Diagram for the Coles organization
Source: (created by author)
Data Dictionary
Customer
Attribute Datatype Size NULL/NOT
NULL
Key
CIN Short text 10 NOT NULL Primary Key
Name Short text 10 NOT NULL
Address Long Text 255 NOT NULL

7
SOFTWARE ENGINEERING
TelephoneNumbe
r
Number 10 NOT NULL
Scheme
Attribute Datatype Size NULL/NOT
NULL
Key
SchemeName Short text 10 NOT NULL Primary Key
Description Long Text 255 NOT NULL
Product
Attribute Datatype Size NULL/NOT
NULL
Key
ProductName Short text 10 NOT NULL Primary Key
Price Currency NOT NULL
Checkout Staff
Attribute Datatype Size NULL/NOT
NULL
Key
SID Short text 10 NOT NULL Primary Key
SName Short text 10 NOT NULL
STelephoneNumbe Short text 10 NOT NULL

8
SOFTWARE ENGINEERING
r
SAddress 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
ProductName 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
SchemeName Short text 10 NOT NULL Foreign Key
RegistrationDate Date NOT NULL

9
SOFTWARE ENGINEERING
ER diagram
Figure 4: Entity Relationship Diagram for the Coles organization
Source: (created by author)

10
SOFTWARE ENGINEERING
Bibliography
[1] Holt, V., Ramage, M., Kear, K. and Heap, N. The usage of best practices and procedures in
the database community. Information Systems, 49, pp.163-181. , 2015.
[2] Schnoes, M., Voß, C. and Nicke, E. Design optimization of a multi-stage axial compressor
using throughflow and a database of optimal airfoils. Journal of the Global Power and Propulsion
Society, 2, pp.516-528. , 2018.
[3] Shen, N. Design of Online Teaching Effect Test System of English Pronunciation Based on
Web Database. Kuram ve Uygulamada Egitim Bilimleri, 18(5), pp.1792-1800. , 2018.
[4] Wu, F. Study on Composition and Development of the Database Management System. ,
2016.