Talk:Software prototyping

From Wikipedia, the free encyclopedia

This article has been improved by the Cleanup Taskforce to conform with a higher standard of quality. Please see its Cleanup Taskforce page for more details on this process, and possible ideas on how you can further improve this article!

[edit] Too technical

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)

[edit] Evolutionary Prototyping

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

[edit] Prototyping#Software prototyping

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)