<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>MOBY Use Case Blocks</title>
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
<meta name="author" content="Fiona Cunningham">
</head>
<body>
<h1>Scenario:</h1>
<br>
Researcher has received a set of 5' UTR's from his organism of interest,
and is interested in the average length of a 5'UTR from this organism.<br>
<br>
<h1>
<h1>General Use Cases</h1>
</h1>
<h1>Average </h1>
<p><b>Scenario Reference: (above)</b></p>
<p><b>Problem: </b>find the average of a series of numbers </p>
<hr width="10%" align="left">
<h2> Background Knowledge: </h2>
<p><br>
</p>
<hr width="10%" align="left">
<h2> Primary Actors: </h2>
<ol>
<li>A biologist</li>
<li>A mathematical properties service provider<a
href="http://snp.cshl.org/"></a> </li>
</ol>
<hr width="10%" align="left">
<h2>Other Actors: </h2>
<hr width="10%" align="left">
<h2>Initial State and preconditions: </h2>
<p><br>
Client has a series of objects, of which one of the properties is a real
number.<br>
</p>
<hr width="10%" align="left">
<h2> End Result: </h2>
<p>Client is returned the average of the real numbers </p>
<hr width="10%" align="left">
<h2> Hypothetical Mobyless Workflow: </h2>
<p><b></b></p>
<ol>
<li>Researcher inputs numbers into a spreadsheet or his calculator to obtain
the result</li>
</ol>
<br>
<hr width="10%" align="left">
<h2> Existing Workflow Limitations: </h2>
<p>Inconvenience and non-integration of the relatively simple task </p>
<hr width="10%" align="left">
<h2>Existing Workflow Exemplars: </h2>
<p></p>
<br>
<hr width="10%" align="left">
<h2> MOBY Workflow: </h2>
<ol>
<li>The client requests services which work on real numbers</li>
<li>Client choses the desired service and gets the result<br>
</li>
</ol>
<hr width="10%" align="left">
<h2>MOBY Workflow Limitations: </h2>
<p>- No such "RealNumber" primitive exists in MOBY, nor are we currently
geared to have one.<br>
- The result is not a MOBY Object, under our existing definition. </p>
<hr width="10%" align="left">
<h2> MOBY Workflow Exemplars: </h2>
<p>- The service is discoverable and therefore integrated and 'pipelineable'<br>
<br>
</p>
<hr width="10%" align="left">
<h2> Discussion: </h2>
Under the current MOBY architecture and MOBY-Triple-based object paradigm
we are stuck when it comes to a problem like this. What is most notable
about this use case is the fact that the hypothesized service works on Numbers
rather than "MOBY Objects". This means that we don't have to have separate
services to calculate e.g. the average length of a set of sequences versus
the average Cy5 signal intensity of a set of microarray spots. I think
this is very much what Andrew was talking about a couple of months ago, but
I was too boneheaded to "get it" at the time... sorry Andrew!<br>
<br>
<hr width="10%" align="left">
<h2> Priority:</h2>
<p>Desirable</p>
<hr width="10%" align="left">
<h2> Key References: </h2>
<p><br>
<a href="%20http://www.genome.gov/page.cfm?pageID=10005336"></a></p>
<hr> <br>
</body>
</html>