Software timing requirements

Shortcomings in system requirements are best addressed from the start rather than waiting for design steps or the product to show them up. The perceived requirements should be recorded in an unambiguous yet understandable way to form a basis for design and testing activities. This paper considers a particular kind of requirement that is difficult to design for-the software timing requirement. Failure to meet timing requirements is often unnoticed before implementation, and may thus be very costly. The author discusses the problem of speeding up programs that are too slow, software functional requirements, software timing requirements, specification and verification