anchor.diff: -= WASL Parser and Generator Prototyping
  -
  -xtUML Project Design Note
  += WASL BridgePoint Migration Sizing and Sequencing
  +
  +xtUML Project Analysis Note
   
   :sectnums:
  +:sectnumlevels: 5
   
   == Abstract
   
  -There are two primary links in a WASL/xtUML prototyping chain.  The first
  -involves parsing WASL on the input/conversion to xtUML.  The second generates
  -WASL from xtUML instance information.  This note documents the design of
  -these utilities.
  -
  -
  -== Document References
  -
  -. [[dr-1]] https://support.onefact.net/issues/10440[10440 - Prototypes]
  -. [[dr-2]] https://support.onefact.net/issues/10414[10414 - Analyze Options for Migration]
  -. [[dr-3]] link:../10414_wasl/ExtractionWithHeaders.xlsx[File Formats:  Extraction with Headers]
  -. [[dr-4]] link:../8073_masl_parser/8277_serial_masl_spec.md[Serial MASL (SMASL) Specification]
  -
  -
  -== Background
  +Migration of WASL models from iUML to BridgePoint involves a substantial
  +engineering effort involving several bits of tooling and testing.  Model
  +conversion, import, editing, and export are to be supported in the tools.
  +Testing, documentation and training are required to support the processes.
  +This note serves as a top-level sizing and planning document to the various
  +analysis and design notes documenting the migration engineering.
  +
  +== Introduction and Background
   
   <<dr-2,2.2>> provides analysis of migration options and recommends
   a path forward from iUML to BridgePoint while leveraging the existing
  
positive.code:   * Copy xtumlmc_build to tools/mc/bin/xtumlmc_build.pl.
    * Change it to strip CRLFs from serial MASL stream.
  
  == User Documentation
  
  == Unit Test
  
  . Run `masl_round_trip` on the build server and see it pass %100.
  
  ---
  
  
negative.code: represented as WASL flat ASCII files into xtUML and importing them into
  BridgePoint.  It also explored ways of exporting WASL-idiom xtUML models
  from BridgePoint to WASL to feed downstream to the model translation
  build chain.  This note presumes familiarity with the contents of that
  report.
  
  == Requirements
  
  === Identification of Tasks
  ==== Training
  ===== Configuration Management
  ===== Basic xtUML Modeling
  ===== Tool Training
  ==== Meta-Modeling
  ===== MASL/WASL Meta-Model
  ===== Enhanced Serial MASL
  ===== Marking
  ==== WASL Parser
  ===== Parse Domain Models
  ====== Type
  ====== Interface and Port
  ====== Domain
  ====== Class
  ====== Relationship
  ====== State Machine
  ====== Terminator
  ====== Activities
  ===== Parse Build Sets
  ====== Deployment
  ==== Updates to `m2x`
  ==== WASL Generation
  ===== Export Domain
  ====== Type
  ====== Interface
  ====== Port
  ====== Domain
  ====== Class
  ====== Relationship
  ====== State Machine
  ====== Terminator
  ====== Activities
  ====== WASL Folder Structure
  ===== Export Build Set
  ====== Deployment
  ==== Updates to `x2m`
  ===== Key Letters
  ==== Domain Editor Compatibility
  ===== WASL Activity Dialect
  ==== Deployment Editor
  ==== Initial Model Migration
  ===== Model Conversion Trial
  ====== Convert Relationships and Events Models
  ====== Semi-Automate Model Conversion
  ==== Testing and Validation
  ===== WASL Compare Utility
  ====== Compare Unedited Model
  ====== Compare Edited Export
  ====== Export Existing Model to WASL
  ==== ASL Editing
  ===== ASL Syntax-Highlighting Editor
  ===== Auto-Indent
  ==== Migrate the SWATS Models
  
  === Sequencing and Dependency Analysis
  === Sizing of Tasks
  === Project Planning
  
  === Convert WASL to Serial MASL (SMASL) (`WaslParser`)
  === Convert Serial MASL (SMASL) to WASL (`wasl`)
  
  == Analysis
  
  