User requirements for UK e-Science grid environments Bruce Beckles University of Cambridge Computing Service.

Slides:



Advertisements
Similar presentations
Quantitative and Scientific Reasoning Standard n Students must demonstrate the math skills needed to enter the working world right out of high school or.
Advertisements

Supporting further and higher education e-Learning and Pedagogy overview Helen Beetham Programme Consultant.
Re-factoring grid computing for usability Bruce Beckles University of Cambridge Computing Service.
Vanessa Pinfold and Terry Hammond Developing a carer strategy for the UK Mental Health Research Network.
Chapter 2 – Software Processes
Surveys and Questionnaires. How Many People Should I Ask? Ask a lot of people many short questions: Yes/No Likert Scale Ask a smaller number.
Evaluating tests and examinations What questions to ask to make sure your assessment is the best that can be produced within your context. Dianne Wall.
User-Interface Design Process Lecture # 6 1Gabriel Spitz.
Identifying Needs and Establishing Requirements John Thiesfeld Jeff Morton Josh Edwards.
Active Review for Intermediate Designs [Clements, 2000]
Chapter 8 The Information Systems Planning Process Meeting the Challenges of Information Systems Planning Charles Cohen Presented by: Pablo De Luca.
Project Workshops Results and Evaluation. General The Results section presents the results to demonstrate the performance of the proposed solution. It.
03/12/2001 © Bennett, McRobb and Farmer Requirements Capture Based on Chapter 6 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Copyright Shanna Smith & Tom Bohman (2003). This work is the intellectual property of the authors. Permission is granted for this material to be shared.
Action Research: For Both Teacher and Student
Chapter 33 Conducting Marketing Research. The Marketing Research Process 1. Define the Problem 2. Obtaining Data 3. Analyze Data 4. Rec. Solutions 5.
Chapter 8: Systems analysis and design
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Developing a result-oriented Operational Plan Training
1 WXGC6102: Object-Oriented Techniques Requirements Capture References: Chapter 6 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
CSE323 การวิเคราะห์และออกแบบระบบ (Systems Analysis and Design) Lecture 03: Requirements Capture Requirements Analysis.
Web Analysis CIS 376 Bruce R. Maxim UM-Dearborn. Web Formulation Activities Identify business need for WebApp Work with stakeholders to describe WebApp.
Making a great Project 2 OCR 1994/2360. Analysis This is the key to getting it right. Too many candidates skip through this section. It’s worth 20% of.
PROPOSING TO WRITE A PROPOSAL? BY PAPIA BAWA. What are Proposals? Long reports usually written in response to a specific request or in response to your.
WEB DESIGN AND PROGRAMMING Get a job. WEB DESIGN AND PROGRAMMING What do employers look for? In your resume – Clean layout, use clear headers and subheads.
There are many occasions for fact-finding during the database system development lifecycle. fact-finding is particularly crucial to the early stages of.
Using Human Component Mapping TO ANALYSE & INTEGRATE HUMAN FACTORS ISSUES & RECORDS WITH RAILWAY HAZARD LOGS 1 Dr. Amanda C. Elliott, Simon Macmull & Harry.
Problem Definition Chapter 7. Chapter Objectives Learn: –The 8 steps of experienced problem solvers –How to collect and analyze information and data.
Regional Seminar 2005 EVALUATING POLICY Are your policies working? How do you know? School Development Planning Initiative.
Therese E. Ritter, MCT New Horizons Computer Learning Centers— Great Lakes A Look at Conflict and Consensus in Decision Making.
Introducing Pegasus: An ethnographic study of the ‘use’ of Grid technologies by the UK particle physics community Will Venters Department of Information.
Addressing Concerns from Patients General rule of thumb: If a person does not want to answer these questions, move on. Do not force the issue. Simply record.
Allison Bloodworth, Senior User Interaction Designer, Educational Technology Services, University of California - Berkeley October 22, 2015 User Needs.
Lecture 7: Requirements Engineering
CS2003 Usability Engineering Usability Evaluation Dr Steve Love.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Requirements Engineering Requirements Elicitation Process Lecture-6.
Requirements Collection By Dr. Gabriel. Requirements A requirement is any function, constraint, or property that the system must provide, meet, or satisfy.
The S.B.R.L. Caller Guide The Best Methods for How to Get Completions.
12/10/15.  It is a Cross Life Cycle Activity (CLCA) that may be performed at any stage ◦ In fact, some part of it (e.g. risk analysis and management)
Writing Software Documentation A Task-Oriented Approach Thomas T. Barker Chapter 5: Analyzing Your Users Summary Cornelius Farrell Emily Werschay February.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall4-1 Interactive Methods to collect Information Requirements Interviewing.
Critiquing a Consulting Proposal  First, think the way the client does  Then, make sure you produce what the client expects, only better.
Behavioral Interviewing Judy Rychlewski Director of Career Services William Jewell College Adaptations by Susan Wade, Baker University.
Systems Development Life Cycle
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
Cover Letter YOUTH CENTRAL – Cover Letters & Templates
Copyright © 2014 by The University of Kansas Developing Multisector Task Forces or Action Committees for the Initiative.
©2011 1www.id-book.com Data Gathering Chapter 7. ©2011 Data Gathering What is data gathering? –The act of gathering data through a study The data can.
© 2007 Open Grid Forum Enterprise Best (Community) Practices Workshop OGF 22 - Cambridge Nick Werstiuk February 25, 2007.
Lecture 10 More Innovation SE3821 Software Requirements and Specification Dr. Rob Hasker (based on slides by Dr. Brad Dennis)
A user-friendly approach to grid security Bruce Beckles University of Cambridge Computing Service A user-friendly approach to grid security “Grid ‘security’?
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Research Methodology & Design. Research: from theory to practice PhilosophyParadigm Theoretical approach Information collection approach Information collection.
Sample Project Context INFO 330. The Deliverables Analyze Org Project Scope Stakeholder analysis User Usability Surveys Personas Info Heuristics Content.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
© 2015 albert-learning.com How to talk to your boss How to talk to your boss!!
44222: Information Systems Development
Proposal Template Project Based Learning Exercise Mehr 1386 Edmond Zahedi.
INFORMATION AND PROGRESS An analysis of what is happening in the Caribbean with information, decision- making and progress in Education.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
SME Instrument How will my proposal be assessed? Bruce Ainsley (in my opinion, based on my experience)
Product Presentation Chapter 14 Presenting the Product Section 14.1 Product Presentation Section 14.2 Objections Section 14.1 Product Presentation Section.
Reporting Overview Business Goals Demystify the report menu
INFORMATION AND PROGRESS
Unit 6: Application Development
Critique Jon Kolko Professor, Austin Center for Design.
Developing and using questionnaires
Presentation transcript:

