CPSC 371 John D. McGregor Session 28 …... Specification and design problem solution specification implementation specification.

Slides:



Advertisements
Similar presentations
Interfacing Lab Part Guide. The Solderless Breadboard Rows along the top and bottom are connected horizontally along the length of the board Holes in.
Advertisements

Conformance Testing of MOST based Applications Towards Effective System Testing André Baresel, Michael Schmidt - DaimlerChrysler AG Contact:
Real Time Consulting LLC Continuously Engineering Real Solutions Complete Outsource Solution Provider.
Ch. 5 Lecture Notes IN4MTX 113 January 2010 Requirements Quality Assurance.
Software Testing and Quality Assurance
The Waterfall Model A Case Study
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
Introduction to Software Engineering Dr. Basem Alkazemi
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
Lab 01:Binary numbers, UP-1 switches, and UP-1 LED’s :
CPSC 872 John D. McGregor Session 12 Software Design, cont’d.
Systems Thinking and Systems Engineering Verification & Validation 14 March 2013 Francois Christophe Galina Medyna Eric Coatanéa.
1 “ Understanding leads to perfection” Author: Herb Isenberg Ph.D A Bird’s Eye View Quality Foundations January 2011.
SpW-10X Router ASIC Testing and Performance Steve Parkes, Chris McClements, Space Technology Centre, University of Dundee Gerald Kempf, Christian Gleiss,
Safety-Critical Systems 6 Certification
CPSC 873 John D. McGregor Session 4 Requirements V & V - continued.
Scientific Computing By: Fatima Hallak To: Dr. Guy Tel-Zur.
SWE © Solomon Seifu CONSTRUCTION. SWE © Solomon Seifu Lesson 13-2 Testing.
IT Requirements Management Balancing Needs and Expectations.
Requirements Engineering ments_analysis.
SoC Verification HW #2 TA: Wei-Ting Tu Assignment: 04/12/06
John D. McGregor Session 2 Preparing for Requirements V & V
CPSC 372 John D. McGregor Module 2 Session 1 More on requirements and the Investment Decision.
Lecture 7: Requirements Engineering
BE-SECBS FISA 2003 November 13th 2003 page 1 DSR/SAMS/BASP IRSN BE SECBS – IRSN assessment Context application of IRSN methodology to the reference case.
Model Checking and Model-Based Design Bruce H. Krogh Carnegie Mellon University.
CPSC 371 John D. McGregor Session 32 This is it..
EURAILSPEED - Milano – November 8th, 2005 MGV SNCF Train Set for on-board Measurement at Great Velocity Eric REBEYROTTE– Technical Manager of SNCF Engineering.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
EML 2023 – Motor Control Lecture 1 – Closed Loop Motor Control.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Mid-Semester Presentation Senior Design October 5, 2010
SYSE 802 John D. McGregor Module 1 Session 2 Requirements Modeling in SysML.
Modeling Issues for Validation, Verification, and Certification (VV&C) Paul Miner NASA Langley Research Center 22 September 2015.
Version 02U-1 Computer Security: Art and Science1 Correctness by Construction: Developing a Commercial Secure System by Anthony Hall Roderick Chapman.
Requirements Engineering ments_analysis.
CPSC 871 John D. McGregor Module 6 Session 2 Validation and Verification.
CPSC 873 John D. McGregor Session 6 Preparing for Architecture V & V.
Anti-lock Brake System Group 2 Presenters: Christan Balnius, Zain Kazim, Mark Pulver Demo Given by: Brian Lawnichak.
CPSC 871 John D. McGregor Module 8 Session 3 Assignment.
Capturing Requirements. Questions to Ask about Requirements 1)Are the requirements correct? 2)Consistent? 3)Unambiguous? 4)Complete? 5)Feasible? 6)Relevant?
CPSC 371 John D. McGregor Session 27 State. Specification and design problem solution specification implementation specification.
Software Engineering Lecture 10: System Engineering.
CPSC 371 John D. McGregor Session 10 Requirements analysis methods.
Documenting an Architecture 10 pages, half pictures.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
WORKSHOP CLOSURE. Learning Outcomes Designing for Pedestrian Safety – Workshop Closure 12-2 You should now be able to:  Describe the influence of planning.
CPSC 872 John D. McGregor Session 18 Evaluating Specification.
© 2009 Artisan Software Tools. All rights reserved. Testing Solutions with UML/SysML Andrew Stuart, Matthew Hause.
CPSC 872 John D. McGregor Session 31 This is it..
1 © 2014 Atego. All Rights Reserved. Infrastructure Bridge Model Matthew Hause – Atego Chief Consulting Engineer
Critical Systems Testing Experts EXB Solutions - Contact us at cFS Workshop – Automated Test for NASA cFS David C. McComas 1, Susanne.
Network Simulators.
A tutorial guide to start with ISE
3 | Analyzing Server, Network, and Client Health
Requirements Verification and Validation
John D. McGregor Session 8 Evaluating Architectures written in AADL
John D. McGregor Session 4 Requirements V & V - continued
Performance Specifications
Documenting an Architecture
QGen and TQL-1 Qualification
QGen and TQL Qualification
Position and Warning.
John D. McGregor Session 6 Preparing for Architecture V & V
John D. McGregor Session 5 Error Modeling
Where Intelligence Lives & Intelligence Management
A simple network connecting two machines
PLC Front Panel.
Presentation transcript:

