Talk:Software prototyping

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing  
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.

Too technical[edit]

I find the verbiage used here to be far too technical for the average information consumer. Could someone who knows more about this please try to tone it down a little? The same thing happens with law articles all of the time. --Czj 20:08, 20 August 2006 (UTC)

Also: This article could use a suitable introductory paragraph, giving a little bit of background. The intro it had read like an essay... it even included the text, "This paper aims to introduce the reader to prototyping techniques as they apply to software engineering and development." It was also basically useless, as it gave no background... the very first sentence was a quote from a book. I have removed that intro. --Czj 20:13, 20 August 2006 (UTC)

Evolutionary Prototyping[edit]

I started to merge Evolutionary Prototyping (which I made a redirect here) but I'm not convinced that it wasn't being used in a different meaning. There fore I'm copying it here (see link preceding for history) for consideration. RJFJR 22:17, 7 September 2006 (UTC)

  • Must be used for systems where the specification cannot be developed in advance e.g. AI systems and user interface systems
  • Developers need special skills and most of the developments are done using RAD
  • Can be only applied to small and medium size projects.
  • System is not well structured.
  • Based on techniques which allow rapid system iterations
  • Verification is impossible as there is no specification. Validation means demonstrating the adequacy of the system

Prototyping#Software prototyping[edit]

This material from Prototyping#Software prototyping belongs here (it needs to be worked up to fit in properly). RJFJR 18:18, 10 September 2006 (UTC)

The process of prototyping involves the following steps

  1. Identify basic requirements
    Basic requirements including the input and output information desired. In this step, the editing rules, security issues will be typically ignored as this is just a rough idea on what it will be like.
  2. Develop Initial Prototype
    After identifying the basic requirements then you will be set to develop an initial prototype and in this initial prototype will include only user interfaces. For example data entry screens and reports.
  3. Knowledge Worker Reviewing
    This will be the step where the iterative process of prototyping starts where knowledge workers first initiate this step, they will evaluate the prototype and give out feedback such as suggestions on changing a certain part or additions of certain element. The involvement of more knowledge workers is important because it will help resolve any discrepancies in areas such as terminology and operational processes.
  4. Revise and Enhancing the Prototype
    A final step in prototyping is to revise and enhance the prototype according to any suggestions from the knowledge workers. If there's any changes and addition you did in this step, you will be required to repeat step 3 and 4 again.

I merged it in as section "overview". We need to check and make sure this model is compatible with the rest of the article. RJFJR 18:22, 10 September 2006 (UTC)

Visual Basic[edit]

VB.Net is an object-oriented programming language and programs in VB.Net can be described using UML. This is not represented in the section on Visual Basic in the article. 14:50, 21 May 2007 (UTC)

The Visual Basic section is also confusing Visual Basic and Microsoft Access. And several of the disadvantages are the result of not-ideal design (which, to be fair, you usually don't take the time for during prototyping), and are not an inherent problem with VB. Riceman0 16:07, 25 June 2007 (UTC)

Evolutionary prototyping[edit]

It is not clean, which part of the text is a citation, and where are the end of each idea. Should be cleaned up a bit. I tried to beautify it, but as I do not have acces to the citated books, I cannot verfiy which part of the text is a citation.

Horizontal vs. vertical prototyping[edit]

The article lacks a framework for categorizing the reasons for prototyping, and the depth one should go to. vertical prototype and horizontal prototype needed to be covered separately. Once those are introduced, it becomes clearer where to tools such as screen generators such as Dan Bricklin's demo program or 4GLs or systems with scripting languages that can add functionality. rhyre (talk) 12:30, 20 March 2010 (UTC)


Why is Scrum mentioned as a prototyping method? Scrums can be used whether or not prototyping is performed. What is the connection here? —Preceding unsigned comment added by (talk) 17:59, 5 May 2010 (UTC)

Software Prototyping[edit]

Hi - What I was searching for was the following:

- Should prototypes also undergo QA / QC testing and checks? — Preceding unsigned comment added by (talk) 04:27, 28 October 2011 (UTC)