The market for a certain item can go down. It can simply be caused by too much of a supply and not enough demand which can usually cause a company to go into debt if they specialize in one product only (e.g. fuels)
Answer:
Entries during the first month would include the following:
Account Title Debit Credit
Interest Expenses $40,260
(1342000*3%)
Kwik $40,260
Cash $459,000
Discount $1,550
Account Receivable $460,550
Sales Return $5,300
Account Receivable $5,300
Allowances for Doubtful Debt $$11,880
Account Receivable $$11,880
Answer:
From the calculation below Up-Towne Movers just paid a dividend of $3.13
Explanation:
The price of share=D1/r-g
The Do is the dividend just paid which is the unknown in the equation
g is the dividend growth rate of 4.3%
r is the required return of 11.1%
The share price is $46.00
$46=Do/(11.1%-4.3%)
46=Do/0.068
by cross-multiplication the equation becomes
$46*0.068
=Do
Do=$46*0.068
Do=$3.13
The dividend just paid by Up-Towne Movers is $3.13 as calculated above from the share price equation
Answer:
a)
To my view, the MD viewpoint is better. In companies the existing process is usually analyzed and the pain points identified whenever there is a need for change. The new system is simply a change to the existing system. The stakeholders' specific needs are not completely addressed. The MD calls for a collection of and analysis of demands from scratch to share its needs , requirements and inhibitions between the principal stakeholders. The CIO and their staff would be able to assess in the requirements review process what worked and what did not work well for the organization.
In assessing the current process, the CIO and his team will align their thinking process with the pain points and correct the existing system. They are not going to build the system in a fresh light. A new system that meets the needs of stakeholders can be developed. For everybody, this is a win-win situation. The point of view of MD is therefore more logical and related.
b)
In the particular case, the most logical and comprehensive system analysis method is:
Primary stakeholder requirements collection: Primary stakeholders using the system must be consulted on their specific requirements and needs. It is also necessary to consider the limitations identified by stakeholders.
Comprehension of existing system and pain points: the current system can be analysed based on requirements collection and pain points can be emphasized in the current system.
A new system that will win for everyone: the new system must primarily comply with the needs of the stakeholders.
Presentation and approval of the system blueprint to stakeholders
Development and implementation of the system: system development can be carried out by the agile method of sprinting.
Monitoring and control of the system: to check for performance deviations, the system implemented should be observed. In order to monitor deviations, specific intervention can be implemented.
