From: "Jeffrey L. Susanj" <jeffrey.l.susanj@boeing.com>
Subject: Re: Worst Case Execution Time Tool?
Date: Wed, 5 Dec 2001 15:31:10 GMT
Date: 2001-12-05T15:31:10+00:00 [thread overview]
Message-ID: <Gnvn3x.227@news.boeing.com> (raw)
In-Reply-To: 3C0E3535.58437022@computer.org
What we have always done is select a scenario that looks like it would
produce the worst case time and run the software on the bench. The
executive can capture the time the frame ends. Not very elegant and not
very rigorous but it gives us a warm fuzzy feeling.
Jeff S.
"StationSteve" <Steven.Suchting@computer.org> wrote in message
news:3C0E3535.58437022@computer.org...
> ...
>
> Guess the marketing guys got tricky again, eh? ;-)
>
> So how (or do?) people typically PROVE that their program will actually
meet their deadlines? If
> somebody does a rate monotonic design, they have to assume the execution
time of task. How does one
> determine the true execution time so that the design can be shown to be
correct?
>
> Thanks again...
>
> Rod Chapman wrote:
>
next prev parent reply other threads:[~2001-12-05 15:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 22:51 Worst Case Execution Time Tool? StationSteve
2001-12-05 0:10 ` Ted Dennison
2001-12-05 17:28 ` Stuart Palin
2001-12-05 18:33 ` Ted Dennison
2001-12-06 14:05 ` StationSteve
2001-12-06 16:40 ` Ted Dennison
2001-12-06 21:27 ` StationSteve
2001-12-06 22:44 ` Ted Dennison
2001-12-07 1:00 ` annonymous
2001-12-05 10:00 ` Rod Chapman
2001-12-05 14:54 ` StationSteve
2001-12-05 15:31 ` Jeffrey L. Susanj [this message]
2001-12-05 17:32 ` Stuart Palin
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox