T HE F IRST R ULE OF S OFTWARE S USTAINABILITY : D O NOT TALK ABOUT S OFTWARE S USTAINABILITY The Problem Time is a facile measurement of software sustainability.

Slides:



Advertisements
Similar presentations
Lehrstuhl Informatik V (Informationssysteme) Prof. Dr. M. Jarke Matthias Jarke I5-Jarke Dagstuhl Perspective Seminar Science of Design: High-Impact.
Advertisements

The complex evaluation framework. 2 Simple projects, complicated programs and complex development interventions Complicated programs Simple projects blue.
Intelligence Step 5 - Capacity Analysis Capacity Analysis Without capacity, the most innovative and brilliant interventions will not be implemented, wont.
Designing Postgraduate Curricula For Transdisciplinary Fields: The case of security and crime science Dr Hervé Borrion* and Prof Richard Wortley, UCL Security.
"Safe and Secure Solutions for Smarter Cities" The value of standardization and certification in planning and managing Smart Cities 12/05/2014Euralarm.
Early Effort Estimation of Business Data-processing Enhancements CS 689 November 30, 2000 By Kurt Detamore.
Software Testing and Quality Attributes Software Testing Module ( ) Dr. Samer Hanna.
Software Construction and Evolution - CSSE 375 Software Maintenance at 30K Feet Shawn and Steve Left – Tibet from ft. (~9 km).
‘Towards a competency model for adaptive assessment to support lifelong learning’ Onjira Sitthisak, Lester Gilbert and Hugh C. Davis Learning Technologies.
Automated Analysis and Code Generation for Domain-Specific Models George Edwards Center for Systems and Software Engineering University of Southern California.
History, Theory, and Philosophy of Science (In SMAC + RT) 7th smester -Fall 2005 Institute of Media Technology and Engineering Science Aalborg University.
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Integrating.
Environmental Terminology System and Services (ETSS) June 2007.
June 1, 2004Computer Security: Art and Science © Matt Bishop Slide #18-1 Chapter 18: Introduction to Assurance Overview Why assurance? Trust and.
Towards an Effective Software Component Certification Process Advisor Silvio Lemos Meira Student Alexandre Alvaro
CMM Overview - 1 © Paul Sorenson CMPUT Software Engineering refs. IEEE Software, March 1988, 73-79, and IEEE Software, July 1993, (Capability.
درس :مهندسي نيازمندي ها استاد: دكتر عبداله زاده دانشجو: خيرالنسا مرچانت Effectiveness of Elicitation Techniques in Distributed Requirement Engineering.
Modeling Software Sustainability W. Christopher Lenhardt RENCI – UNC, Chapel Hill, NC.
Integrative and Comparative Biology 2009 C. Schwenk, D.K. Padilla, G.S. Bakken, R.J. Full.
Software Process and Product Metrics
BIS310: Week 7 BIS310: Structured Analysis and Design Data Modeling and Database Design.
The Re-engineering and Reuse of Software
IT Professional Perspectives, Discussions, and Recommendations Steven K. Wall IT7833 IT Strategy, Policy and Governance.
ALISE 2014 Conference Jeonghyun Kim & William E. Moen
“Enhancing Reuse with Information Hiding” ITT Proceedings of the Workshop on Reusability in Programming, 1983 Reprinted in Software Reusability, Volume.
CSCE 548 Secure Software Development Test 1 Review.
Workshop Planning Sustainable Innovation 11:00-12:30.
1 Cooperative Wireless Networking Elza Erkip Department of Electrical and Computer Engineering Polytechnic Institute of New York University.
OASIS WSQM TC Meeting Dugki Min. 컴퓨터공학부 건국대학교 Agenda 1. Roll Call 2. Review and approval of the agenda 3. Review and approval of the previous.
Supplementary Specifications (Chapters 20,22 - Requirements Text) 1.
SCSC 311 Information Systems: hardware and software.
BUSINESS INFORMATICS descriptors presentation Vladimir Radevski, PhD Associated Professor Faculty of Contemporary Sciences and Technologies (CST) Linkoping.
Learning outcomes for BUSINESS INFORMATCIS Vladimir Radevski, PhD Associated Professor Faculty of Contemporary Sciences and Technologies (CST)
Basic Concepts Software Architecture. What is Software Architecture? Definition: – A software architecture is the set of principal design decisions about.
Becerra-Fernandez, et al. -- Knowledge Management 1/e -- © 2004 Prentice Hall Epilogue The Future of Knowledge Management.
Model-Driven Analysis Frameworks for Embedded Systems George Edwards USC Center for Systems and Software Engineering
UCLA Enterprise Directory Identity Management Infrastructure UC Enrollment Service Technical Conference October 16, 2007 Ying Ma
The International Classification for Patient Safety: an overview In collaboration with WHO Classifications, Standards and Terminology March 2011.
Abstract We present two Model Driven Engineering (MDE) tools, namely the Eclipse Modeling Framework (EMF) and Umple. We identify the structure and characteristic.
©Ian Sommerville 2004 Software Engineering. Chapter 28Slide 1 Chapter 28 Process Improvement.
Center for Reliable Engineering Computing (REC) We handle computations with care Founded 2000.
Cerberus: A Context-Aware Security Scheme for Smart Spaces presented by L.X.Hung u-Security Research Group The First IEEE International Conference.
Some Thoughts on Guidelines for Empirical Research Mike Barker Visiting Scholar, NAIST.
EVA Workshop, 26 March 2003, Florence, Italy1 COINE Cultural Objects In Networked Environments Anthi Baliou University of Macedonia,Library Thessaloniki,
IFS310: Module 6 3/1/2007 Data Modeling and Entity-Relationship Diagrams.
Software Testing Definition Software Testing Module ( ) Dr. Samer Odeh Hanna.
Method Engineering Fiona Gelink Group 3.  The method  Advantages of the method  Related literature  PDD  Steps of the method  References.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Process Modeling
Mittuniversitetet Building trust and confidence through sustainable information systems research Karen Anderson Professor, Archives and Information Science.
COMPUTER SCIENCE Computer science (CS) is The systematic study of algorithmic.
1 컴퓨터 교육 2 학기 김혜원 Teaching Networking and Operating System to Information Systems Majors D. Robert Adams and Carl Erickson Department of computer Science.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 9: Design Engineering Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Chapter 3: The Requirements Workflow [Arlow and Neustadt, 2005] CS 426 Senior Projects in Computer Science University of Nevada, Reno Department of Computer.
What is technology?. Technology is not… Only things that move Only computers Only things that use electricity.
NASA Earth Exchange (NEX) A collaborative supercomputing environment for global change science Earth Science Division/NASA Advanced Supercomputing (NAS)
Prevention & Protection SAME ENDS DIFFERENT MEANS? THE FUTURE STRUCTURE AND PURPOSE OF CFOA’ s PREVENTION AND PROTECTION ACTIVITIES.
Slide #18-1 Introduction to Assurance CS461/ECE422 Fall 2008 Based on slides provided by Matt Bishop for use with Computer Security: Art and Science.
Using core competencies in curriculum design
CSCE 548 Secure Software Development Test 1 Review
Introduction to Software Engineering
Assist. Prof. Magy Mohamed Kandil
WP2. Excellent university for the researchers
Model-Driven Analysis Frameworks for Embedded Systems
UNDERGROUNDCOAL.COM.AU March ’09
Software Engineering Experimentation
Automated Analysis and Code Generation for Domain-Specific Models
N E E D S Premier Courseware User Group Session
Utilizing CI environment for efficient and effective testing of NFRs
Presentation transcript:

T HE F IRST R ULE OF S OFTWARE S USTAINABILITY : D O NOT TALK ABOUT S OFTWARE S USTAINABILITY The Problem Time is a facile measurement of software sustainability. The field of computational science and engineering lacks a common definition and understanding of software sustainability. If you cannot define it, how can you measure it? If you cannot measure it, how can you engineer sustainable software? If you cannot define it, how can you educate or train domain scientists and software practioners? A lack of a definition results in a misalignment with established software engineering theory and best practice that enables software artifacts to endure. Software Sustainability is… …a composite, non-functional requirement (NFR), which is a measure of a number of software quality attributes. The genetic building blocks of technically sustainable software : Maintainability: the effort required to locate and fix an error in operational software; Extensibility: the software’s ability to be extended and the level of effort; required to implement the extension. #KarlskronaManifesto #SustainabilityDesign Sustainability is systemic. – … is multidimensional. – … is interdisciplinary. – … transcends the system’s purpose. – … applies to both a system and its wider contexts. – … requires action on multiple levels. – … requires multiple timescales. – Changing design to take into account long-term effects doesn’t automatically imply sacrifices. – System visibility is a precondition for and enabler of sustainability design. Education, Education, Education… Software Engineers already know how to build sustainable software. A lack of a definition results in a misalignment with established software engineering theory and best practice that enables software artifacts to endure. SWEBOK v3.0 establishes a baseline for the body of knowledge for the field of software engineering. The Challenge of Software Sustainability Defining the metrics and measures to demonstrate the sustainability of software and software systems. Venters et. al. (2014) The Blind Men and the Elephant: Towards an Empirical Evaluation Framework for Software Sustainability. Journal of Open Research Software, 2 (1). Venters et. al., (2014) Software Sustainability: The Modern Tower of Babel. Proceedings of the Third International Workshop on Requirements Engineering for Sustainable Systems co-located with 22nd International Conference on Requirements Engineering (RE 2014), Penzenstadler et. al., (2014). Safety, Security, now Sustainability: The Non-Functional Requirement for the 21.st Century IEEE Software, 31(3), pp: Becker et. al., (2015) Sustainability Design and Software: The Karlskrona Manifesto. In: 37th International Conference on Software Engineering, 16th-24th May 2015, Florence, Italy, Becker et. al., (2016) Requirements: The Key to Sustainability. IEEE Software Special Issue: The Future of Software Engineering. Venters et. al., (2014) Software Sustainability: The Modern Tower of Babel. Proceedings of the Third International Workshop on Requirements Engineering for Sustainable Systems co-located with 22nd International Conference on Requirements Engineering (RE 2014), Venters et. al., (2014) Software Sustainability: The Modern Tower of Babel. Proceedings of the Third International Workshop on Requirements Engineering for Sustainable Systems co-located with 22nd International Conference on Requirements Engineering (RE 2014), Becker et. al., (2015) Sustainability Design and Software: The Karlskrona Manifesto. In: 37th International Conference on Software Engineering, 16th- 24th May 2015, Florence, Italy, Penzenstadler et. al., (2014). Safety, Security, now Sustainability: the Non- Functional Requirement for the 21st Century IEEE Software, 31(3), pp: Becker et. al., (2016) Requirements: The Key to Sustainability. IEEE Software Special Issue: The Future of Software Engineering. #SustainabilityDesign #KarlskronaManifesto