Discussion on prototype tools for development projects based on B/S architecture

The prototype here is only for projects that are based on B/s architecture.

There are a number of professional prototyping tools such as Axure, Mockflow, Infomaker, and some "unprofessional" software: Photoshop, Dreamweaver, and so on, if you have the patience to use word for prototypes, and of course pens, paper, and Eraser.

I have been exposed to a lot of prototyping tools, and have done a lot of so-called prototypes, different projects, different companies, and the tools used are not the same.

What kind of tools do you think you use to make prototypes,

The 1th depends on which tools are best suited for communication and communication between project personnel.

The 2nd is to see if the prototype is familiar with the tool, and to show the prototype in the quickest and most accurate way. This is very important, the prototype is not only the most direct display of the project, but also to be able to quickly respond to the relevant personnel to see the changes in the project as soon as possible.

The 3rd is to facilitate the late modification and filing of the prototype production personnel.

The 4th is to see whether the production is a low-fidelity prototype or a high-fidelity prototype.

It is undeniable that many project managers because of tight time, heavy task, can not tolerate the programmer "idle" and other reasons. Will not spend a lot of time on the design of prototypes.

At the same time, most of the project's prototype is the most confusing is how much it is thinning to what extent, that is, when the visual designer can enter the work, when the background program can start programming. The development sequence of general B/S architecture is: prototype-"vision-" front end-"backstage, its order is not straight, the first 3 steps should be circular cycle."

Two kinds of prototypes are produced based on the above two reasons, one is the base Fidelity prototype and the other is the high Fidelity prototype. If you act in strict accordance with the rules, pure as a project to show and interactive description of the prototype, should only be "low-fidelity" This form of expression, but this is only an ideal, as the project progresses, we will be more and more high fidelity prototype, everyone in the prototype to see more visual effects. Now more and more prototyping software is to enhance the control of the custom vision, is not all the prototype software can be added to the background and vision from the prototype software into development software is the ultimate goal of these companies ....

So far I have not seen a complete prototype of a project is fully based on the low Fidelity prototype as a deliverable. At present, the most contact is the use of Dreamweaver production of high-fidelity prototype, there is no denying the use of Dreamweaver prototype has many drawbacks.

For example, Dreamweaver is not a team of all people, interactive designers, visual designers, front-end engineers, background engineers should be aware of and will use Dreamweaver. After all, we are doing B/s architecture system development, not to say to Dreamweaver proficient, but at least should be achieved as the use of Word software can carry out basic operations bar. Visual designers who do not understand the front end have a gorgeous effect and do not understand the interaction designers who explain how the controls are implemented, their final deliverables will be pale and unconvincing.

As a system based on B/s architecture, most of the JSP pages generated are from HTML files. To a certain extent it can also be said that the production is located in the middle of the low Fidelity prototype and the front page of the High Fidelity HTML page compromise solution is not a method.

I think the better way to work is the UI designer and project manager in the printed form of demand analysis of a single module for discussion, real-time in the paper hand-painted out the control of the module, to determine the operation of all the controls in the module and to show the data, as far as possible to ensure its correctness. The project leader was then kept "within 3 meters", looking at the prototype to make the prototype come true. This does not waste the project manager a lot of time. The project manager is not stare in a daze, he can consider other problems in the process of prototype implementation, or do other things, but just can't leave. It is important to have the project manager within 3 meters. In the process of prototyping, there will be many problems that have not been discovered at first, such as interactive methods, and some detail problems. Make sure that the prototype and the person responsible are able to discuss them in time. Do not expect the scoring machine, OA Synergy, or Skpye, MSN or anything to find him in time. Let all the project managers develop this habit. That is: The beginning of the project, do not go anywhere. It will take weeks to work out a high-fidelity prototype with the designer.

Of course, in the early stage can also be a large number of personnel to participate in the prototype seminars and project needs analysis meetings, but finally remember to pull the project manager, so that the project manager and responsible for the production of prototypes to maintain within 3 meters.

The article topic uses the word "discussion", is ten card to think in this kind of question discussion space is very big, each company and the team also should have its own working method, perhaps uses the nimble and changeful way reasonable production and the use prototype is the most suitable way.