Proposed Online Information System For G’Day Mate Retail Company
Purpose
The case that is under study is G’Day Mate Retail Company. This is a company which was established in the year 1999 and this is famous for selling garments for both men and women. Firstly, this company had only eight retail stores in New South Wales. But with expanding the business and quality of product, the business started getting popularity and people from outside NSW were also interested in buying products from G’Day Mate. The organization now wants to expand its business outside NSW and already two retail shops outside NSW were under construction. The company wants to make its business process online so that people all over the world can buy products from them.
The purpose of the report is to propose an online system for G’Day Mate Retail Company. The system that is proposed will allow the people to browse all the items from outside NSW as well as in NSW. The purpose is to make the business system more expanding.
The current system that runs in G’Day Mate Retail Company is that all processes are done manually in the retail stores. With the expansion of the market, the system is getting complicated. The existing system is dealt manually and it is very difficult to maintain all the retail store. New retails that are opening outside NSW cannot be seen manually by the owner of G’Day Mate Retail Company. So, automatic information system is to be proposed for the company.
The new proposed information system will help the people to browse all the items from all over the world. The people can sort the products in terms of gender, shape, type, and color of the items. The items that the customer likes can add those items in the wish list or they can directly add those items in the cart. The customer can select two option of delivery. They can choose home delivery option or they can choose pick up option themselves. There will be an option for providing customer feedback for the product they buy. The customer can also select an option for the desired delivery of shipping from all the options that comes on the screen. The proposed information system also allows the customer to track the item that they have purchased during shipping process.
The data is handled manually in the system. When an item gets sold, the item is noted in the stock book from the list that is already mentioned in the stock book. The inventory is managed by an inventory book which keeps the details of the items that are available in the store. Two person keeps look on the stock. When items are brought to the shop, items are counted and note down in the stock book. The quantity of item bought, the color, size and type of items are noted in the book. The items left in the inventory is also noted and manufacturing of products are done accordingly.
Many employees are appointed to manage the stores at different location. When a particular item or particular size of the item is not available in the store, then it is noted down and according it is bought from the store.
Existing (Manual) System
There is another team who looks at the management of retail price of the products that are available in the store. The amount of discount that can be given on a particular item is done by this group of people and all the discounts given are noted in the management book along with profit before discount and profit after discount.
After the billing is made, the items that are being billed are noted down in the sales book. The sales book and the inventory book are matched at the end of every month. This processes handling manually becomes very much difficult as there is not proper system in the stores of G’Day Mate Retail Company.
The new system that has been decided to implement is an automatic system where all the items will be managed with an application software that will be used in all the stores of G’Day Mate Retail Company. As the expansion is the business is to be done globally, all the stores are connected to each other using this information system. Different stores have different inventories from where the items are brought to the store and the quantity as well as other details of the items are noted in the computer system. An application is used for entering all the details about the product, the quantity available in that store and the discount price of the items is noted. All these details are entered by logging in as admin in that app. All stores have different inventory and quantity of items may differ in different stores of G’Day Mate Retail Company. If a product is not available in one store, the customer can order the same product from another store if delivery is possible from that store.
The new system that is built will allow all the process to be done automatically with the help of application that is proposed to be implemented in G’Day Mate Retail Company. This application that is made for this company will automatically calculate the profit amount or the loss amount faced by that company. In the new p[proposed information system, there is no need to maintain a store book or a billing book as all the details of the products are entered into the system and the admins who have access to the application can view the data automatically. For the existing handling all the data manually is very difficult. There is no need to maintain many similar management books for handling the data in the store.
The actors who are involved in this system is the customer, and the admins who maintain the database of the system.
Table Name |
Field Name |
Data Type |
Field Size |
Description |
customer |
cust_id |
Primary Key |
||
cust_fname |
||||
cust_lname |
||||
cust_daddress |
||||
cust_landmark |
||||
cust_country |
||||
cust_pin |
||||
cust_email |
||||
cust_phone |
||||
rating_id |
Foreign Key |
|||
rating |
rating_id |
Primary Key |
||
date_of_rating |
||||
rating_value |
||||
rating_time |
||||
orders |
order_id |
Primary Key |
||
date_of_shipping |
||||
discount |
||||
expected_delivery |
||||
description |
||||
cust_id |
Foreign Key |
|||
product_id |
Foreign Key |
|||
review |
review_id |
Primary Key |
||
prdct_id |
||||
description |
||||
cust_id |
Foreign Key |
|||
product |
product_id |
Primary Key |
||
prdct_name |
||||
prdct_quantity |
||||
prdct_price |
Foreign Key |
|||
inventory |
inventory_id |
Primary Key |
||
date_added |
||||
cost_per_item |
||||
item_available |
||||
admin |
admin_id |
Primary Key |
||
admin_fname |
||||
admin_lname |
||||
admin_email |
||||
admin_phone |
||||
inventry_id |
Foreign Key |
Main menu: The main menu will have sign up button and a login button that will take the admin or the customer to their respective pages. If the user clicks on the sign up page, a sign up page will open that will have the details credentials of the user that will be stored in the database. The admin will not have any signup process.
After login page the, the next page will be directed to product page from where the customer can select their respective products. The products can be filtered by the customer with their choice. They can select their products according to their choice. They can also select the types of product on their will.
From the admin end, the admin can add products or delete products. They can also modify the products when needed. The forms that admin will add or delete the products will have the product id that will generate automatic number for the product id and the product name and the product type is also entered by the admin.
The form where the admin will alter the product details consists of all the fields similar to that of add or delete page, and will have a change or alter button to modify the details.
List and explain various managerial reports (and queries) that your new IS is able to produce. Managerial reports are very important as they provide input which inform managers’ decisions. The more useful, and innovative your reports are, the higher your mark for this assessment (also the more the reports, the better). You can use the following sub-headings, if you want, to explain your reports in a more structured way:
The management gives an opportunity for the customers to select their delivery dates from the option that are given to them. This is an attractive option for the customers as they can get the delivery as expected.
There can also be a payment option for the customer which will state that the customer can pay later after completing the return period of the product. This will help the business to attract more customers.
Task Name |
Duration |
Start |
Finish |
Action Plan for Learning Process |
76 days |
Sat 7/07/18 |
Thu 27/09/18 |
Research Planning |
12 days |
Sat 7/07/18 |
Thu 19/07/18 |
Formation of Research Team |
2 days |
Sat 7/07/18 |
Mon 9/07/18 |
Analysis of Research Requirement |
1 day |
Tue 10/07/18 |
Tue 10/07/18 |
Identification of Research Questions |
2 days |
Wed 11/07/18 |
Thu 12/07/18 |
Identify Scope of Research |
2 days |
Fri 13/07/18 |
Sat 14/07/18 |
Estimate Research Timeline |
1 day |
Sun 15/07/18 |
Sun 15/07/18 |
Allocation of Resources and Time for the Research |
2 days |
Mon 16/07/18 |
Tue 17/07/18 |
Initiation of Research |
2 days |
Wed 18/07/18 |
Thu 19/07/18 |
Research Development |
16 days |
Fri 20/07/18 |
Sat 4/08/18 |
Determination of Research Problems |
3 days |
Fri 20/07/18 |
Sun 22/07/18 |
Access to Necessary Media |
1 day |
Mon 23/07/18 |
Mon 23/07/18 |
Access to Online Library |
2 days |
Tue 24/07/18 |
Wed 25/07/18 |
Selection of Literary Sources |
2 days |
Thu 26/07/18 |
Fri 27/07/18 |
Literature Review |
2 days |
Sat 28/07/18 |
Sun 29/07/18 |
Collection of Necessary Data |
4 days |
Mon 30/07/18 |
Thu 2/08/18 |
Collection of Secondary Data |
2 days |
Fri 3/08/18 |
Sat 4/08/18 |
Data Analysis |
5 days |
Sun 5/08/18 |
Thu 9/08/18 |
Analysis of Primary Data |
3 days |
Sun 5/08/18 |
Tue 7/08/18 |
Analysis of Secondary Data |
2 days |
Wed 8/08/18 |
Thu 9/08/18 |
Application Development |
15 days |
Fri 10/08/18 |
Fri 24/08/18 |
Requirement Gathering |
2 days |
Fri 10/08/18 |
Sat 11/08/18 |
Requirement Analysis |
3 days |
Sun 12/08/18 |
Tue 14/08/18 |
Designing |
5 days |
Wed 15/08/18 |
Sun 19/08/18 |
Testing |
3 days |
Mon 20/08/18 |
Wed 22/08/18 |
Evaluation |
2 days |
Thu 23/08/18 |
Fri 24/08/18 |
Research Evaluation |
16 days |
Sat 25/08/18 |
Tue 11/09/18 |
Evaluation of Data |
4 days |
Sat 25/08/18 |
Tue 28/08/18 |
Reflection on Research Undertaken |
5 days |
Wed 29/08/18 |
Mon 3/09/18 |
Documentation of Learning Outcomes |
4 days |
Tue 4/09/18 |
Fri 7/09/18 |
Issues Identification and Future Planning |
3 days |
Sun 9/09/18 |
Tue 11/09/18 |
Research Closure |
12 days |
Wed 12/09/18 |
Thu 27/09/18 |
Complete All Activities in Research |
2 days |
Wed 12/09/18 |
Thu 13/09/18 |
Documentation of Entire Research |
6 days |
Fri 14/09/18 |
Fri 21/09/18 |
Validation of the Research and Learning |
2 days |
Mon 24/09/18 |
Tue 25/09/18 |
Team Sign Off |
2 days |
Wed 26/09/18 |
Thu 27/09/18 |