MN507: Software Engineering Report - System Requirements Analysis

This software engineering report analyzes the system requirements for the Coles organization. It begins by outlining the functional requirements, such as customer and store registration, scheme details, and purchase reporting, including the top spenders and customers spending over $1000 annually. Non-functional requirements like 24x7 availability, reliability, scalability, usability, maintainability, and recoverability are also detailed. The report utilizes Use Case modeling, Sequence Diagrams, and Data Flow Diagrams to illustrate system processes. Data dictionaries for customer, product, checkout staff, purchase, and registration attributes are provided. Finally, an Entity Relationship (ER) diagram represents the database structure, and a comprehensive bibliography of relevant software engineering resources is included.

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.........................................................................................................................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 Coles organization are provided below:
 The system should be able to provide the detail of the customers and the store the
registration details in the system. In addition to this, the details of the scheme for which
the customers are being enrolled into are stored in the system as per the scheme details.
 The customers are identified by their CIN and the entire details of the customers are
referred with this CIN.
 Additionally, the details of the checkout staffs are also being stored in the system. StaffID
would be used for the staffs to indicate or to refer to the entire details of the staffs in the
system.
 In addition to this, the details of the spending made by the customers would be published
as a report by the system for customers. The top three customers spending the most in the
purchases are provided to the staffs from the system. The system should also provide the
details of the customers spending more than $1000 in the year.
Non-functional requirements
The non-functional requirements of the system to be developed for the Coles organization
is are described below:
 The system that is to be developed for the organization should be available for 24x7
services. As the company is into retails and hence, the system should be made available
to the customers of the organization for maximum benefits of the company.
 The system which is developed must be reliable enough to provide the users with the
required data and data provided should be correct. The system should not be halting

3
SOFTWARE ENGINEERING
during the business procedures of the organization. In addition to this, the system is to be
trusted to provide the users with the right functionality with the correct processes for the
system.
 The system should be scalable as the Coles organization is a large organization and the
expansion of the organization would be mean that data of the organization would be
expanding to a great extent and hence, the scalability features of the system would be
helpful for them to increase the amount of data and other features in the system at any
point of time.
 The usability of the system should be implemented efficiently and the users of the system
should be able to perform the activities in the system efficiently. The navigation features
and the detailed reports generated in the system should be feasible enough and the overall
look of the interface of the system should be appealing to the customers.
 The maintenance of the system should be feasible enough and the cost and resources
required for the should be very minimal and the organization should not require any
excessive planning and allocation for the development of the system. Hence, the
maintainability of the system should be efficient.
 The recoverability feature of the system developed for the Coles organization is very
essential as the data stored in the system are both confidential and the important. Hence,
the data should not be lost or data should not be stolen from the system in any scenario.

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

7
SOFTWARE ENGINEERING
CIN Short text 10 NOT NULL Primary Key
Name Short text 10 NOT NULL
Address Long Text 255 NOT NULL
TelephoneNumbe
r
Number 10 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
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 Key

8
SOFTWARE ENGINEERING
NULL
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
StaffID Short text 10 NOT NULL Foreign Key
SchemeName Short text 10 NOT NULL
Description Long text 255 NOT NULL
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] Dennis, A., Wixom, B.H. and Roth, R.M. Systems analysis and design. John wiley & sons. ,
2018.
[2] Dević, S. and Luković, I. Development of a Database for the Common Information Model of
Power Grids. Information Technology and Control, 46(3), pp.319-332. , 2017.
[3] Tsui, F.F., Karam, O. and Bernal, B., 2016. Essentials of software engineering. Jones &
Bartlett Learning.
[4] Rajlich, V., 2016. Software engineering: the current practice. Chapman and Hall/CRC.
[5] Leach, R.J., 2018. Introduction to software engineering. Chapman and Hall/CRC.