In the proposed information system for the pizza shop the stake holders will be as follows,
The owner of the restaurant or the sponsor of the project to develop the information system. The owner is responsible for the creation of the environment so that the information system development project can be completed in time and budget. Other stakeholders in this information system development project.
Staffs at the shop (Such as the managers and the other staffs at the shop and its branches).
The customers of the shop;
Local authorities and the government.
Creditors for the company.
Suppliers of the company.
Competitors in the market.
System Requirements
Functional Requirements
- Enable the customer to view the products menu, create an account, login to the system and place an order.
- Pickup or delivery Service both provided
- Display the food items ordered, the individual food item prices and the payment amount calculated.
- Prompt customer to review and confirm the meal order.
- Visual confirmation of the order place
- Provision of online tracking the order while delivery or making an order.
- Encouraging Cash payment on delivery or pickup
- Expanding more payment options such as online, efptos, paypal.
- Promotional vouchers, special offers and discounts provided to build up sales
- Enable the Owner/manager to view, create, edit and delete food category and descriptions
- allow confirmation of pending orders.
- allow generation of sales report for the orders made.
- allow the Owner/manager to update additional information (description, photo, ingredients, offers, discounts etc.) for a given food item.
- allow the Owner/manager to update price for a given food item when required.
Non Functional Requirements
- Performance- Sufficient network bandwidth, quick response
- Backup and data recovery- provision for data backup, past sales records, order history, customer feedbacks
- Maintainability- easy to maintain
- Usability by target customers feedback and demands
- Expandability - upgradable system with more features
- Safety- safe user interface, encrypted if required
Use case stories
The customer log in to the online portal of the pizza shop. If the user is not registered then the user have to register by providing credentials. After this the user will be able to see the menu on the site and can select the pizza they want to have. In the next step, the user will proceed to check for the bill to know the total amount to pay. After this they will check for any offers available to them introduced by the shop (Kurniawan, Harefa and Sujarwo 2014 ). If available they will utilize the offer to reduce the payment amount. Now the system administrator will notify the nearest shop and the shop will deliver the product to the customer.
Another use case related to completion of the payment process. After the pizza is delivered at the clients address or the order is placed at the shop, then the information system will generate the bill that needs to be paid. If there is any promotional offer going on at that time, the users and the accountant will apply the offer which will reduce the total amount payable by the customer (Solomencevs and Osis 2015). At the end of the payment by the customer it will generate a receipt for the customer and will record the sales in the database.
Brief descriptions of the use cases
In the first use case there are three actor’s customer, system administrator and the delivery boy. The customer will book pizza selecting from the menu provided. After this the administrator will notify the nearest shop to deliver the pizza. The delivery boy of the shop will send the product to the customer and receive the payment.
In the second use case the payment done by the customer is processed. In this use case both the payments done by cards or online method are processed and described. The main actors are the customer and the accountant of the shop.
Assumptions made
The information about the customers like their ages, preferences for pizzas, frequency of their visit to the website (for online ordering system) and to the physical shop.
The clients who are placing orders will pay for the food using the credit or debit cards therefore, the POS (Point Of Sale) system used by the delivery boy must be integrated with the central information system.
The online ordering system will updated frequently so that the new products will be available to the customers and the some items that are not popular enough are eliminated from the system periodically.
The availability of the pizza is dependent on the suppliers, therefore the owner must check the flow of materials for the shops and update the menu on the site and in the information system frequently.
The client who orders online for the pizza should be the same person who have an account in the information system of the pizza shop.
References
Kurniawan, A., Harefa, B.B. and Sujarwo, S., 2014. Unified modeling language tools collaboration for use case, class and activity diagram implemented with HTML 5 and javascript framework. Journal of Computer Science, 10(8), p.1440.
Seidl, M., Scholz, M., Huemer, C. and Kappel, G., 2015. The Use Case Diagram. In [email protected] Classroom (pp. 23-47). Springer International Publishing.
Singh, A. and Sharma, E.S., 2014. Functional Test Cases Generation Based on Automated Generated Use Case Diagram. International Journal of Innovative Research in Advanced Engineering (IJIRAE), (8).
Solomencevs, A. and Osis, J., 2015, April. The algorithm for getting a UML class diagram from Topological Functioning Model. In Evaluation of Novel Approaches to Software Engineering (ENASE), 2015 International Conference on (pp. 341-351). IEEE.
