TWiki> ComputingStrategy Web>UseCases (revision 1)EditAttach

Currently this is basically just a paste from the file I was typing into at CSG. Tidying up in progress from me - and you?

Initials indicate the contributor; no initial means either me, or everyone, or indeterminate.


As an actor, I (as a non-research-compute-intensive standard academic) want use cases we might call:

access network, wireless [and wired]

conveniently read and edit files [i.e. all relevant viewers and editors - emacs,
pdfviewer, graphics file viewers and editors, stuff for reading MS
documents, sound, video... stuff in a std Linux distribution almost
covers it but there will be some other stuff...]

IS: edit MS documents

recover lost files [i.e. reliable backups]

write talks and papers [stuff above, plus LaTeX , Metafont,...]

write presentations, lectures and other teaching material, inc. videos, screencasts

write, get approved and submit grant applications

collaborate with colleagues, here or not, on
- formal papers
- informal notes
- software

configuration manage papers, lectures etc., including with remote people

set up a meeting, including booking a room for it (ideally, not just during office hours)

read web

write web pages and put them where (certain) other people can read them

write and run and distribute programs in various languages, various versions

print

email

arrange tutorials and other meetings with students (inc. by course/role/my responsibilities) - named groups not individuals...

set and mark work and submit marks and give feedback

set and mark online work and exams

check that the computing-based coursework I'm setting works as I expect

write and submit exams securely (preferably without having to queue
for a particular machine in fact!)

attend and give online meetings/seminars (Skype or equivalent)

get prompt help when something doesn't work for me

-- I want to be able to do this all off-site in an adequately secure way

-- and I want to have some of my personal stuff and some of my work
stuff in the same place (unison)



Then there is a lot of information that I want to be available and up
to date when I need it, mostly on the web; that is, I want to be able to:


Access

- or in some cases CRUD:

- student info (Euclid plus things not covered)

-- tutorial groups

-- examiners' meeting stuff

- staff info (rooms, phone numbers, web pages...)

- course info

- meeting info

- room booking info (ideally, I'd like to be able to book a room myself)

- seminar info

- recruitment info (securely; group file space...)

Some of this I also want to be able to update and make available to
the right people, e.g. course info.

Missing stuff:

heavy research computing

multicore and cluster computing

hosting virtual machine clusters that might be very temporary, elastic
(IS/PA) ][Layer on top making this easy for users to
do... possibilities exist...]

keeping things visible, archiving - e.g., course web pages for
previous instantiations, course software even harder; research data
following funder requirements;...

see other people's stuff, e.g. other courses that relate to mine
e.g. content of prerequisite courses as this cohort of students did
them

make research papers, software, people etc. visible and findable to
increase impact

mailing lists, more abstractly: communicate with groups of people who
are interested in some research or other topic

share calendar (IS)

Roles:

student
- undergrad
- taught postgrad
- research postgrad

admin ... finance, hr, ...

contract research staff

visitors

computing staff

---

Evolution...

Future requirements - trends, how may things change?

Different philosophies of working, e.g. preferring to self-manage vs
wanting stuff provided?

Two questions:
What are requirements?
How are these requirements met?

-- PerditaStevens - 24 Jul 2012

Edit | Attach | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 24 Jul 2012 - 13:26:34 - PerditaStevens
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies