Abstract
A variay of tools, based on object-orimted design methodology is already available commercially. Many new tools are being developed. Many applications built by using these tools are inherently time-critical. However, it is widely known that object-orimted methodologies, in spite of all their virtues, are pretty awkward in verifying quantitative time correctness of the specification, design and implementation of the developed product. This paper discusses same reasons of why object-oriented methods cannot be quite aware of timing problems and how the situation could be improved. The discussion is illustrated with examples from HRT-HOOD and OMT. The technical contents of the paper is based on a new generation software tool LIMITS, which is designed and built as a coprocessor to an OMI tool (EU grant COP-94-1577). Key theoraical and methodological issues of LIMITS insist on introductioo of non-functional requirements (timing, safety, reliability, ac.) early in the requirements specification stage, selection of time model with appropriate complexity to support formal verification of all the timing properties, support to all life-cycle stages and combining formal verification with informal (simulation) study.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.