Here are a few of the things I'd like testers to look for:
How does it break?
I want MOMDYN to be interactive, so you don't just view examples, you build your own models from the ground up. A challenge in designing the interface is that I want to not just be able to add components to the model, but edit or delete them along the way. So, what if I create a frame, add points, vectors, bodies, then decide later that I want to update a parameter in the frame I started with? Well, then all the later components that depend on that frame need to be updated in turn. I've worked to handle and test all those possible dependencies, but even still I get crashes from time to time if something is handled wrong. As you are testing, please try editing all kinds of possible fields, and if the app crashes, let me know how you got there and I'll try to fix it.
Does the interface make sense?
The menu button on the upper left is your starting point editing what you see on screen. If you open the expansion panels, you'll see various different components that you can add, delete, or edit. Click the question marks on the right hand side to bring up help documentation. You can also enter a help menu from the welcome screen. Does the help explain how to use MOMDYN in an effective way? Do the menus behave the way you expect them to?
Are the dynamics correct?
This is for those of you who are trained in the field. When you tap the simulate button, do the objects move the way you'd expect them to? When you view the report tab, are the equations correct? Can you replicate textbook problems?
What do you want to see next?
This is open-ended, think of this as my "polling the audience." I have an idea of the direction I'd like to go with this app, and the state I want it to be in when it finally releases. I'd like to know what you would like to see.
No comments:
Post a Comment