Modeling and Simulation - naughty or nice

From Computer Science Wiki
Revision as of 13:45, 7 December 2018 by Mr. MacKenty (talk | contribs) (Created page with "right|frame|This a problem set for you to work through <ref>http://www.flaticon.com/</ref> This is a problem set. Some of these are easy, others are far m...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
This a problem set for you to work through [1]

This is a problem set. Some of these are easy, others are far more difficult. The purpose of these problems sets are:

  1. to build your skill applying computational thinking to a problem
  2. to assess your knowledge and skills of different programming practices


What is this problem set trying to do[edit]

To exercise your thinking about modeling and simulation.

The Problem[edit]

As you think about modeling and simulation, you should build two different models which mathematically represent what factors should contribute to being "bad" or "good". Remember, a model has:

  1. I have identified important features of whatever events I hope to represent.
  2. I identified rules that control those features and their relationships.
  3. I have expressed those rules with math.
  4. I have adjusted for how likely each factor is.

Once you have developed a model, please build a simulation for it. We are primarily concerned with the probability of being categorized as "naughty" or "nice". We are also concerned with "how much is any one person "naughty or nice".

How you will be assessed[edit]

Your solution will be graded using the following axis:


Scope

  • To what extent does your code implement the features required by our specification?
  • To what extent is there evidence of effort?

Correctness

  • To what extent did your code meet specifications?
  • To what extent did your code meet unit tests?
  • To what extent is your code free of bugs?

Design

  • To what extent is your code written well (i.e. clearly, efficiently, elegantly, and/or logically)?
  • To what extent is your code eliminating repetition?
  • To what extent is your code using functions appropriately?

Style

  • To what extent is your code readable?
  • To what extent is your code commented?
  • To what extent are your variables well named?
  • To what extent do you adhere to style guide?

References[edit]

A possible solution[edit]

Click the expand link to see one possible solution, but NOT before you have tried and failed!

not yet!