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 tablets 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.
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.
The document discusses key knowledge for developing an e-menu prototype for a Thai restaurant, including details on e-menus for restaurants, the restaurant service process, software usability, and mobile application development. It analyzes the existing restaurant service process and identifies issues that can be improved with an e-menu system. A tablet e-menu is determined to be the most suitable option for the restaurant as it is small, easy to install, and allows customers to order directly from their table.
The document discusses customizing system settings through the Control Panel, including changing the desktop display, date and time, mouse settings, multimedia devices, and printers. It provides instructions on accessing and using the Control Panel to modify these settings.
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 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.
The document summarizes user feedback on an e-menu prototype for a Thai restaurant, including suggestions to:
1) Allow ordering quantities directly from the main menu instead of multiple steps.
2) Add the ability to enter customer order comments.
3) Separate set menus into individual items when orders are sent to the kitchen.
4) Add a button to easily request the main course from the main menu.
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.
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 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.
The document discusses key knowledge for developing an e-menu prototype for a Thai restaurant, including details on e-menus for restaurants, the restaurant service process, software usability, and mobile application development. It analyzes the existing restaurant service process and identifies issues that can be improved with an e-menu system. A tablet e-menu is determined to be the most suitable option for the restaurant as it is small, easy to install, and allows customers to order directly from their table.
The document discusses customizing system settings through the Control Panel, including changing the desktop display, date and time, mouse settings, multimedia devices, and printers. It provides instructions on accessing and using the Control Panel to modify these settings.
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 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.
The document summarizes user feedback on an e-menu prototype for a Thai restaurant, including suggestions to:
1) Allow ordering quantities directly from the main menu instead of multiple steps.
2) Add the ability to enter customer order comments.
3) Separate set menus into individual items when orders are sent to the kitchen.
4) Add a button to easily request the main course from the main menu.
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.
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.
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 and adequate security.
3. UML diagrams including a use case diagram, class diagram, and ER diagram to model the e-menu system.
4. Designs of the restaurant service process and e-menu workflow to integrate the new e-menu system into current operations.
The document summarizes users' perceptions of an e-menu prototype for a Thai restaurant. It identifies 9 key issues with the prototype based on user feedback, such as the inability to enter order quantities or customer comments. For each issue, it provides a suggested improvement, the reasoning behind it, and the potential benefits. Overall, the suggestions aim to make the e-menu interface more user-friendly and better meet the needs of customers and restaurant staff.
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 provides an analysis and design for developing an e-menu prototype for a Thai restaurant. It includes:
1. Functional requirements for the e-menu iPad application and web application, including ordering, viewing orders, and requesting services.
2. Non-functional requirements like real-time information transfer, user-friendly interfaces, and adequate security.
3. Use case, class, and entity-relationship diagrams to model the e-menu system and database.
4. Current and proposed redesigns of the restaurant's food ordering process incorporating the e-menu system.
5. A workflow diagram depicting the e-menu ordering process.
Users, UX, and Technology: Going hi-tech with your classroom AV systemBohyun Kim
The document summarizes renovations made to an audiovisual classroom setup based on user feedback. Key points:
- The classroom was upgraded with multiple screens, cameras, microphones, and touchpad control. However, instructors reported usability issues.
- Issues included short mouse/keyboard wires, screens timing out, confusing preset arrangements, and an unintuitive control panel. Solutions like wireless peripherals, settings changes, and additional presets were implemented.
- Users preferred reverting to a single mirrored display rather than grappling with the complex multi-screen setup. This highlighted that technology should facilitate tasks rather than be the focus.
- Lessons included validating upgrades with users, prioritizing
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.
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 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 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.
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 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.
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.
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 and adequate security.
3. UML diagrams including a use case diagram, class diagram, and ER diagram to model the e-menu system.
4. Designs of the restaurant service process and e-menu workflow to integrate the new e-menu system into current operations.
The document summarizes users' perceptions of an e-menu prototype for a Thai restaurant. It identifies 9 key issues with the prototype based on user feedback, such as the inability to enter order quantities or customer comments. For each issue, it provides a suggested improvement, the reasoning behind it, and the potential benefits. Overall, the suggestions aim to make the e-menu interface more user-friendly and better meet the needs of customers and restaurant staff.
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 provides an analysis and design for developing an e-menu prototype for a Thai restaurant. It includes:
1. Functional requirements for the e-menu iPad application and web application, including ordering, viewing orders, and requesting services.
2. Non-functional requirements like real-time information transfer, user-friendly interfaces, and adequate security.
3. Use case, class, and entity-relationship diagrams to model the e-menu system and database.
4. Current and proposed redesigns of the restaurant's food ordering process incorporating the e-menu system.
5. A workflow diagram depicting the e-menu ordering process.
Users, UX, and Technology: Going hi-tech with your classroom AV systemBohyun Kim
The document summarizes renovations made to an audiovisual classroom setup based on user feedback. Key points:
- The classroom was upgraded with multiple screens, cameras, microphones, and touchpad control. However, instructors reported usability issues.
- Issues included short mouse/keyboard wires, screens timing out, confusing preset arrangements, and an unintuitive control panel. Solutions like wireless peripherals, settings changes, and additional presets were implemented.
- Users preferred reverting to a single mirrored display rather than grappling with the complex multi-screen setup. This highlighted that technology should facilitate tasks rather than be the focus.
- Lessons included validating upgrades with users, prioritizing
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.
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 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 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.
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 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.
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 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.
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.
This document describes the software development process used to create an e-menu application. It involved requirements gathering, prototyping, and direct observation. The process included designing the database, UML diagrams, workflows and classes. A first prototype was developed in .NET and feedback was gathered. Requirements and designs were refined and a final prototype was created in Xcode on iPad and for the back office in .NET. Staff were interviewed and the final prototype was demonstrated and recommendations were made.
THE SACRIFICE HOW PRO-PALESTINE PROTESTS STUDENTS ARE SACRIFICING TO CHANGE T...indexPub
The recent surge in pro-Palestine student activism has prompted significant responses from universities, ranging from negotiations and divestment commitments to increased transparency about investments in companies supporting the war on Gaza. This activism has led to the cessation of student encampments but also highlighted the substantial sacrifices made by students, including academic disruptions and personal risks. The primary drivers of these protests are poor university administration, lack of transparency, and inadequate communication between officials and students. This study examines the profound emotional, psychological, and professional impacts on students engaged in pro-Palestine protests, focusing on Generation Z's (Gen-Z) activism dynamics. This paper explores the significant sacrifices made by these students and even the professors supporting the pro-Palestine movement, with a focus on recent global movements. Through an in-depth analysis of printed and electronic media, the study examines the impacts of these sacrifices on the academic and personal lives of those involved. The paper highlights examples from various universities, demonstrating student activism's long-term and short-term effects, including disciplinary actions, social backlash, and career implications. The researchers also explore the broader implications of student sacrifices. The findings reveal that these sacrifices are driven by a profound commitment to justice and human rights, and are influenced by the increasing availability of information, peer interactions, and personal convictions. The study also discusses the broader implications of this activism, comparing it to historical precedents and assessing its potential to influence policy and public opinion. The emotional and psychological toll on student activists is significant, but their sense of purpose and community support mitigates some of these challenges. However, the researchers call for acknowledging the broader Impact of these sacrifices on the future global movement of FreePalestine.
Chapter wise All Notes of First year Basic Civil Engineering.pptxDenish Jangid
Chapter wise All Notes of First year Basic Civil Engineering
Syllabus
Chapter-1
Introduction to objective, scope and outcome the subject
Chapter 2
Introduction: Scope and Specialization of Civil Engineering, Role of civil Engineer in Society, Impact of infrastructural development on economy of country.
Chapter 3
Surveying: Object Principles & Types of Surveying; Site Plans, Plans & Maps; Scales & Unit of different Measurements.
Linear Measurements: Instruments used. Linear Measurement by Tape, Ranging out Survey Lines and overcoming Obstructions; Measurements on sloping ground; Tape corrections, conventional symbols. Angular Measurements: Instruments used; Introduction to Compass Surveying, Bearings and Longitude & Latitude of a Line, Introduction to total station.
Levelling: Instrument used Object of levelling, Methods of levelling in brief, and Contour maps.
Chapter 4
Buildings: Selection of site for Buildings, Layout of Building Plan, Types of buildings, Plinth area, carpet area, floor space index, Introduction to building byelaws, concept of sun light & ventilation. Components of Buildings & their functions, Basic concept of R.C.C., Introduction to types of foundation
Chapter 5
Transportation: Introduction to Transportation Engineering; Traffic and Road Safety: Types and Characteristics of Various Modes of Transportation; Various Road Traffic Signs, Causes of Accidents and Road Safety Measures.
Chapter 6
Environmental Engineering: Environmental Pollution, Environmental Acts and Regulations, Functional Concepts of Ecology, Basics of Species, Biodiversity, Ecosystem, Hydrological Cycle; Chemical Cycles: Carbon, Nitrogen & Phosphorus; Energy Flow in Ecosystems.
Water Pollution: Water Quality standards, Introduction to Treatment & Disposal of Waste Water. Reuse and Saving of Water, Rain Water Harvesting. Solid Waste Management: Classification of Solid Waste, Collection, Transportation and Disposal of Solid. Recycling of Solid Waste: Energy Recovery, Sanitary Landfill, On-Site Sanitation. Air & Noise Pollution: Primary and Secondary air pollutants, Harmful effects of Air Pollution, Control of Air Pollution. . Noise Pollution Harmful Effects of noise pollution, control of noise pollution, Global warming & Climate Change, Ozone depletion, Greenhouse effect
Text Books:
1. Palancharmy, Basic Civil Engineering, McGraw Hill publishers.
2. Satheesh Gopi, Basic Civil Engineering, Pearson Publishers.
3. Ketki Rangwala Dalal, Essentials of Civil Engineering, Charotar Publishing House.
4. BCP, Surveying volume 1
Beyond Degrees - Empowering the Workforce in the Context of Skills-First.pptxEduSkills OECD
Iván Bornacelly, Policy Analyst at the OECD Centre for Skills, OECD, presents at the webinar 'Tackling job market gaps with a skills-first approach' on 12 June 2024
Level 3 NCEA - NZ: A Nation In the Making 1872 - 1900 SML.pptHenry Hollis
The History of NZ 1870-1900.
Making of a Nation.
From the NZ Wars to Liberals,
Richard Seddon, George Grey,
Social Laboratory, New Zealand,
Confiscations, Kotahitanga, Kingitanga, Parliament, Suffrage, Repudiation, Economic Change, Agriculture, Gold Mining, Timber, Flax, Sheep, Dairying,
Leveraging Generative AI to Drive Nonprofit InnovationTechSoup
In this webinar, participants learned how to utilize Generative AI to streamline operations and elevate member engagement. Amazon Web Service experts provided a customer specific use cases and dived into low/no-code tools that are quick and easy to deploy through Amazon Web Service (AWS.)
Gender and Mental Health - Counselling and Family Therapy Applications and In...PsychoTech Services
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
Elevate Your Nonprofit's Online Presence_ A Guide to Effective SEO Strategies...TechSoup
Whether you're new to SEO or looking to refine your existing strategies, this webinar will provide you with actionable insights and practical tips to elevate your nonprofit's online presence.
This presentation was provided by Racquel Jemison, Ph.D., Christina MacLaughlin, Ph.D., and Paulomi Majumder. Ph.D., all of the American Chemical Society, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.
Philippine Edukasyong Pantahanan at Pangkabuhayan (EPP) CurriculumMJDuyan
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 𝟏)-𝐏𝐫𝐞𝐥𝐢𝐦𝐬
𝐃𝐢𝐬𝐜𝐮𝐬𝐬 𝐭𝐡𝐞 𝐄𝐏𝐏 𝐂𝐮𝐫𝐫𝐢𝐜𝐮𝐥𝐮𝐦 𝐢𝐧 𝐭𝐡𝐞 𝐏𝐡𝐢𝐥𝐢𝐩𝐩𝐢𝐧𝐞𝐬:
- Understand the goals and objectives of the Edukasyong Pantahanan at Pangkabuhayan (EPP) curriculum, recognizing its importance in fostering practical life skills and values among students. Students will also be able to identify the key components and subjects covered, such as agriculture, home economics, industrial arts, and information and communication technology.
𝐄𝐱𝐩𝐥𝐚𝐢𝐧 𝐭𝐡𝐞 𝐍𝐚𝐭𝐮𝐫𝐞 𝐚𝐧𝐝 𝐒𝐜𝐨𝐩𝐞 𝐨𝐟 𝐚𝐧 𝐄𝐧𝐭𝐫𝐞𝐩𝐫𝐞𝐧𝐞𝐮𝐫:
-Define entrepreneurship, distinguishing it from general business activities by emphasizing its focus on innovation, risk-taking, and value creation. Students will describe the characteristics and traits of successful entrepreneurs, including their roles and responsibilities, and discuss the broader economic and social impacts of entrepreneurial activities on both local and global scales.
1. ANNOTATION OF
KNOWLEDGE OF
THE DOMAIN
Created by Traitet Th.
Subject: E-menu on iPad for Thai restaurant
Created Date 31 July 2012
Topic: Annotation Revised Date 6 Sep 2012
Revision No. 1.0
Content: Annotation of knowledge of the domain
Document Name A01-001
2. 2 KEY KNOWLEDGE OF THE DOMAIN
1. Electronic menu (e-menu) for restaurants
2. Restaurant service process
3. Software usability and Human-Computer Interaction
(HCI)
4. Software development methodologies and
prototyping technique
5. Mobile application development for e-menu on iOS or
Android devices
4. 4 1) E-MENU FOR RESTAURANT
Main Objectives of e-menu (Jenie 2011)
• Display list of food and beverages including images
• Process the restaurant services from ordering to payment
Three general kinds of touch screen e-menu system (Conceptic no
date)
• Table side touch screen e-menu
• E-menu for waiting area
• Tablet e-menu
Pictures are taken from Emenu USA (2011) and Conceptic (no date)
5. 5 1) E-MENU FOR RESTAURANT
1 Table-side touch screen e-menu
Table-side touch screen e-menu
• Equipment: Personal computer
• Installation: Need to modify table
Benefits
• No falling problem
Disadvantages
• Difficult to install
Difficult to install & • Need to prepare electrical plugs at all tables
Need electrical plugs
Pictures are taken from Emenu USA (2011) and Conceptic (no date)
6. 6 1) E-MENU FOR RESTAURANT
2 E-menu for waiting area
E-menu for waiting area
• Equipment: LCD TV with touch screen
• Installation: Need to prepare area to install
Benefits
• Bigger images
• Less cost because it requires only one LCD
Disadvantages
• Only one person can order at a time.
• Not suitable for this restaurant because customers
Cannot order can not order on their tables.
at dining table • Need extra space to install.
Pictures are taken from Emenu USA (2011) and Conceptic (no date)
7. 7 1) E-MENU FOR RESTAURANT
3 Tablet e-menu
Tablet E-menu
• Equipment: Tablet e.g. iPad
• Installation: Don’t need to modify table
Benefits
• Slim and small size
• Easy to install
• Build-in wireless connection
Disadvantages
Small & • Falling problem
• Smaller screen size than others
Easy to use • Theft
8. 8 1) E-MENU FOR RESTAURANT
After discussion with the restaurant manager and staff, we found that the tablet e-menu was the most
suitable because it was smaller and simpler to install.
Order at
No Compared Item Size Installation Summary
table
It is not suitable for this restaurant because
1 E-menu at waiting area No Big Difficult
it is inconvenient for the customers.
Table side touch screen e- It is difficult to install because of its size
2 Yes Medium Difficult
menu and it needs power supply.
It can order at the dinning table and
3 Tablet e-menu Yes Small Easy
it is cheaper and easier to install.
Final decision with restaurant manager: Tablet e-menu
10. 10 2) RESTAURANT SERVICE PROCESS
Analysis of a existing restaurant service process
Issues of existing system
1. Need to wait for waiting staff
before giving order and making
payment.
2. Waiting staff must deliver order
to kitchen and bar.
E-menu system
1. Order is send directly from a
table to bar and kitchen.
Process of taking order & making payment can be improve by e-menu.
Pictures are adopted from Crowston, Rubleske and Howison (2006)
11. 11 2) RESTAURANT SERVICE PROCESS
Problem: Personal contact between waiting staff and customers
Description
Service Request Diagram
• E-menu may reduce the personal
contact between customers and
waiting staff (Studentwebstaff 2009).
Solution
• The system should have a “service
request” feature to call waiting staff.
• Request Waiter
• Request Main Benefits
Course
• Customers can request services
• Request Bill
easier compared to the existing
system.
• Customers don’t want to have to look
around to find a waiter.
Solution: Customers can request a waiter from e-menu system.
Benefits: Customers can easily request a waiter.
Pictures are adopted from Crowston, Rubleske and Howison (2006)
12. 12 2 ) R E S TA U R A N T S E RV I C E P R O C E S S
As-it or current system
1. Ordering Issues
2
• A waiter must spend time to
Service
Request
take and transfer an order to
the kitchen and bar.
• Customers are less inclined to
1
order more food during busy
Ordering
time.
• Paper-based menus have
insufficient information e.g.
pictures and details of food.
2. Request Service Issues
• A waiter has to observe
customers when they want to
request a main course.
• The customers have to look
around to request waiter and
These issues can be solved by e-menu system
bill.
13. 13 2 ) R E S TA U R A N T S E RV I C E P R O C E S S
New Service Process by e-menu system
1. Ordering
2
- Order is transferred to bar and
Service
Request
kitchen automatically.
- Customers find it easy to order
more food and beverages.
- Customers can check their
1
order status.
Ordering
- Customers can select menu
with full details and pictures.
2. Service request
- Customers can request service
on e-menu
- Waiters have more time to
provide service.
E-menu can enhance ordering and requesting services
15. 15 SOFTWARE USABILITY & HCI
HCI: Human-Computer Interaction
Improving Software Quality by HCI design
• Quality of software should support
• Users can use software without specialised business needs.
IT knowledge • HCI is an important factor to measure
• Easy to use & without long instruction a quality of software (Dubey 2012
(Edexcel 2010) , Majid 2011),
• Touch screen interfaces can enhance usability because it is easy to use.
• Developing e-menu system should concern HCI design.
16. 16 SOFTWARE USABILITY & HCI
How to measure HCI Design?
Good HCI Design & Example of applying
No Description
Usability the concept for e-menu
1 Visibility Know result of each operation Screen is updated after placing order
Customers can always return to a previous
2 Feedback Easy to return to a previous screen
screen of e-menu.
Easy to recognize when use software Make user-friendly and non-complex user
3 Memorability
again interfaces
4 Learnability Easy to accomplish basic tasks Reduce unnecesaary steps as much as possible
5 Efficiency Quick to learn and perform tasks Make it be simple and easy to use
6 Satisfaction Pleasant to use software Put nice images and suitable colours
(Norman and Nielsen 2011; Nielsen 1993)
Above criteria should always be concerned when developing an e-menu application.
However, only usability is insufficient. Developers must be aware of SW development
methodology.
18. 4 ) S O F T WAR E D E V E L O P M E N T
18 METHODOLOGIES
AN D P R O TO T Y P I N G T E C H N I Q U E
Comparison table among Waterfall, Agile and RAD with prototyping approach
RAD with
No Compared Item Waterfall Agile Description
Prototyping
Waterfall approach clearly separates development
1 Traditional approach Yes No No processes, and doesn't return to a previous stage.
(Khan et al. 2011)
Iterative process can improve a quality of application
Uses iterative process
2 No Yes Yes and increase customer satisfaction (Hoffer, George
and Valacich 2008).
Agile and RAD use a iterative process, which is
Software is likely fit with business
3 No Yes Yes flexible when a requirement is changed (Kendal
needs. 2011).
RAD is an experimental method, which may result in
4 Experimental approach No No Yes insufficiently understand the overall business
requirements (Khan et al. 2011).
Iterative process able to increase the overall cost and
Able to increase the overall cost
5 No Yes Yes time. For example, after requirements are changed, a
and implementation time project will need more time to develop (Cobb 2011).
A large project needs a lot of developers and much
time to implement. It is difficult to observe at a
6 Appropriate for a large project Yes Yes No customer site and make a prototype at a short time
(Meso and Jain 2011)
The software development methodology is considered in the “Justification of the approach” section
19. 4 ) S O F T WAR E D E V E L O P M E N T
19 METHODOLOGIES
AN D P R O TO T Y P I N G T E C H N I Q U E
Mapping RAD Modeling with e-menu development
Capture Requirements What?
Observation – Discussion – Interview
(Observation at the restaurant) • Develop a final prototypes of e-menu application
Where?
2.5 months for prototype
Quick Analysis and Design Iterate
(UML and other design • At a Thai casual dinning restaurant
process
documents)
development
How?
Develop Prototype • Observation at a restaurant to gather requirements
(1st by .Net & 2nd by .NET & • Discussion with manager to summarise needs
Xcode) • Develop the first prototype by .NET & Web services
• Develop the final prototype on iPad (Objective-c language on
Customer Evaluation of Prototype xCode software)
Throughout (Get feedback from • Observation, discussion and interviews
development observation, discussion and Observation to understand as-it system.
process interviews) Discussion to gather requirements
Interviews the restaurant manager, waiting staff and
Develop Final Product chefs
RAD Prototype Model (Sommerville 2004) Reason using .Net to develop the first prototype
• Saving time: Researcher is more familiar with .NET
• Testing web services: Website developed by .NET can test
web services before integrating with xCode (iPad)
Key concepts of RAD methodology When?
• Gather requirements & evaluate prototype by • Developing and observing between July and August 2012
observation, discussion and interview. • Presenting the first and final prototypes in July and August
2012, respectively.
• Working closely with users throughout the developing process.
21. 4 ) M O B I L E AP P L I C AT I O N D E V E L O P M E N T F O R
21
E - M E N U O N I O S AN D AN D R O I D D E V I C E S
Comparison table between Apple’s iOS and Google Andriod
Objective
• To chose an effective way to develop a
No Platform Apple's iOS Google's Android prototype of e-menu system.
1 Owner Apple Google System analysis
2 Tablet devices iPad Samsung, HTC, HP, and etc.
• It is better if e-menu system can support
both iOS and Andriod devices because
3 Sizes of tablet screens 1 Several sizes based on devices both of them are famous platforms.
4 Operating system (OS) iOS Android based on Linux OS
Conditions
5 Programming language Objective-C Mainly in Java • Only two months for developing a
Object Oriented prototype.
6 Yes Yes
Programming (OOP) • They use different tools and languages.
Apple Xcode and Google App Inventor, IBM Eclipse
7 Preferred developing tool
Interface builder and Netbean Solutions
• Develop web services on .NET
8 Open source platform No Yes
• Provide web services to both Apple and
9 Annual fee for development $99 per year One time registration fee $25 Andriod devices
Software approval before Spend 3-4 weeks for app approval • However, the prototype is developed on
10 No need iPad (Apple device) for this case study
publishing by Apple
first.
(Ray 2012; Wei-Meng Lee 2012; Goadrich 2011)
Reasons
Problem: How to develop e-menu to support both Apple and Android devices • Restaurant owner, staff and the learner
? are more familiar with iPad than Andriod
devices.
• iPad has only one size of screen, which is
Solutions: Use Web services (platform independent) to provide easier to develop.
• Using Web services because they are
functionalities to iOS and Andriod platforms.
platform independent.
22. 4 ) M O B I L E AP P L I C AT I O N D E V E L O P M E N T F O R
22
E - M E N U O N I O S AN D AN D R O I D D E V I C E S
Use web services to support both iPad and Andriod devices
Key concept
- Development based on Model-
View-Controller (MVC) model
Web Services
Separate layers to three layers;
- Data Model Layer
- Controller Layer
Platform independent by web services
- Model Layer
Decision for this case study
- ASP.Net: It can develop web
services more easily because the
learner is familiar with this platform.
- SQL Server: It is compatible with
.Net because their owners are the
same (Microsoft).
- iPad or iOS platform: The
restaurant manager and staff are
more familiar with iPad than
Adopted from Microsoft ASP.NET Team (2009).
24. 24 REFERENCES
CONCEPTIC (no date). iPad eMenu for restaurant. [online]. Last accessed 9 August 2012 at: http://www.emenu-international.com/iPad-
menu-for-restaurants.
CROWSTON, Kevin, RUBLESKE, Joseph and HOWISON, James (2006). Coordination Theory: A Ten-Year Retrospective. [online]. Last
accessed 8 August at: http://crowston.syr.edu/system/files/CT%20Review%20to%20distribute.pdf.
EDEXCEL (2010). Human Computer Interaction. [online]. Last accessed 7 August at:
http://www.edexcel.com/migrationdocuments/BTEC%20Nationals%20from%202010/Unit-23-Human-Computer-Interaction.pdf.
EMENU USA (2011). eMenu Pictures. [online]. Last accessed 9 August at: http://www.emenuny.com/pictures.html.
GANTTHEAD (2010). Rapid Application Development process. [online]. Last accessed 9 August at:
http://www.gantthead.com/content/processes/11306.cfm.
JENIE, Renan Prasta, et al. (2011). Designing user interface e-menu based on Android platform. [online]. Last accessed 9 August at:
http://ict.binus.edu/metamorph/file/research/Journal%20-%20Android%20Komodo%202.pdf.
MAJID, Rogayah Abd, et al. (2011). Users’ frustration and HCI in the software development life cycle. [online]. International Journal of
Information Processing and Management, 2 (1.5), 44-48. Article from Human and Sciences Research Center last accessed 8 August at:
http://www.humanpub.org/ijipm/ppl/4_%20IJIPM%20Vol2%20No.1-4.pdf.
MESO, Peter, JAIN, Radhika (2006). Agile Software Development: Adaptive Systems Principles and Best Practices. [online]. Information
Systems Management, 23(3), 19-30. Article from Mendeley last accessed 9 August at: http://www.mendeley.com/research/Agile-
software-development-adaptive-systems-principles-best-practices
Microsoft ASP.NET Team (2009). ASP.NET MVC Overview. Last accessed 9 Aug 2012at: http://www.asp.net/mvc/tutorials/older-
versions/overview/asp-net-mvc-overview.
NIELSEN, Jakob (1993). Usability Engineering. San Francisco, Morgan Kaufmann.
NORMAN, Donald A. and NIELSEN, Jakob (2010). Gestural interfaces: A step backward in usability. Interactions, 17 (5), 46-49.
STUDENTWEBSTAFF (2009). Use of E-Menus in the Restaurant Industry. [online]. Last accessed 9 August at:
http://www.studentwebstuff.com/mis/showthread.php?t=8049
Editor's Notes
The key knowledge of the domain is based on literature review.
The annotation of e-menu types were used to discuss a suitable solution with restaurant manager.
The final decision was a simulated situation that if the restaurant owner would like to invest for an e-menu system.
Diagram is copied from my system analysis and design document