These are some of the questions I have been asked frequently. The answers are below.

1. Why would someone do screen prototypes?
2. Why does MockupScreens create sketches instead of "real" screens?
3. I have Visual Studio (VB, JDeveloper, QTDesigner...), do I need MockupScreens?
4. I do screen prototypes with Visio (Word, ...) , do I need MockupScreens?
5. I do screen prototypes with FrontPage (DreamVeawer, ...) , do I need Mockups?
6. What is the most effective way to organize mockups?
7. How often is MockupScreens updated?
8. I think feature XYZ is a must / I need feature XYZ.

Both to capture and clarify application requirements. The screens are by far the easiest medium of communication among various parties collaborating on software project. Often, customers don't really understand what are you talking about until they see the screens. In this way you can quickly prototype multiple alternatives that everyone can understand and evaluate.

2. Why does MockupScreens create sketches instead of "real" screens?

Showing the life-looking prototype to the customer or managers can spell disaster. They will percieve "almost finished" application and you can't say or do anything to explain otherwise. The easiest way to avoid this is to have mockups that clearly don't look even close to the real thing.

3. I have Visual Studio (VB, JDeveloper, QTDesigner...), do I need MockupScreens?

Yes, for the following benefits:

• far greater productivity
• populating screen elements with data
• non-programmers can "draw" the screens
• mockups don't look even close to the real thing
• screens are organized into scenarios

4. I do screen prototypes with Visio (Word, ...) , do I need MockupScreens?

Yes, for the following benefits:

• screens are organized into scenarios
• simple maintenance of previous work
• far less limitations

5. I do screen prototypes with FrontPage (DreamVeawer, ...) , do I need Mockups?

Yes, for the following benefits:

• screens are organized into scenarios
• simple maintenance of previous work
• far greater productivity
• non-programmers can "draw" the screens
• mockups don't look even close to the real thing
• screens are organized into scenarios

6. What is the most effective way to organize mockups?

The most effective way is to create one scenario, name it "Repository", and store each application screen there once as a template. When you work on a real scenario, and you need a screen you have already created, just copy it from "Repository" and tweak the content.

7. How often is MockupScreens updated?

New features: 2-3 times a year.

Small improvements and bug fixes: all the time.

8. I think feature XYZ is a must / I need feature XYZ.

I will gladly listen to any comment or idea you might have. But if it's not something both feasible and *really* great, than it boils down to whether you have paid your copy of my product.