Desire Product - ScanBooker

Product #10

"ScanBooker"

Purpose of the Product

"The reason the product is being developed."

Background of the project

"A short description of the work being done, and the situation that triggered the analysis effort."

<p>The Cognition and Brain Sciences Unit (CBSU) of the Medical Research Council conduct research studies involving brain scanning of volunteer subjects. </p> <p>At the CBSU's home in Cambridge, England, a new Magnetic Resonance Imaging (MRI) scanner has recently been installed. Organisational development to support research studies involving the scanner is continuing. </p> <p>In addition to providing an internal scanning service to CBSU researchers, the scanner is used externally by other researchers in Cambridge in three ways: </p> <ul> <li> direct collaboration with a member of the CBSU; </li> <li> scheduled time that the CBU assigns to members of the Wolfson Brain Imaging Centre (WBIC) under the two centres collaborative agreement (these scans would not necessarily involve a direct collaboration with any member of the CBSU); </li> <li> via a commercial party (e.g. drug company) buying scanner time from the CBSU. </li> </ul> <p>A number of CBSU staff have expressed the desire to develop a database system to support the scanning service. To form agreement about which of various directions of system implementation to take, and to de-risk the implementation of service support, the motivation arose to analyse the requirements of supporting a scanning service. </p> <p>Since the software development was started, this requirements document has been maintained to reflect the broadening scope of the system and deepening analysis of the work. </p>

Goals of the work

"Create and maintain a capacity to make medical images"

Stakeholders

"The roles or names of people and organizations who will finance or otherwise contribute to, or are affected by the product."

<p>The host, members, and friends of <a href="http://appropriatesoftware.net/scanbooker/Home.html"><em>ScanBooker</em></a> club. </p>

Users of the Product

"A list of the potential users of the product."

<h4>The Unit Administrator</h4> <p>Reviews radiographer hours, hours of scanning time, planning volunteer payments, billing grants, billing external organisations for scanner time. </p> <h4>The Facility Administrator</h4> <p>Scanner scheduling, scanning session confirmation, radiographer time, MRI training courses, tracks studies, tracks activity ethical approvals, selling scanner time, respond to data requests from volunteers, audits and reports on activity ethical approvals, audits and reports on studies. </p> <h4>The Receptionist</h4> <p>Welcomes visitors when arriving for appointments at the unit. </p> <h4>The Diary Secretary</h4> <p>Send email of 'next week' diary events to all staff. </p> <h4>The Scanner Radiographer</h4> <p>Getting volunteer information, recording volunteer screening, volunteer consent forms, booking volunteers into slots, recording any problems with scanning (per slot), recording experience with volunteers. </p> <h4>The Researcher</h4> <p>Involved with making applications for approval of study, reviewing scanning schedule to request slots, specifying requirements for volunteers (e.g older, left handed, English as native language). Reviewing record of their own training, booking themselves in for training slots. Reviewing number of scans still available on their ethics approval. Adding feedback about volunteers (good subject, moved a lot, a bit claustrophobic etc). Adding comments about success of scanning slots for feedback. Preparing and submitting ethics approval forms. </p> <h4>The Untrained Researcher</h4> <p>A researcher who has not successfully completed the scanner safety training course. </p> <h4>The Volunteer Subject</h4> <p>Register specifying availability, choosing scanning slots from those available that match their profile, receive and respond to invitations to attend scanning slots, terminate registration, make requests for data under the data protection act. </p> <h4>The External Researcher</h4> <p>A researcher who is not a member of the unit. These researchers will probably need similar access to that of internal researchers (as above) perhaps with some restrictions. </p> <p>External researchers download visitors forms (which they all have to sign before they can scan here), downloading various other forms (our consent form etc). </p> <h4>The Buildings Maintenance Engineer</h4> <p>Conducts maintenance tasks within the MRI Scanner Building. </p> <h4>The Software Maintenance Engineers</h4> <p>Maintain and upgrade the product. </p>

Naming Conventions and Definitions

"A glossary containing the meanings of all names, acronyms, and abbreviations used within the requirements specification. Select names carefully to avoid giving a different, unintended meaning."

<h4>The Unit</h4> <p>The Cognition and Brain Sciences Unit (CBSU) of the Medical Research Council. </p> <h4>The Facility</h4> <p>Part of the unit used to provide scanning services. </p> <h4>The Imaging Management Committee (IMC)</h4> <p>Management committee for the facility. </p> <h4>The IIG</h4> <p>? </p> <h4>MRI Scanner</h4> <p>Magentic Resonance Imaging scanner. </p> <h4>MRI Scanner Building</h4> <p>The building within which the MRI scanner is located. </p> <h4>MEG Scanner</h4> <p>Magnetic Ecephalography scanner. </p> <h4>Block</h4> <p>A 15 minute interval of time on a scanner. Blocks are used to make variable length slots. </p> <h4>Slot</h4> <p>A variable length interval of time on a scanner. Slots are made from a continuous set of blocks. </p> <h4>Scanning Session</h4> <p>A slot. </p> <h4>Video Training Session</h4> <p>A training session where researchers receive instruction about safety. </p> <h4>Practical Training Session</h4> <p>A training session where researchers learn practical aspects of safety. </p> <h4>Research Activity</h4> <p>A specific process or procedure that will be undertaken within a study. </p> <h4>Study</h4> <p>A scientific study conducted by researchers. </p> <h4>Structural Scan</h4> <p>A scan of the anatomical structure of a brain. </p> <h4>Functional Scan</h4> <p>A scan of the functional dynamics of a brain. </p> <h3>Adjacent Work</h3> <p>The scanning work is adjacent to: </p> <ul> <li> the Imaging Management Committee's proceedings </li> <li> the scanner system </li> <li> the researchers' studies </li> <li> the ethics committees </li> <li> the unit's internal accounting system </li> <li> the unit's external billing system </li> <li> the panel assessment system (shared register of volunteers) </li> <li> the population of potential researchers </li> <li> the population of potential volunteers </li> </ul>

