This article will cover three prototype implementation models in traditional software process models!

First, disposable prototype development

1. Definition: Verify and clarify the requirements description of the system, and reconstruct the system.

2. Flow chart

3. Typical examples

A prototype of the graphical user interface (GUI) was developed after the developer communicated with the customer and received the customer’s requirements. After that, the system was not developed in GUI, but in C++ or some other language.

4. Favorable conditions

(1) Reduce risk in a project, see if something can be done.

Reduce risks in the project and assess what can and cannot be done;

(2) Capture requirements(e.g. whether clients like the GUI or not)

Capture requirements, such as whether the customer likes the GUI interface.

5. Disadvantages

(1) Resources can be wasted, so control is needed.

Resources can be wasted and therefore need to be controlled.

(2) Good Project Management is required.

Good project management is required.

(3) Good communication with the client is required.

Maintain good communication with customers.

(4) When is it a good time to stop developing the prototype

There is no telling when to stop prototyping.

2. Evolutionary prototyping

1. Definition: Gradually improve and refine the prototype to evolve into the final system.

2. Flow chart

3. Typical examples

Like the car industry, a model is being refined.

4. Favorable conditions

(1) The client can see The changes that they want.

Customers can see the changes they want.

(2) Very good for improving user interface acceptance.

It helps improve the acceptance of the user interface.

5. Disadvantages

(1) Very weak on (e.g. system keeps changing)

Bad for documentation, for example: the system is constantly changing, so the documentation is not easy to write.

(2) The entire project needs strong project control, The same as leader needs to monitor development.

Strong project control is required throughout the project, and leaders need to monitor the progress of the project.

(3) When it is a good time to stop evolving and finishing the project and possible lead to a badly structured system.

We don’t know when to stop development and end the project; So this is likely to lead to a poorly structured system.

(4) Special development staff may be required.

Special developers may be required.

6. Application

1) Small projects.

Small projects.

(2) Limited projects that are Limited by time or money

A limited project limited by time or money.

(3) Those projects that need done quickly.

Projects that need to be done quickly.

(4) Projects whose details cannot be determined in advance.

A project whose details cannot be determined in advance.

(5) Projects with a high graphical content.

Graphically rich projects.

Incremental prototyping

1. Definition: On the basis of establishing the overall design of the software, incremental development method is adopted to make the prototype into the final system.

2. Flow chart

3. Typical examples

English version:

A software company and a client may agree on delivery of system parts. For example, a website delivery might be:

1st January – Delivery of web-server, web-pages,verification and validation scripts.

5th February – Delivery of database, security software.

21st February – Delivery of merchant payment system.

Chinese version:

A software company and a customer reach an agreement for the delivery of system components. For example, a site delivery might be:

January 1 – Delivery of ① Web server; (2) the web; ③ Validation and validation scripts.

Feb 5 – Delivery of database and security software.

February 21 – Merchant payment system delivery.

4. Favorable conditions

(1) Good for breaking a larger system into parts, so components can be built easier.

It is ideal for breaking up larger systems into parts, so components can be built more easily.

(2) Customer sees the system in stages, so no “big bang” approach.

Customers see the system in stages, so there may be less of a “big bang” attitude.

5. Disadvantages

(1) Requires good communication and agreement.

Good communication and negotiation is required.

(2) Requires good project management, control and monitoring work.

Good project management, control and monitoring is required.

(3) Communication and agreement

Good communication and negotiation is required.

(4) Requires good project management, control and monitoring work.

Good project management, control and monitoring is required.

Fourth, concluding remarks

  • Pay attention to the public number Monday laboratory, the first time to pay attention to learning dry goods, more selected columns for you to unlock ~
  • If this article is useful to you, be sure to like it and follow it
  • See you next time! 🥂 🥂 🥂