|
|
# Use Case: ACE3P New Project
|
|
|
|
|
|
## Description
|
|
|
A scientist uses modelbuilder to create a new ACE3P simulation.
|
|
|
A scientist uses CMB modelbuilder to begin a new ACE3P simulation.
|
|
|
|
|
|
## Design Scope
|
|
|
System black box
|
... | ... | @@ -16,7 +16,9 @@ Scientist |
|
|
User has started modelbuilder (aka the "System").
|
|
|
|
|
|
## Main Success Scenario
|
|
|
1\. User invokes command to create a new project. System provides a list of available workflows, and user selects ACE3P. System also provides a default directory for projects, with an option for the User to change this for the new project.
|
|
|
1\. User invokes command to create a new project. System provides a list of available workflow names, and user selects ACE3P. System also provides a default directory for the project's persistent store, with an option for the User to change this for the new project.
|
|
|
|
|
|
* Ideally, the list of simulation names does not require file navigation by the User.
|
|
|
|
|
|
2\. System responds by opening attribute panel and displaying ACE3P simulation template in it.
|
|
|
|
... | ... | @@ -24,16 +26,16 @@ User has started modelbuilder (aka the "System"). |
|
|
* Ideally, the System closes any open UI panels except Attributes, RenderView, and Resource.
|
|
|
* Ideally the Attribute and Resource panels indicate that the attribute resource is modified.
|
|
|
|
|
|
3\. User invokes command to load model file into the project. System provides a file browser or equivalent, and User navigates to the file to load.
|
|
|
3\. User invokes command to load a model file into the project. System provides a file browser or equivalent, and User navigates to the file to load.
|
|
|
|
|
|
4\. System responds by loading the file, displaying it in the RenderView panel, and adding it to the Resource panel.
|
|
|
|
|
|
* Ideally, the system does not bring up any panel to select which reader to use, but just loads the model using what makes sense for ACE3P preprocessing (smtk importer for mesh session?)
|
|
|
* Ideally, the system does not bring up any panel to select which reader to use, but just loads the model using what makes sense for ACE3P preprocessing (perhaps the smtk importer for mesh session?)
|
|
|
* Ideally, the Resource panel also indicates that the model resource is modified.
|
|
|
|
|
|
5\. User creates and edits attributes for whatever ACE3P simulation(s) s/he wants. When done, or at any time during the process, User invokes command to save the project.
|
|
|
5\. User creates and edits attributes for the ACE3P package(s) of interest. When done, or at any time during the process, User invokes command to save the project.
|
|
|
|
|
|
6\. System responds by writing the relevant files to the project folder, and the various UI panels no longer show the resources as modified.
|
|
|
6\. System responds by writing the relevant files to the project folder, and updates its UI panels to no longer show the resources as modified.
|
|
|
|
|
|
7\. User invokes command to close the project.
|
|
|
|
... | ... | @@ -41,7 +43,7 @@ User has started modelbuilder (aka the "System"). |
|
|
|
|
|
9\. User can then: (i) Close modelbuilder; (ii) At some later time, restart modelbuilder; and (iii) Invoke command to open a project.
|
|
|
|
|
|
8\. System responds by first providing a way for the User to identify the project directory, then loads the project resources. The System will display the 3 panels as before (Attribute, RenderView, Resource).
|
|
|
8\. System responds by first providing a way for the User to identify the project directory, then loads the project resources. When complete, the System displays the 3 panels as before (Attribute, RenderView, Resource).
|
|
|
|
|
|
## Additional Notes
|
|
|
|
... | ... | |