CPSC 371 John D. McGregor Session 28 …..

Specification and design problem solution specification implementation specification

Driver in or out of the system What does having humans in the system as opposed to outside the system change about requirements solicitation?

CAS content/uploads/2013/01/Dahm-AIAA AIAA-Aerospace-Sciences-Keynote.pdf

SEBok oKv1.3_full.pdf

/StateStrategy.pdf aviour_Annex1.6.pdf

metrics Descriptive metrics – # of requirements – # of actors – … Prescriptive metrics – Next slide

Qualities of requirements model Correctness Completeness Consistency Verifiable Validatable How do we evaluate each of these?

Completeness - Traceability Matrix Manual/automatic maintenance

Shape Physical Geometry What is SAVI Consistency? AFE 59S1 – 6 types of consistency – Interface – Compositional – Constraint – Behavioral – Version – Verification 16 October 2013 Executive Board Meeting – Aerospace Valley 11 PNP or NPN Junction Altimeter Avionics Model Speed Indicator Landing Gear Model Weight on Wheels Switch Ground Proximity Warning System Radio Altimeter On Ground In Flight Engine Indication and Crew Alerting System Air/Ground Signal

What is SAVI Consistency? AFE 59S1 – 6 types of consistency – Interface – Compositional – Constraint – Behavioral – Version – Verification AFE 61 – 8 types of consistency – Data Value Type Semantics Metadata – Model Property Semantics Metadata Behavior 16 October 2013 Executive Board Meeting – Aerospace Valley 12 Runtime Consistency: Data Safety, Latencies, Buffer Overflow, Resource Sharing, Data Ordering, etc. Mathworks 64-bit Unix pi = pi = Mathworks 32-bit Windows Signal connectivity analysis doesn’t need wiring length but signal latency and jitter analysis does.

SAVI Consistency Checks 16 October 2013 Executive Board Meeting – Aerospace Valley 13 Solid models Hyd power supply BSCU Accumulator AADL-SysML models

s/WorkUnits/Tasks/QualityEngineering/Qualit yControl/RequirementsEvaluation.html~Conte nts

src=s&source=web&cd=1&ved=0CCAQFjAA&u rl=http%3A%2F%2Fasterweb.jpl.nasa.gov%2F paa%2FProtectedAreaArchiveOverview-- Compressed.ppt&ei=kNZzVI_hDYGnNtCAgtAO &usg=AFQjCNHScLKCpl8J2WBB8By1Nm84syT 9OA&bvm=bv ,d.eXY

“Test” the requirements Select scenarios to sample over stakeholder roles Have stakeholders write scenarios to validate the requirements Verify the requirements by using the scenarios on the design

What does it mean to … Infect Propagate

Coverage?

Car OBD Phone Cloud