MN507 Software Engineering Database Design Project

Desklib provides solved assignments and past papers to help students succeed.

MN507 OVERVIEW OF SOFTWARE
ENGINEERING

Contents
Introduction...........................................................................................................................................3
Functional Requirements of the case study are:...................................................................................4
Non- Functional Requirements of the real life scenarios are:...............................................................4
Use Case diagram..................................................................................................................................5
Sequences diagram...............................................................................................................................6
DFD model.............................................................................................................................................6
Data dictionary of DFD..........................................................................................................................7
ERD:.....................................................................................................................................................10
MS Access Database prototype...........................................................................................................11
Conclusion...........................................................................................................................................12
Table of figures
Figure 1: Use Case Diagram...................................................................................................................4
Figure 2: Sequence diagram..................................................................................................................6
Figure 3: DFD model..............................................................................................................................7
Figure 4: Ms Access.............................................................................................................................11
Tables of table:
Table 1: Usecase Table..........................................................................................................................5
Table 2: Admin.......................................................................................................................................7
Table 3: System Table..........................................................................................................................10

Introduction
The report consists of the database design using Ms Access and also the use case diagram in which
the supermarket of the customer will have profits and the awards can be rewarded to the
customers. There is about the DFD model which will let the user know about the data flow of the
case study.

Functional Requirements of the case study are:
1. Customer should be able to login into the system properly.
2. Customer Id will be generated by the system automatically.
3. Record of the customer purchase should be correct.
4. The gift will be awarded to the customers who have purchased the products more than the $1000.
Non- Functional Requirements of real life scenarios are:
1. The cost of the system will be nominal.
2. The efficiency of the system will be good.
3. The products which are purchased from the supermarket are reliable.
4. The delivery management of the supermarket will be good and provides proper security [1].
Figure 1: Use Case Diagram

Use Case diagram
Use case diagram is the easiest way of them represent the user interaction which helps to show the
relationship of the attribute and entity. This helps to have the goals of the system which have the
user interactions. This has the basic flow of event of use case. This includes the component such as:
Actor: This helps the user to show the interaction with the system with the application and have the
external objects to consume and produce data.
System: There is a specific sequence which has the interaction between the system and actors.
Goals: The result of th4e successful use case has described the variant and activities of goals [1].
Table 1: Usecase Table
Use Case Description
Admin The admin will be the person who will see the
system records and all. The admin used to
register him into the system so that he/she can
see the record for the system who are
registering into the supermarket. So that they
can see their loyalty of the customer.
Customer The customers who are registering them into the
system will get the customer ID which will be the
primary key for the unique identification of the
row. The customer who will purchase the item
will get the points and when their purchase is
$1000 then they will get the gold coin and the
first three customers who have more money on
the products of supermarket will get the surprise
award and Here the customer will get the CIN
which will be reset after when the year will finish
[1].
Staff The staff will check out the products which are
purchased by the customers and then the
customer will have all the records on the

database of the system.
Sequences diagram
This diagram helps to take the situation and then proceed. It shows the sequence of the diagram
where the customer will ask the system for registration with the details of the customers and then
there will be CIN generated by the system to have the unique identification.
Figure 2: Sequence diagram
DFD model
This stands for the data flow diagram which is used for the representation of data flow that how the
flow will be going off the data of the business system. This involves the process of the system which
is transferred into the data for the report generation and file storage. This usually used for the
logical information, constructions requirement, simplicity notation, automated requirements of the
system.

Figure 3: DFD model
Data dictionary of DFD
Table 2: Admin
Attributes Data type Length Description
Admin_Id Integer 10 The Id of the admin will
be in the integer type.
Admin_Name Varchar 45 The name will be in
varchar type of the
admin
Admin_cont Integer 10 The mobile number of
the admin who can
contact.
Admin_Email Varchar 45 The Email of the admin
will be in varchar and
this will help to send the
notification to the

customer who will
receive the awards or
coins.
Cust_ID Integer 10 The foreign key for the
reference for the table.
Table 3: Customer Table
Attributes Data type Length Description
Csut_Id Integer 10 The Id of the customer
will be in the integer
type which will be the
primary key.
Cust_Name Varchar 45 The name will be in the
varchar type of the
customer [2].
Cust_phone Integer 10 The mobile number of
the customer who can
contact.
Cust_Address Varchar 45 The customer address is
necessary because if the
gift will be rewarded to
them then the gift will
be sent to the customer
who will receive the
awards or coins.
Table 4: Staff Table
Attributes Data type Length Description
Staff_Id Integer 10 The Id of the staff will
be in the integer type
which will be the

primary key.
Staff_Name Varchar 45 The name will be in
varchar type of staff.
Staff_mobile Integer 10 The mobile number of
the staff who can
contact.
Cust_ID Integer 10 The foreign key for the
reference for the table
[2].
Staff_Email Varchar 45 The Email of the staff
will be in varchar and
this will help to send the
notification to the
customer who will
receive the awards or
coins.

Table 3: System Table
Attributes Data type Length Description
System_Id Integer 10 The Id of the staff will
be in the integer type
which will be the
primary key.
Cust_ID Integer 10 The foreign key for the
reference for the table.
Admin_cust Integer 10 The foreign key for the
reference for the table.
ERD:
This stands for the entity-relationship diagram which helps to understand the relationship between
the tables. This has different symbols, connectors, etc. this consist of mainly entity and attributes
and also helps to show the relationship between them [3].

MS Access Database prototype
Figure 4: Ms Access

Conclusion
The report concludes that the user will understand more about the database using MS- access and
then the user will able to understand the flow of the diagram by studying the DFD of the database
design. There is use case diagram present which will help the user to have the interaction between
the entity and attributes. There is sequence diagram made which will explain the sequence of the
interaction All the diagram are made using draw.io which is easy to use and explain.