Computer Associates 2007 Annual Report Download - page 67

Download and view the complete annual report

Please find page 67 of the 2007 Computer Associates annual report below. You can navigate through the pages in the report by either clicking on the pages listed below, or by using the keyword search tool below to find specific information within the annual report.

Page out of 144

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144

The SFAS No. 142 goodwill impairment model is a two-step process. The first step is used to identify potential impairment by
comparing the fair value of a reporting unit with its net book value (or carrying amount), including goodwill. If the fair value
exceeds the carrying amount, goodwill of the reporting unit is considered not impaired and the second step of the impairment
test is unnecessary. If the carrying amount of a reporting unit exceeds its fair value, the second step of the goodwill impairment
test is performed to measure the amount of impairment loss, if any.The second step of the goodwill impairment test compares
the implied fair value of the reporting unit’s goodwill with the carrying amount of that goodwill. If the carrying amount of the
reporting unit’s goodwill exceeds the implied fair value of that goodwill, an impairment loss is recognized in an amount equal
to that excess. The implied fair value of goodwill is determined in the same manner as the amount of goodwill recognized in a
business combination. That is, the fair value of the reporting unit is allocated to all of the assets and liabilities of that unit
(including any unrecognized intangible assets) as if the reporting unit had been acquired in a business combination and the
fair value of the reporting unit was the purchase price paid to acquire the reporting unit.
Determining the fair value of a reporting unit under the first step of the goodwill impairment test, and determining the fair
value of individual assets and liabilities of a reporting unit (including unrecognized intangible assets) under the second step of
the goodwill impairment test, is judgmental in nature and often involves the use of significant estimates and assumptions.
These estimates and assumptions could have a significant impact on whether an impairment charge is recognized and the
magnitude of any such charge. Estimates of fair value are primarily determined using discounted cash flow and are based on
our best estimate of future revenue and operating costs and general market conditions. These estimates are subject to review
and approval by senior management. This approach uses significant assumptions, including projected future cash flow, the
discount rate reflecting the risk inherent in future cash flow, and a terminal growth rate. There was no impairment charge
recorded with respect to goodwill for fiscal year 2007.
The carrying value of capitalized software products, both purchased software and internally developed software, and other
intangible assets, are reviewed on a regular basis for the existence of internal and external facts or circumstances that may
suggest impairment.The facts and circumstances considered include an assessment of the net realizable value for capitalized
software products and the future recoverability of cost for other intangible assets as of the balance sheet date. It is not possible
for us to predict the likelihood of any possible future impairments or, if such an impairment were to occur, the magnitude
thereof.
Intangible assets with finite useful lives are subject to amortization over the expected period of economic benefit to the
Company. We evaluate the remaining useful lives of intangible assets to determine whether events or circumstances have
occurred that warrant a revision to the remaining period of amortization. In such cases the remaining carrying amount of the
intangible asset is amortized over the revised remaining useful life.
We performed our annual assessment during the fourth quarter of fiscal year 2007 and concluded that an impairment charge
of approximately $12 million, relating to certain identifiable intangible assets that were not subject to amortization, which
were acquired in conjunction with a prior year acquisition should be recorded. For fiscal year 2007, the impairment charge was
reported in the “Restructuring and other” line item in the Consolidated Statements of Operations. The balance of assets with
indefinite lives at March 31, 2007 and 2006 was $14 million and $26 million, respectively.
Accounting for Business Combinations
The allocation of purchase price for acquisitions requires extensive use of accounting estimates and judgments to allocate the
purchase price to the identifiable tangible and intangible assets acquired, including in-process research and development, and
liabilities assumed based on their respective fair values.
Product Development and Enhancements
We account for product development and enhancements in accordance with SFAS No. 86, “Accounting for the Costs of
Computer Software to be Sold, Leased, or Otherwise Marketed. SFAS No. 86 specifies that costs incurred internally in researching
and developing a computer software product should be charged to expense until technological feasibility has been established
for the product. Once technological feasibility is established, all software costs are capitalized until the product is available for
general release to customers. Judgment is required in determining when technological feasibility of a product is established
and assumptions are used that reflect our best estimates. If other assumptions had been used in the current period to estimate
55