Scope of the Work

"An analysis of the stories that might be supported by the new product."

The product supports these stories:

Story #124
"Hide week when updating schedule"

Story #125
"Read week of scanning schedule"

Story #126
"Read details of scanning session"

Story #127
"Register new medical imaging research project"

Story #128
"Read help messages which explain application functionality"

Story #129
"Register new medical imaging researcher"

Story #130
"Earmark scanning schedule time for various purposes"

Story #131
"Set a registered organisation as the default"

Story #132
"Register new medical imaging research ethics approval"

Story #133
"Read details of scanning schedule earkmark"

Story #21
"Create new scanning session"

Story #142
"Create new scanner maintenance session"

Story #143
"Conduct scanner maintenance session"

Story #144
"Recruit new volunteers for scanning studies"

Story #145
"Promote external researcher usage of scanner facility"

Story #146
"Researcher requests place on scanning training course"

Story #147
"Schedule more scanning training courses"

Story #148
"Researcher attends video training session"

Story #149
"Create scanning training appointment"

Story #150
"Cancel scanning training appointment"

Story #151
"Researcher attends scanning training practical"

Story #152
"Propose new scanning study to Imaging Management Committee"

Story #153
"Imaging Management Committee approves new scanning study"

Story #154
"Propose new research activity to Medical Ethics Committee "

Story #155
"Medical Ethics Committee approves new research activity"

Story #156
"Apply for extension to medical ethics approval"

Story #157
"Medical Ethics Committee approves extension to medical ethics approval"

Story #158
"Researcher requests scanning sessions"

Story #159
"External researcher requests scanning sessions"

Story #160
"Call for registered volunteers to attend scanning sessions"

Story #161
"Volunteer cancels scanning session"

Story #162
"Volunteer attends scanning appointment"

Story #163
"Check structural scans"

Story #164
"Report on usage of scanning time"

Story #165
"Charge internal scanning usage"

Story #166
"Charge external scanning usage"

Story #167
"Send scanning facility conduct guidelines to researcher"

Story #179
"Make notes about scanning schedule week"

Story #180
"Read notes about scanning schedule week"

Story #181
"Book registered volunteers into scanning sessions"

Story #30
"Create, read, update, or delete records of the objects of the domain"

Story #182
"Read list of active volunteers"

Story #183
"Read list of active projects"

Story #184
"Register new cost code"

Story #185
"Report on projects using scanning facility time"

Story #186
"Report on medical ethics committee approvals in use at scanning facility"

Story #187
"Create new scanner methods session"

Story #188
"Report what happened in scanning session"

Story #189
"Record scanning training session outcome"

Story #190
"Read list of upcoming scanning training sessions"

Story #252
"Adjust applied application constraints on user operations"

Story #253
"Read account of cost of project scanning sessions "

Story #255
"Use a Web browser client to interact with the system."

Story #256
"Read list of scan image files"

Story #257
"View scan image"

Story #258
"Receive message alerts for upcoming events (such as approval renewal)"

Story #27
"Register new medical imaging research volunteer subject"

Scope of the System

"Determine, with the appropriate stakeholders, which part of the story should be supported by some sort of product and what part should be done entirely by the user."

The product shall satisfy these requirements:

Notes

<p>These requirements haven't yet been associated with any stories. </p> <h4>Look and Feel Requirements</h4> <p><em>"This section contains requirements relating to the spirit of the product, particular demands for the product, such as corporate branding, colors to be used, and so on."</em> </p> <p>The product shall look and feel like a smart, business-like, university-based, software application service. </p> <p>The product shall carry the unit's logo in the corporate colour of PMS 228 except on printable forms which shall carry the unit's logo in greyscale. </p> <p>The product shall look and feel uncluttered and friendly. </p> <h4>Maintainability and Support Requirements</h4> <p><em>"Specification of the time necessary to make specified changes to the product, the level of support that the product requires, and description of other platforms or environments to which the product must be ported"</em> </p> <h4>Maintenance Requirements</h4> <p>The product shall be maintained within the unit. </p> <h4>Supportability Requirements</h4> <p>The product shall be supported within the unit. </p> <h4>Adaptability Requirements</h4> <p>The product is expected to run under Linux. </p> <p>The product might eventually be provided to other research scanning facilities in the UK (~15), in Europe (~30?), and in the US (~150). </p> <h3>Original Document</h3> <p>This document started life as a <a href="http://project.kforge.appropriatesoftware.net/scanbooker/trac/wiki/RequirementsSpecification">wiki page</a>. </p>

Collections

This product has been included in the following collections:

Collection
Medical Research

END

Desire

Sections:

In this section:

"ScanBooker"

Product #10

"ScanBooker"

Purpose of the Product

Background of the project

Goals of the work

Stakeholders

Users of the Product

Naming Conventions and Definitions

Scope of the Work

Scope of the System

Data model Requirements

Legal Requirements

Look and feel Requirements

Functional Requirements

Security Requirements

Notes

Collections