1 Ontology Summit 2011 Track 3 Value Metrics & Value Models Ontology Use - Maintenance Todd Schneider Raytheon 17 February 2011.

Slides:



Advertisements
Similar presentations
Making the System Operational
Advertisements

SOFTWARE MAINTENANCE 24 March 2013 William W. McMillan.
1 / 24 CS 425/625 Software Engineering Software Evolution Based on Chapter 21 of the textbook [SE-8] Ian Sommerville, Software Engineering, 8 th Ed., Addison-Wesley,
Software Configuration Management
Software Quality Metrics
SAK5102 Software Evaluation Measuring External Attributes.
Systems maintenance & adoption Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: November 2013.
SIM5102 Software Evaluation
1 Software Engineering II Presentation Software Maintenance.
Notion of a Project Notes from OOSE Slides - modified.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification.
Maintenance = Software Evolution Any changes after the client has accepted the product is considered maintenance. n Any Changes? n What might these be?
Software Process and Product Metrics
Software maintenance Managing the processes of system change.
CS 577b Software Engineering II -- Introduction
Chapter 9 – Software Evolution and Maintenance
SEG Software Maintenance1 Software Maintenance “The modification of a software product after delivery to correct faults, to improve performance or.
1 Earth System Modeling Framework ESMF Usability and Training
11/09/2015Dr Andy Brooks1 MSc Software Maintenance MS Viðhald hugbúnaðar Fyrirlestrar 1 & 2 The SWEBOK Chapter on Software Maintenance © IEEE
Software Metrics - Data Collection What is good data? Are they correct? Are they accurate? Are they appropriately precise? Are they consist? Are they associated.
SOFTWARE ENGINEERING1 Introduction. Software Software (IEEE): collection of programs, procedures, rules, and associated documentation and data SOFTWARE.

Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Error reports as a source for SPI Tor Stålhane Jingyue Li, Jan M.N. Kristiansen IDI / NTNU.
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
SQA System Overview Chapter 4. Where we have been so far, Where we are going Where do software errors come from? What is quality? How can quality be measured?
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Using error reports in SPI Tor Stålhane IDI / NTNU.
Other Quality Attributes Other Important Quality attributes Variability: a special form of modifiability. The ability of a system and its supporting artifacts.
Chapter 11 Maintaining the System System evolution Legacy systems Software rejuvenation.
Question To know that quality has improved, it would be helpful to be able to measure quality. How can we measure quality?
SOFTWARE MAINTENANCE 1. TOPICS TO BE DISCUSSED.. Definition of Maintenance Software Maintenance Types of Maintenance Maintenance Process Need of Maintenance.
A Best Practice Approach for Software Maintenance - Sustaining Critical Capability Paul R. Croll Chair, IEEE Software and Systems Engineering Standards.
Manag ing Software Change CIS 376 Bruce R. Maxim UM-Dearborn.
Software evolution l Software evolution is the term used in software engineering (specifically software maintenance) to refer to the process of developing.
The Traditional System Development Life Cycle There are a number of important steps in the creation of a system, regardless of which approach you use.
SOFTWARE ENGINEERING1 Introduction. SOFTWARE ENGINEERING2 Software Q : If you have to write a 10,000 line program in C to solve a problem, how long will.
Software quality factors
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 21 Slide 1 Software evolution 1.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Software Maintenance Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
Herriman High Computer Programming 1A Software Development Cycle Things to Know.
1 Overview of Maintenance CPRE 416-Software Evolution and Maintenance-Lecture 3.
Objectives Understand Corrective, Perfective and Preventive maintenance Discuss the general concepts of software configuration management.
CS352 – Software Engineering II Lecture 17: SW Quality Assurance Landscape Slides by Mohammad El-Ramly, PhD.
System Maintenance Modifications or corrections made to an information system after it has been released to its customers Changing an information system.
Economic Justification. Good Enough Quality Time to market Time to market Time to profit Time to profit.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 21 Slide 1 Software evolution.
CS223: Software Engineering Lecture 32: Software Maintenance.
Software Maintenance1 Software Maintenance.
1 / 14 CS 425/625 Software Engineering Software Change Based on Chapter 27 of the textbook [SE-6] Ian Sommerville, Software Engineering, 6 th Ed., Addison-Wesley,
Software Development Module Code: CST 240 Chapter 6: Software Maintenance Al Khawarizmi International College, AL AIN, U.A.E Lecturer: Karamath Ateeq.
Tutorial 4 IT323.  Q1. As a software project manager in a company that specializes in the development of software for the offshore oil industry, you.
1 Ontology Summit 2011 Track 3 Value Metrics & Value Models Synthesis Rex Brooks Starbourne Communications Todd Schneider Raytheon 31 March 2011.
Software Configuration Management
Overview Software Maintenance and Evolution Definitions
Maintenance Issues in Software Engineering
Chapter 18 Maintaining Information Systems
McCall’s Quality Factors
Introduction SOFTWARE ENGINEERING.
Software Development CMSC 202.
How does a Requirements Package Vary from Project to Project?
CS 425/625 Software Engineering Software Evolution
Systems maintenance & adoption
Software Development Process
Maintenance.
Chapter 9 – Software Evolution and Maintenance
Software metrics.
Chapter 8 Software Evolution.
Software Maintenance Main issues: why maintenance is such an issue
Presentation transcript:

