A procedure for risk management with reference to software

Towards management of software as assets: A literature review with additional sources

“…Surely, if the issue is a ''bug'' then quality literature should be helpful; perhaps even show a direction to solve the lead-in question of ''what did we learn'' or ''what should have been learned'' from it. Unfortunately, this has not been the case; prior Software Quality works included [30,[35][36][37][38]207]. Quite a bit of literature was perused to make certain that, in prior readings, nothing was missed that might be relevant here.…”

“…Generally accepted Software Project Management textbooks, such as Hughes and Cotterell [116], Humphrey [117], Kemerer [132] and Royce [198] do not add anything to this. What is still missing is a well thought out view of software risk - [31][32][33]6,233,234,177] add this dimension. There have been numerous attempts to formulate a much more rigorous methodology; for instance Keidar [129] with an attempt to link Risk Management to Markov Chains.…”

Integrated IT management tool kit

“…This linkage has far-reaching importance vis-à-vis the handling of trends and governing management direction and corporate thinking, particularly, but not exclusively, concerning IT's contribution to overall organizational performance. Many technology and business trends affect IT, IT departments, and IT inventory and management [3]. Corporate decisions about delivering IT services have to be based on business considerations, including services to be delivered, service priorities, resource allocation, cost-effective delivery methods, and economic efficiency.…”

“…Typically, efforts to improve an organization's ability to develop, deploy, and maintain software-dependent systems focus on individual productivity measures rather than on strategic (corporate) assets and needs [2,3]. This view is too simplistic, as software (whether enterprise or home) is no longer developed by individuals.…”