P1247176258rkNRM - PowerPoint PPT Presentation

1 / 22
About This Presentation
Title:

P1247176258rkNRM

Description:

Integrated Test Systems and Tools for test of highly complex ... Program Distribution (CVS, Bit torrent, git, Logiweb) Auto Code (Matlab/Simulink, SCADE) ... – PowerPoint PPT presentation

Number of Views:58
Avg rating:3.0/5.0
Slides: 23
Provided by: tennah
Category:

less

Transcript and Presenter's Notes

Title: P1247176258rkNRM


1
Rovsing Company Overview
2
Rovsing Company Overview
  • Danish company founded in 1992
  • Established a subsidiary in Ireland in 2006
  • Currently establishing a subsidiary in the USA
  • Primary business areas
  • Integrated Test Systems and Tools for test of
    highly complex Hardware Systems
  • Development of critical and non-critical Software
    Systems
  • Independent Software Verification and Validation
    (ISVV)
  • Networks and Command Control Solutions
  • Engineering Logistics Support
  • Rovsing today employs around 70 engineers
  • Many of Rovsings engineers are specialised in
    software testing

3
Rovsing Key Customers
  • Key Customers
  • European Space Agency
  • EADS Space Transportation
  • EADS Astrium
  • Alcatel Space
  • Alenia Spazio
  • Thales-Alenia Space
  • Galileo Industries (ESNIS)
  • EADS CASA Espacio
  • SNECMA
  • THALES
  • Hughes Information Sys.
  • DLR
  • EUMETSAT
  • ESRIN
  • ESO
  • CNES
  • Centre Spatial Guyanais

4
Why Independent Verification
  • Because it saves money
  • Because it saves calendar time
  • Because it has a Return Of Interest (ROM) between
    1.2 and 10

5
Why Early Verification
  • Defects cheaper to correct the earlier they are
    found
  • Cost tends to triple per phase defects remain
    undetected
  • Methods exist ISVV methods are applicable for
    early verification
  • ISVV methods are not constrained to independent
    verification

6
Examples of Rovsing ISVV The ATV
  • Automated Transfer Vehicle (ATV)
  • Rovsing has performed ISVV on the critical parts
    of the on-board software for the European
    Automated Transfer Vehicle (ATV)
  • Monitoring and Saving Unit
  • Flight Application Software
  • More than 500 findings, and
  • Roughly 50 have resulted in corrective actions
  • Findings are most numerous in the beginning of
    the project (see chart)

7
Examples of Rovsing ISVV Gaia
  • Gaia on-board software
  • Rovsing is performing ISVV on the critical parts
    of the on-board software the Gaia spacecraft
    (80.000 lines of code)
  • Accepted / Reported findings so far

8
CSTS Flight Software Verification Bread Boarding
9
Why Verification Bread Boarding
  • The approach to verification must be compatible
    with the chosen software lifecycle
  • To do early verification, the approach to
    verification must be in place from the start of
    the development
  • The developers must be aware of the chosen
    approach to verification from the start of the
    development

10
Phase 1 Activities
  • Looking into the crystal bowl
  • Development life cycle review
  • Method review and tailoring
  • Initial development

11
Looking into the crystal bowl
  • ISVV (Independent Verification)
  • Program Distribution (CVS, Bit torrent, git,
    Logiweb)
  • Auto Code (Matlab/Simulink, SCADE)
  • Literate programming (CWEB, Logiweb, pod, doc,
    javadoc, Doxygen, XML, AXIOM)
  • Real time garbage collection
  • Formal verification

12
Sample Literate Program
Combinations
13
ECSS-E40B Divide and Conquer
14
Design method/notation
  • UML (Not very ECSS-E40B compatible)
  • HOOD (Heavy, OO-bound, Ada-centric)

15
Hood light
16
Proposed Phase 2 Activities (200k ROM)
  • Review of development life cycle with focus on
    verification
  • Case study comprising development and
    verification
  • Staff of three
  • Person A Development, verification, and
    validation
  • Person B Second person doing verification and
    validation
  • Person C ISVV

17
Development and early verification
18
Development and early verification
19
Proposed Phase 2 Output
  • Software Requirement Specification (SRS TS)
  • Software Design Document (SDD, DDF) including
    code
  • Software Verification and Validation Plan (SVVP)
    including test suites
  • ISVV Report (ISVVR)
  • Final report proposing life cycle and the
    associated approach to verification

20
Philosophies
  • KISS (Keep It Simple Stupid)
  • Use open source when feasible (GCC, LaTeX, etc)
  • Use open source standards (PDF, html, Internet,
    etc)
  • Push verification onto developers
  • Early verification
  • Independent verification

21
Reduced Phase 2 Activities (90k ROM)
  • Omit Person B (Second person doing Verification
    and Validation)
  • Omit Person C (ISVV)

22
QUESTIONS
Write a Comment
User Comments (0)
About PowerShow.com