HCMDSS Panel Software and Systems Engineering

Presentation Transcript

HCMDSS Panel Software and Systems Engineering John Anton Kestrel Institute November 16-17, 2004

State of business craftsmanship How it goes today (generally): prerequisites - > spec (possibly UML) - > (incompletely computerized) code creation - > testing (unit, coordination, demonstrate checking) [spiral] Use 'best practices' (e.g., CMM-N) UML-based instruments Labview , MathWorks (Matlab, Stateflow, Simulink), Modelica Documentation bolster (e.g., through UML devices, 3GL IDEs, and so on.) Quality affirmation In-house QA, COTS devices, outsourced administrations Problems air holes referential honesty device semantics, apparatus reconciliation code perceivability/openness (e.g., Labview, MathWorks) code convenientce (e.g., MathWorks) property appraisal on code MC/DC testing difficulty high certification can be inconsistent with code clarity non-consistency of item plan arrangements and their application

Best practice SEI (CMM-N) Praxis (best practice on steroids) Others Model checking CMU (solid authority) NASA (with work from U Kansas) U Cincinnati (BDDs) Rockwell-Collins (with work from UT/Austin) Others Code QA providers device merchants benefit suppliers "N-GL" situations Programmatica (OGI/Galois) Eclipse (IBM, open space) Specware (Kestrel Institute, Kestrel Technology) "Safe" code Simple (MISRA) C (JPL with Kernighan & Ritchie bolster) Safety basic Java (The Open Group push with Bush, Bollella, Locke bolster) Correct-by-development advancements Kestrel, NASA, Z, B, … Automated cert ification bolster AutoSmart (JavaCard, FIPS 140-2, Kestrel) Reusable ( cert ified) modules Middleware (VU, Wash U, … ) Others Aspect weaving Code level (AspectJ,UBC, IBM) Spec level (HandlErr, and so on., Kestrel) Others … Some ebb and flow investigate for high confirmation code

Problems to address for HCMDSS Language Inconsistency, absence of exactness Multiple controls for administrative evaluators to fight with Software range, area subtle elements Blank screen For designers, analyzers, evaluators Application code reuse has not met starting guarantee Optimization, stages, change affect, befuddled models, properties of piece

Considerations Formal Jargon Libraries of details

Toward effective (re) cert ification - Formal Jargon What is it? In every space, a depiction in rationale of essential terms, definitions, adages, attractive properties, usefulness, conduct, imperatives Organized in a semantically rich scientific categorization (efficient advancement) Developed, distributed and kept up as a standard Why think of it as? Correspondence (engineers, plug & play, FDA, … ) Improve financial matters in the cert ification prepare Basis for (conceptual) detail libraries How to arrive? Consider improvement of another "product offering" of measures (NIST, The Open Group, OMG) Domain members team up with administrative bodies (FAA, FDA,… ) Start with a solitary area to serve as style-guide for others

Toward proficient (re) cert ification - Specification and confirmation libraries Use formal (institutionalized) dialect (Formal Jargon) Libraries of determinations Standardized, space particular dialect Proven properties Support 'plug & play' Address usefulness & behavior interfaces (static and element viewpoints) "strategies" (e.g., blunder taking care of) Include reference usage and consistence tests Proof libraries Mechanisms for field-time cert ification upkeep Run-time observing chronicle audit Pharmaceutical experience - yet don't sit tight for terrible news FAA structure for plane upkeep

Summary Promising bearings Formality Abstraction Challenges Composition "Strategy" (outline level orders) Runtime vulnerabilities COTS segments and cert ification Tech exchange

Bio John Anton is the organizer of Reasoning Systems, and Kestrel Technology LLC, where he is currently President/CEO. He is likewise President/CEO/Co-originator of the non-benefit Lexia Institute, whose mission is to create and convey innovation to help dyslexic individuals and their instructors. Moreover, he is a Manager at the Kestrel Institute. Anton has ability in the zones of control hypothesis, flag handling, programming advancements, and their application. As VP for Advanced R&D at Systems Control, Inc., he drove a group that fabricated the Reconfigurable Inflight Control System (RIFCS) for McDonnell Aircraft – manufactured utilizing innovation from CTRL C (the ancestor to today's Matlab), which was additionally worked under his administration. Anton was an Adjunct Professor at Santa Clara University where, for a long time, he showed courses in direct frameworks hypothesis, ideal and stochastic control, and choice hypothesis. He got a Ph.D. in Applied Mathematics from Brown, a B.S. from Notre Dame, and was a Fulbright Fellow at the Technische Hochschule, Germany.