1. Add a plan name.
2. Depending upon where you would like your new model to be saved, as appropriate:
1. Select an existing project from the drop-down menu,
2. Create a new project, or alternatively…
3. Use the default “None (private).”
3. Optionally (if you already have a set of test inputs created in Excel or a mind map), select “Choose File” to import the file.
4. Click the “Create” button.

If you are wondering which Parameters and Values to enter into your plan, do not be discouraged! It is a little tricky for almost all new users. You might find these 3 sources of information helpful to get started:

• View some sample plans to get ideas about typical kinds of inputs.
• “Start with a Verb and Noun” and ask “reporter questions” (who, what, when, where, why, how, how many).
• Check out the “How can I best identify variation in the system I’m testing?” help file.

Also, remember that you usually should not include Parameters for every field in your System Under Test. You’ll need to consider how the System Under Test works to appropriately identify a good set of test inputs for your plan. Include Parameters and Values if they should (or logically might) impact how your System Under Test operates (either by themselves or when interacting with other Values in your System Under Test). For example:

• If the system works exactly the same, whether someone’s name is Jim Green or Susan Smith, you may want to leave “First Name” and “Last Name” out of your Enterprise Designer variation ideas.
• If the gender of users would impact how the system works, you would probably want to include “Gender” as a Parameter (with male and female as the sample Values).

*We used the word “scenarios” fairly loosely here. They are actually sets of optimized test conditions at this point. The first set of test conditions should be executed in your first test script, and so on.