By Topic

The impact of reliability requirements on development life cycle

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Bidokhti, N. ; Cisco Syst., San Jose, CA

This paper will discuss the importance of defining reliability and availability requirements upfront and its role in product development life cycle. In addition, it will review how to trace the requirements throughout the product life cycle. In designing a new product, much time and effort is spent defining time to market and functional requirements. In the mean time there is usually less attention paid to reliability, availability and fault management requirements. Therefore, defining clear product reliability & availability requirements becomes an afterthought, or it is only modeled once the product architecture is completed. At the first glance it makes sense, since the design team may not be familiar with reliability, availability and fault management requirements. The team tends to address the functional requirements before any other types of requirements. This is the natural course of action; however this type of thought process will lend itself to building a less desirable product. Knowing these facts, how do we address this necessary and important aspect of a product design as early in the development life cycle process as possible?

Published in:

Reliability and Maintainability Symposium, 2008. RAMS 2008. Annual

Date of Conference:

28-31 Jan. 2008