Note 2 - Significant Accounting Policies

6 Months Ended

Jun. 30, 2015

Accounting Policies [Abstract]

Significant Accounting Policies [Text Block]

2. Significant Accounting Policies

Use of Estimates

The preparation of financial statements in conformity with GAAP requires us to make estimates and assumptions that affect the reported amounts of assets and liabilities and disclosure of contingent assets and liabilities at the date of the financial statements, and the reported amounts of revenues and expenses during the reporting period. These estimates include: the amount of stock-based compensation expense; the allowance for doubtful accounts; the estimated lives, valuation, and amortization of intangible assets (including capitalized software); depreciation of long-lived assets; valuation of warrants; post-employment benefits, and accruals for liabilities. While we believe that such estimates are fair, actual results could differ materially from those estimates.

Revenue Recognition

We market and license our products indirectly through channel distributors, independent software vendors (“ISVs”), value-added resellers (“VARs”) (collectively, “resellers”) and directly to corporate enterprises, governmental and educational institutions and others. Our product licenses are perpetual. We also separately sell intellectual property licenses, maintenance contracts, which are comprised of license updates and customer service access, as well as other products and services.

Software license revenues are recognized when:

● Persuasive evidence of an arrangement exists, (i.e., when we sign a non-cancellable license agreement wherein the customer acknowledges an unconditional obligation to pay, or upon receipt of the customer’s purchase order), and

● Delivery has occurred or services have been rendered and there are no uncertainties surrounding product acceptance (i.e., when title and risk of loss have been transferred to the customer, which occurs when the media containing the licensed program(s) is provided to a common carrier or, in the case of electronic delivery, when the customer is given access to the licensed program(s)), and

● The price to the customer is fixed or determinable, as typically evidenced in a signed non-cancellable contract, or a customer’s purchase order, and

● Collectability is probable. If collectability is not considered probable, revenue is recognized when the fee is collected.

Revenue recognized on software arrangements involving multiple deliverables is allocated to each deliverable based on vendor-specific objective evidence (“VSOE”) or third party evidence of the fair values of each deliverable; such deliverables include licenses for software products, maintenance, private labeling fees, and customer training. We limit our assessment of VSOE for each deliverable to either the price charged when the same deliverable is sold separately or the price established by management having the relevant authority to do so, for a deliverable not yet sold separately.

If sufficient VSOE of the fair value does not exist so as to permit the allocation of revenue to the various elements of the arrangement, all revenue from the arrangement is deferred until such evidence exists or until all elements are delivered. If VSOE of the fair value does not exist, and the only undelivered element is maintenance, then we recognize revenue on a ratable basis. If VSOE of the fair value of all undelivered elements exists but does not exist for one or more delivered elements, then revenue is recognized using the residual method. Under the residual method, the fair value of the undelivered elements is deferred and the remaining portion of the arrangement fee is recognized as revenue.

Certain resellers (“stocking resellers”) purchase product licenses that they hold in inventory until they are resold to the ultimate end user (an “inventory stocking order”). At the time that a stocking reseller places an inventory stocking order, no product licenses are shipped by us to the stocking reseller; rather, the stocking reseller’s inventory is credited with the number of licenses purchased and the stocking reseller can resell (issue) any number of licenses from their inventory at any time. Upon receipt of an order to issue a license(s) from a stocking reseller’s inventory (a “draw down order”), we will ship the license(s) in accordance with the draw down order’s instructions. We defer recognition of revenue from inventory stocking orders until the underlying licenses are sold and shipped to the end user, as evidenced by the receipt and fulfillment of the stocking reseller’s draw down order, assuming all other revenue recognition criteria have been met.

There are no rights of return granted to resellers or other purchasers of our software products.

Revenue from maintenance contracts is recognized ratably over the related contract period, which generally ranges from one to five years.

All of our software licenses are denominated in U.S. dollars.

Deferred Rent

The lease for our office in Campbell, California, as amended (See Note 6), contains free rent and predetermined fixed escalations in our minimum rent payments. We recognize rent expense related to this lease on a straight-line basis over the term of the lease. We record any difference between the straight-line rent amounts and amounts payable under the lease as part of deferred rent in current or long-term liabilities, as appropriate.

