home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!ogicse!news.u.washington.edu!ns1.nodak.edu!plains.NoDak.edu!overmyer
- From: overmyer@plains.NoDak.edu (Scott Overmyer)
- Newsgroups: comp.software-eng
- Subject: Re: Rapid Prototyping
- Message-ID: <Bz6Mr4.I4J@ns1.nodak.edu>
- Date: 13 Dec 92 05:18:40 GMT
- Article-I.D.: ns1.Bz6Mr4.I4J
- References: <Byynwy.1qC@bcstec.ca.boeing.com> <1992Dec9.172130.21909@den.mmc.com>
- Sender: usenet@ns1.nodak.edu (News login)
- Organization: North Dakota Higher Education Computing Network
- Lines: 22
- Nntp-Posting-Host: plains.nodak.edu
-
- In article <1992Dec9.172130.21909@den.mmc.com> heck@hercules.den.mmc.com writes:
- >In article 1qC@bcstec.ca.boeing.com, spady@bcstec.ca.boeing.com (Robyn Spady) writes:
- >
- >The key to correct or proper use of a methodology is training and education. Not
- >only do the software developers need to be trained, but also the managers and
- >the customer. That way everyone knows what they are getting and do not expect
- >the prototype to be the complete system. Prototyping is an powerful anaysis tool
- >that can be abused just like any other tool.
- >
- 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?
-
- scotto...
- --
- Scott P. Overmyer |
- College of Business | Walter Payton for President.
- Minot State University |
- Minot, North Dakota 58701 USA |
-