2022-04-05 QA Architecture for 2022R1

Public Page

Date: Apr 4, 2022

Agenda

• Antitrust

• Committee Welcome

• Recap 2022R1 with Jira Review

• BMS QA

• Code List QA

• Test Instances QA

• Spell Check

• Run Build and Test Instances

• Approve 2022R1 Release

Meeting Minutes

• Antitrust Accepted

• Committee Welcome

  • Ramesh joined briefly but decided he would join next week when we discuss the API initiative.

  • The Next QA will be held in St. Louis/St. Charles around the CONNEX event. This will be an in person QA with a virtual element if people are not able to attend.

  • Fun piece of knowledge share, Andy got a 911 Emergency call late afternoon because I somehow blew up every Test Instance, both Invalid and Valid. Luckly we only had 2 changes in the Code List, so we started over and created a new Database and it was validated.

• Recap 2022R1 with Jira Review

  • To Do Jiras

    • R12022-118 to create a tool to create duplicates was determined to move to next release.

    • R12022-119 to create a tool to add schema tags and words to dictionary is moved to next release

      • Andy created a Tool to capture the Words and Tags but it does not add to the dictionaries automatically

  • In Progress Jiras

    • R12022-9 Create new Open API Architecture Guidelines continued and moved to next release

    • R12022-10 Create Domains for Open API moved to next release to be continued

    • R12022-126 Document Best Practices for API moved to next release to be continued

    • R12022-146 Create Assignment Add Implementation Guide with Test Cases

      • Some of this work will be moved in this release to have the test cases available for CIECA Simplified.

      • The work will be moved to the next release and continued because it is not complete

  • QA JIRAS

    • R12022-127 BMS Delete duplicate Phone number section

    • R12022-254 BMS Correct <RepairInvoiceDetails> hyperlink

    • R12022-256 BMS Correct <VehicleDesc> and <RentalVehicleDesc> Hyperlinks under RentalAssignment

    • R12022-124 Dictionary add State Litigation Venue Code Spelling and State Providence

      • The Jira captures a number of other Codes that were added. These are codes that have merged words or uppercase lettering that is flagged by MS spellcheck as an error.

      • The Jira captures a number of Codes that have misspellings that need to be fixed

    • R12022-125 Code List Addition for BSW for Blind Spot Warning; this was requested in the last release but in QA was thought to be a duplicate. The code was taking back to the Committee that proposed it, Emerging Technologies, and it was determined that it was different from BSM, Blind Spot Monitoring and needed to be its own code. It was approved by Architecture for this release.

    • R12022-117 Test Instance to add invalid test to verify that UserDefinedArea more than 1 would error as expected. This came up in the last QA because the BMS and Schema were out of sync. The BMS was updated in the last release to make it optional instead of optional repeating to match the schema. This suggestion was to verify that repeating UserDefinedAreas would error.

• BMS QA

  • The Title Page was updated with the new Release Version and Date

  • Phone Number was marked to remove the second phone number duplicate, the Committee Reviewed the Schema and decided the fist phone number needed to be deleted.

    • There was a change to the number of area code being 5 instead of 3 in the written description.

  • The Hyperlinks were reviewed for the above JIRAS and confirmed

    • The hyperlinks were discovered while doing analysis for Projects or while moving the Implementation guides. All of the hyperlinks have not been reviewed to make sure they are referencing the correct hyperlinks.

  • Reviewed the Change Log

  • Approved

• Code List QA

  • Approved the additions of BSW to Options and 6.5.0 for BMS Version

  • Approved

• Test Instances

  • Verified that BSW and 6.5.0 was in Test Instances to be confirmed

  • Verified the New Test Instances for Assignment

    • The OPEN Enum causes confusion. The Open Enum allows companies to add to the list as they seem needed without having to get the code approved in a CIECA Release. It is still a good idea to bring these items to CIECA, however, due to companies having a faster release schedule, this will help them add necessary codes. An OPEN Enum does not mean that you can send anything and the schema will not break. The Code has to be in the Code List to be correct.

  • Approved

• Spell Check

  • BMS Spell Check was good

  • Code List Spell Check; not so good

    • The 2021R2 QA we recognized that the Master Code List was not being spell checked and we went through each of the tabs and did a spell check. We found that numerous misspellings were in the document

    • Andy found a way that we could spell check all the tabs instead of executing them 1 by 1. https://www.ablebits.com/office-addins-blog/2018/08/15/spell-check-excel/#:~:text=How%20to%20spell%20check%20the,Yep%2C%20it%27s%20that%20easy

      • You can go to any tab and do a Select All and then press F7

    • The Index page does not have a link to the Change Log, and some users may not be familiar with Excel to know about the ctrl + arrow keys taking you to the First Worksheet or the Last Worksheet. We would like to add a link to Change log, but the discussion was should it be added alphabetical, bottom or both. We also wanted to verify that the MACRO would not add this to the database. Later it was found that the First Worksheet and Last 3 Worksheets are ignored by the MARCRO. We created a https://cieca.atlassian.net/browse/R22022-112

    • There was a message that ShippingFulfilment was changed to Shippingfulfilment to be in sync with the Tab. However, this caused a spell check error. The note was removed from the description and was added to the Change Log and instead of the misspelling it was stated that shippingfulfilment with a Capital F was corrected to be in sync.

    • The Words Dictionary for the BMS and Excel was added to for words that were combination words and capitalization. However, the Architecture committee feels that we need to verify some of these items with the Committees that created them.

      • https://cieca.atlassian.net/browse/R22022-113

    • In Transmission Code, Code List Enum was spelled Emum so it was corrected as well as some other spellings that the committee knew was 100% valid.

    • All spell check accepted

• Run Build and Test Instances

  • The 911 Emergency happened again, all of the test instances errored, both Valid and Invalid

  • Make a long story short. The misspelling of Emum made the macro default to a closed Enum in the database. At some point the schema Common Global types was changed to be Closed Enum, however, the Code list is an Open Enum. When the spell check updated Emum to Enum, the Macro created it as an Open Enum as expected. This caused everything to error.

    • The BMSCommonGlogalTypes.xsd had to be changed to make TransmissionCode a type of TransmissionCodeOpenEnumType.

    • The spelling of Emum was corrected to Enum

    • The build was executed and test instances validated

• Motion was made by Dan Webster to approve 2022R1 Release and motion was approved by the committee

• The Release was completed and merged to master by the committee.

Thank you everyone and Great Teamwork!

Action items

Decisions

1. 2022R1 Release is Approved for April 20, 2022 Release

Participants

• Paulette Reed

• Dan Webster

• Mike Hastings

• Andy Bober

• Paul Barry

Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee.