This page has moved, please click here to continue User account management-Use Cases

PIMS SRS > Use Case Suite > User account management 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-Reg new user: Register new user

Summary: The Administrator will need to register new users in this web application.
Importance: Expected
Priority: Expected
Use Frequency: Once per user
Direct Actors:
Admin: Web-site administrator
Main Success Scenario:
  1. Administrator visits "user accounts" page
  2. click to create new user
  3. see user profile page
  4. enter indentifying information: username, email, real name, password (twice) and set permissions for database access
  5. submit form
  6. system records new user information, displays updated user-profile page and sends email confirming login information to user
Alternative 4a
Scenario Extensions:
    Username is already taken
    1. see error message requesting new values and user accounts page
    2. click to cancel error
    3. perform UC-Reg new user: Register new user, steps 2-6
Alternative 3a
Scenario Extensions:
    User is not an administrator
    1. system displays error message

UC-New passwd: Request new password

Summary: If a user forgets their password,the administrator can edit the user profile to create a new one.
Importance: Expected
Priority: Desired
Use Frequency: Rarely
Direct Actors:
Admin: Web-site administrator
Main Success Scenario:
  1. Administrator visits "user accounts" page
  2. click to edit user's profile
  3. see user profile page
  4. select user by name
  5. enter new password (twice)
  6. perform UC-Reg new user: Register new user,steps 5 and 6
Alternative 3a
Scenario Extensions:
    User is not an administrator
    1. system displays error message
Variations
  1. The same steps are used to update other user account preferences, as in UC-Edit profile: Edit user profile.

UC-Edit profile: Edit user profile

Summary: Users can edit some of their own account preferences, depending on their database permissions.
Importance: Expected
Priority: Desired
Use Frequency: Rarely
Prereq:
User must belong to a user group with appropriate access rights
Main Success Scenario:
  1. User visits "user accounts" page
  2. click to edit own profile
  3. see own user-profile page
  4. edit relevant fields
  5. perform UC-Reg new user: Register new user,steps 5 and 6
  6. system logs record of changes made including user Id, date and details
Alternative 5a
Scenario Extensions:
    Administrator enters inappropriate information, e.g.text for numerical fields
    1. see error message requesting new values are entered, and user profile page
    2. click to cancel error
    3. perform UC-Edit profile: Edit user profile steps 5-6

UC-View profile: View user profile

Summary: Users can view basic information from the profiles of other users, or editable details of their own. Administrators can see the whole profile.
Importance: Expected
Priority: Desired
Use Frequency: Rarely
Main Success Scenario:
  1. User visits "user accounts" page
  2. click to view own profile
  3. see editable details in own user-profile page
Alternative 2a
Scenario Extensions:
    User wishes to view another user's profile
    1. click to view another user's profile
    2. see basic details in user-profile page
Variations
  1. If the request is from an administrator, the whole profile can be seen.

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.