User requirements for UK e-Science grid environments Bruce Beckles University of Cambridge Computing Service

Background (1) Growing technical concern about “grid technologies”: –Suitability and Direction –particularly amongst “grid developers” and deployers –over the last year “Workshop on Requirements Capture for Collaboration in e-Science” Intense discussion within the UK Grid Engineering Task Force (ETF)

Background (2) – WSRF The WSRF standard: –announced at the start of the year –“the way forward for grid technology” WSRF is an “open standard”: –designed “in secret”, with “limited consultation” –by the Globus Alliance, IBM and HP Concern about the viability of current e-Science projects

A Technical Perspective “grid technologies” and “grid infrastructure”: –“low level plumbing” for “grid applications” If the plumbing is wrong then application development is futile. “The Globus Toolkit” / “WSRF”: –What is the question? –No question, can’t critique!

Another Perspective… Grid technology developer: “Here’s a thing I just developed. I’m sure it’ll be useful to you for something or other. Go on, give it a whirl…” Grid infrastructure developer: “OK, I’ll deploy it so that my application developers can use it. Boy, this sure is complicated to deploy… Umm, what did you say it should be used for again?” Grid application developer: “Right, so this is the latest grid technology? Great. I’ll build it into my application… Now my application is five times as large, doesn’t do anything useful and I have a migraine. Why am I doing this?” End-user: “I am confused. Please help.”

What problem are we trying to solve? Difficult problem but no clear formulation: –can’t use systematic approach, so… –use combination of: Intuition: complex problem, intuition unreliable Trial and error: complex problem, lots of trials! Luck The ETF’s goal: To deploy grid infrastructure that is useful to the UK e-Science community Is it useful?: –Don’t know unless have a clear, technical statement of “useful” –So…

The ETF’s position (then) Concerned that: –not delivering useful “grid infrastructure” –not clear what it should deliver –not clear what “grid technology” to use A requirements gathering exercise: –Gather data to help address these concerns –Some more enthusiastic than others

Proposed Requirements Capture Exercise Discussed on ETF mailing list Active involvement by ETF members Intended consultation with: –UK e-Science Usability Task Force (UTF) –UK e-Science User Group

Phase 1: Contacts Canvass ETF: –opinions on relevant: issues people –detailed interviews as appropriate Ask e-Science Centres via ETF: –description of their projects –contacts for these projects –contacts for other projects that might benefit from “grid technology”. Examine UK e-Science Stakeholders Meeting attendance list Use ‘snowball’ technique to gather further contacts

Phase 2: Requirements Elicitation Analyse contacts to determine ‘representative’ cross-section Undertake contextual interviews: –about 5 interviews/‘user group’ –about 10 such groups Raw data made available to interested parties

Phase 3: Requirements Analysis Data analysis: –Contextual Design (Beyer & Holtzblatt) –Interaction Design (Cooper & Reimann) Produce: –user personas (‘grid users’) –user scenarios (‘grid application use’) Derive: –detailed use cases –technical specifications

Phase 4: Validation Choose representative sample of contacts Design questionnaire: –Describe newly generated requirements –Ask respondents to rate them in importance Follow best survey practice

So what happened? “the ETF should not put too much effort into gathering new statements of requirements” “other groups should take this responsibility” – Director,. UK e-Science Core Programme (as reported to the ETF).

The ETF’s position (now) “Requirements analysis? Never heard of it.” (I paraphrase)

And from this we learnt? Requirements gathering is a political activity. So either: –be willing to defy political authorities, or –convince them that you will validate their decisions, or –convince them that you will produce nothing of interest.

So now? No longer directly working for e-Science Programme. Still working within University of Cambridge Responsible for: –promotion of e-Science and its related technologies within University –allows a scaled-down version of requirements gathering University of Cambridge: –leading research university, so… likely to have a reasonably representative sample of potential users of “grid technology”. So watch this space… (and all help gratefully received!…)