Incentives that we received upon entering into the lease agreement are recognized on a straight-line basis as a reduction to rent over the term of the lease. We record the unamortized portion of these incentives as a part of deferred rent in current or long-term liabilities, as appropriate.

Postemployment Benefits (Severance Liability)

Nonretirement postemployment benefits, including salary continuation, supplemental unemployment benefits, severance benefits, disability-related benefits and continuation of benefits such as health care benefits, are recognized as a liability and a loss when it is probable that the employee(s) will be entitled to such benefits and the amount can be reasonably estimated. The cost of termination benefits recognized as a liability and an expense includes the amount of any lump-sum payments and the present value of any expected future payments. There was no severance liability reported at June 30, 2015 or December 31, 2014.

Software Development Costs

We capitalize software development costs incurred from the time technological feasibility of the software is established until the software is available for general release, in accordance with GAAP. Such capitalized costs are subsequently amortized as costs of revenue over the shorter of three years or the remaining estimated useful life of the product.

Research and development costs and other computer software maintenance costs related to the software development are expensed as incurred.

Long-Lived Assets

Long-lived assets are assessed for possible impairment whenever events or changes in circumstances indicate that the carrying amounts may not be recoverable, whenever we have committed to a plan to dispose of the assets or, at a minimum, annually. Typically, for long-lived assets to be held and used, measurement of an impairment loss is based on the fair value of such assets, with fair value being determined based on appraisals, current market value, comparable sales value, and discounted future cash flows, among other variables, as appropriate. Assets to be held and used (which assets are affected by an impairment loss) are depreciated or amortized at their new carrying amount over their remaining estimated life; assets to be sold or otherwise disposed of are not subject to further depreciation or amortization. No such impairment charge was recorded during either of the three or six-month periods ended June 30, 2015 or 2014.

Allowance for Doubtful Accounts

We maintain an allowance for doubtful accounts that reflects our best estimate of potentially uncollectible trade receivables. The allowance is based on assessments of the collectability of specific customer accounts and the general aging and size of the accounts receivable. We regularly review the adequacy of our allowance for doubtful accounts by considering such factors as historical experience, credit worthiness, and current economic conditions that may affect a customer’s ability to pay. We specifically reserve for those accounts deemed uncollectible. We also establish, and adjust, a general allowance for doubtful accounts based on our review of the aging and size of our accounts receivable.

The following table sets forth the details of the Allowance for Doubtful Accounts for the three-month periods ended June 30, 2015 and 2014:

	Beginning Balance		Charge Offs		Recoveries		Provision			Ending Balance
2015	$	22,900	$	—	$	—	$	(7,000	)	$	15,900
2014		23,100		—		—		(2,700	)		20,400

The following table sets forth the details of the Allowance for Doubtful Accounts for the six-month periods ended June 30, 2015 and 2014:

	Beginning Balance		Charge Offs		Recoveries		Provision			Ending Balance
2015	$	32,600	$	—	$	—	$	(16,700	)	$	15,900
2014		42,000		—		—		(21,600	)		20,400

Concentration of Credit Risk

For the three and six-month periods ended June 30, 2015 and 2014, respectively, we considered the customers listed in the following tables to be our most significant customers. The tables set forth the percentage of sales attributable to each customer during the periods presented, and the respective customer’s ending accounts receivable balance as a percentage of reported accounts receivable, net, as of June 30, 2015 and 2014.

	Three Months Ended June 30, 2015			As of June 30, 2015			Three Months Ended June 30, 2014			As of June 30, 2014
Customer	Sales			Accounts Receivable			Sales			Accounts Receivable
Alcatel-Lucent		7.6	%		22.3	%		0.4	%		15.0	%
Centric		5.3	%		4.0	%		8.6	%		8.2	%
Elosoft		15.6	%		1.5	%		7.5	%		10.2	%
Ericsson		0.0	%		0.0	%		8.5	%		16.4	%
G E		1.4	%		4.2	%		12.1	%		23.1	%
Raytheon		19.4	%		28.8	%		1.1	%		0.0	%
Thermo LabSystems		2.2	%		3.6	%		5.0	%		8.6	%
Total		51.5	%		64.4	%		43.2	%		81.5	%

	Six Months Ended June 30, 2015			As of June 30, 2015			Six Months Ended June 30, 2014			As of June 30, 2014
