Skip to content

ImportExport

Jump to bottom
LAPTOP-N364A3DK\helmu edited this page Jan 31, 2019 · 14 revisions

Import and Export

The hoReverse ReqIF feature supports:

For standards like

  • SPICE
  • Functional Safety (e.g. ISO 26 62 2)

you need to establish bi-diretional traceability with e.g. external Requirements and Tests.

ReqIF defines:

  • ReqIF exchange format
  • Workflow/Roundtrip how to do the exchange of requirements
    • From viewpoint EA
      • Import initial ReqIF requirements
      • Change EA Tagged Values (ReqIF attributes/columns)
      • Export updated ReqIF requirements
      • Import the ReqIF requirements in the other requirement or test tool

Import/Export Formats

Example

Features

  • Structured list
  • Import Specification
    • Import type
    • EA Elementtype + ≪Stereotype>>
    • Packages to import
    • EA State of new created elements
    • Advanced
      • Package deleted elements
      • Identifier instead of name (configurable)

Import Specification

You can define your imports by means of an Import Specifications. With Import Specifications you can define:

  • What module to export to which EA Package
  • Group imports to import everything with one click
  • Parameter for Import like:
    • Column which is the identifier of a requirement/test
    • Assign import columns/attributes to EA Model - Elements
      • Name
      • Alias
      • Notes
      • Linked Documents (only ReqIF)
  • State of new requirements
  • Attributes to write back

Specification

// Importer settings to import ReqIf, DoorsCsv, DoorsReqIF, xmlStruct into EA packages:
// - Specify import rules to import a type of file into one or more EA Packages.
// - see class: 'FileImportSettingsItem'
//
// Rules: 
// - A File path may be written with either '\', or '/'
//
// Settings:
// - Name:            The name in the EA menu to use this particular specification  
// - Description:     Further description visualied as tooltip in the menu description
// - ListNo:          hoReverse imports all specifications with the same ListNo with one click in the EA Menu 
// - InputFile:       The Path of the file to import, you have to use the extensions (*.csv, *.reqif,, *.reqifz, *.xml) depending on the particular 'ImportType'
// - PackageGuidList: The list of Guids for the packages to import into. The compressed *.reqifz format allows/demands one GUID for each imported 'Module'. The other file types only support one GUID/package.
// - ObjectType:      The valid EA ObjectType to create for each imported row (e.g. 'Requirement').
// - Stereotype:      The EA Stereotype to use for each imported row (e.g. 'Functional Requirement')
// - ImportType:      'DoorsCsv'   = Doors *.csv import format for requirements (tested with Doors 9.6)
//                    'DoorsReqIf' = DOORS reqif format (*.reqif, *.reqifz)
//                    'ReqIf'      = ReqIf format (*.reqif, *.reqifz)
//                    'XmlStruct'  = Structured xml for requirements, tests or so
// - StatusNew:       The EA status property to set for new EA element
// - StatusChanged:   The EA status property to set for changed EA elements (only supported for ImportType 'DoorsCsv')
// - RtfNameList      ["Object Text",],
// - AttrNameList     ["RequirementID", "Object Heading", "Object Text"],
// - AttrNotes        The attribute name to import into the EA property 'Note', e.g. "Object Text"
// - RtfNameList      List of attribute names to import into the EA property 'Linked Document', e.g.  ["Object Text",]
// - AliasList        List of attribute names to import into the EA property 'Alias', e.g. ["RequirementID"] or ["ReqIF.ForeignID"]
// - AttrNameList     List of attribute names to import into the EA property 'Name', e.g.  ["RequirementID", "Object Heading", "Object Text"]
// - EmbeddedFileStorageDictionary
//                    Dictionary of embedded files to store. If blank or empty then don't store embedded files. 
//                    Embedded files are stored in the EA Element as EA Files. 
//                    DOORS: Doors stores embedded files as *.ole. Currently *.pdf and *.wmf are decoded.
// - IdList"          Only "XmlStruct":
//                    List of attribute names to use for ImportType "XmlStruct" as unique ID, e.g.  ["ForeignID"]  
  "Importer":
  [

References

Glossary

  • GUID Universally unique identifier used by EA to uniquely identify an object
  • MCDF Microsoft Compound Document Format (used by DOORS embedded files)
  • ReqIF Information of a file or folder with *.reqif or *.reqifz
  • ReqIF Roundtrip, often called ReqIF Workflow. The Standard how to exchange ReqIF requirements between two partners
  • ReqIF Standard of the OMG to exchange requirements between different tools, see OMG Specification
  • ReqIF Workflow: ReqIF workflow specifies how to exchange requirements between tools. Often called Roundtrip
  • SPICEProcess Reference Model to assess process maturity.
  • Traceability

www.hoModeler.de hoTools, hoReverse, ScriptDotNet, ReqIF

Clone this wiki locally