Transcending Performability for System Attributes’ Consistency
Abstract: ©2010 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must first be obtained from the IEEE.
System attributes (such as reliability and performance) are usually managed by different engineering groups, where each group works independently. This separation starts from the requirement phase, and continues throughout the entire development process. This situation often results in inconsistencies among system attributes, which cause ambiguous specification, and in turn affects the system design. Providing a consistent view among all system attributes is the motivation of this study. The root cause of the problem is that system attributes are not really independent. For example, a system is “available” only if certain “performance” requirements are met. In other words, performance requirements determine whether a system is working or not, and availability is the probability that a system is working. Therefore, availability specification and performance requirement are closely related. Author: Yin, Meng-Lai ; Arellano, Rafael; Copyright: Institute of Electrical & Electronics Engineers, Inc. Keywords: RAMS 2010 Proceedings, Reliability Model, Requirements Flow down, Product Development Planning URL: /ec/2010/08/quality-tools/transcending-performability-for-system-attributes-consistency.pdf Access: QIC hidden AND free to members subscribers
Keywords: RAMS 2010 Proceedings - Reliability Model - Requirements Flow Down