Customer	Sales			Accounts Receivable			Sales			Accounts Receivable
Alcatel-Lucent		4.1	%		22.3	%		4.0	%		15.0	%
Centric		3.6	%		4.0	%		7.1	%		8.2	%
Elosoft		13.1	%		1.5	%		6.9	%		10.2	%
Ericsson		0.3	%		0.0	%		6.8	%		16.4	%
G E		1.6	%		4.2	%		12.5	%		23.1	%
IDS		3.3	%		0.0	%		5.6	%		0.0	%
Raytheon		16.6	%		28.8	%		0.0	%		0.0	%
Total		42.6	%		60.8	%		42.9	%		72.9	%

Derivative Financial Instruments

We currently do not have a material exposure to either commodity prices or interest rates; accordingly, we do not currently use derivative instruments to manage such risks. We evaluate all of our financial instruments to determine if such instruments are derivatives or contain features that qualify as embedded derivatives. All derivative financial instruments are recognized in the balance sheet at fair value. Changes in fair value are recognized in earnings if they are not eligible for hedge accounting or in other comprehensive income if they qualify for cash flow hedge accounting.

Fair Value of Financial Instruments

The fair value of our accounts receivable, accounts payable and accrued liabilities approximate their carrying amounts due to the relative short maturities of these items.

The fair value of warrants at issuance and for those recorded as a liability at each reporting date are determined in accordance with the Financial Accounting Standards Board’s (“FASB”) Accounting Standards Codification (“ASC”) 820, “Fair Value Measurement,” which establishes a fair value hierarchy that prioritizes the assumptions (inputs) to valuation techniques used to price assets or liabilities that are measured at fair value. The hierarchy, as defined below, gives the highest priority to unadjusted quoted prices in active markets for identical assets or liabilities and the lowest priority to unobservable inputs. The guidance for fair value measurements requires that assets, liabilities and certain equity instruments measured at fair value be classified and disclosed in one of the following categories:

● Level 1: Defined as observable inputs, such as quoted (unadjusted) prices in active markets for identical assets or liabilities.

● Level 2: Defined as observable inputs other than quoted prices included in Level 1. This includes quoted prices for similar assets or liabilities in active markets, quoted prices for identical or similar assets and liabilities in markets that are not active, or other inputs that are observable or can be corroborated by observable market data for substantially the full term of the assets or liabilities.

● Level 3: Defined as unobservable inputs to the valuation methodology that are supported by little or no market activity and that are significant to the measurement of the fair value of the assets or liabilities. Level 3 assets and liabilities include those whose fair value measurements are determined using pricing models, discounted cash flow methodologies or similar valuation techniques, as well as significant management judgment or estimation.

As of June 30, 2015, all of our $96,400 Warrants Liability reported at fair value was categorized as Level 3 inputs (See Note 4).

Recent Accounting Pronouncements 

In April 2015, FASB issued Accounting Standards Update (“ASU”) No. 2015-05 “Intangibles—Goodwill and Other—Internal-Use Software (Subtopic 350-40): Customer’s Accounting for Fees Paid in a Cloud Computing Arrangement” (“ASU 2013-05”). The objective of ASU 2015-05 is to provide guidance to reporting entities in the accounting for fees paid in a cloud computing arrangement. Specifically, if a cloud computing arrangement includes a software license, then the entity should account for the software license element of the arrangement consistent with the acquisition of other software licenses. If a cloud computing arrangement does not include a software license, the entity should account for the arrangement as a service contract. The guidance will not change GAAP for an entity’s accounting for service contracts. The amendments in this ASU are effective for annual periods beginning after December 15, 2015, including interim periods within those annual periods. Early adoption is permitted. We are currently evaluating this ASU in order to determine whether or not its adoption will have a material impact on our results of operations, cash flows or financial position.

