Discussion of “Accounting for Software Development Costs and the Cost of Capital: Evidence from IPO Underpricing in the Software Industry”

2008 ◽  
Vol 23 (2) ◽  
pp. 305-310
Author(s):  
John R. M. Hand
2005 ◽  
Vol 80 (4) ◽  
pp. 1211-1231 ◽  
Author(s):  
Emad Mohd

I investigate the impact of implementing SFAS No. 86, which provides an exception to the GAAP requirement of the immediate expensing of research and development (R&D), on information asymmetry. Using bid-ask spread and share turnover as proxies for information asymmetry, I find that after the introduction of SFAS No. 86, information asymmetry decreases for software firms relative to that of other high-tech firms. Within the software industry, I find that information asymmetry is significantly lower for firms that capitalize (capitalizers) than for those who expense (expensers) software development costs. Thus, accounting for software development costs per SFAS No. 86 reduces information asymmetry and, consequently, the cost of capital. As well, investors' uncertainty about the future benefits of software development costs is reduced when firms capitalize these costs.


Author(s):  
Subhas C. Misra ◽  
Vinod Kumar ◽  
Uma Kumar

The last few decades—especially the end of 20th century and the beginning of 21st century—have shown an increase in the interest in automation of different activities. Automation is dependent in its core on sound functional software. The complexity of software development has increased significantly over the years. Articles showing the failure of projects in the software industry are not surprising. Standish Group (1994) reports show that about 53% of projects get completed, but they do not meet the cost and schedule requirements, and about 31% are canceled before the completion of the projects. These failure reports are significantly alarming. With the tremendous growth in the complexity of software development in the last 10 to 15 years, the management of risks in software engineering activities is becoming an important and nontrivial issue from three perspectives: project, process, and product. Therefore, researchers and practitioners are continually trying to find effective risk management approaches. This article should help the academicians, researchers, and practitioners interested in the area of risk management in software engineering to gain an overall understanding of the area.


Author(s):  
Ignacio Velez-Pareja ◽  
Joseph Tham
Keyword(s):  

2011 ◽  
Author(s):  
Huong Giang (Lily) Nguyen ◽  
Xiangkang Yin ◽  
Luong Hoang Luong

Sign in / Sign up

Export Citation Format

Share Document