Ron Kratzke, Vitech Corporation MBSE for System Testing Managing the development of system testing using the principles of Model.

Slides:



Advertisements
Similar presentations
Integration of MBSE and Virtual Engineering for Detailed Design
Advertisements

Requirements Specification and Management
Presentation by Prabhjot Singh
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Verification Planning and Compliance Matrices Brian Selvy Wednesday, August 13, :30 – 5:00 p.m. Phoenix West Conference Room.
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
CMPUT Software Process & QualityProcess Categories - slide# 1©P. Sorenson Engineering Process Category  Processes that specify, implement, or maintain.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
21st Annual Arizona Space Grant Consortium Symposium
Software Testing Prasad G.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
IV&V Facility Model-based Design Verification IVV Annual Workshop September, 2009 Tom Hempler.
Acquiring Information Systems and Applications
Enterprise Architecture
Effective Methods for Software and Systems Integration
S/W Project Management
CLEANROOM SOFTWARE ENGINEERING.
Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.
Software Configuration Management (SCM)
Merlin Bar Graph: Problems, Solutions, Progress Status
Software System Engineering: A tutorial
Software Engineering Chapter 8 Fall Analysis Extension of use cases, use cases are converted into a more formal description of the system.Extension.
1 Lecture 5.2a: SEF Ch 8 SE Outputs Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
From Use Cases to Test Cases 1. A Tester’s Perspective  Without use cases testers will approach the system to be tested as a “black box”. “What, exactly,
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
10/16/2015Bahill1 Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
P1516.4: VV&A Overlay to the FEDEP 20 September 2007 Briefing for the VV&A Summit Simone Youngblood Simone Youngblood M&S CO VV&A Proponency Leader
Develop Project Charter
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
Model-Based Systems Engineering on a Quick Reaction Program 20 May 2015 Charles H. Patton Engineering Manager and Systems Engineer Copyright  2015 Northrop.
International Workshop Jan 21– 24, 2012 Jacksonville, Fl USA Model-based Systems Engineering (MBSE) Initiative Slides by Henson Graves Presented by Matthew.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Winter 2007SEG2101 Chapter 31 Chapter 3 Requirements Specifications.
Software Requirements Specification Document (SRS)
Digital Design Using VHDL and PLDs ECOM 4311 Digital System Design Chapter 1.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Software Engineering Lecture 10: System Engineering.
Copyright © 2007, Oracle. All rights reserved. Managing Items and Item Catalogs.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
1 © 2014 Atego. All Rights Reserved. Infrastructure Bridge Model Matthew Hause – Atego Chief Consulting Engineer
 System Requirement Specification and System Planning.
SQA project process standards IEEE software engineering standards
An Overview of Requirements Engineering Tools and Methodologies*
2012 Spring Simulation Interoperability Workshop
SQA project process standards IEEE software engineering standards
IEEE Std 1074: Standard for Software Lifecycle
Software Requirements
IS442 Information Systems Engineering
The Open Group Architecture Framework (TOGAF)
Engineering Processes
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
PSS verification and validation
Chapter 4: Project Integration Management
Presentation transcript:

Ron Kratzke, Vitech Corporation MBSE for System Testing Managing the development of system testing using the principles of Model Based System Engineering

Context Diagram - Verification Process (Ref: INCOSE Handbook Ver Oct 2011) Vitech Corporation2 Controls - Applicable Laws and Regulations - Industry Standards - Agreements - Project Procedures and Standards -Project Directives Outputs - Verification Strategy - Verification Enabling System Requirements - Verification Constraints on Design - Verification Procedures -Final RVTM - Verified System - Verification Report Enablers - Organization / Enterprise Policies, Practices, and Procedures - Organization / Enterprise Infrastructure - Project Infrastructure - Verification Enabling Systems Activities - Plan Verification - Perform Verification Inputs - System Requirements - Verification Criteria - Specification Tree - Updated RVTM - Interface Requirements - Integrated System - Interface Control Documents - Integration Report

Model-Based Systems Engineering Model-based systems engineering (MBSE) is the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases. – From “INCOSE Systems Engineering Vision” 2020 INCOSE-TP September, 2007 Vitech Corporation3

MODELS Vitech Corporation4

Everyone has a model … VITECH CORPORATION5

System Testing has to account for a number of items… Vitech Corporation6 Requirements Functions (Behavior Architecture) Components (Physical Architecture) Testing

MBSE Verification Process Model Must … Provides insight into the problem and potential solutions Provide order and traceability Possess integrity and consistency Have ability demonstrate and explain the test program Vitech Corporation7

Is The VCRM Enough??? Vitech Corporation8

Additional Information Needed In addition to the method, shouldn’t we also know? – Objective – Environment – Special Conditions – Success Criteria Vitech Corporation9 Ref: A Day in the Life of a Verification Requirement Tutorial, Northrop Grumman, Steve Scukanec, 27 th Annual T&E Conference, March 14, 2011

Status of Completing the Verification Wouldn’t we also want to track? – Method (which is in the VCRM) – Planning Status – Completion Status – Where / When the Verification Event will take place Vitech Corporation10

Verification Requirement Statement Vitech Corporation11 Verification Requirement Description statement provides the details on HOW the verification will be accomplished

Relating Requirements to Verification Vitech Corporation12 Function, Requirement verified by (verifies) Verification Requirement Verification Requirement attributes: - Description - Method - Status - Level Add two more attributes

Table Output from Model … Vitech Corporation13 Provides the data from the model to provide overall status of verification planning… But what about the test events?

What about the actual Testing? Vitech Corporation14 Function, Requirement verified by (verifies) Verification Requirement What test events are planned? Which Verification Requirements will be verified in which test event? Who is doing the testing? What Organization is responsible? What configuration is going to be used in testing? Which Test Procedures will be used during any particular Test Event?

What about the actual Testing? Vitech Corporation15 Function, Requirement verified by (verifies) Verification Requirement Verification Event fulfilled by (fulfills) Add “Verification Event” to specify and describe a Test Event which will be used to verify a subset of Verification Requirements (for example, Limited User Test, Laboratory Bench Test, Operational Test, etc.)

What about the actual Testing? Vitech Corporation16 Function, Requirement verified by (verifies) Verification Requirement Verification Event Organization Test Procedure assigned to (responsible for) employs (employed by) Test Configuration employs (employed by) fulfilled by (fulfills) Relate the Verification Event to an Organization, Test Configuration, and Test Procedure

Provide a complete picture… Vitech Corporation17

Verification Event Information Vitech Corporation18

What about time and resources for the Verification Requirement? Vitech Corporation19 Function, Requirement verified by (verifies) Verification Requirement Verification Event Organization Test Procedure assigned to (responsible for) employs (employed by) Test Configuration employs (employed by) fulfilled by (fulfills) Test Activity executed by (executes)

Test Activity – Detailed Test Planning Vitech Corporation20

Produce a Test Plan from the Model Vitech Corporation21

Summary … System Testing model – Extends traditional VCRM to provide added insight – Plan Verification Events including support resources – Manage Testing Activity sequence and timing – Produce Test Plans Traceability Completeness Consistency Document Generation Vitech Corporation22

Ron Kratzke, Vitech Corporation MBSE for System Testing Questions ???