1 / 3

LSDAM Working Experiment Diagram

LSDAM Working Experiment Diagram. Notes: I have added a self-association on Experiment – as I was working with the information from Jenny, it seemed to me the “Work Flow”, “Method”, and “Procedure” from Jenny’s sample could be supported by “Experiment”

dacia
Download Presentation

LSDAM Working Experiment Diagram

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LSDAM Working Experiment Diagram Notes: • I have added a self-association on Experiment – as I was working with the information from Jenny, it seemed to me the “Work Flow”, “Method”, and “Procedure” from Jenny’s sample could be supported by “Experiment” • Consider that distinguishing between these things in the DAM might not be necessary • Color-coding here is meant to assist in mapping the instance diagram on next slide, to the class diagram here • Remember ExperimentalItem has association to Material (and through inheritance to BiologicSpecimen) and Animal; I did not include it on the diagram to keep things focused • Remember ProcessedData has association to Finding; I did not include it on the diagram to keep things focused

  2. LSDAM Gene Expression instance diagram The “Project” concept defined in the sample, but name of the Project was not provided My assumption Project can consist of multiple Work Flow; Other “Work Flow” were not listed in the sample, but included for illustration “Method” from the sample; Method is part of Work Flow; Experiment is part of Experiment “Procedure” from the sample; Procedure is part of Method ; Experiment is part of Experiment

  3. Things to consider – might be out of Generic Assay scope, not sure? • In some instances, caLIMS2: Output Type for a given procedure equates to LSDAM: Data in current model • The .dat and .cel are the result of the Procedure: U133P2array scan (CGOS: create *.dat and create (.dat to) *.cel) • In some instances, caLIMS2: Output Type for a given procedure equates to LSDAM: ProcessedData in current model • The .chp is the result of the Procedure: GCOS U133P2GeneExpression Analysis • In some instances, the caLIMS2: Input Type for a given procedure equates to LSDAM: Data in current model • The .dat is Input for Procedure: CGOS U133P2GeneExpression Analysis • I may just be looking at things from to high of a perspective, but, to me, this seems to support a suggestion from a previous iteration that we should have just one level of Data (and not Data and ProcessedData) in the LS DAM • currently we have Experiment-results in/ is the result of-Data; there is no association between Experiment and ProcessedData • Perhaps we need to rename Data to make more generic – Results, ExperimentalResults? • Experiment – produces / is the product of – Results • Results can be data (.dat or .cel, etc.), processed data (.chp, etc.) • This also seems to support including an association from ExperimentalItem to Data (or whatever we rename it to)? • The ExperimentalItem in Procedure:GCOS U133P@GeneExpression Analysis is the .dat (“Data”) and the result is a .chp (a different instance of “Data"

More Related