Answer:
Equivalent units
Materials 10,200
Covnersion Cost 9, 100
Explanation:
![\left[\begin{array}{cccc}&$Physical Units&$Materials&$Conversion\\$Beginning&2,000&0.6&0.4\\$Transferred out&9,000&&\\$Ending&3,000&0.8&0.3\\$Equivalent Units&&10,200&9,100\\\end{array}\right]](https://tex.z-dn.net/?f=%5Cleft%5B%5Cbegin%7Barray%7D%7Bcccc%7D%26%24Physical%20Units%26%24Materials%26%24Conversion%5C%5C%24Beginning%262%2C000%260.6%260.4%5C%5C%24Transferred%20out%269%2C000%26%26%5C%5C%24Ending%263%2C000%260.8%260.3%5C%5C%24Equivalent%20Units%26%2610%2C200%269%2C100%5C%5C%5Cend%7Barray%7D%5Cright%5D)
The equivalent units will be calcualte as follow:
transferred out
ending x completion
<u> (beginning x completion) </u>
Equivalent units
<u>Materials</u>
9,000 + 3,000 x 80% - 2,000 x 60% = 10,200
<u>Conversion Cost</u>
9,000 + 3,000 x 30% - 2,000 x 40% = 9,100
Answer:
Correct option is (d)
Explanation:
Current liabilities are part of obligations of the organization that it needs to meet within one year. Current maturities of long term debt represents that part of long term debt such a bonds or loans that need to be paid of in the current financial year.
It is shown as a separate item in the balance sheet as it is paid off using highly liquid asset such as cash.
Answer:
26 packages
Explanation:
Given that:
The demand D = 186 packages in a week
Standard deviation = 13packages
The lead time L = 1.5 weeks
Order quantity Q = 750 packages
The Confidence service Level = 0.95
At the service level (SL) if we find the P(Z) of the SL using Excel, we have:
P(Z) = NORMSINV(0.95)
P(Z) = 1.64
Thus;
the safety stock = Z × SD√L
= 1.64 \times 13 (1.224745)
= 1.64\times15.92
= 26.11156
≅ 26 packages
Answer:
The last option is wrong, the correct option to that question is: Extreme Programming.
And the correct answer is that option.
Explanation:
To begin with, the name of <em>"Extreme Programming"</em> refers to a specific methodology of development of software that mainly focuses in the improvement of software quality and the responsiveness to changing customers requirements. Moreover, this methodology best fits in the cases where the system project comes with unclear requirements and where there is a short time schedule due to the fact that as a type of agile software development it advocates frequent releases in short time cycles that are primarily focus on introducing checkpoints in where the requirements of the consumers who are unclear can be adopted.
