C# Sharp Language PLease Assignment 2 – Stack and Queues Weight: 10% Late Submission Policy: Late submissions will be pe

Business, Finance, Economics, Accounting, Operations Management, Computer Science, Electrical Engineering, Mechanical Engineering, Civil Engineering, Chemical Engineering, Algebra, Precalculus, Statistics and Probabilty, Advanced Math, Physics, Chemistry, Biology, Nursing, Psychology, Certifications, Tests, Prep, and more.
Post Reply
answerhappygod
Site Admin
Posts: 899603
Joined: Mon Aug 02, 2021 8:13 am

C# Sharp Language PLease Assignment 2 – Stack and Queues Weight: 10% Late Submission Policy: Late submissions will be pe

Post by answerhappygod »

C# Sharp Language PLease
Assignment 2 – Stack and Queues
Weight: 10%
Late Submission Policy: Late submissions will
be penalized, 5% per day up to 5 working days, and will not be
accepted after 5 days after the due date.
Plagiarism: Please note that if your solution
was found to match another student, then I am required to grade
your work zero and report to Associate Dean.
Task
In this assignment, you are tasked with creating a simple game.
In this game, the user is required to guess all numbers in a number
sequence that was generated randomly. For a higher score, the user
has to guess all the numbers in the least number of steps.
You can use the following steps to complete this game:
See the sample output below:
Deliverables
Grading
This assignment will be graded based upon the following
criteria:
Program
100%
Excellent
100%
Good
75%
Fair
50%
Poor
25%
Program execution
20%
Program executes correctly with no syntax or runtime errors,
The program executes with a minor (easily fixed error)
Program executes with a somewhat minor (somewhat easily fixed
error)
Program does not execute
Correct output 20%
Program displays correct output with no errors
Output has minor errors
Output has multiple errors
Output is incorrect
Design of output 16%
Program displays more than expected
Program displays minimally expected output
Program does not display the required output
Output is poorly designed
Design of logic 20%
Program is logically well designed
Program has slight logic errors that do not significantly affect
the results
Program has significant logic errors
Program is incorrect
Standards
14%
Program is stylistically well designed
Few inappropriate design choices (i.e., poor variable names,
improper indentation)
Several inappropriate design choices (i.e., poor variable names,
improper indentation)
Program is poorly written
Documentation 10%
Program is well documented
Missing one required comment
Missing two or more required comments
Most or all documentation missing
Join a community of subject matter experts. Register for FREE to view solutions, replies, and use search function. Request answer by replying!
Post Reply