Scribd Logo
Upload

Welcome to Scribd!

  • 1K views

    DSTR Assignment Question APU

    Uploaded by

    Alvin Alphius Jeffrey
    This document outlines requirements for developing a food order and delivery system. The system must allow customers to place orders that include multiple items, and store delivery information. Orders should be searchable and editable by order number or customer name. The most recently placed orders must be viewable first, and staff should fulfill orders sequentially without skipping any. The system needs validation rules and good programming practices. Students must submit a report explaining their code and algorithms, along with presenting their solution.

    Copyright:

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

    DSTR Assignment Question APU

    Uploaded by

    Alvin Alphius Jeffrey
    1K views3 pages
    This document outlines requirements for developing a food order and delivery system. The system must allow customers to place orders that include multiple items, and store delivery information. Orders should be searchable and editable by order number or customer name. The most recently placed orders must be viewable first, and staff should fulfill orders sequentially without skipping any. The system needs validation rules and good programming practices. Students must submit a report explaining their code and algorithms, along with presenting their solution.

    Original Description:

    DSTR assignment question by Asia Pacific University

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document outlines requirements for developing a food order and delivery system. The system must allow customers to place orders that include multiple items, and store delivery information. Orders should be searchable and editable by order number or customer name. The most recently placed orders must be viewable first, and staff should fulfill orders sequentially without skipping any. The system needs validation rules and good programming practices. Students must submit a report explaining their code and algorithms, along with presenting their solution.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    1K views3 pages

    DSTR Assignment Question APU

    Uploaded by

    Alvin Alphius Jeffrey
    This document outlines requirements for developing a food order and delivery system. The system must allow customers to place orders that include multiple items, and store delivery information. Orders should be searchable and editable by order number or customer name. The most recently placed orders must be viewable first, and staff should fulfill orders sequentially without skipping any. The system needs validation rules and good programming practices. Students must submit a report explaining their code and algorithms, along with presenting their solution.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    You are on page 1of 3

    FOOD ORDER AND DELIVERY SYSTEM

    This project requires you to develop an Ordering System to handle all the primary
    information of the customer orders. A computer application is needed for their customer
    service personnel to process purchases that require delivery to their customers. The
    system must have the following functionalities:

    a) The system should contain (at least) the following options:


     Create a new order
     Search for an order
    i. Delete an order
    ii. Modify an order
     View orders information (most recent order must be viewed first)
    i. Fulfill order

    b) The following data is required when creating a new order: order number, item
    code(s), item type(s) (ie. burger, spaghetti, coke, and etc.), quantity, cost per item,
    delivery information (see part c) for more information), fulfilled order (assigned
    ‘N’ by default and denotes that the order has not been fulfilled), and total cost of
    the purchase (including delivery charges). Note that a single purchase may
    contain multiple items.

    c) The delivery information for a new order should contains the following
    information: recipient name, address, telephone number, and delivery charges.
    The delivery charge is 5% of the total cost of the item(s) purchased.

    d) The customer service personnel should be able to search for a particular order by:
     Order number
     Recipient name
    Once the order is found, the customer service personnel should be given the
    option to modify the data for a particular attribute (data field), or to delete an
    order. Note that only the recipient name, address and/or telephone number
    attributes may be modified.

    e) When viewing orders, the most recent order (based on order number) must be
    displayed first. The customer service personnel should then fulfill the orders (in
    sequence starting from the most recent order) by updating the fulfilled order field
    to ‘F’. Note that the customer service personnel should not be allowed to skip any
    order when fulfilling the orders. The fulfilled order will then be sent to the
    delivery list and automatically removed from the orders list.

    f) Include all validations required for the system and use good programming
    practices (eg. indentation, meaningful identifier names, comments, and etc.).
    Assignment Requirements
    You are required to submit a hardcopy as well as a softcopy of assignment report and
    source code. The report should contain:
    - Detailed explanation of the data structures and classes created, with proper
    justification on your decisions (include source code defining classes, data members,
    and method headers only).
    - Brief explanation about the algorithms used to implement the functionalities stated
    above (include code snippets of important parts of implementation).
    - Source code of the main function, with screenshots showing program’s input and
    output interactions.
    You have to present your assignment solution and answers to the lecturer during a
    Q&A session that will be conducted after the hand-in date.

    If you use some code which has been taken or adapted from another source (book,
    magazine, internet, forum, etc.) then this must be cited and referenced using Harvard
    Referencing Style within your source code, and this must be mentioned explicitly in the
    report. Failure to reference code properly will be treated as plagiarism. Automated tools
    for checking code similarities among submissions will be used, and all detected cases will
    be treated as cheating.

    Assessment marks are divided as follows:


    Implementation Quality Documentation Presentation
    Marks % 50% 30% 20%

    Submission deadline: October 14th 2019

    What You Need to Hand In?


    1. You are required to hand in the individual assignment report on or before the due
    date.

    2. The attached CD should include a softcopy of the report, in addition to the C++
    files of the programs. The organization of files and folders must adhere to the
    following instructions precisely:
     A folder named “StudentFirstName-StudentID” should contain the report
    file (Microsoft Word), and the C++ (*.cpp / *.h) files ONLY. All additional
    project files (especially if you use Visual Studio) should be removed.
     Make sure to DELETE all non-source-code files, including executables
    (*.exe).

    3. You should present an executable solution during Q&A session to demonstrate


    program execution, the working of the data structure, your understanding of the
    code, and ability to modify / fix it.

    4. You have to submit your assignment with Coursework Submission and Feedback
    Form (CSFF) attached.
    Marking Criteria:
    The program submitted will be evaluated according to the following performance criteria:

    Distinction (90% and above)


    - Program compiles and executes perfectly
    - At least 90% of the required functionalities are correctly implemented
    - Efficient data structures and\or algorithms are used in the implementation
    - Clear coding style and structure, and code is properly commented
    - Functionalities are fully tested/validated in program execution

    Credit (70% – 89%)


    - Program compiles and executes
    - Between 70% and 90% of the required functionalities are correctly implemented
    - Implementation uses a data structure or algorithm that is not most efficient
    - Clear coding style, and code is properly commented
    - Functionalities are not fully tested/validated in program execution

    Pass (50% - 69%)


    - Program compiles perfectly and executes
    - Between 50% and 70% of the required functionalities are correctly implemented
    - Implementation uses inefficient data structures or algorithms
    - Unclear coding style, or code is not properly commented
    - Functionalities are not full tested/validated in program execution, or produce errors in
    some cases

    Marginal Fail (30% - 49%)


    - Program does not compile or run, but coding logic is almost correct
    - Between 30% and 50% of the required functionalities are correctly implemented
    - Implementation uses inefficient data structures or algorithms
    - Unclear coding style, and no comments provided
    - Functionalities are not tested/validated in program execution

    Fail (below 30%)


    - Program is not given
    - Program does not compile or run
    - Less than 30% of the required functionalities are implemented
    - Implementation uses very inefficient data structures or algorithms
    - No proper code structure and no comments provided

    You might also like