Alberto Pasquini CARE Workshop 14-15/4/2001 Page 1/11 CARE Workshop Alberto Pasquini Assessment of Software Intensive and Interactive Systems Deep Blue.

Slides:



Advertisements
Similar presentations
Chapter 13: The Systems Perspective of a DSS
Advertisements

Chapter 1: The Database Environment
Chapter 26 Legacy Systems.
Chapter 27 Software Change.
Chapter 24 Quality Management.
No 1 IT Governance – how to get the right and secured IT services Bjorn Undall and Bengt E W Andersson The Swedish National Audit Office Oman
1 EBIP Synthesis Report Preliminary policy messages Vladimir López-Bassols, OECD EBIP Workshop October 2001, Rome.
2 Introduction A central issue in supporting interoperability is achieving type compatibility. Type compatibility allows (a) entities developed by various.
Cultural Heritage in REGional NETworks REGNET. REGNET Development process.
Integra Consult A/S Safety Assessment. Integra Consult A/S SAFETY ASSESSMENT Objective Objective –Demonstrate that an acceptable level of safety will.
Page 1 CARE/ASAS Activity 3: ASM workshop Brétigny, 19 December 2001 Autonomous Aircraft OHA CARE-ASAS Activity 3: ASM Autonomous Aircraft OHA.
Winter Education Conference Consequential Validity Using Item- and Standard-Level Residuals to Inform Instruction.
Modern Systems Analyst and as a Project Manager
Ch.1 Introduction to Software Engineering The Evolution 1.1 The Evolving Role of Software 1/15 In the early days: User Computer Software = Place a sequence.
Chapter 14 Software Testing Techniques - Testing fundamentals - White-box testing - Black-box testing - Object-oriented testing methods (Source: Pressman,
Minimum Weight Plastic Design For Steel-Frame Structures EN 131 Project By James Mahoney.
Mafijul Islam, PhD Software Systems, Electrical and Embedded Systems Advanced Technology & Research Research Issues in Computing Systems: An Automotive.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement 1.
Lecture 8: Testing, Verification and Validation
Software Tools Lecture 10: Software Tools Dr Valentina Plekhanova University of Sunderland, UK.
Chapter 11 Software Evolution
Formal models of design 1/28 Radford, A D and Gero J S (1988). Design by Optimization in Architecture, Building, and Construction, Van Nostrand Reinhold,
Global Analysis and Distributed Systems Software Architecture Lecture # 5-6.
Database Administration
From Model-based to Model-driven Design of User Interfaces.
Improving System Safety through Agent-Supported User/System Interfaces: Effects of Operator Behavior Model Charles SANTONI & Jean-Marc MERCANTINI (LSIS)
Scalable Rule Management for Data Centers Masoud Moshref, Minlan Yu, Abhishek Sharma, Ramesh Govindan 4/3/2013.
5 december 2011 Living Probabilistic Asset Management Dr.ir. J.A. van den Bogaard.
CS540 Software Design Lecture 1 1 Lecture 1: Introduction to Software Design Anita S. Malik Adapted from Budgen (2003) Chapters 1.
Reliability Risk Assessment
Chapter 11 Artificial Intelligence and Expert Systems.
SESSION 10 MANAGING KNOWLEDGE FOR THE DIGITAL FIRM.
Notion of a Project Notes from OOSE Slides - modified.
Meaningful Learning in an Information Age
Introduction to Systems Analysis and Design
Hazards Analysis & Risks Assessment By Sebastien A. Daleyden Vincent M. Goussen.
IT Job Roles Task 20. Software Engineer Job Description Software engineers are responsible for creating and maintaining software of various different.
1 Prediction of Software Reliability Using Neural Network and Fuzzy Logic Professor David Rine Seminar Notes.
Chapter 1 Database Systems. Good decisions require good information derived from raw facts Data is managed most efficiently when stored in a database.
Introduction to Systems Analysis and Design Trisha Cummings.
DeFINE Workshop, Pisa, 25-26/11/2002 1/11 Cognitive Ergonomics Alberto Pasquini Deep Blue Srl.
Lecture 1 What is Modeling? What is Modeling? Creating a simplified version of reality Working with this version to understand or control some.
Chapter 1 Software and Software Engineering. A Quick Quiz 1. What percentage of large projects have excess schedule pressure? 25% 50% 75% 100% 2. What.
Business Analysis and Essential Competencies
11 C H A P T E R Artificial Intelligence and Expert Systems.
ETICS2 All Hands Meeting VEGA GmbH INFSOM-RI Uwe Mueller-Wilm Palermo, Oct ETICS Service Management Framework Business Objectives and “Best.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
Challenges of unusually many under-prepared electrical engineering students Error Minding Gaps within the Bubble Presenter: Simon Winberg.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
David Baglee Dr. David Baglee. School of Computing & Technology E: T: Reliability Centred Maintenance.
Fundamentals of Information Systems, Third Edition2 Principles and Learning Objectives Artificial intelligence systems form a broad and diverse set of.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Lecture 7: Requirements Engineering
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Software Maintenance Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Chapter 2: Software Maintenance Omar Meqdadi SE 3860 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
RLV Reliability Analysis Guidelines Terry Hardy AST-300/Systems Engineering and Training Division October 26, 2004.
Describe the potential of IT to improve internal and external communications By Jim Green.
Human Reliability HUMAN RELIABILITY HUMAN ERROR
DeSIRE Workshop, Pisa, 25-26/11/2002 1/7 A Case Study in Air Traffic Control Alberto Pasquini Deep Blue Srl.
Alberto Pasquini – Deep Blue Safety Assessment in MFF ASAS TN2 3-5 April 2006, Rome MENU: COVER | SUMMARY | OVERVIEW | TASKS | ALLOCATIONSCOVER SUMMARY.
Virtual Track Surveying Paul Furniss. An introduction to Omnicom Engineering A few words from Gary Sanford the UK Sponsor What is the OmniSurveyor3D System?
Software Project Management
Tools of Software Development
Chapter 8 Software Evolution.
Hazards Analysis & Risks Assessment
Chapter 1: Software and Software Engineering
Presentation transcript:

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 1/11 CARE Workshop Alberto Pasquini Assessment of Software Intensive and Interactive Systems Deep Blue

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 2/11 System functions are used in a process and are the results of a combination of computerized tools and human agents Humans have a central role in performing the activities needed for the for the process goals Large amount of information are stored and managed and elaborated by computers Organizational structures, rules, operative procedures, training, other hardware and software tools play a key role in the process The problem (1) Software Intensive and Interactive Systems

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 3/11 Provide inputs for decision making during design, certification, assessment and operation Quantitative risk assessment in safety analysis and safety cases Easy comparison between different systems and different architectural solutions The problem (2) Potential benefits of the quantitative analysis of Software Intensive and Interactive Systems

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 4/11 Reliability growth models can provide information about: failure rate, or number of residual faults, or failure on demand State of the art State of the art in the quantitative analysis of Software Intensive and Interactive Systems When combined with information about software architectures and operative usages they can give us information about the reliability of these architectures Used for design decision (when to stop testing, etc.) Limited confidence in the quantitative measure R1R1 R2R2 R3R3 R4R4 R5R5 P1P1 P2P2 P3P3 P4P4 P5P5 P6P6

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 5/11 Static characterisation of the operational profile of these systems Limitations of the state of the art (1) Still based on task models of errors when considering the interaction with human agents The operative environment changes (Arianne 5) Interactions with operators changes with skill and training (Therac 25) Procedures and rules are revised and up-dated (Italian railways) ProbabilityActivity 3x10 -3 Error of omission where the items being omitted are embedded in a procedure rather than at the end 3x10 -2 General human error of commission … Chernobyl (deliberated deactivation of the reactor protection system) Colwich, Purely, Cowden, Watford Junction, etc. (train driver failing to apply the brakes after acknowledging receipt of audible and visual warning of red signal)

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 6/11 Limitations of the state of the art (2) System boundary Extended System boundary Adapted from Fault Tree Handbook – Nuclear Regulatory Commission

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 7/11 The research proposal What can reasonably be done (Considering that as we enlarge the circle we are dealing with a more and more uncertain environment) A research proposal based on Distributed Cognition and Reliability Engineering switching the focus on the knowledge needed for the process and on its availability

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 8/11 Distributed Cognition developed to analyse the interaction of humans with cognitive artefacts Human cognition (and activity) mediated by artefacts (rules, tools, representations), internal and external to the mind Ability of the human mind in processing symbolic information strongly bounded, and complex activity requires the aid of artefacts Knowledge for human cognitive activity not located exclusively in the brain, but distributed among brain and cognitive artefacts employed to carry out the activity Distributed Cognition (1) writing, printing and computers shopping list, book-marker

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 9/11 Knowledge can be distributed in different ways between human and cognitive artefacts needed for the activity Distribution changes with time Knowledge stored in artefacts from which it can be activated and used Distributed Cognition (2) Knowledge more or less easy to maintain and to up-date, depending on the type of components wherein it is stored easily and naturally context sensitive help, or hardware tool with "affordance"with difficulty guideline, difficult to locate, or with unclear procedures

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 10/11 Model of knowledge distribution within a process Analysis of different possible distributions and of their evolution Estimation of the probability that knowledge is available and correctly activated (for example a software procedure containing the knowledge of the designers) Distributed Cognition + Reliability Engineering Comparison of different possible design solutions with different distributions of knowledge

Alberto Pasquini CARE Workshop 14-15/4/2001 Page 11/11 Safecomp Safety and Reliability of Industrial Computer Systems Budapest, Hungary, Sept ISSRE Software Reliability Engineering Hong Kong, China, 28 Nov. - 1 Dec With associated workshop on Software Assessment Cross fertilisation of Communities (or ads.)