Software Engineering

Running head: SOFTWARE ENGINEERING
Software Engineering
Name of the Student
Name of the University
Author’s note:

SOFTWARE ENGINEERING1
Table of Contents
Functional Requirements:................................................................................................................2
Non-Functional System:..................................................................................................................4
Context Diagram:.............................................................................................................................5
Level 1 DFD:...................................................................................................................................6
Level 2 DFD:...................................................................................................................................7
Data Dictionary:...............................................................................................................................7
Gantt Chart:.....................................................................................................................................9
Verification and Validation:..........................................................................................................13
Verification Methods:................................................................................................................13
Validation Methods:..................................................................................................................14
Bibliography:.................................................................................................................................15

SOFTWARE ENGINEERING2
Functional Requirements:
Data Storage: The system needs to save the information of the customer to a safe
location. The system can later retrieve these data from that location to conduct various processes.
The system will also handle stocks and purchase. Therefore, the data related to these processes
needs to be stored. The system requires a technology that can store, allow retrieving and
processing the recorded data efficiently. This data storage will be directly connected to the
system server. The data storage devices will not be responsible for only storing the data but also
checking the integrity of the data.
Authentication: The authentication method refers to the technique of validating the user
credentials. These user credentials are user name and user id. The system will identify whether
the user is a customer, staff or management using this method. The authentication method also
prevents unregistered users from accessing the system. Various systems uses authentication
using various methods. The proposed system at super market does not allow the customer to
authenticate. However, the staff will use the Customer Identification Number to authenticate the
user account. This will allow the organization to have complete control over the system
activities.
Authorization: Authorization comes into the big picture when authentication is
successfully completed and the system has allowed the user to access it. However, the proposed
system will have many levels of users from customer to manager. Each of this user group will
have different functionality to use and information to access. The system will make sure that
information will be accessed by only authorized users. This is implemented using the
authorization method into the core of the system. This way system makes sure that manager can

SOFTWARE ENGINEERING3
have overall control over the system. This method allow to implement user hierarchy in the
system.
Creating FlyBus Card: The customer will have a FlyBus card which will store every
detail of him/her. This card will be generated after the registration of the customer is done. In
order to register into the system, the customer will provide name, address, and telephone number
to the staff. During this registration, the system will enroll the customer into the scheme. The
system will auto generate the Customer Identification Number for each customer. This Customer
Identification Number will be different for each customer. Each time the customer purchase
something, the FlyBus Card has to be brought to the store.
Product Purchase: The system will allow the customer to purchase product from the
store. In contrast to the online purchase, the customer does not select all the products and pay
himself using the login credentials. In case of online purchase, the customer select the virtual
representation of the products and later receives the physical product. The proposed system
cannot track the purchase of the customer until it is not recorded by the staff into the system.
There is no virtual cart option in this store. The system will also calculate the total purchase
made by each customer and select the winners of the scheme.
Payment Handling: The system needs a payment handling sub-system that can accept
payment from the customers. The payment can be done using hard cash and cards. In case the
payment is done using cash, the staff will enter the quantity of the notes and coins provided. In
case the card is used, then the system will store the card number, card holder name, bank name
and few more details regarding payment. Each payment will be done against a single purchase.
The system does not accept payments in installment.