In August 2014, FASB issued ASU No. 2014-15 “Preparation of Financial Statements - Going Concern (Subtopic 205-40)”. Under U.S. GAAP, continuation of a reporting entity as a going concern is presumed as the basis for preparing financial statements unless and until the entity's liquidation becomes imminent. Preparation of financial statements under this presumption is commonly referred to as the going concern basis of accounting. If and when an entity's liquidation becomes imminent, financial statements should be prepared under the liquidation basis of accounting in accordance with Subtopic 205-30, Presentation of Financial Statements-Liquidation Basis of Accounting. Even when an entity's liquidation is not imminent, there may be conditions or events that raise substantial doubt about the entity's ability to continue as a going concern. In those situations, financial statements should continue to be prepared under the going concern basis of accounting, but the amendments in the update should be followed to determine whether to disclose information about the relevant conditions and events. The amendments in this ASU are effective for the annual period ending after December 15, 2016, and for annual periods and interim periods thereafter. Early application is permitted. We will evaluate the going concern considerations in this ASU, however, at the current period, we do not believe that the Company has met conditions which would subject its consolidated financial statements to additional disclosure.

In June 2014, FASB issued ASU No. 2014-12 “Compensation – Stock Compensation (Topic 718)” (“ASU 2014-12”). The objective of ASU 2014-12 is to resolve the diverse accounting treatment being applied in practice by reporting entities in the accounting for share-based payment awards that require a specific performance target to be achieved in order for employees to become eligible to vest in the awards, particularly those awards whose terms may provide that the performance target could be achieved after the employee completes the requisite service period. That is, the employee would be eligible to vest in the award regardless of whether the employee is rendering service on the date the performance target is achieved. ASU 2014-12 is effective for annual periods and interim periods within those annual periods beginning after December 15, 2015, and earlier adoption is permitted. The share-based payment awards we currently have outstanding which have performance targets do not contain clauses wherein the performance target could be achieved after the employee completes the requisite service period; accordingly, adoption of ASU 2014-12 did not have a material impact on our results of operations, cash flows or financial position.

In May 2014, FASB issued ASU No. 2014-09 “Revenue from Contracts with Customers (Topic 606)” (“ASU 2014-09”). ASU 2014-09 is the end result of a joint project initiated by FASB and the International Accounting Standards Board (“IASB”). IASB is the body that sets International Financial Reporting Standards (“IFRS”). The goal of FASB’s and IASB’s joint project was to clarify the principles for recognizing revenue and to develop a common revenue standard for accounting principles generally accepted in the United States (“GAAP”) and under IFRS. Specifically, ASU 2014-09:

1. Removes inconsistencies and weaknesses in revenue requirements.

2. Provides a more robust framework for addressing revenue issues.

3. Improves comparability of revenue recognition practices across entities, industries, jurisdictions, and capital markets.

4. Provides more useful information to users of financial statements through improved disclosure requirements.

5. Simplifies the preparation of financial statements by reducing the number of requirements to which an entity must refer.

The core principle of ASU 2014-09 is that an entity should recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. ASU 2014-09 is effective for annual reporting periods beginning after December 15, 2017, including interim periods within such annual period. Early adoption is not permitted. We are currently evaluating this ASU in order to determine whether or not its adoption will have a material impact on our results of operations, cash flows or financial position.

In April 2014, FASB issued ASU No. 2014-08 “Presentation of Financial Statements (Topic 205) and Property, Plant and Equipment (Topic 360)” (“ASU 2014-08”). The objective of ASU 2014-08 is to address issues in Subtopic 205-20, “Presentation of Financial Statements – Discontinued Operations”, that gave rise to complexity and difficulties in practice. Generally, ASU 2014-08 is effective for discontinued operations that occur within annual periods beginning on or after December 31, 2014, and interim periods within those years. Early adoption is permitted, but only for discontinued operations that have not been reported in financial statements previously issued or available for issuance. We currently have no discontinued operations to report; consequently, adoption of ASU 2014-08 did not have a material impact on our results of operations, cash flows or financial position.