MN507 Overview of Software Engineering Assignment Sample

• Subject Code : MN507
• University : Melbourne Institute of Technology My Assignment Services is not sponsored or endorsed by this college or university.
• Subject Name : IT Computer Science

Woolworths Rewards

Table of Contents

Functional Requirements.

Non-Functional Requirements.

Use Case Model

Class Diagram..

Entity Relationship Diagram..

Data Dictionary.

Functional Requirements

The main functional requirements for the system are as following:

Customer Form – When a customer visits the store, a customer form will be filled by the admin staff to make the boll. A unique customer no will be issued to the customer and whenever the same customer revisits the store the same customer no will be used in every transaction.

Product Details – All the details of the product must be store in the system. When a new product is launched, a product no will be generated which is a unique number.

Billing – All the billing details will be saved in the system to generate an automated bill to the customer.

Billing Details – All the product details that are purchased by the customer will be saved in the billing details section with the quantity.

Maximum Purchase – As the purchased details of the customer are saved into the system, the maximum purchase made by the customer can be retrieved in the report section.

Reward – When a customer is rewarded for maximum purchase, the details must be saved into the system.

Non-Functional Requirements

Usability – The system must be easy to use for beginners. No special training must be required for users.

Reliability – As the system automates all business processes of the store, human errors will get eliminated. Hence, the data retrieved from the system is reliable and accurate.

Scalability – With the increase in business, no. of transactions will increase. Hence, the developed system must be able to save a large data set.

Security – All security and privacy acts will be fulfilled. Only authorized users will be given access to the system. Also, additional security measures will be implemented.

Accessibility – The system must be available at all times without any interruption. A proper backup strategy will be developed for avoiding any data loss.

Use Case Model

Figure 1: Use Case Diagram

According to the given scenario, there are four actors – receptionist, customer, checkout staff, and management. The process starts when a customer comes to the store. When he collects the items, he reaches the reception or billing counter where all his details will be saved into the system. A unique CIN number will be generated. A bill will be generated by the receptionist. The customer then goes to checkout staff and the staff notes his CIN number to record all purchase details. At the year-end, the management checks all details of purchase history and take out the customer name who has purchased maximum and then reward him.

Class Diagram

Figure 2: Class Diagram

There are five classes in this scenario. The classes' names are Customer, Products, Billing, BillingDetails, CustomerRewards, LoyaltyRewards. All these classes will add their respective data to the system. Customers are to add and modify the customer details by generating a unique CIN number. Similarly, Products will save all product details. The bill details of the customer will be saved into the billing entity whereas all product details that are billed in a particular bill will be saved in BillingDetails. CustLoyalty is for recording all customer purchase details into the system.

Entity Relationship Diagram

Figure 3: Entity Relationship Diagram

In the above ERD, we have considered six entities – customer, product, Billing, BillingDetails, PurchaseRecord, and CustomerRewards. All the customer details will be saved in the Customer table with a unique CIN number that is auto-generated by the system. The products are the master table for saving all product details. When a customer picks some items, he visits the billing counter where the receptionist makes his bill. The product details of a bill are saved in BillingDetails. After bill generation, the customer goes to the checkout counter where check out staff records all his purchasing details based on CIN number. All details will be saved in the PurchaseRecord entity. When a customer is rewarded based on purchase history, the reward details will be saved in the CustomerRewards entity.

Data Dictionary

Remember, at the center of any academic work, lies clarity and evidence. Should you need further assistance, do look up to our Computer Science Assignment Help