Differences between revisions 2 and 3
Revision 2 as of 2006-11-15 21:30:34
Size: 2758
Editor: lfrq80
Comment:
Revision 3 as of 2006-11-17 15:47:14
Size: 2798
Editor: lfrq80
Comment: Reorganizing the MIM pages
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from DefineProcess

Use Case Name : DefineProcess

For Feature : MIMEditor

Editors: DavidKane

TableOfContents([2])

Summary

A user wants to add a high-level process to a map.

Step-by-Step User Action

  1. User specifies that a process should be added
  2. User labels the process
  3. 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.

PageComment2

Molecular_Interaction_Maps/DefineProcess (last edited 2009-02-12 01:03:27 by localhost)

Funding for Cytoscape is provided by a federal grant from the U.S. National Institute of General Medical Sciences (NIGMS) of the Na tional Institutes of Health (NIH) under award number GM070743-01. Corporate funding is provided through a contract from Unilever PLC.

MoinMoin Appliance - Powered by TurnKey Linux