CAN ANYONE PLEASE POST A FLOWCHART OF LOGIC 2!!!!!

Post by **answerhappygod** » Mon Jul 11, 2022 9:54 am

: Can Anyone Please Post A Flowchart Of Logic 2 1 (167.9 KiB) Viewed 33 times

: Can Anyone Please Post A Flowchart Of Logic 2 2 (184 KiB) Viewed 33 times

: Can Anyone Please Post A Flowchart Of Logic 2 3 (77.11 KiB) Viewed 33 times

APS145 Applied Problem Solving Workshop - 10 Workshop Value: 10 marks ( 5% of your final grade) Workshop Overview Vending machines now almost run without any human maintenance. They employ the "internet of things" (IoT) enabling real-time updates on stock levels, payments, and alerts for machine maintenance. Electronic payments use both swipe and "tap" technology for debit and credit cards and even accept cell phone payments using "near field communications" (NFC). No physical money is stored! Maintenance costs are drastically reduced with these enhancements over the older models as routine inventory and money pickups are eliminated. The only time a service provider needs to physically visit the machine, is for restocking inventory and addressing any general mechanical maintenance (which would be infrequent). But how should this all work? Workshop Details Applications of vending machines essentially have two main logical components to define: 1. Hardware States (physical interface) 2. Software Logic (main functional logic/controller) States Hardware states are triggered by the software layer that implement the overall system process. The system has 6 main states (or modes): 1. Power-On 2. Power-Off 3. Idle/Ready (stand-by: waiting for customer) 4. Active (customer interaction building an order) 5. Payment (final step in customer transaction) 6. Cancel You define these For each of these states, both the hardware and software components will have their own set of defined processes.
APS145 [Logic 1] Hardware States o Hardware components have only two possible states: "enabled" or "disabled" As the machine changes from one state to another, the various hardware components need to be initialized to the new state and should be set to complement o the initial state of the software logic (example: disable controls that don't apply to the current state and only enable those that should be) o The software logic will modify/change the hardware components as needed after the initialization of the hardware is set to the new state [Logic 2] Product Selection (define Idle and Active states) o Limited to a single letter (column) button followed by a single number (row) button sequence (ex: "A" button + "9" button) o After selecting a product, you can enter a quantity from 1-9 followed by the Enter key. The Correct button can be used to erase the quantity before the Enter key is pressed. o Products can only be added to a transaction if the requested quantity for the item is in-stock (has inventory) o Multiple products can be added to a single transaction by entering one selection after another o Using the Pay button will indicate the end of the session Applied Problem Solving [Logic 3] Acceptable Payments & Product Inventory (define Payment and Cancel states) o Credit card (tap/swipe) o Bank card (tap/swipe) o NFC phone payment o Phone application payment O $$ NO CASH $$ o Following a successful payment, inventory must be adjusted in real-time (hint: local and remote data) o Inventory minimum stock levels must be enforced (if the quantity in-stock reaches the minimum stock level set for that product's row & column location, more products should be ordered Hardware Controls/Interface (see last page for illustrations) • Payment Module: LCD Colour Screen: • Column/Row buttons: • "Enter" button: • "Correct" button: "Cancel" button: "Pay" button: Physical hardware for reading credit cards, debit, NFC, Tap etc. 10" wide X 6" high (10 cm X 15 cm) Column-letter buttons (A-E), row-number buttons (1-10) Adds a product selection to the session (transaction), or applies entered quantity Used to backspace an entry/quantity, NOT remove an already added item Cancels the entire session and resets Triggers the payment process and finalizes the session
APS145 Data Structures Use the following data structures in your solution: "Product" ("Inventory" is simply a collection/array of "Product" data) slotID sku quantity maxQuantity minQuantity Applied Problem Solving price description // Unique location slot ID (physical placement in the machine ex: "D8") // Unique product identifier // Actual quantity available (physically in machine at the given slotID) // Maximum machine qty that can be stocked for the slotID // Re-order when this qty is reached (based on: maxQuantity - quantity) // Vending machine price to charge customer per unit // Product name "Transaction" ("Session" is simply a collection/array of "Transaction" data) slotID quantity price description // Unique location slot ID (physical placement in the machine ex: "D8") // Requested quantity // Price per single unit quantity // Product name