Answer:
sum, price, count
Explanation:
Programmers should use significant names for the variables.
Not only it makes it easier for them to remember what kind of information is stored in each variable, but it also makes life simpler for anyone who would read the code later.
Names like sum, price and count are significant names ( assuming they actually hold this kind of data), and will make the re-reading of the program code much easier.
Answer:
Kanban System
Explanation:
Kanban can be regarded as one of Lean tools which is been designed to carry out reduction of the idle time in a production process. The idea or concept behind this Kanban system, is to make delivery of needs of the process needs at exactly the it needs it. Kanban can be reffered to as visual cards. Kanban can as well be explained as scheduling system that is used for lean manufacturing as well as just-in-time manufacturing. Taiichi Ohno, who was an industrial engineer at Toyota carried out development of kanban so that there could be an improved manufacturing efficiency. Kanban is considered as one method used to achieve JIT.
It should be noted that Kanban System is One tool of Lean that is a container, card, or visual limit that signals when work needs to be done or replenishment needs to be initiated .
Answer:
a). SLE =$37.5
b). ARO =75
c). ALE = $2,812.5
Explanation:
a).Single loss Expectancy (SLE) is starting point in determining the single loss of an asset that will occur and calculated this;
SLE = asset value * exposure factor.
Asset value =$500,
Exposure factor is simply the percentage of asset lost.
In this case out of 1000 phones, 75 were damaged or loss.
In percentage;
75 ÷ 1000 =0.075, 0.075×100=7.5%(exposure factor).
Therefore,
SLE = $500×7.5%= $37.5.
b). ARO - Annual Rate of Occurrence is the number of times a threat on a single asset is expected to occur in one year.
In the case the damage or loss occured in 75 devices in one year.
c). ALE - Annualized loss Expectancy is the product of SLE and ARO.
Therefore;
ALE = $37.5 × 75 = $2,812.5.
