Reusing Modeling Elements in IV&V Thomas Otani Naval Postgraduate School 2009 NASA Independent Verification and Validation (IVV) Annual Workshop John Ryan.

Slides:



Advertisements
Similar presentations
NATIONAL AERONAUTICS AND SPACE ADMINISTRATION 1 NASA Earth Science Data Systems (ESDS) Software Reuse Working Group CEOS WIGSS-22 Annapolis, MD September.
Advertisements

Testing Workflow Purpose
Chapter 05: Evolutionary Requirements Definition : Requirements  “Requirements are capabilities and conditions to which the system, and more broadly.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Systems Engineering in a System of Systems Context
Establishing IV&V Properties Steve Raque, NASA IV&V Facility Dr. Doron Drusinsky, Naval Postgraduate School 9/4/20091Establishing IV&V Properties.
Soft. Eng. I, Spring 07Dr Driss Kettani, from I. Sommerville1 CSC-3324: Chapter 5 Requirements Engineering Reading: Chap. 6, 7 + annex.
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
SE 555 – Software Requirements & Specifications Introduction
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
Introduction to Software Testing
IV&V Facility Model-based Design Verification IVV Annual Workshop September, 2009 Tom Hempler.
System Software Integration Testing Mars Polar Lander Steven Ford SYSM /05/12.
Chapter : Software Process
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
Transitioning From Software Requirements Models to Design Models
S/W Project Management
UML - Development Process 1 Software Development Process Using UML (2)
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Second RMSIG Workshop Methodology and Process Wolfram Höpken.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
8:15 AM Tuesday September 15, 2009 Karl Frank, Point of Contact for Constellation Projects Establishing IV&V Expectations Diagrams for illustrative purposes.
Rational Unified Process Fundamentals Module 4: Disciplines II.
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
T. Dawson, TASC 9/11/13 Use of a Technical Reference in NASA IV&V.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Object-Oriented Analysis and Design An Introduction.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Ocean Observatories Initiative Data Management (DM) Subsystem Overview Michael Meisinger September 29, 2009.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Rational Unified Process Fundamentals Module 5: Implementing RUP.
Modeling Component-based Software Systems with UML 2.0 George T. Edwards Jaiganesh Balasubramanian Arvind S. Krishna Vanderbilt University Nashville, TN.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Systems Analysis and Design in a Changing World, Fourth Edition
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Chapter 1 Applying UML and Patterns. The Need for Software Blueprints Knowing an object-oriented language and having access to a library is necessary.
Validating Requirements Determining Completeness and Correctness of Requirements Using the System Reference Model IV&V Workshop 16 September 2009.
Process: A Generic View
IV&V T ESTING S TRATEGIES FOR I NDEPENDENT V ERIFICATION OF NASA M ISSION S OFTWARE I MPLEMENTATION 3 rd Annual Workshop on Independent Validation and.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Software Prototyping Rapid software development to validate requirements.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Prof. Hany H. Ammar, CSEE, WVU, and
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Coming up: Unified Modeling Language Introduction.
Software Engineering Lecture 10: System Engineering.
September 8, 2008NASA IV&V Facility Workshop on Validation Morgantown, WV 1 SRM Reuse Presented by Thomas W. Otani Joint work with Doron Drusinsky, Bret.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Introduction to the Unified Modeling Language.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
Model Based Engineering Environment Christopher Delp NASA/Caltech Jet Propulsion Laboratory.
Critical Systems Testing Experts EXB Solutions - Contact us at cFS Workshop – Automated Test for NASA cFS David C. McComas 1, Susanne.
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Introduction to Software Testing
System Modeling Assessment & Roadmap Joint OMG/INCOSE Working Group
Chapter 1 The Systems Development Environment
Presentation transcript:

Reusing Modeling Elements in IV&V Thomas Otani Naval Postgraduate School 2009 NASA Independent Verification and Validation (IVV) Annual Workshop John Ryan Reuse Working Group Lead

Outline The IV&V Reuse Working Group The System Reference Model (SRM) Reuse in SRM Reusable Modeling Elements SRM Reuse Framework Intermediate Reuse Repository Conclusion 2009 IVV Annual Workshop2Sept 15 - Reusing Modeling Elements

The Reuse Working Group Objectives Provide reusable modeling artifacts to support in NASA IVV efforts to:  Reduce labor cost and time of product deliverables  Reduce duplication of modeling artifacts  Increase scope, flexibility, and responsiveness  Leverage previous understandings of systems and behaviors 2009 IVV Annual Workshop3Sept 15 - Reusing Modeling Elements

The Reuse Working Group Previous Goals Define the definition and attributes of reuse and use artifacts Define how reuse integrates with the product lines Define the process and requirements for a Reuse Repository Current Goals To demonstrate the feasibility and value of reuse through focused projects To increase the supply and availability of reusable artifacts To increase community capability and interest to leverage existing artifacts 2009 IVV Annual Workshop4Sept 15 - Reusing Modeling Elements

The Reuse Working Group Scope The WG will define and recommend areas within modeling, validation, and verification activities for reuse, and will provide support (analytical, development, management, and training) to enable reuse within those activities across projects. Focus on: Reuse of existing artifacts Reuse of newly developed artifacts derived from existing artifacts Developing initial modeling, assertion, and report templates Reuse of modeling artifacts (Initially) Reuse for science and exploration mission projects 2009 IVV Annual Workshop5Sept 15 - Reusing Modeling Elements

System Reference Model We advocate the use of System Reference Model (SRM) for the IV&V team to capture its understanding of the problem domain The SRM contains Written Use Cases UML artifacts and a set of formal assertions and accompanying test scenarios to model precisely the required behavior of the system 2009 IVV Annual Workshop6Sept 15 - Reusing Modeling Elements

