Digital inclusion – a CS perspective Alex Poulovassilis ESRC TLRP-TEL Inclusion and Impact conference, 10-11 June 2010.

Slides:



Advertisements
Similar presentations
Knowledge Exchange for Impact: Perspectives from Relu Amy Proctor Newcastle University.
Advertisements

1 Stakeholder Engagement in Relu Jeremy Phillipson Assistant Director, Relu Programme.
Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Prescriptive Process models
CS487 Software Engineering Omar Aldawud
CS 325: Software Engineering January 13, 2015 Introduction Defining Software Engineering SWE vs. CS Software Life-Cycle Software Processes Waterfall Process.
Evaluation of a Large-scale VRE Implementation - ELVI Staff and students using the VRE benefit from the greater transparency and communication that it.
Alternate Software Development Methodologies
ISE554 Human Computer Interaction Design 2.2 User Interface Design.
Chapter Extension 19 Alternative Development Techniques © 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke.
Provisional draft 1 ICT Work Programme Challenge 2 Cognition, Interaction, Robotics NCP meeting 19 October 2006, Brussels Colette Maloney, PhD.
SE 450 Software Processes & Product Metrics 1 Defect Removal.
© 2003 Turoff 1 The Nature of Information Systems and Employment in IS Murray Turoff Information Systems Department.
Ch7: Software Production Process. 1 Questions  What is the life cycle of a software product?  Why do we need software process models?  What are the.
CS351 - Software Engineering (AY2005)1 What is software engineering? Software engineering is an engineering discipline which is concerned with all aspects.
DECISION SUPPORT SYSTEM DEVELOPMENT
© 2005 Prentice Hall2-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
CSC230 Software Design (Engineering)
Frequently asked questions about software engineering
Lecture 1.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Chapter 1- Introduction
Chapter 1- Introduction Lecture 1 Ready, fire, aim (the fast approach to software development). Ready, aim, aim, aim, aim... (the slow approach to software.
S/W Project Management
CSI315 Web Applications and Technology Overview of Systems Development (342)
PGD-1303 Software Project Management?. What is software? Software  Computer programs and associated documentation Documentation includes  requirements.
Chapter 2 The process Process, Methods, and Tools
Information Systems Security Computer System Life Cycle Security.
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
Developing a result-oriented Operational Plan Training
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
Principles on evaluating FIWARE relevance for Phase 3 proposals.
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
Lecture 7: Requirements Engineering
Lecture 1 The University of Lahore Software Engineering Saeed Akhtar
Systems Life Cycle A2 Module Heathcote Ch.38.
Software Engineering - Abdul Majeed. What is software? Definition of Software Engineering Software Process Generic view of Software Engineering Software.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Ch7: Software Production Process. 1 Waterfall models  Invented in the late 1950s for large air defense systems, popularized in the 1970s  Main characteristics:
An Introduction to Software Engineering. Objectives  To introduce software engineering and to explain its importance  To set out the answers to key.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification.
Teaching slides Chapter 1. Chapter 1: Introduction Introduction Components of a computer Building the software products What is software engineering?
Chapter 1- Introduction Lecture 1. Topics covered  Professional software development  What is meant by software engineering.  Software engineering.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
CS223: Software Engineering Lecture 16: The Agile Methodology.
CS223: Software Engineering Lecture 18: The XP. Recap Introduction to Agile Methodology Customer centric approach Issues of Agile methodology Where to.
1 Requirements Engineering for Agile Methods Lecture # 41.
Systems Development Process Developing our own software The Business Perspective Copyright © 2016 Curt Hill.
HO CHI MINH CITY NATIONAL UNIVERSITY HO CHI MINH CITY UNIVERSITY OF TECHNOLOGY SYSTEM ANALYSIS AND DESIGN LECTURER: Nguyen Thanh Tung.
Project Management Software development models & methodologies
Unit 6 Application Design.
CompSci 280 S Introduction to Software Development
Introduction to Systems Analysis and Design
Methodologies and Algorithms
Chapter 1- Introduction
Digital media & interaction design
Software Processes (a)
System Design Basics IB Computer Science.
Frequently asked questions about software engineering
Frequently asked questions about software engineering
Information Systems in Global Business Today
An Introduction to Software Engineering
What are your Career Options?
Fundamentals of Human Computer Interaction (HCI)
CS385T Software Engineering Dr.Doaa Sami
CS310 Software Engineering Lecturer Dr.Doaa Sami
Computing Science Education An Industry Perspective
Presentation transcript:

Digital inclusion – a CS perspective Alex Poulovassilis ESRC TLRP-TEL Inclusion and Impact conference, June 2010

Computer Science Computer Science is a relatively new and evolving discipline It has its roots in multiple disciplines and continues to have strong affinities with these: – maths, logic, physics, engineering, psychology, organisational psychology, management, philosophy … Computer systems involve both hardware and software: – this is sometimes blurred by references to (digital) technology – but there is a distinction between digital devices (and networks of these) – and the software that runs on them The discipline of Computer Science mostly involves research into, and development of, the software running on digital devices, not the devices themselves (the study of hardware is part of Computer Systems Engineering)

Computer Science – User Focus Within the discipline of Computer Science, the development of computer systems has always been strongly user-focussed: – 1940s/50s: individuals played roles of user, programmer, hardware engineer – 1960s/70s: increasing application areas for computer systems; formal career structures emerged for computer scientists; but users still involved in most phases of the software development process: Requirements analysis Specification Prototyping and user interface design Testing – 1990s onwards: advent of Agile software development methodology: user stakeholders are full members of the development team, with programmers team communication by face-to-face discussion rather than documents rapid feedback from testing and evaluation of small system increments

Computer Science & Digital Inclusion Importance of understanding the needs of users – how do the proposed services match with their current and evolving goals; what are their preferences for how to access these services? – Such concerns are naturally part of the design, evaluation and maintenance (evolution) of computer systems – It is important to involve user stakeholders as equal members within development and maintenance teams c.f. Agile methodology – All these aspects are part of the CS area of software engineering

Computer Science & Digital Inclusion Important that services are easy to understand, easy to use, non-threatening, appealing... so as to remove technology barriers and draw in previously excluded people: – These concerns are of relevance to the Human- Computer-Interaction (HCI) area of CS

Computer Science & Digital Inclusion Important not to lose sight of the individual user in designing new services Users individual needs should not be assumed to be fully catered for by addressing the perceived needs of a particular group of users (even if user stakeholders are involved as equal partners): – Importance of personalisation of service delivery, provided by the use of appropriate adaptation techniques within the software code – Importance of gathering and analysing information about users actual usage of services – hence need for information management, data mining

Computer Science & Digital Inclusion Importance of providing equivalent services with different interfaces or running on different hardware, for different user groups, according to their access needs and preferences: – Same core functionality but with some differences of interface or deployment – Modular software development, and management of multiple software configurations is part of the CS area of software engineering and has the potential to make more economically feasible the development and maintenance of multiple versions of software services

Computer Science & Digital Inclusion Importance of defining, and designing for, the role of new services within the broader processes that people and organisations will be using them within Importance of monitoring how deployment of new services alters these processes – This is part of information systems design

Conclusion Computer Scientists may be able to contribute to Digital Inclusion through their expertise and research in areas such as: – software engineering – software development methodologies – HCI – personalisation and adaptation – information management and data mining – information systems design

A note on Sustainability Hardware and software have a natural lifetime For the prototypes that are output by research projects, this may be quite short Open-source software and service-based software development can mitigate against this More importantly, the knowledge gained, methodologies developed and employed, fundamental computing techniques researched and developed, and evaluation results obtained, are all sustainable into the longer term future, to be built upon by new projects and initiatives