Topic 1: Emerging paradigms for improvements of software reliability Outbrief summary.

Slides:



Advertisements
Similar presentations
-Grids and the OptIPuter Software Architecture Andrew A. Chien Director, Center for Networked Systems SAIC Chair Professor, Computer Science and Engineering.
Advertisements

1 From Grids to Service-Oriented Knowledge Utilities research challenges Thierry Priol.
Information Society Technologies programme 1 IST Programme - 8th Call Area IV.2 : Computing Communications and Networks Area.
© Chinese University, CSE Dept. Software Engineering / Software Engineering Topic 1: Software Engineering: A Preview Your Name: ____________________.
Software Engineering 1. Software development – the grand view 2. Requirements engineering.
4.1.5 System Management Background What is in System Management Resource control and scheduling Booting, reconfiguration, defining limits for resource.
Secure software and COTS group Steve Gribble, Somesh Jha, Angelos Keromytis, Carl Landwehr, Peter Lee, Martin Rinard Workshop on Resilient Financial Information.
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
High-confidence Software for Cyber Physical Systems Drexel University Philadephia, PA Vanderbilt University Nashville, Tennessee Aniruddha Gokhale *, Sherif.
Dynamic Service Composition with QoS Assurance Feb , 2009 Jing Dong UTD Farokh Bastani UTD I-Ling Yen UTD.
The Architecture Design Process
Software Testing and Quality Assurance: Introduction and Terminology
CSC 402, Fall Requirements Analysis for Special Properties Systems Engineering (def?) –why? increasing complexity –ICBM’s (then TMI, Therac, Challenger...)
Software Architecture in Practice
April 13, 2004CS WPI1 CS 562 Advanced SW Engineering General Dynamics, Needham Tuesdays, 3 – 7 pm Instructor: Diane Kramer.
1 FM Overview of Adaptation. 2 FM RAPIDware: Component-Based Design of Adaptive and Dependable Middleware Project Investigators: Philip McKinley, Kurt.
Maintenance = Software Evolution Any changes after the client has accepted the product is considered maintenance. n Any Changes? n What might these be?
PRINCE2: 2009 in Practice Andy Murray, Outperform BPUG Workshops at Project Challenge are supported by:
Issues and Ideas in Software Reliability for FCS Joe Loyall BBN Technologies.
 A set of objectives or student learning outcomes for a course or a set of courses.  Specifies the set of concepts and skills that the student must.
