Scribd Logo
Upload

Welcome to Scribd!

  • 29 views

    Available. Drinks, Etc. With Some Information Included With It. Available On The Store

    Uploaded by

    Shawn James
    The document outlines functional and non-functional requirements for a food ordering kiosk system. The functional requirements specify that customers can order food, see item information and prices, check their order, and select a payment method. The non-functional requirements address operational issues like uptime, performance goals for response time, security standards, and cultural considerations for the user interface.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Available. Drinks, Etc. With Some Information Included With It. Available On The Store

    Uploaded by

    Shawn James
    29 views2 pages
    The document outlines functional and non-functional requirements for a food ordering kiosk system. The functional requirements specify that customers can order food, see item information and prices, check their order, and select a payment method. The non-functional requirements address operational issues like uptime, performance goals for response time, security standards, and cultural considerations for the user interface.

    Original Description:

    Original Title

    funtional-non-functional

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines functional and non-functional requirements for a food ordering kiosk system. The functional requirements specify that customers can order food, see item information and prices, check their order, and select a payment method. The non-functional requirements address operational issues like uptime, performance goals for response time, security standards, and cultural considerations for the user interface.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    29 views2 pages

    Available. Drinks, Etc. With Some Information Included With It. Available On The Store

    Uploaded by

    Shawn James
    The document outlines functional and non-functional requirements for a food ordering kiosk system. The functional requirements specify that customers can order food, see item information and prices, check their order, and select a payment method. The non-functional requirements address operational issues like uptime, performance goals for response time, security standards, and cultural considerations for the user interface.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 2

    2.

    1 FUNCTIONAL REQUIREMENTS

    2.1.1 Orders placement


    REQ001. The customer can order food and drinks in the kiosk
    REQ002. The customer shall be able to acknowledge if the food/drink is
    available.
    REQ003. The customer can search items by menu categories such as Burgers.
    Drinks, etc.
    REQ004. The customer shall be able to see pictures of the food/drink along
    with some information included with it.
    REQ005. The customer shall be able to find different variety of food/drink
    available on the store.
    REQ006. The customer shall be able to see estimated price of the order
    REQ007. The customer can check ordered items before confirming.
    REQ008. The customer can cancel ordered items before confirming.

    2.1.2 Schedule of orders


    REQ009. The kiosk shall be able to place orders in a queue.
    REQ0010. The kiosk shall be able to inform the customer about the
    placement of their orders in queue.

    2.1.3 Payment Method


    REQ011. The customer shall be able to select payment option.
    REQ012. The customer shall be able to pay through cash or card transaction.
    2.2 NON-FUNCTIONAL REQUIREMENTS

    2.2.1 Operational Requirements

    REQ. The system will operate in Windows Operating System Platform

    REQ. The kiosk shall locate at perspective zone.

    REQ. The system shall be completely operational at least 98% of the operating time.

    REQ. The system shall generate a paper of receipt for the transaction.

    REQ. The system shall provide useful information including authentic images of foods

    and drinks so restaurant customers can easily understand menu description.

    2.2.2 Performance Requirements

    REQ. Down time after a failure shall not exceed 2 hours.

    REQ. The system shall provide real-time information with quick response.

    REQ. All transaction shall take less than 2 seconds.

    2.2.3 Security Requirements

    REQ. The system shall incorporate both physical and data security.

    REQ. The system shall meet Payment Card Industry (PCI) standards.

    REQ. The system shall have adequate security to access system information.

    2.2.4 Cultural and Political Requirements

    REQ. The system will not use any text, images, or media that will offend the customers

    using the kiosk.

    REQ. The system will use English language only.

    REQ. The system user interfaces shall user-friendly and easy to use.

    You might also like