SAS_06_STOL_Tool_Cooper Automated Systems Test and Operations Language (STOL) Analysis Tool Jason G. Cooper July 20, 2006.

Slides:



Advertisements
Similar presentations
E-Science Data Information and Knowledge Transformation Thoughts on Education and Training for E-Science Based on edikt project experience Dr. Denise Ecklund.
Advertisements

High level QA strategy for SQL Server enforcer
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 1: Introduction.
2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Test Automation Success: Choosing the Right People & Process
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Universal Design for Learning (UDL). UD in Architecture a movement of designing structures with all potential users in mind incorporated access features.
Action Research in Healthcare: judging value and impact Dr Annetta Smith
Symptomatic Analysis for Software Maintenance A technology designed for SERC.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Software Metrics II Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
Active Review for Intermediate Designs [Clements, 2000]
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Certified Business Process Professional (CBPP®)
Resume Extraction with Business Process Management (BPM) tools
SQA Architecture Software Quality.
Business Process Management Certification Tony Benedict.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Computer Systems & Architecture Lesson Software Product Lines.
LÊ QU Ố C HUY ID: QLU OUTLINE  What is data mining ?  Major issues in data mining 2.
The design process z Software engineering and the design process for interactive systems z Standards and guidelines as design rules z Usability engineering.
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
UML - Development Process 1 Software Development Process Using UML (2)
Overview of the Database Development Process
SAS_08_AADL_Exec_Gluch MAC-T IVV Model-Based Software Assurance with the SAE Architecture Analysis & Design Language (AADL) California Institute.
 The software systems must do what they are supposed to do. “do the right things”  They must perform these specific tasks correctly or satisfactorily.
1 Software Testing (Part-II) Lecture Software Testing Software Testing is the process of finding the bugs in a software. It helps in Verifying and.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
CLEANROOM SOFTWARE ENGINEERING.
Ciarán O’Leary Wednesday, 23 rd September Ciarán O’Leary School of Computing, Dublin Institute of Technology, Kevin St Research Interests Distributed.
Independent Verification and Validation (IV&V) Techniques for Object Oriented Software Systems SAS meeting July 2003.
RUP Implementation and Testing
Design Science Method By Temtim Assefa.
Risk Management for Technology Projects Geography 463 : GIS Workshop May
WP4/T4.1 D4.1 Detailed Report on Indicators. Overall stragtegy Case studies Types of networks Types of impact indicators (Network) Model definition Algorithm.
Learning outcomes for BUSINESS INFORMATCIS Vladimir Radevski, PhD Associated Professor Faculty of Contemporary Sciences and Technologies (CST)
(On secondment at) Praxis High Integrity Systems Bath Dependable Systems Group School of Mathematical & Computer Sciences Heriot-Watt University Edinburgh.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Lecture on Computer Science as a Discipline. 2 Computer “Science” some people argue that computer science is not a science in the same sense that biology.
A Design Science (Multi-Methodological) Approach to IS Research Presented by: Dr. Jay F. Nunamaker, Jr. 1.
CHAPTER 6 Employee Training and Development
MSFC Avionics Department Flight Software Group CMM Level 2 Certified Automated Software Coding Standards System Development Team Assessment Team Luis Trevino.
Development of Methodologies for Independent Verification and Validation of Neural Networks NAG OSMA-F001-UNCLASS Methods and Procedures.
Systems Analysis and Design in a Changing World, Fourth Edition
Chapter 3: Software Project Management Metrics
An Evaluation Tool for Natural Language Processing Systems Audrey N. Mbeje Department of Computer Science Ball State University November 09, 2000.
Reusing Modeling Elements in IV&V Thomas Otani Naval Postgraduate School 2009 NASA Independent Verification and Validation (IVV) Annual Workshop John Ryan.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
Theme 2: Data & Models One of the central processes of science is the interplay between models and data Data informs model generation and selection Models.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 15a: Product Metrics for Software Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Stanford University 1 CADUI' June FUNDP Namur The Mecano Project Angel R. Puerta Knowledge Systems Laboratory Stanford University Stanford.
July, 2008 Impati – Software Test Solutions. July, Contents Testing Service Overview and Approach Test Services and Industries Key Services Offering.
Methodology Review Chapter 7 Part 2: Design Methodology Object-Oriented Modeling and Design Byung-Hyun Ha
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
CHAPTER 7 Employee Training and Development
Intelligent Systems Development
Risk Management for Technology Projects
DT249/4 Information Systems Engineering Lecture 0
PMRIPT Portal Team.
Software Independent Verification and Validation (IV&V)
HCI in the software process
Ada – 1983 History’s largest design effort
HCI in the software process
Human Computer Interaction Lecture 14 HCI in Software Process
Chapter 2 Process Models
Dept. of Computation, UMIST
Presentation transcript:

SAS_06_STOL_Tool_Cooper Automated Systems Test and Operations Language (STOL) Analysis Tool Jason G. Cooper July 20, 2006