Executable SRM We advocate that the SRM be executable for it to be truly useful Executable SRM includes a computer-aided tool to validate behavior specifications Software automation is the key to the successful validation (and verification) of the behaviors of complex systems Traditional manual process is woefully inadequate in locating subtle errors in increasingly complex software-intensive systems of systems 2009 IVV Annual Workshop7Sept 15 - Reusing Modeling Elements

Reuse in SRM Two types of reuse in SRM: Adoption Reuse  An existing artifact (e.g. activity diagram) is reused in another product Instantiation Reuse  A concrete artifact is created from a generic template An idea of generic assertion template was presented at IEEE SSIRI IVV Annual Workshop8Sept 15 - Reusing Modeling Elements

Sample Assertion Template Resusing Modeling ElementsSept 15 - IVV Annual Workshop9

Test Scenario Patterns These are the types of test patterns that must accompany every assertion Obvious Success Obvious Failure Event Repetitions Time-interval Repetitions Overlapping Time-interval Repetitions Resusing Modeling ElementsSept 15 - IVV Annual Workshop10

More Reusable Modeling Elements Behavioral and structural products for conceptual system and subsystem views Written Use Cases, Use Case Diagrams, Activity Diagrams, Sequence Diagrams, Communication Diagrams, State Diagrams, Class Diagrams Goals, Constraints, External Actors/Stakeholders, Some Internal Actors, Actions/Functions Reuse by Context: Subsystem, Behavior, Design Choices, Mission Characterizations 2009 IVV Annual Workshop11Sept 15 - Reusing Modeling Elements Note: The actions/functions in Behavioral Diagrams may be reusable but not necessarily in the sequence defined in the diagrams

More Reusable Modeling Elements SysGoals Product PBRA Products Assertions Behavioral and structural products associated with design subsystem component views Other Reports, References, Templates 2009 IVV Annual Workshop12Sept 15 - Reusing Modeling Elements

Example: SysGoals Product Characterize/Classify Missions by: Mission Type: Orbiter/Lander Location/Destination: Earth Orbit, Non-Earth Planetary Orbit Orbit Type: LEO, Polar, Geocentric, etc. Number of Orbiters, Solo/Cluster Overall Objectives and Science Requirements Communication Signal Bands and Availability Autonomous vs. Commanded Operations Length of Mission Launch and Landing Plans Environment/Conditions Environmental Limitations and Safety Precautions Capabilities, Limitations, and Risks 2009 IVV Annual Workshop13Sept 15 - Reusing Modeling Elements

Modeling Reuse with Classifications Identify Commonalities and Differences Associate Goals to Characterizations Associate Sub Goals to Characterizations Develop Reusable SysGoal Products in respect to context by characterization 14Sept 15 - Reusing Modeling Elements2009 IVV Annual Workshop Common and Generic Goals, Behaviors, Actions, Actors, etc. Additional and Specific Goals, Behaviors, etc. for Classification

NEAP Project 2009 IVV Annual Workshop15Sept 15 - Reusing Modeling Elements

Reuse Process 16Sept 15 - Reusing Modeling Elements2009 IVV Annual Workshop Reuse Repository Reuse Repository Discovery Packaging Classification Search Validation Adaptation/ Integration

SRM Reuse Framework Three initial use cases to identify the actors and behaviors of the desired reuse library: Add SRM artifacts to the reuse library Browse the reuse library Retrieve and reuse SRM artifacts 2009 IVV Annual Workshop17Sept 15 - Reusing Modeling Elements

Use Case: Add SRM Artifacts 2009 IVV Annual Workshop18Sept 15 - Reusing Modeling Elements

Use Case: Browse Artifacts 2009 IVV Annual Workshop19Sept 15 - Reusing Modeling Elements

Use Case: Browse by Activity 2009 IVV Annual Workshop20Sept 15 - Reusing Modeling Elements

Use Case: Retrieve and Reuse 2009 IVV Annual Workshop21Sept 15 - Reusing Modeling Elements

Conceptual Model 2009 IVV Annual Workshop22Sept 15 - Reusing Modeling Elements

Elements in the Prototype 2009 IVV Annual Workshop23Sept 15 - Reusing Modeling Elements

Intermediate Reuse Repository Reuse Working Group is using svn to control new reuse artifacts within a Together Project: The Reuse Repository Working Group acts as current librarian to define or accept new reuse additions The Reuse Repository will provide different folder views to browse by: [contexts] Behavior Product Subsystem (associate reusable products) Design Component (associated reusable products) Project {All contexts may be further decomposed by classifications} 2009 IVV Annual Workshop24Sept 15 - Reusing Modeling Elements

A Prototype Beyond svn Eclipse plugin Must integrate with other tools used by the IV&V team First prototype will support Only basic searches by id and name Backend database is object-oriented Artifacts maintained in the XML format Sept 15 - IVV Annual Workshop25Resusing Modeling Elements

Conclusion Short-term Goal Implement the prototype Intermediate Reuse Repository using svn  Evaluate the prototype for its effectiveness  Promote the use of Intermediate Reuse Repository with a pilot project Start the construction of a basic proof-of-concept prototype that supports only a limited number of elements in the reuse conceptual model Long-term Goal Meet the Objectives and Goals of the Reuse Working Group  Reuse (of modeling elements) becomes a fully integrated aspect of the IV&V workflow 2009 IVV Annual Workshop26Sept 15 - Reusing Modeling Elements

Questions? 2009 IVV Annual Workshop27Sept 15 - Reusing Modeling Elements