Cytoscape Wiki|
← Revision 3 as of 2006-11-17 15:47:14
Size: 2798
Comment: Reorganizing the MIM pages
|
← Revision 4 as of 2006-11-17 20:39:56 →
Size: 2810
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| || '''Use Case Name''' : DefineProcess || | || '''Use Case Name''' : ../DefineProcess || |
| Line 55: | Line 55: |
| Shared MimEditorUseCaseComments | Shared ../MimEditorUseCaseComments |
| Line 57: | Line 57: |
| A process differs from a VirtualCompartment, in that species can go into a VirtualCompartment by way of binding. A process has no notion of inside or outside. | A process differs from a ../VirtualCompartment, in that species can go into a ../VirtualCompartment by way of binding. A process has no notion of inside or outside. |
Summary
A user wants to add a high-level process to a map.
Step-by-Step User Action
- User specifies that a process should be added
- User labels the process
- User optionally associates the process with other maps
Visual Aides
A process is represented with a labeled box:
attachment:defineprocess1_061115_dwk.png
Process can serve as inputs as well as outputs in maps. For example exposure to a drug can be a process that originates an interaction (e.g. inhibition).
Requirements for Cytoscape
TBD
Importance
Many maps refer to processes that are important in the context of the map, even if the details of the process are not. A process is an abstraction of those activities.
Other Examples
Comments
Shared ../MimEditorUseCaseComments
A process differs from a ../VirtualCompartment, in that species can go into a ../VirtualCompartment by way of binding. A process has no notion of inside or outside.