Gary M. Holtwick
ABSTRACT
Several years ago, we undertook the task of designing and constructing a software computer measurement system. The initial requirements we made of the system, problems that arose during the development phase when we actually tried to adhere to those requirements, the solutions to these problems, and subsequent use and modification of the completed product form the basis of discussion here.
Index Terms
- Designing a commercial performance measurement system
Recommendations
Measurement of software requirements derived from system reliability requirements
FSM '10: Proceedings of the Workshop on Advances in Functional Size Measurement and Effort EstimationReliability 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 ...
Identifying Derived Performance Requirements of System Components from Explicit Customer- and Application- Facing Performance Requirements
ICPE '17: Proceedings of the 8th ACM/SPEC on International Conference on Performance EngineeringExplicitly stated response time, throughput, and other performance requirements of an application implicitly impose other performance requirements on the system components that implement it. We call these derived performance requirements. The explicit ...
Designing a Measurement Method for the Portability Non-functional Requirement
IWSM-MENSURA '13: Proceedings of the 2013 Joint Conference of the 23nd International Workshop on Software Measurement (IWSM) and the 8th International Conference on Software Process and Product MeasurementThis paper proposes a measurement method to measure the non-functional portability software requirement. The proposed method complies with the COSMIC ISO 19761 measurement method standard. The details of the design steps are presented and explained. ...
Comments