Answer:
Here is the Python program:
COOKIES_PER_BAG = 40 #sets constant value for bag of cookies
SERVINGS_PER_BAG = 10 #sets constant value for serving in bag
CALORIES_PER_SERVING = 300 #sets constant value servings per bag
cookies = int(input("How many cookies did you eat? ")) #prompts user to input how many cookies he or she ate
totalCalories = cookies * (CALORIES_PER_SERVING / (COOKIES_PER_BAG / SERVINGS_PER_BAG)); #computes total calories consumed by user
print("Total calories consumed:",totalCalories) #displays the computed value of totalCalories consumed
Explanation:
The algorithm is:
- Start
- Declare constants COOKIES_PER_BAG, SERVINGS_PER_BAG and CALORIES_PER_SERVING
- Set COOKIES_PER_BAG to 40
- Set SERVINGS_PER_BAG to 10
- Set CALORIES_PER_SERVING to 300
- Input cookies
- Calculate totalCalories: totalCalories ← cookies * (CALORIES_PER_SERVING / (COOKIES_PER_BAG / SERVINGS_PER_BAG))
- Display totalCalories
I will explain the program with an example:
Lets say user enters 5 as cookies he or she ate so
cookies = 5
Now total calories are computed as:
totalCalories = cookies * (CALORIES_PER_SERVING / (COOKIES_PER_BAG / SERVINGS_PER_BAG));
This becomes:
totalCalories = 5 * (300/40/10)
totalCalories = 5 * (300/4)
totalCalories = 5 * 75
totalCalories = 375
The screenshot of program along with its output is attached.
Answer:
1)engagement
2)clarity
, consistency
, simplicity
3)consistency
4)clarity
,consistency
,simplicity
Explanation:
The answers of the four parts are as mentioned above.
If the game is engaging the interest of the interested players will be retained certainly.
If it is clear, consistent and simple, then you will definitely be able to retain the kind of fun the game will be creating in the intended player audiences.
If its consistent, then the game will certainly require one type of approach.
And if its clear, consistent and simple then the game will be providing the flexibility for the future modification.
Hence the above answer.
Answer:
Notifying the errors is always useful .
Explanation:
The errors should always be notified to the developer. It is useful and is important. When we provide notifications on the screen, it helps the user and it can be used to provide feedback. In regard to developmental work, it has to be important and confidential and we use the help of email to inform or notify errors to the organization. This will help the company from negative criticism and helps the company perform better. We can also write an error log when we face the same error again and again even after notifying the developer organization. This helps to put a reminder to the organization that immediate check has to be dome and eliminate the error from the source.
Some disadvantages are if we do not keep timer implementation, the alert keeps on popping on the screen, which is irritable.
Soporte ,Protección, Movimiento, Homeostasis mineral ,<span>Producción de células sanguíneas</span><span />
Answer:
yes
Explanation:
the faster the processor the better the computer loads things and works faster, there's little to no latency depending on the wifi