2SAS_06_STOL_Tool_Cooper Outline Problem/Approach Overview Problem/Approach Overview General Discussion General Discussion Technology Readiness Level Technology Readiness Level Potential Applications Potential Applications Data Availability Data Availability Barriers Barriers In-Depth Project Plans In-Depth Project Plans

July 20, SAS_06_STOL_Tool_Cooper Problem / Approach The IV&V community has expressed a need for automated assistance in regards to STOL script analyses activities The IV&V community has expressed a need for automated assistance in regards to STOL script analyses activities Currently, practitioners have no automated methods to assist in analysis triage for STOL scripts Currently, practitioners have no automated methods to assist in analysis triage for STOL scripts To research algorithms and methodologies most suitable for STOL test script analysis Develop and evaluate an automated analysis tool to assist practitioners with STOL-related tasks Phase One Activities: Initial Knowledge Discovery Tool Software Development Verification and Test Evaluation Recommendations

July 20, SAS_06_STOL_Tool_Cooper Outline Problem/Approach Overview Problem/Approach Overview General Discussion General Discussion Technology Readiness Level Technology Readiness Level Potential Applications Potential Applications Data Availability Data Availability Barriers Barriers In-Depth Project Plans In-Depth Project Plans

July 20, SAS_06_STOL_Tool_Cooper Technology Readiness Level (TRL) This project begins at TRL 2 This project begins at TRL 2 TRL 2 (Technology Concept Formulated) is focusing theories and principles on the specific application area TRL 2 (Technology Concept Formulated) is focusing theories and principles on the specific application area In this project’s case, the team will be determining complexity and behavioral metrics to be used for automated analysis techniques In this project’s case, the team will be determining complexity and behavioral metrics to be used for automated analysis techniques

July 20, SAS_06_STOL_Tool_Cooper Potential Applications The development of such an automated analysis tool has the potential for usage in STOL script activities across multiple domains. The development of such an automated analysis tool has the potential for usage in STOL script activities across multiple domains. A commonly phrased mantra is “test like you fly, fly like you test.” In following this testing framework, an analysis tool could offer benefits not only to verification of flight software test activities, but also to command scripts used for mission operations. A commonly phrased mantra is “test like you fly, fly like you test.” In following this testing framework, an analysis tool could offer benefits not only to verification of flight software test activities, but also to command scripts used for mission operations.

July 20, SAS_06_STOL_Tool_Cooper Data Availability The research team is currently identifying which STOL version to focus initial efforts, as well as most commonly-occurring STOL script errors in the IV&V domain The research team is currently identifying which STOL version to focus initial efforts, as well as most commonly-occurring STOL script errors in the IV&V domain Several potential projects, which utilized STOL, are available for retrospective analyses Several potential projects, which utilized STOL, are available for retrospective analyses The specific project for test and evaluation will be determined in the latter stages of the software development phase The specific project for test and evaluation will be determined in the latter stages of the software development phase

July 20, SAS_06_STOL_Tool_Cooper Barriers STOL Version: determining the most common version of the scripting language will limit the applicability of the initial tool. In the second phase, this may be mitigated by supporting multiple versions of the scripting language. STOL Version: determining the most common version of the scripting language will limit the applicability of the initial tool. In the second phase, this may be mitigated by supporting multiple versions of the scripting language. Metrics: standard complexity metrics will apply to portions of this scripting language. However, certain aspects of the language require new metrics to be assessed. Metrics: standard complexity metrics will apply to portions of this scripting language. However, certain aspects of the language require new metrics to be assessed.

July 20, SAS_06_STOL_Tool_Cooper Outline Problem/Approach Overview Problem/Approach Overview General Discussion General Discussion Technology Readiness Level Technology Readiness Level Potential Applications Potential Applications Data Availability Data Availability Barriers Barriers In-Depth Project Plans In-Depth Project Plans

July 20, SAS_06_STOL_Tool_Cooper Initial Knowledge Discovery Determine behavioral knowledge to extract from STOL constructs Determine behavioral knowledge to extract from STOL constructs Determine complexity metrics to apply Determine complexity metrics to apply Capture most commonly occurring STOL errors in IV&V project for domain knowledge Capture most commonly occurring STOL errors in IV&V project for domain knowledge

July 20, SAS_06_STOL_Tool_Cooper Tool Software Development Requirements Definition Requirements Definition Architecture Definition Architecture Definition Implementation Implementation Unit Testing and “Seed” Testing Unit Testing and “Seed” Testing

July 20, SAS_06_STOL_Tool_Cooper Verification and Test Evaluation Select project and underlying STOL scripts Select project and underlying STOL scripts IV&V practitioner and tool analyze 50% of selected scripts; results comparison IV&V practitioner and tool analyze 50% of selected scripts; results comparison Practitioner utilizes tool for remaining 50% of scripts; feedback and usability captured Practitioner utilizes tool for remaining 50% of scripts; feedback and usability captured

July 20, SAS_06_STOL_Tool_Cooper Questions?