high reliability

[article]

Testing Strategies to Increase System Availability

Summary:

The more critical a system is, the more highly available that system needs to be. However, it is very difficult—if not impossible—to measure every way a system can fail or to predict how long it will take to recover. But don’t worry! There are still many test strategies you can employ to understand your system’s failures, reduce downtime, and increase availability.

The more critical a system is, the more highly available that system needs to be. However, it is very difficult—if not impossible—to measure every way a system can fail or to predict how long it will take to recover. But don’t worry! There are still many test strategies you can employ to understand your system’s failures, reduce downtime, and increase availability.

About the author

About the author

Implementing Agile in an FDA-regulated Environment

While many industries have adopted agile, the medical device industry, which develops products for life-critical applications-where quality and reliability are clearly a top-priority, remains largely stuck under the “waterfall.” Medical device firms must comply with FDA regulations that overwhelmingly suggest a controlled, phase-gated approach to software development. Unfortunately, many companies and development organizations interpret FDA regulations to require a steep waterfall.

[article]

Is One Hundred Percent Code Coverage Enough?

Member Submitted
Summary:

This paper defines some commonly used code coverage measures and discusses their strengths, weaknesses, and the relationship between measures. Examples are used to illustrate some measures and to indicate common traps and pitfalls. Light is shed on the confusing nomenclature in the area of code coverage: different names for the same measure; same name for different measures. Finally, recommendations for the usage of code coverage are given.

This paper defines some commonly used code coverage measures and discusses their strengths, weaknesses, and the relationship between measures. Examples are used to illustrate some measures and to indicate common traps and pitfalls. Light is shed on the confusing nomenclature in the area of code coverage: different names for the same measure; same name for different measures. Finally, recommendations for the usage of code coverage are given.

About the author

[article]
[article]

White Paper: Software Performance Test Methodology

Member Submitted
Summary:

This white paper covers a proven performance-testing methodology that was developed from eight years of experience. This paper covers the six phases of this methodology: Assessment, Planning, Scripting, Execution, Analysis, Report, and Feedback; as well as the advantages of following this methodology.

This white paper covers a proven performance-testing methodology that was developed from eight years of experience. This paper covers the six phases of this methodology: Assessment, Planning, Scripting, Execution, Analysis, Report, and Feedback; as well as the advantages of following this methodology.

About the author

[article]

Traceability as a QA planning tool

Member Submitted
Summary:

Rapid prototyping and development techniques combined with Agile development methodologies are pushing the envelope on the best practice of testing early and testing often. Keeping pace with the quick development turn-around and shorter time to market and being adaptive to late changes in requirements requires effective management of quality process. The use of traceability of test artifacts-test cases, test defects, test fixtures-mapped to the requirements-needs, features, use cases and supplementary requirements-as a QA scheduling and planning tool though mentioned in passing and claimed to have been practiced, has been largely overlooked by the industry. This paper looks into such a possibility through the use of a study for software that involves iterative application development practices and tries to bring this aspect of the technique into focus as a QA management tool.

Rapid prototyping and development techniques combined with Agile development methodologies are pushing the envelope on the best practice of testing early and testing often. Keeping pace with the quick development turn-around and shorter time to market and being adaptive to late changes in requirements requires effective management of quality process. The use of traceability of test artifacts-test cases, test defects, test fixtures-mapped to the requirements-needs, features, use cases and supplementary requirements-as a QA scheduling and planning tool though mentioned in passing and claimed to have been practiced, has been largely overlooked by the industry. This paper looks into such a possibility through the use of a study for software that involves iterative application development practices and tries to bring this aspect of the technique into focus as a QA management tool.

About the author

About the author

[article]

Software Triage

Member Submitted
Summary:

At some point in the software development lifecycle, regardless of which model you use, we have to make some tough decisions. What defects do we fix? Which should we let go? How do we decide? Triage is one way!

At some point in the software development lifecycle, regardless of which model you use, we have to make some tough decisions. What defects do we fix? Which should we let go? How do we decide? Triage is one way!

About the author

[article]

Synchronize Distributed Object Cache with SQL Server 2005

Member Submitted
Summary:

NCache lets you cache data closer to your application in the middle-tier so you can reduce expensive trips to the database. This in turn significantly speeds up your application. It also makes it more scalable because the load on your database is reduced allowing it to handle a larger number of clients without any hardware upgrades.

NCache lets you cache data closer to your application in the middle-tier so you can reduce expensive trips to the database. This in turn significantly speeds up your application. It also makes it more scalable because the load on your database is reduced allowing it to handle a larger number of clients without any hardware upgrades.

About the author

[article]

An Effective Production Rollout using a Hub-N-Spoke Release Management Process

Member Submitted
Summary:

In this article the author discusses the time-tested Hub-N-Spoke Release Management process that ensures a holistic view of the code (new or modified) is considered before releasing it into the production environments. This process was used successfully by data management groups of a large financial company. Subsequently the use of this Release Management process resulted in improvements in the code release process.

In this article the author discusses the time-tested Hub-N-Spoke Release Management process that ensures a holistic view of the code (new or modified) is considered before releasing it into the production environments. This process was used successfully by data management groups of a large financial company. Subsequently the use of this Release Management process resulted in improvements in the code release process.

About the author

[article]

Identifying Risks

Member Submitted
Summary:

In this article, Vidya Viswanath discusses how to effectively identify risks. She provides lists of questions that should be asked when identifying and classifying risks.

In this article, Vidya Viswanath discusses how to effectively identify risks. She provides lists of questions that should be asked when identifying and classifying risks.

About the author

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.