Talk:Prototyping

message: Yes. Newspapers hardly ever "stop the presses" to change the first version. Coal miners must get the coal that is actually in the ground -- there is no point in constructing some sort of "prototype" coal mine. People that milk cows learn to milk on an actual cow, not some sort of prototype. Pet stores sell the actual pet, rather than letting people start with a "prototype pet" before they get the actual pet. Restaurant chefs may "experiment" with new recipes, but even the experiments use real food ingredients, rather than some sort of "prototyping" material.
--68.0.120.35 21:20, 27 December 2006 (UTC)
thread_title:  Can you think of a business in which prototyping would not work? 

message: There's a very good article on Software Prototyping that doesn't appear to even get a mention here. Is this something that needs to be addressed?
:I made a note to see the software prototyping article in that section. (I want to leave part of it here because it is a significant form of prototyping, but I removed some of the details and will work on merging them into the software protoyping article.)  I removed the merge to tag havign donme this. RJFJR 17:50, 10 September 2006 (UTC)
thread_title:  Software Prototyping 

message: I removed the following unreferenced text from the Software prototyping section. Please put it back if you can find any references for it:
In the mid-1980s, prototyping was seen as the solution to the problem of requirements analysis within software engineering. Prototypes are any form of deliverables that model an application  allowing users to visualize the application that is not yet constructed. Prototypes help users get an idea of what the system will look like, and make it easier for users to make design decisions without waiting for the system to be built. When they were first introduced the initial results were considered amazing. Major improvements in communication between users and developers were often seen with the introduction of prototypes. Early views of the screens led to fewer changes later and hence reduced overall costs considerably.
However, over the next decade, while proving a useful technique, it did not solve the requirements problem:
* Managers, once they see the prototype, often have a hard time understanding that the finished design will not be produced for some time.
* Designers often feel compelled to use the patched-together prototype code in the real system, because they are afraid to 'waste time' starting again.
* Prototypes principally help with design decisions and user interface design. However, they can not tell what the requirements were originally.
* Designers and end users can focus too much on user interface design and too little on producing a system that serves the business process.
Lakeworks (talk) 12:05, 27 January 2008 (UTC)
thread_title: Removed text

message: "Epson uses inkjet technology to create world's first 20-layer, ultra-thin circuit board"
Is this historical enough to use as a reference in this article?
(Is this really the world's first 20 layer circuit board? If not, I would be very interested in knowing when the "world's first 20 layer circuit board" was made.)
--68.0.120.35 21:20, 27 December 2006 (UTC)
thread_title:  20-layer circuit board prototype 

message: query for settling unverified information
(dated 10-april-2008)
Advantages of prototyping
    * May provide the proof of concept necessary to attract funding
    * Early visibility of the prototype gives users an idea of what the final system looks like
    * Encourages active participation among users and producer
    * Enables a higher output for user 
:(what higher output? large amount of output? highly desireable output? or what else?)
    * Cost effective (Development costs reduced)
:(could use for more detail explanation? what makes cost effective? besides labour cost & what else?)
    * Increases system development speed
    * Assists to identify any problems with the efficacy of earlier design, requirements analysis and coding activities
    * Helps to refine the potential risks associated with the delivery of the system being developed
Xmlv (talk) 18:25, 9 April 2008 (UTC)
thread_title:  A section of students revisions