This page has moved, please click here to continue Interfacing to lab instruments-Use Cases

PIMS SRS > Use Case Suite > Interfacing to Lab Instruments Use Cases

Release Information

Project: PIMS
Internal Release Number: 0.1
Related Documents:

Default Aspects of All Use Cases

Direct Actors:
User: end-user in any role
System: The PIMS system being built
Admin: Web-site administrator, has authority to perform security-critical operations.
Scientist: Post-graduate or post-doctoral wet lab scientist
Senior Scientist: Post-doctoral scientist
Group leader: someone with authority to add users to a group, usually a senior scientist.
Technician: Technical staff
Experimenter: Scientist, or technician sometimes PI
PI: head of lab
When actors are not listed, assume User is doing it.
Items beginning with "see" indicate that System has presented a new screen.
Stakeholders: Project Owners and other members
Prereq: User is logged in except for UC-Log in
TIP: See detailed tips in the guidelines for writing use cases.

Use cases


Target management
UC-Add new target
UC-Edit target
UC-View target status
UC-Add details of a citation to a target
UC-Find citations relating to a target

Bioinformatics
UC-Target selection
UC-BLAST sequence
UC-Genomic DNA available
UC-cDNA available
UC-Is target registered
UC-Align sequences
UC-Predict TM helices
UC-Design primers
UC-Order primers

Sample Tracking
UC-Create sample
UC-Edit sample
UC-Track sample
UC-Sample discard
UC-Move sample
UC-Generate barcode
UC-Scan barcode
UC-View current experiment outputs
UC-View location

Reagent management
UC-Add reagent
UC-Edit reagent
UC-New container
UC-View reagents

Experiment/Protocol management
UC-Create protocol
UC-Edit protocol
UC-View protocol
UC-New experiment
UC-Update experiment
UC-Add next experiment
UC-Remove experiment
UC-Create screening solutions
UC-New crystalization plate
UC-View experiment
UC-New multi-well experiment
UC-Screen conditions

Project management
UC-Create project
UC-Add target to project
UC-Add user to project

Logging in and out
UC-Log in
UC-Log out

User account management
UC-Reg new user
UC-New passwd
UC-Edit profile
UC-View profile

Data Access Rights management
UC-new-owner
UC-new-group
UC-add-user
UC-remove-user
UC-add-permission
UC-remove-permission
UC-add-create
UC-remove-create
UC-new-condition
UC-set-condition

Reporting
UC-Print protocol
UC-Print experiment
UC-Audit trail

Interfacing to laboratory instruments
UC-Robot-input
UC-Robot-input-series
UC-Robot-control
UC-Robot-generate
UC-Robot-convert

Data mining and visualisation
UC-Search PIMS

Installation and upgrading
UC-Config site
UC-Submit form

Mobile data collection


Workflow tools


Scheduling

UC-Robot-input: Receive measurement from lab instrument

Summary: System recieves output of fixed size from a laboratory instrument, e.g. an image
Importance: Expected
Priority: Expected
Use Frequency: Often
Direct Actors: System
Main Success Scenario:
  1. TODO

UC-Robot-input-series: Receive multiple measurements from lab instrument

Summary: System recieves output series from a laboratory instrument, e.g. from a time course
Importance: Expected
Priority: Expected
Use Frequency: Often
Direct Actors: System
Main Success Scenario:
  1. TODO

UC-Robot-control: Send control file to a robot

Summary: System sends a robot control file to a laboratory instrument, and attaches a copy to the current experiment
Importance: Expected
Priority: Desired
Use Frequency: Often
Direct Actors: System
Main Success Scenario:
  1. TODO

UC-Robot-generate: Generate control file for liquid-handling robot

Summary: System generates a control file for a liquid-handling robot from an experiment description
Importance: Desired
Priority: Desired
Use Frequency: Sometimes
Direct Actors: System
Main Success Scenario:
  1. TODO

UC-Robot-convert: Convert liquid-handling robot-control file for different robot

Summary: System converts a control file for a liquid-handling robot for use with a different robot
Importance: Desired
Priority: Optional
Use Frequency: Sometimes
Direct Actors: System
Main Success Scenario:
  1. TODO

UC-name: USE CASE NAME

Summary: 1-3 SENTENCES
Importance: Essential | Expected | Desired | Optional
Priority: Essential | Expected | Desired | Optional
Use Frequency: Always | Often | Sometimes | Rarely | Once
Direct Actors: ACTOR1, ACTOR2, ACTOR3
Prereq:
PRECONDITION
Main Success Scenario:
  1. STEP
  2. STEP
  3. STEP
Alternative "index"
Scenario Extensions:
    BRANCH CONDITION
    1. ALTERNATIVE STEP
    2. ALTERNATIVE STEP
    3. ALTERNATIVE STEP
Variations
TODO: Check for words of wisdom and discuss ways to improve this template.
Company Proprietary
Copyright © 2003-2004 Jason Robbins. All rights reserved. License terms. Retain this copyright statement whenever this file is used as a template.