HW/SW/FW Allocation – Page 1 of 14CSCI 4717 – Computer Architecture CSCI 4717/5717 Computer Architecture Allocation of Hardware, Software, and Firmware.
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
OASIS WSQM TC Meeting Dugki Min. 컴퓨터공학부 건국대학교 Agenda 1. Roll Call 2. Review and approval of the agenda 3. Review and approval of the previous.
RUP Design RUP Artifacts and Deliverables
Virtualization: Not Just For Servers Hollis Blanchard PowerPC kernel hacker.
Software Engineering Introduction and Overview Takes customer-defined goals and constraints and derives a representation of function, performance, interfaces,
Programming Models & Runtime Systems Breakout Report MICS PI Meeting, June 27, 2002.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
High Performance Embedded Computing © 2007 Elsevier Lecture 3: Design Methodologies Embedded Computing Systems Mikko Lipasti, adapted from M. Schulte Based.
4.2.1 Programming Models Technology drivers – Node count, scale of parallelism within the node – Heterogeneity – Complex memory hierarchies – Failure rates.
10 Software Architecture CSCU 411 Software Engineering.
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Advanced Computer Networks Topic 2: Characterization of Distributed Systems.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Investigating Survivability Strategies for Ultra-Large Scale (ULS) Systems Vanderbilt University Nashville, Tennessee Institute for Software Integrated.
SONIC-3: Creating Large Scale Installations & Deployments Andrew S. Neumann Principal Engineer, Progress Sonic.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
Software Reliability Research Pankaj Jalote Professor, CSE, IIT Kanpur, India.
Software Metrics Cmpe 550 Fall Software Metrics.
Software Debugging, Testing, and Verification Presented by Chris Hundersmarck November 10, 2004 Dr. Bi’s SE516.
Architecture Analysis Techniques
NetQoPE: A Middleware-based Netowork QoS Provisioning Engine for Distributed Real-time and Embedded Systems Jaiganesh Balasubramanian
A QoS Policy Modeling Language for Publish/Subscribe Middleware Platforms A QoS Policy Modeling Language for Publish/Subscribe Middleware Platforms Joe.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
CSE 303 – Software Design and Architecture
Dr. DEVENDRA TAYAL– THE SCOPE OF SOFTWARE ENGINEERING.
Variability ViewPoint Runtime Vari-Arch, 2010 Danny, Elisa and Jennifer.
SelfCon Foil no 1 Variability in Self-Adaptive Systems.
Topic 2: The Role of Open Standards, Open-Source Development, & Different Development Models & Processes (on Industrializing Software) ARO Workshop Outbrief,
Hosted by: Institute for Software Integrated Systems (ISIS) Vanderbilt University Software Reliability for FCS Discussion Format May 18-19, 2004 ARO Workshop.
Simula Research Laboratory Lokaliteter & Forskning
ARO Workshop Wendy Roll - May 2004 Topic 4: Effects of software certification on the current balance between software/system modeling, analysis and testing.
Computing Systems: Next Call for Proposals Dr. Panagiotis Tsarchopoulos Computing Systems ICT Programme European Commission.
Services – a perspective on building applications Richard Swale ETSI TIPHON Wg1 chair VoIP Technologist BTexaCT ITU Workshop on IP Networking and Mediacom.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
Gerhard Dueck -- CS3013Architecture 1 Architecture-Centric Process  There is more to software development then going blindly through the workflows driven.
ARO Workshop Wendy Roll - May 2004 Topic 4: Effects of software certification on the current balance between software/system modeling, analysis and testing.
© Chinese University, CSE Dept. Software Engineering / Software Engineering Topic 1: Software Engineering: A Preview Your Name: ____________________.
CS 5150 Software Engineering Lecture 21 Reliability 2.
Syndicate Members: 1. GC Muhammad Uzair 2. GC Umer Naveed Malik.
Project Management What is Project Management?
Architecting Web Services
Architecting Web Services
IEEE Std 1074: Standard for Software Lifecycle
Software Reliability It is defined as the ability of a system or component to perform its required functions under stated conditions for a specified period.
Architectures of distributed systems
Supply chain management
Presentation transcript:

Topic 1: Emerging paradigms for improvements of software reliability Outbrief summary

ARO Workshop – Topic 1 2 Topic 1: Emerging paradigms for improvements of software reliability Issues and research ideas (1)  How to represent, understand and visualize complex dependencies among components?  We have to recognize that SW will never be perfect. We better prepare to accept and manage imperfect SW, and research should focus on this.  Fault management should be integrated with planning to figure out how to reconfigure the system upon a failure. Software FDIR–How?  Fault containment and isolation must be designed into SW systems (as it is designed into physical systems)  Cost of SW reliability has to be considered in the context of ROI.  QoS issues should be address both statically (design-time) and dynamically (run-time). Both have to be addressed while building FCS.  Scale of complexity: code size, multiple end-to-end req’s in a distributed systems, multiple layers, changing number of participants, very dynamic environment

ARO Workshop – Topic 1 3 Topic 1: Emerging paradigms for improvements of software reliability Issues and research ideas (2)  Model-based Analysis/Testing requires a model (abstraction) of the system based on the requirements. How does this scale up to the level of system of systems on FCS?  What is being done: guidelines for FCS suppliers (JA-1003)  If commercial technology is used, QoS concerns (“controls”) have to be “bolted” onto it. Consequence: technology-neutral specification of QoS is needed.  QoS-based resource allocation – trade-offs between reliability and other aspects.  Model-based toolchains should allow debugging in terms of the high-level models.  Novel paradigm: Dynamic adaptability / Goal-driven programming – To address needs of fault mgmt – Analogy with adaptive control … but must be analyzable..  Paradigms should support early analysis with uncertain requirements – Design space exploration