1 Ontology Summit 2011 Track 3 Value Metrics & Value Models Ontology Use - Maintenance Todd Schneider Raytheon 17 February 2011

2 Ontology Maintenance To what Extent does the Use of Ontologies and Semantic Technologies Improve or Worsen the Maintenance of Services, Systems or Products that employ them? For Services, Systems or Products using Ontologies How much does the Cost of Maintenance affect the Value Proposition?

3 Maintenance Modification of a product after delivery to correct faults, to improve performance or other attributes ISO/IEC 14764: –Corrective maintenance: Reactive modification of a software product performed after delivery to correct discovered problems. –Adaptive maintenance: Modification of a software product performed after delivery to keep a software product usable in a changed or changing environment. –Perfective maintenance: Modification of a software product after delivery to improve performance or maintainability. –Preventive maintenance: Modification of a software product after delivery to detect and correct latent faults in the software product before they become effective faults.

4 Question Metrics Should Answer What costs are increased or reduced in corrective, adaptive, perfective, or preventive maintenance with the use of ontologies?

5 Maintenance Costs vs Metrics Maintenance costs in systems using ontologies will vary depending on how ontologies are used in the system (e.g., life-safety critical) but the metrics will be the same.

6 Corrective Maintenance (aka Bug Fixes) Metrics –Numbers of concepts or relations modified –Number of rules/axioms modified –Number of sub-systems/components impacted –Lines of codes impacted –Amount of testing needed –Amount of change to documentation –Legal consequences/costs

7 Adaptive/Perfective Maintence Metrics –Number of additional ontologies –Number of additional or modified concepts or relations –Number of addition rules/axioms –Lines of code impacted –Number of tests modified –Amount of testing needed –Amount of change to documentation –Amount of change to training

8 Preventive Maintenance Metrics –Numbers of concepts or relations modified –Number of rules modified –Number of sub-systems/components impacted –Lines of codes impacted –Amount of testing needed –Amount of change to documentation

9 Cost Dependences Depends on ontology & axiom/rule complexity –Possible huge impact on testing Depends on how ontologies used in system –Information Model –Workflow/Process control –User Interface –Deployment –Simulation –Training

10 Conjecture To the extent that the use of ontologies and semantic technologies simplifies a system, there is an equivalent reduction in maintenance efforts and costs.

11 Next Steps Continue discussion on Community Input Page –OntologySummit2011_ValueMetrics_CommunityInput (Initial population TBD).OntologySummit2011_ValueMetrics_CommunityInput Metric(s) and values mapped to each category of the Ontology Application Framework (Track 1) –Matrix will be added to Community Input page