home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.software-eng
- Path: sparky!uunet!europa.asd.contel.com!emory!swrinde!cs.utexas.edu!torn!nott!ObjecTime.on.ca!ObjecTime.on.ca!bran
- From: bran@helix.ObjecTime.on.ca (Bran Selic)
- Subject: Re: Rapid Prototyping
- Message-ID: <1992Dec16.003700.29558@ObjecTime.on.ca>
- Sender: news@ObjecTime.on.ca
- Reply-To: bran@ObjecTime.on.ca (Bran Selic)
- Organization: ObjecTime Limited
- References: <Byynwy.1qC@bcstec.ca.boeing.com> <1992Dec9.172130.21909@den.mmc.com> <Bz6Mr4.I4J@ns1.nodak.edu>
- Date: Wed, 16 Dec 92 00:37:00 GMT
- Lines: 28
-
- In article <Bz6Mr4.I4J@ns1.nodak.edu>, overmyer@plains.NoDak.edu (Scott Overmyer) writes:
- |> >
- |> Is everyone speaking about rapid prototyping as an interactive,
- |> "throw-away" simulation of the user interface to a system under
- |> design/development? If this is the common definition, then
- |> I'm curious to know how people are using rapid prototyping in the
- |> requirements arena. Specifically, is anyone saying that rapid prototyping
- |> can be used to specify requirements?
-
- ROOM (Real-Time Object-Oriented Modeling) is methodology developed
- originally at Bell-Northern Research which is based on a series of
- executable formal models. The earliest models, in fact, primarily
- capture requirements. This is crucial since requirements for complex
- distributed systems (such as communication protocol standards) are
- invariably incomplete and inconsistent. Prototyping of requirements
- is used to detect such flaws and also to build up an intuition
- about the requirements which no amount of intellectual foresight
- can replace.
-
- --
- *------------------------------------------------------------*
- * Bran Selic | phone: (613) 591-3435 *
- * Vice President R&D | fax: (613) 591-3784 *
- * ObjecTime Limited | e-mail: bran@objectime.on.ca *
- * 340 March Road | *
- * Kanata, Ontario, CANADA | *
- * K2K 2E4 | *
- *------------------------------------------------------------*
-