Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assessment Results #1

Open
28 of 30 tasks
timomitchel opened this issue Aug 4, 2019 · 0 comments
Open
28 of 30 tasks

Assessment Results #1

timomitchel opened this issue Aug 4, 2019 · 0 comments

Comments

@timomitchel
Copy link

timomitchel commented Aug 4, 2019

Checklist/Rubric

Part I: Creating Directories and Files; Initializing Git and Pushing to GitHub

  • I named my directories correctly.
  • I named my files correctly.
  • I structured my files and directories correctly.
  • I made one initial commit.
  • I pushed my initial commit to GitHub.

Part II: Top Down Design

  • I broke down larger processes into smaller layers.
  • I added and committed my changes with a properly formatted commit message starting with a present-tense verb and a capital letter.
  • I pushed my changes to Github.

Part III: Classes, Objects, Attributes, and Methods

Class #1 Checklist

  • I structured and named my directories and files correctly.
  • The four attributes I chose for Class Assessment Results #1 represent properties or characteristics.
  • I identified the data type (string, integer, boolean, array, hash/object, datetime) for attributes in Class 1.
  • The four methods I chose for Class Assessment Results #1 represent behaviors or actions.
  • I described what the methods do in Class 1, including which attributes they use or modify.
  • I added and committed the class_1.txt file separately with a properly formatted commit message.

Class #1 Example Object Checklist

  • The object I chose for Class 1 is an instance of this class.
  • I listed the values for each attribute of this object.
  • I listed the results of each method for this object.
  • I added and committed the class_1_example_object.txt file separately with a properly formatted commit message.

Class #2 Checklist

  • The four attributes I chose for Class #2 represent states or characteristics.
  • I identified the data type (string, integer, boolean, array, hash/object, datetime) for attributes in Class 2.
  • The four methods I chose for Class #2 represent behaviors or actions.
    buy_the_restaurant is not something that the Restaurant class would or could do. A Person or Patron class would have such behavior or methods available. We also want present tense verbs, so close_early instead of closing_early.
  • I described what the methods do in Class 2, including which attributes they use or modify.
  • I added and committed the class_2.txt file separately with a properly formatted commit message.
    We would like to see another class other than Restaurant that describes something you could find in a restaurant. Some examples could be Employee, Menu, or Bar.

Class #2 Example Object Checklist

  • The object I chose for Class 2 is an instance of this class.
  • I listed the values for each attribute of this object.
  • I listed the results of each method for this object.
  • I added and committed the class_2_example_object.txt file separately with a properly formatted commit message.

Hey Zac! This is really close, but I think that the directions might have confused you. Your first class of Restaurant is great, but for the second class we want you to choose something else that you would find in a restaurant. We don't want the same class for both examples.Please add a file class_3.txt and a file class_3_example_object.txt with 4 attributes and 4 methods that belong to the class and example object just like you did with the first class and example object of Restaurant. Add, commit, and push these changes, and let us know when you've made the updates. Thanks Zac!

Assessment Results

  • Technical Ready
  • Pending
  • Not Technical Ready
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant