DesignWise Process – Sharing & Maintenance
Tips and best practices for the long-term management of DesignWise assets.
Part 1. Collaboration and review
Sharing also ensures that assets do not get lost when people transition to different roles or move to other job opportunities.
While sharing enables the most interactive access to DesignWise capabilities, sometimes export is more practical. Some of the most popular collaboration formats include mind maps, Excel, and feature files.
Notes can be used to keep track of your design ideas, to post questions to your collaborators, or to mark outstanding actions to complete the model.
Revisions (accessed from the dropdown near the model name) provide version control capabilities where you can see your colleagues’ actions and, if necessary, return the model to the previous state.
Part 2. Release preparation and ongoing maintenance
When your scenario suite is finalized, it can be a good idea to ensure test data consistency with the help of “freezing”.
We will focus on the situation where the test suite can be re-generated completely. Regarding sources of information, new requirements are the one mentioned most often, but you should not overlook execution and defect reports. While DesignWise does not execute your tests, establishing the feedback loop and ensuring your DesignWise model includes the interactions that have caused issues in the system is critical for the long-term value of the tool.
This category includes renaming values, adding/removing values that do not affect constraints, and changing the script.
- To avoid unnecessary complications when you just want to rename an individual Value, we recommend that you do that by clicking on the actual Value, not on the parameter name.
- Adding or removing values can be done via Edit, Bulk Edit, or Mind Map modes – depending on the number and format of changes.
- Within Auto-scripts, you can edit the content of each step and its position in the overall script by hovering over and clicking the pencil/arrow icons:
We will take a look at 2 examples: significant updates to the constraint logic and merging ideas from multiple models.
Example 1: When the input set is constant and the constraint logic is changing, you have to either delete relevant constraints 1-by-1 or, if the updates are drastic, bulk delete them and start from scratch.
- You can leverage the browser search to identify constraints for the necessary values:
- You can add parameters via copy-paste in Bulk Edit or via parameter lookup in the “New Parameter” dialog (note: parameter lookup works at the project level):
- You can add constraints via copy-paste in Advanced Mode
- Depending on the elements of each model, it may be more efficient to merge 3 exports in Excel and create a new asset from Excel import:
- If you are dealing with the integration testing, we often recommend decreasing the level of detail – in other words, do not merge all parameters & values from multiple models, but instead reevaluate which are the crucial ones from the integration perspective and abstract the rest.