<span>High Shore Inc. adopts a new technology purely out of social pressure. In this case, High Shore Inc. would be classified as part of the early group of adopters of new technology. Those that adopt a new technology early on, typically tend to be more profitable but also more critical. Though the adaptation came from social pressure, High Shore Inc. still has expectations that the technology needs to meet to maintain their companies growing needs. </span>
        
             
        
        
        
Answer:
the  true cash balance as on June 30 is  $79,039
Explanation:
The computation of the true cash balance as on June 30 is given below:
Unadjusted Balance as Per Bank Statement on Jun 30  $81,500
Add: Deposit in Transit Jun   $3,150
Less: Outstanding Check Jun30	$(5,611)
True Cash Balance As on Jun 30	$79,039
hence, the  true cash balance as on June 30 is  $79,039
 
        
             
        
        
        
<span>data inconsistency
Let's look at the available options and see what makes or does not make sense.
data normalization
* Data normalization is the process of having each piece of data in the database entered only once. If you need the same data element multiple times, you put the data element into a table and each time you need that element, you make a reference to that table which holds the only copy of that piece of data. This process is used to simplify making changes to that data element. If the element changes, you make the change to a single piece of data in the database and that change is reflected everywhere else in the database that uses that element. That's not the issue with this problem, so it's a bad choice.
data accuracy
* Close, but not quite. The data in the database is accurate and does have the correct address and a correct variant of the person's name. So this isn't the right choice either.
data redundancy
* This is a problem that addressed by data normalization. And just like data normalization doesn't address this question's problem, neither does this address it. So another bad choice.
data inconsistency
* BINGO! The root issue is that minor variations in the format of a name result in what the database considers to be an unique name. And hence an unique person. This is the correct choice.
data duplication
* Another name for redundancy. So another bad choice.</span>
        
             
        
        
        
Answer:
Cost of asset less expected residual value
/Expected useful life (years
Explanation:
Where the depreciable amount is charged in equal amounts to each reporting period over the expected useful life of the asset, this method of calculating depreciation is known as straight line method.
The yearly percentage of cost lost through accrued depreciation in straight line method is found by following formula:
Cost of asset less expected residual value
/Expected useful life (years)