Larger scale systems require higher-level abstractions
IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
Software requirements: objects, functions, and states
Software requirements: objects, functions, and states
IEEE Software
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Software Requirements
On Non-Functional Requirements in Software Engineering
Conceptual Modeling: Foundations and Applications
A standards-based reference framework for system portability requirements
Computer Standards & Interfaces
| Hi-index | 0.00 |
Reliability is typically described initially as a non functional requirement at the system level. Systems engineers must subsequently apportion these system requirements very carefully as either software or hardware requirements to conform to the reliability requirements of the system. A number of concepts are provided in the ECSS, ISO 9126, and IEEE standards to describe the various types of candidate reliability requirements at the system, software, and hardware levels. This paper organizes these concepts into a generic standards-based reference model of the requirements at the software level for system reliability. The structure of this reference model is based on the generic model of software requirements proposed in the COSMIC -- ISO 19761 model, thereby allowing the measurement of the functional size of such reliability requirements implemented through software.