This document describes research into users' perceptions of an e-menu application for a Thai restaurant in the UK. 12 staff members participated in interviews about the prototype e-menu system demonstrated on an iPad. Key findings included:
1. Staff saw benefits like convenience for ordering and checking orders, as well as improving customer service. However, concerns around cost and issues for older users were also identified.
2. Features like detailed food descriptions and images, ordering extra items, and checking order status were seen as important for an e-menu app.
3. While the prototype was well received, limitations around a small sample size and technical issues need addressing in further research. The findings can help inform developing a real
This document describes research into users' perceptions of an e-menu application for a Thai restaurant in the UK. 12 staff members, representing 67% of total staff, participated in interviews. The presentation and demonstration of the e-menu system were necessary due to most staff's lack of background knowledge. Users were familiar with Apple devices like iPad and iPhone. Key findings included that e-menus provide convenience for customers and staff, improve customer service, and reduce human errors. However, e-menus may be an issue for older customers and cause technical problems. Features like dish details, ordering functionality, and service requests were identified as important.
The document describes research into users' perceptions of an e-menu application for a Thai restaurant in the UK. 10 staff members comprising managers, wait staff, and chefs were interviewed after demonstrating an e-menu prototype on an iPad. The primary findings were that users saw benefits in convenience but also issues in cost. Specifically, users felt an e-menu would conveniently allow customers to view detailed food information and order extra items, while staff could easily update the menu. However, some felt the technology may be too expensive. Overall, the research concluded the e-menu's convenient features should be considered in developing a real application.
The document provides an annotation of knowledge related to developing an e-menu system for a Thai restaurant. It discusses key aspects of the domain including e-menus for restaurants, restaurant service processes, software usability, development methodologies, and mobile app development. It analyzes different types of e-menu systems and identifies tablet e-menus as the most suitable option for the restaurant. It also diagrams the existing restaurant service process and how an e-menu could improve it by allowing direct ordering from tables.
Natural Language Processing: From Human-Robot Interaction to Alzheimer’s Dete...Jekaterina Novikova, PhD
The document discusses several topics related to natural language processing:
1. Spoken human-robot interaction, including hybrid chat-task dialogue and multimodal dialogue evaluation. Reinforcement learning was used to optimize task completion and engagement.
2. Evaluation of natural language systems, including problems with existing automatic metrics and improving human evaluation methods. Referenceless quality estimation was also discussed.
3. Alzheimer's detection from language, including the effect of heterogeneous data, semi-supervised multimodal learning, and early prediction of Alzheimer's using analysis of spontaneous speech from famous people.
This document outlines a research project to develop a prototype electronic menu (e-menu) application for casual dining restaurants. The objectives are to analyze business requirements, design system documents and an e-menu prototype, and gather user perceptions of the prototype. The research framework involves key issues analysis, design documents, a software development process using RAD and prototyping, and direct observation. The outcomes will include recommendations for e-menu application development.
This document contains a list of potential artefacts and outcomes from a project to develop an electronic menu (e-menu) application for restaurants. It includes system analysis and design documents, a prototype e-menu application for iPad and website, videos demonstrating the e-menu features, and documents collecting user feedback on the prototype. The format of the artefacts includes documents, diagrams, applications, videos and user research findings.
This document provides a recipe for creating a blended learning program. It discusses mixing together various ingredients like learner profiles, performance outcomes, learning environments, and feasibility. It recommends blending strategies, modes, and tools like e-learning modules, online forums, and face-to-face workshops. The document also covers serving the blended program through good implementation plans, coordinating activities, clear communications, and engaging stakeholders. The goal is to provide a supreme blended learning experience that sticks to budget requirements.
This document describes research into users' perceptions of an e-menu application for a Thai restaurant in the UK. 12 staff members, representing 67% of total staff, participated in interviews. The presentation and demonstration of the e-menu system were necessary due to most staff's lack of background knowledge. Users were familiar with Apple devices like iPad and iPhone. Key findings included that e-menus provide convenience for customers and staff, improve customer service, and reduce human errors. However, e-menus may be an issue for older customers and cause technical problems. Features like dish details, ordering functionality, and service requests were identified as important.
The document describes research into users' perceptions of an e-menu application for a Thai restaurant in the UK. 10 staff members comprising managers, wait staff, and chefs were interviewed after demonstrating an e-menu prototype on an iPad. The primary findings were that users saw benefits in convenience but also issues in cost. Specifically, users felt an e-menu would conveniently allow customers to view detailed food information and order extra items, while staff could easily update the menu. However, some felt the technology may be too expensive. Overall, the research concluded the e-menu's convenient features should be considered in developing a real application.
The document provides an annotation of knowledge related to developing an e-menu system for a Thai restaurant. It discusses key aspects of the domain including e-menus for restaurants, restaurant service processes, software usability, development methodologies, and mobile app development. It analyzes different types of e-menu systems and identifies tablet e-menus as the most suitable option for the restaurant. It also diagrams the existing restaurant service process and how an e-menu could improve it by allowing direct ordering from tables.
Natural Language Processing: From Human-Robot Interaction to Alzheimer’s Dete...Jekaterina Novikova, PhD
The document discusses several topics related to natural language processing:
1. Spoken human-robot interaction, including hybrid chat-task dialogue and multimodal dialogue evaluation. Reinforcement learning was used to optimize task completion and engagement.
2. Evaluation of natural language systems, including problems with existing automatic metrics and improving human evaluation methods. Referenceless quality estimation was also discussed.
3. Alzheimer's detection from language, including the effect of heterogeneous data, semi-supervised multimodal learning, and early prediction of Alzheimer's using analysis of spontaneous speech from famous people.
This document outlines a research project to develop a prototype electronic menu (e-menu) application for casual dining restaurants. The objectives are to analyze business requirements, design system documents and an e-menu prototype, and gather user perceptions of the prototype. The research framework involves key issues analysis, design documents, a software development process using RAD and prototyping, and direct observation. The outcomes will include recommendations for e-menu application development.
This document contains a list of potential artefacts and outcomes from a project to develop an electronic menu (e-menu) application for restaurants. It includes system analysis and design documents, a prototype e-menu application for iPad and website, videos demonstrating the e-menu features, and documents collecting user feedback on the prototype. The format of the artefacts includes documents, diagrams, applications, videos and user research findings.
This document provides a recipe for creating a blended learning program. It discusses mixing together various ingredients like learner profiles, performance outcomes, learning environments, and feasibility. It recommends blending strategies, modes, and tools like e-learning modules, online forums, and face-to-face workshops. The document also covers serving the blended program through good implementation plans, coordinating activities, clear communications, and engaging stakeholders. The goal is to provide a supreme blended learning experience that sticks to budget requirements.
This document provides a recipe for creating a blended learning program. It discusses mixing together various ingredients like learner profiles, performance outcomes, learning environments, and feasibility. It recommends blending strategies, modes, and tools. Examples of blending include using e-learning modules as the main ingredient and supplementing with online forums, assessments, and face-to-face workshops. The document stresses implementing blended learning with clear communications, seamless activities for learners, and reviewing effectiveness.
This document lists various artifacts created as part of developing an e-menu application for restaurants, including requirements documents, design diagrams, prototypes, and presentation materials. It also includes outcomes like user perceptions of the prototype and recommendations for further development.
This document lists various artifacts created as outcomes of developing an e-menu for restaurants, including software requirements documents, UML diagrams, an e-menu application prototype for iPad and web services, presentation materials, and documents evaluating users' perceptions of the e-menu prototype and providing recommendations.
This document lists various artifacts created as outcomes of developing an e-menu system for restaurants, including software requirements documents, UML diagrams, workflow diagrams, the e-menu application prototype developed for iPad and web, presentation materials, and documents evaluating users' perceptions of the prototype and providing recommendations. It provides an overview of the system analysis, design, development, and testing process for the e-menu system.
This document lists various artifacts created as outcomes of developing an e-menu for restaurants, including software requirements documents, UML diagrams, an e-menu application prototype for iPad and web services, presentation materials, and documents evaluating users' perceptions of the e-menu prototype and providing recommendations.
This document provides a wrap around conclusion for a project developing an e-menu application for a Thai restaurant. It summarizes the key stages of research including reviewing relevant knowledge areas, designing a research framework and action plan, developing prototypes of the e-menu app, gathering user feedback, and identifying limitations and recommendations. The research contributed system design documents, e-menu prototypes, analysis of user perceptions, and recommendations to help produce a functional e-menu system meeting business needs.
Slide 4 - User Interface Design.pptx interface rather than its functionality ...DennisAnaafi1
interface rather than its functionality
•A poorly designed interface can cause a user to make catastrophic errors
•Poor user interface design is the reason why so many software systems are never used
This document discusses user experience (UX) and its key elements. UX aims to cover all aspects of a person's experience with a system, beyond usability alone. The UX design process involves research methods like questionnaires, interviews, and observation to understand user behavior. An interdisciplinary UX team is needed that may include designers, engineers, and researchers from fields like psychology and anthropology. The goal is to design innovative user interfaces based on insights from UX research.
This document describes AugMenu, an augmented reality ordering system for restaurants. It discusses the motivation for the project, related work in augmented reality interfaces and user studies, and the methodology used including user and environment analysis, task analysis, observation, interviews, evaluations, and technical specifications. The outcome will be a new augmented reality-based menu design and integrated ordering system.
This document provides an overview of the research and outcomes for developing an e-menu prototype for a Thai restaurant. [1] It reviews the research question, objectives, and framework, which focused on identifying key issues, requirements, and users' perceptions of the prototype. [2] It discusses the structure of the portfolio that will contain artifacts like system analysis documents, the prototype application, and presentations to demonstrate features. [3] The outcomes include analyzing requirements, developing the prototype, evaluating users' feedback, and recommending how to approach future e-menu development.
User testing is the most effective usability evaluation method. It involves observing representative users attempting typical tasks to identify usability issues. Only 5 users are typically needed to find the most critical problems. Multiple short tests with revisions between are better than one large study. Issues are best identified by directly observing what users do rather than just listening to what they say. Regular user testing throughout development prevents major issues that are costly to fix late.
Presentation to company division stakeholders about guidelines and best practices. The presentation was part of a series of presentations I made periodically on HCI and UX education and advocacy.
This document discusses the importance of user experience (UX) in designing software and websites. It notes that when assumptions are made without considering the user perspective, software often fails or is disliked by users. The document advocates for user-centered design which takes into account user needs, goals, tasks, environment and limitations to build products that are intuitive and address the real problems of users. Following a user-centered design process can lead to increased adoption, improved productivity, lower support costs and a return on investment.
Fixing the program my computer learned: End-user debugging of machine-learned...City University London
This document summarizes Dr. Simone Stumpf's research into enabling end users to debug machine-learned programs. It discusses how machine-learned programs work and the challenges end users face in debugging programs they can't see the source code of. It describes formative studies exploring different explanation approaches and the types of feedback users provide. It also covers integrating user feedback to change the machine's reasoning, identifying unpredictable user-provided features, and directions for future work.
http://fr.droidcon.com/2014/agenda/detail?title=Ingredients+of+Awesome+App
There are an increasing number of apps that come with great design nowadays, and most of the carefully crafted apps resonate with the Android users due to their great and consistent User Experience (UX) design. Many developers and designers try hard to create an app with great UX by largely referring to the Android Design Guideline, however, to make remarkable UX design is certainly more than that, and often they missed certain important items from their check list. If you want to check if your app(s) is heading the right direction to awesomeness, be sure to check out this ‘advanced’ check list in making awesome Android apps.
Speaker: Taylor Ling
I am very passionate about User Experience (UX), not so much on the ethnography part, but more on the User Interface execution that can directly influence UX and Usability, particularly on the mobile devices (Android always come first!).
I am currently the GDE for UX/Design, and enjoy going around the world to share my experience on UI/UX Design.
Currently crafting pixels at snappymob.com.
The document provides recommendations for developing an e-menu prototype for a Thai restaurant. It recommends following a RAD and prototyping approach, with direct observation throughout the development process. It outlines designing system analysis documents like use case diagrams, class diagrams, and ER diagrams to model requirements and design the database with relevant tables and columns. The final prototype would be developed on iPad using Objective-C and the backend on .NET, with feedback gathered during testing to further refine the system.
e-Questionnaire (HR Project at Central Electricity Board)ferane912nad
A student at the University of Mauritius is conducting research for their final year HR project on electronic Performance Management Systems (ePMS). They have developed a questionnaire to assess how CEB employees accept and adapt to the new ePMS, and how it has improved on traditional performance appraisal systems. The student is requesting participation by completing the 26 question survey, which should take 10-15 minutes. The survey contains questions on attitudes towards and use of ePMS, the impact on performance management, and demographic information. All responses will be kept confidential and used for academic purposes only.
The document discusses research into a prototype e-menu system for Thai restaurants, summarizing suggestions from interviews to improve the system's features, such as allowing ordering by quantity, adding customer comments, separating set menus, and making it easier to request the main course. The suggestions aim to address issues like usability, language support, and kitchen communication in order to better meet business needs and customer satisfaction. Overall, the research seeks to identify additional requirements and solutions to further develop the e-menu software.
This document provides a recipe for creating a blended learning program. It discusses mixing together various ingredients like learner profiles, performance outcomes, learning environments, and feasibility. It recommends blending strategies, modes, and tools. Examples of blending include using e-learning modules as the main ingredient and supplementing with online forums, assessments, and face-to-face workshops. The document stresses implementing blended learning with clear communications, seamless activities for learners, and reviewing effectiveness.
This document lists various artifacts created as part of developing an e-menu application for restaurants, including requirements documents, design diagrams, prototypes, and presentation materials. It also includes outcomes like user perceptions of the prototype and recommendations for further development.
This document lists various artifacts created as outcomes of developing an e-menu for restaurants, including software requirements documents, UML diagrams, an e-menu application prototype for iPad and web services, presentation materials, and documents evaluating users' perceptions of the e-menu prototype and providing recommendations.
This document lists various artifacts created as outcomes of developing an e-menu system for restaurants, including software requirements documents, UML diagrams, workflow diagrams, the e-menu application prototype developed for iPad and web, presentation materials, and documents evaluating users' perceptions of the prototype and providing recommendations. It provides an overview of the system analysis, design, development, and testing process for the e-menu system.
This document lists various artifacts created as outcomes of developing an e-menu for restaurants, including software requirements documents, UML diagrams, an e-menu application prototype for iPad and web services, presentation materials, and documents evaluating users' perceptions of the e-menu prototype and providing recommendations.
This document provides a wrap around conclusion for a project developing an e-menu application for a Thai restaurant. It summarizes the key stages of research including reviewing relevant knowledge areas, designing a research framework and action plan, developing prototypes of the e-menu app, gathering user feedback, and identifying limitations and recommendations. The research contributed system design documents, e-menu prototypes, analysis of user perceptions, and recommendations to help produce a functional e-menu system meeting business needs.
Slide 4 - User Interface Design.pptx interface rather than its functionality ...DennisAnaafi1
interface rather than its functionality
•A poorly designed interface can cause a user to make catastrophic errors
•Poor user interface design is the reason why so many software systems are never used
This document discusses user experience (UX) and its key elements. UX aims to cover all aspects of a person's experience with a system, beyond usability alone. The UX design process involves research methods like questionnaires, interviews, and observation to understand user behavior. An interdisciplinary UX team is needed that may include designers, engineers, and researchers from fields like psychology and anthropology. The goal is to design innovative user interfaces based on insights from UX research.
This document describes AugMenu, an augmented reality ordering system for restaurants. It discusses the motivation for the project, related work in augmented reality interfaces and user studies, and the methodology used including user and environment analysis, task analysis, observation, interviews, evaluations, and technical specifications. The outcome will be a new augmented reality-based menu design and integrated ordering system.
This document provides an overview of the research and outcomes for developing an e-menu prototype for a Thai restaurant. [1] It reviews the research question, objectives, and framework, which focused on identifying key issues, requirements, and users' perceptions of the prototype. [2] It discusses the structure of the portfolio that will contain artifacts like system analysis documents, the prototype application, and presentations to demonstrate features. [3] The outcomes include analyzing requirements, developing the prototype, evaluating users' feedback, and recommending how to approach future e-menu development.
User testing is the most effective usability evaluation method. It involves observing representative users attempting typical tasks to identify usability issues. Only 5 users are typically needed to find the most critical problems. Multiple short tests with revisions between are better than one large study. Issues are best identified by directly observing what users do rather than just listening to what they say. Regular user testing throughout development prevents major issues that are costly to fix late.
Presentation to company division stakeholders about guidelines and best practices. The presentation was part of a series of presentations I made periodically on HCI and UX education and advocacy.
This document discusses the importance of user experience (UX) in designing software and websites. It notes that when assumptions are made without considering the user perspective, software often fails or is disliked by users. The document advocates for user-centered design which takes into account user needs, goals, tasks, environment and limitations to build products that are intuitive and address the real problems of users. Following a user-centered design process can lead to increased adoption, improved productivity, lower support costs and a return on investment.
Fixing the program my computer learned: End-user debugging of machine-learned...City University London
This document summarizes Dr. Simone Stumpf's research into enabling end users to debug machine-learned programs. It discusses how machine-learned programs work and the challenges end users face in debugging programs they can't see the source code of. It describes formative studies exploring different explanation approaches and the types of feedback users provide. It also covers integrating user feedback to change the machine's reasoning, identifying unpredictable user-provided features, and directions for future work.
http://fr.droidcon.com/2014/agenda/detail?title=Ingredients+of+Awesome+App
There are an increasing number of apps that come with great design nowadays, and most of the carefully crafted apps resonate with the Android users due to their great and consistent User Experience (UX) design. Many developers and designers try hard to create an app with great UX by largely referring to the Android Design Guideline, however, to make remarkable UX design is certainly more than that, and often they missed certain important items from their check list. If you want to check if your app(s) is heading the right direction to awesomeness, be sure to check out this ‘advanced’ check list in making awesome Android apps.
Speaker: Taylor Ling
I am very passionate about User Experience (UX), not so much on the ethnography part, but more on the User Interface execution that can directly influence UX and Usability, particularly on the mobile devices (Android always come first!).
I am currently the GDE for UX/Design, and enjoy going around the world to share my experience on UI/UX Design.
Currently crafting pixels at snappymob.com.
The document provides recommendations for developing an e-menu prototype for a Thai restaurant. It recommends following a RAD and prototyping approach, with direct observation throughout the development process. It outlines designing system analysis documents like use case diagrams, class diagrams, and ER diagrams to model requirements and design the database with relevant tables and columns. The final prototype would be developed on iPad using Objective-C and the backend on .NET, with feedback gathered during testing to further refine the system.
e-Questionnaire (HR Project at Central Electricity Board)ferane912nad
A student at the University of Mauritius is conducting research for their final year HR project on electronic Performance Management Systems (ePMS). They have developed a questionnaire to assess how CEB employees accept and adapt to the new ePMS, and how it has improved on traditional performance appraisal systems. The student is requesting participation by completing the 26 question survey, which should take 10-15 minutes. The survey contains questions on attitudes towards and use of ePMS, the impact on performance management, and demographic information. All responses will be kept confidential and used for academic purposes only.
The document discusses research into a prototype e-menu system for Thai restaurants, summarizing suggestions from interviews to improve the system's features, such as allowing ordering by quantity, adding customer comments, separating set menus, and making it easier to request the main course. The suggestions aim to address issues like usability, language support, and kitchen communication in order to better meet business needs and customer satisfaction. Overall, the research seeks to identify additional requirements and solutions to further develop the e-menu software.
Restaurant e-menu on iPad, Rapid Application Development (RAD), Model-View-Controller (MVC), ASP.Net, Xcode, Web services, iPad application and mobile application development.
This dissertation develops a prototype electronic menu (e-menu) application for use on iPads in restaurants. The research employed a case study of a Thai restaurant to gather requirements and test the prototype. Users found the e-menu convenient and able to improve customer service by preventing human errors. Recommendations included following software development processes and a Model-View-Controller design for the e-menu system. The dissertation documents the research process and presents system analysis documents, the prototype, and users' positive perceptions of the e-menu application.
The document provides recommendations for developing an e-menu prototype for a Thai restaurant. It discusses software development processes based on RAD, prototyping, and direct observation. System analysis and design documents are created, including use case diagrams, class diagrams, ER diagrams, and workflow diagrams. Technical designs include an initial e-menu design using MVC, communication between .NET and iOS platforms using web services, and Xcode development with classes, view controllers, storyboards, and application settings.
The document presents the final prototype of an e-menu application for restaurants. It lists 15 functional requirements of the e-menu including allowing customers to order food, search menus, check orders, request services from staff, and view order statuses. It also provides screenshots and descriptions to illustrate how the e-menu would function on an iPad for customers and staff.
The document provides an overview of the functionalities of an e-menu website for restaurant staff. It includes:
1) A process diagram showing the workflow from a customer's entrance to payment.
2) Details on managing tables, including opening and closing orders, checking order details, and manual ordering.
3) Explanations of operating orders, including changing order statuses to cooking, serving, and served for starters and main courses.
This document presents the final prototype of an e-menu application for iPad and summarizes its main features. The e-menu allows customers to easily browse menu categories to find food and drink choices. It displays appetizing images and descriptions of dishes. Customers can view the order status, add more items to their order, check the total price, and amend the order before confirming. The e-menu is intended to enhance the dining experience and increase restaurant revenue by reducing wait times and encouraging additional orders.
This document provides justifications for the approaches used in a research project to develop an e-menu prototype for a Thai restaurant. It discusses:
1) The relationship between research objectives, approaches, and outcomes using a case study methodology.
2) The justification of using a case study methodology, RAD software development, direct observation for requirements gathering, and group interviews for data collection. Reasons for each approach are provided.
3) An action plan was needed to manage the time-consuming nature of some approaches like case study and direct observation. RAD and prototyping helped reduce time for implementation.
This document provides analysis and design documents for developing an e-menu prototype for a Thai restaurant, including:
1. Functional requirements for an e-menu iPad application and web application for restaurant staff and customers.
2. Non-functional requirements regarding system performance, security, and data integration.
3. UML diagrams including a use case diagram and class diagram to model the system.
4. Entity-relationship and revised entity-relationship diagrams to design the database.
5. Process diagrams depicting the current and proposed e-menu-based food ordering workflows in the restaurant.
This document outlines the objectives and plans for a dissertation project on developing an e-menu system. The objectives are to complete the dissertation on time, manage the software development project and portfolio, identify implementation issues, and use the document for communication. The initial plan involved meetings, requirements gathering, analysis, design, prototypes, and finishing by September 10th. The updated plan shows delays but an almost finished final prototype. Key actions in June included drafting a literature review and contacting stakeholders.
The document provides instructions for installing and testing e-menu software and a related website. It explains how to:
1) Install the e-menu iPad application using Xcode and test it on the iPad simulator.
2) Install the e-menu website using Visual Studio .NET, IIS, and SQL Server and configure the connection strings.
3) Test the installed e-menu website by accessing it through a web browser.
This document provides a list of 62 references from various sources such as journal articles, books, and websites. The references cover topics related to software engineering, user interface design, requirements gathering, agile methodologies, and mobile application development. The references include publication dates ranging from 2004 to 2012.
The document discusses a study on users' perceptions of an e-menu prototype for a Thai restaurant. It identifies several issues with the prototype based on user feedback, such as the inability to enter order quantities or customer comments directly from the main menu. The document then provides recommendations to address these issues, such as allowing quantity selection and comment entry on the main menu screen to streamline the ordering process.
The document presents the functionalities of an e-menu website for restaurant staff. It includes:
1) A process diagram showing the customer flow and order status updates from opening a table to closing out.
2) Features for managing tables including opening/closing orders, checking order details, and manual order entry.
3) Options for operating orders including updating cooking/serving status for starters, mains, drinks and sweets.
4) A section on managing service requests from customers for the waiter or billing.
This document presents the final prototype of an e-menu application for iPad. It summarizes the main features, including menu categories, ordering items, menu details, confirming orders, checking order status, and benefits. The e-menu allows customers to easily browse the menu, place orders, check order status, and enhances the dining experience. It also increases revenue, reduces wait times, and improves customer service for the restaurant.
This document provides justifications for the approaches used in a research project to develop an e-menu prototype for a Thai restaurant. It discusses:
1) The relationship between research objectives, approaches, and outcomes using a case study methodology.
2) The justification for using a case study methodology, RAD software development, direct observation for requirements gathering, and group interviews for data collection. Reasons included enabling an in-depth understanding of business needs and processes.
3) The document concludes the approaches allowed for a deep understanding of requirements but were time-consuming, requiring an action plan for effective time management.
This document provides analysis and design documents for developing an e-menu prototype for a Thai restaurant. It includes:
1) Functional requirements for the e-menu iPad application and web application for restaurant staff.
2) Non-functional requirements including real-time information transfer, user-friendly interfaces, and system security.
3) Use case, class, and ER diagrams to model the e-menu system and database.
4) Current and proposed restaurant service processes incorporating the e-menu system.
5) A workflow diagram of the e-menu prototype. The document outlines the analysis and design work completed for the e-menu prototype project.
The document outlines the objectives and plans for a dissertation project on developing an e-menu system. The objectives are to complete the dissertation on time, manage the software development and portfolio production, identify implementation issues, and use the document for communication. The plans include timelines for literature review, requirements gathering, analysis, design, coding, testing, documentation, presentations, and final submission by September 10th. Updates note some delays but that the final prototype is almost finished, and presentations to stakeholders were completed on schedule.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
FREE A4 Cyber Security Awareness Posters-Social Engineering part 3Data Hops
Free A4 downloadable and printable Cyber Security, Social Engineering Safety and security Training Posters . Promote security awareness in the home or workplace. Lock them Out From training providers datahops.com
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
1. Created by Traitet Th.
Project: E-menu on iPad for Thai restaurant Created Date 16 Aug 2012
Revised Date 3 Sep 2012
Topic: Description of research & discussion of outcomes
Revision No. 1.0
Content: Users’ perceptions on e-menu application Document Name D03-001
2. CONTENT
1. Interview Processes
2. Sampling for this case study
3. Primary finding
4. Findings
• Benefits
• Issues
• Features
5. Limitations
6. Appendix
4. 1.1) INTERVIEW PROCESSES
• Prepare the presentation and demonstration of
e-menu system
• Prepare the questions for group interviews
• Present video presentation of the e-menu
system
• Demonstrate software prototype on iPad and
Website
• Test e-menu functionalities with restaurant
managers and waiting staffs
• Perform group interviews with restaurant
manager, waiting staff and chefs
5. 1.2) SAMPLING FOR THIS CASE STUDY
Type of sampling: Convenience sampling
Case study at: A Thai casual dinning restaurant in UK
8% Interviewees
Manager x 1
• Restaurant Manager
Waiting Staff x 5 • Waiting Staff
50%
42% • Chef
Chef x6
33%
• Total Interviewers: 12 People (67%)
67%
• Total staff: 16 people (33%)
6. SEMI-STRUCTURED INTERVIEW QUESTIONS
1. Have you seen e-menu before? When? How?
2. Have you used e-menu before? When? How?
3. Can e-menu help you understand more details of food and drinks? Why?
4. Do you think that e-menu makes it easy to order extra food and drinks whilst
eating? Why?
5. Do you think that e-menu make it easy to request services e.g. call
waiter, main course, billing? Why?
6. Do you prefer ordering by e-menu or by waiter in this kind of restaurant?
Why?
7. Does e-menu reduce personal contact between customer and restaurant
staff?
Interview restaurant staff on 10 Aug 2012 between 18.30 – 23.00
7. INTERVIEW QUESTIONS
SEMI-STRUCTURED
8. What are main benefits of e-menu in your opinion? What? How?
9. What are main issues if implemented in this restaurant? What? How?
10. What are important features of e-menu that should be provided? What?
How?
11. Has the demonstrate software some good points? What? How?
12. What do you think about e-menu prototype?
• Feedback (Easy to back to previous screen)
• Memorability (Easy to remember to use the next time)
• Learnability (Easy to use and learn without user manual)
• Efficiency (Easy to perform tasks)
• Satisfaction (Pleasant to use software)
8. 2) PRIMARY RESULTS
The perception of e-menu system
for Thai Casual dinning restaurants in UK.
9. DATA ANALYSIS
Data Collection Data Analysis Finding
at a Thai restaurant in UK Identify – Coding - Categorize Users’ perception on e-menu
Semi-Structure
Content analysis Convenience – Attraction - Expensive
group interviews
The middle image copied from
10. 3.1) USERS REQUIRE PRESENTATION OF E-MENU
Proportion of staff who have Proportion of staff how have ever
heard about e-menu application used e-menu application
8%
Have ever heard about Have ever used e-
e-menu app x7 menu app x1
42%
58%
Have never heard Have never used app
about e-menu app x5 x11
92%
Importance of presentation and demonstrating e-menu system before interviews
e
Background
Group
Interviews
Demonstrat
Lack of
Presentation and
Most restaurant staffs Group interviews with
demonstration are
have no background in e- needed to explain the restaurant
key concept and features
menu application. of e-menu system. manager, waiting staff
11. 3.2) USERS FAMILIAR WITH APPLE DEVICES
Proportion of using Tablet Devices Proportion of using Mobile Devices
17%
42%
50% 16%
67%
8%
Use iPad x5 Use iPhone x8
Use Andriod Tablet x1 Use Andriod mobile phones x2
No Tablet Device x6 Use other mobiles x2
Why iPad was suitable for this case study?
Familiarity
learn
Easy to
Most staff members are familiar It helps them to easily learn &
with Apple devices e.g. iPhone understand the e-menu system
and iPad
13. USERS’ PERCEPTIONS
Benefits of e-menu
application Issues of e-menu application
Y
MAJORIT
• • High cost
Y
MAJORIT
Convenience
MINORITY
• Improve customer services • Older people
MINORITY
• Reduce human error • Technical issues
• High attraction
15. 1) CONVENIENCE
Customer Restaurant Staff
1. Easy to revise menu details
1. Easy to order • Images
• Details of food & drinks • Description
Perceptions
• Images • Prices
2. Easy to order additional food and drinks 2. Easy to add new promotions
3. Easy to check order status 3. Able to sell seasonal dishes without
printing new menus
Conclusion
The above perceptions should be considered when producing
an real e-menu application.
develop e-
Considered Features: Details of dishes, ordering extra food & drinks
How to
menu
and checking order status
16. 2) IMPROVING CUSTOMER SERVICE
• Receive their orders faster.
• Ease of calling a waiter.
• Ease of requesting their main dish when they want it.
• Ease of requesting their bill.
• Simple to order extra drinks and food.
• The customers are not disturbed when asking for extra drinks.
Conclusion
Improving customers services is an important
factor of using e-menu application.
develop
e-menu
How to
Considered Features: Order management and calling services
17. 3) PREVENTING HUMAN ERROR
1. Prevent forgetting orders
• Some extra orders, e.g. drinks, can be ignored during a busy time.
2. Reduce cooking wrong orders
Perceptions
• Poor handwriting by waiting staff
• Taking a wrong order by new part-time staff
• Incorrect communication between waiters and chefs
Conclusion
E-menu could prevent communication
problems and increase customer satisfaction.
develop
e-menu
How to
Considered Features: Transferring orders to a kitchen and bar
18. 4) HIGH ATTRACTION
1. A new technology for restaurant industry.
Perceptions
2. E-menu have not been used by any Thai restaurant in the UK.
3. E-menu differentiates a restaurant from competitors.
4. E-menu enhance dining experience for customers.
Conclusion
Using e-menu might increase a number of customers and target groups.
develop
e-menu
How to
Considered Features: Elegant User Interfaces & Easy to use
20. 1) HIGH COST
Reduce Cost Higher cost
• Labour cost • Hardware
• Printing menu cost • Software
Increase revenue
Maintenance cost
• More drinks
Damage
• More customers
Lifetime
Most users concerned about cost of e-menu,
which is much more expensive than paper-based menu.
21. DRAWBACK 2) OLDER PEOPLE
• Some older people in UK are
familiar with iPad e.g. E-
reader.
UK OLDERS
S
• Some older people might not want
to use e-menus because ordering
from waiters is more convenient.
• Some older people might not be
familiar with using new technology
Countermeasure
Older people may not want 1. User guide
2. Bigger text
to use e-menu to order 3. Easy to call waiter
22. TECHNICAL ISSUES
1. Installation position
2. Integration with POS (Post of Sales) System
3. Damage of iPad because of liquids
4. Run out of iPad battery during usage
5. Stability of system
6. Speed of application
Above technical issues are needed to consider
when produce a real e-menu system.
24. E-MENU FEATURES SHOULD BE PROVIDED
Clear description of food & Details of dishes
drinks • Picture
Show ordered items • Price
Show total price • Menu description
Call waiter
Request services
Check order status
Cancel menu
The important features, which should be provided
by e-menu system.
25. E-MENU FEATURES COULD BE PROVIDED
Integrate to a Post of Sale (POS) system
Advertise new promotions during meals
Register membership
Add special seasonal menus
Take photos to share on social network
Cancel some menus in case of lacking ingredient
Show an amounts ingredient or nutrition
Show history of particular food or drinks e.g. Wine
Monitor orders by restaurant owners and managers from outside
Report best seller items.
Calculate ingredient requirements
The above additional requirements should be considered
based on particular business requirements
27. FUTURE OF CASTUAL DINING RESTAURANT
E-menu ordered by
customers
E-menu ordered (Tablet e.g. iPad and
by waiting staff Android devices)
(Pocket PC and Future
smart phones)
Paper-based
Menu Now & future
Now
29. LIMITATIONS OF THIS RESEARCH
1. This research did not interview any end-users, namely, restaurant
customers.
2. This research did not interview older people on their perceptions of
ordering meals using iPad.
3. This research did not analyse investment feasibility of e-menu
system.
The future research can additionally study to expand
knowledge from this research.
31. REFERENCES
BRYNE, Michelle (2001). Sampling for qualitative
research. AORN Journal, 73, 494.
EISING, Martin (2010). Data Analysis Overview.
[online]. Last accessed 6 September 2012 at:
http://www.dashboardinsight.com/articles/new-concepts-
in-business-intelligence/data-analysis-overview.aspx.
Editor's Notes
The questions of group interviews are separated into two main questions with regards to the research question.The perception of e-menu system for Thai casual dinning restaurants in UKThe perception of e-menu features.Note that that list of questions for group interviews are shown in this appendix
\\
Group Interview Objective: Qualitative data analysis consists of identifying, coding, and categorizing patterns found in the data. BRYNE, Michelle (2001). Sampling for qualitative research. AORN Journal, 73, 494.3. Researcher is a toolReference pictureshttp://www.dashboardinsight.com/articles/new-concepts-in-business-intelligence/data-analysis-overview.aspx
Importance of presentation and demonstrating e-menu system before interviewsMost restaurant staffs have not background about e-menu system.Need to demonstrate so that they understand what are features of e-menu application.The learner uses quantitative data to analyse basic perceptions
This information informally asked during observation.Reason of choosing iPad to develop the prototype Most staffs are familiar to Apple devices such as iPhone and iPadIt make them be easy to learn the systemAndroid devices have several specifications and screen size. Therefore, they are more difficult to develop than iPad (from literature review)
Note that some above features have not been implemented in the final prototype.Important features should be concerned;Details of food and drinksImages of food and drinksOrdering additional food and drinksChecking order status
The above perceptions received from restaurant staff. However, future research can interview restaurant customers to get obvious opinions directly.
Thai restaurants have a lot of part-time staffs (more than 60%) who are one-year postgraduate students. After they graduate, those restaurants have to find new part-time students.Therefore, the restaurants always hire new part-time staffs who can make a communication mistake e.g. receiving order, saying menu names, communicating with chefs.
Although using e-menu might increase a number of customers. However, increasing revenue is more likely to be considered by restaurant owner.
However, the restaurant manager suggested that it should do investment analysis to estimate return investment period before making a decision.Futher research, should estimate roi
According to users’ perceptions, older people may not want to use e-menu to order, however, creating user guide, using bigger texts are important features to support older people.
However, restaurant manager mentions that adding more features should concern that the customers will spend more time in restaurant. It can reduce turn over rate.