Titlebook: Software Failure Risk; Measurement and Mana Susan A. Sherer Book 1992 Springer Science+Business Media New York 1992 Processing.Risk Measure

珍爱

书目名称Software Failure Risk影响因子(影响力)




书目名称Software Failure Risk影响因子(影响力)学科排名




书目名称Software Failure Risk网络公开度




书目名称Software Failure Risk网络公开度学科排名




书目名称Software Failure Risk被引频次




书目名称Software Failure Risk被引频次学科排名




书目名称Software Failure Risk年度引用




书目名称Software Failure Risk年度引用学科排名




书目名称Software Failure Risk读者反馈




书目名称Software Failure Risk读者反馈学科排名

BROW

Book 1992al loan system, a funds transfersecuritysystem, and a payables processing system. Her well-written,practicaltext enables users to design original software modules, aswell as tocritically assess commercial software products.

intrude

Applying the Methodology to a Funds-Transfer Security Systemn of wire transfers as well as manual records paralleling the system accounts. software exposure in this environment is relatively low compared to the potential magnitude of exposure because of the effectiveness of these hazard mitigators.

无关紧要

Applying the Methodology to a Payables Processing Systemtesting at a specific installation. Second, the system was developed with a more advanced software language. Finally, because the system is fairly small, a complete report of the results could be included.

SEEK

Introduction crucial to the viability of many organizations. “An increasing portion of our GNP is devoted to the collection, analysis, packaging, movement of information.” Information has become a commodity and it resides in computers (B. Jenkins, quoted in Burgess, 1988).

小母马

Software Failure Riskas physical destruction of hardware, are managed with the same techniques as other risks in our society. Risks associated with the development and use of software, however, pose some special problems. Software is often unique; little historical information is available to analyze its risk. The compl

东西

表两个

Applying the Methodology to a Payables Processing Systemortunities. First, it enabled development guidelines to be provided to the project team as the software was being developed rather than waiting until testing at a specific installation. Second, the system was developed with a more advanced software language. Finally, because the system is fairly sma

nonplus

Apraxia

Software Testingently no methods for proving system correctness, testing is necessary to find inherent faults in the code and gain confidence in the software’s reliability prior to release. Software testing decisions require implicit trade-offs between software quality and cost. Software development managers recogn