Minutes of P2654 Working Group Meeting No.120, 2021-08-16

 Meeting called to order:  11:06AM EDT

The slide references relate to the pack used during this meeting, located here: 
http://files.sjtag.org/P2654WG/P2654_Meeting_120.pdf

The cumulative reference pack is located here: http://files.sjtag.org/P2654WG/P2654_Reference_Pack.pptx (updated Dec 31, 2020)

iMeetCentral site: https://ieee-sa.imeetcentral.com/sjtag-sg/ 

1. Roll Call

Ian McIntosh (Leonardo) (chair)
Terry Duepner (National Instruments)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Joel Irby (AMD)
Louis Ungar (A.T.E. Solutions)
Carl Walker (Cisco)
Brad Van Treuren (VT Enterprises Consulting Services)

Guests:
---

Excused:

Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Bill Huynh (Marvell Inc.)
Tom Thompson (for IEEE)

2. Agenda

  • Brad moved to accept the agenda, seconded by Terry, no objections.

3. IEEE Patent Slides

  • {Slides 5-10}
  • Patent and Copyright slides reviewed without comment.

4. Review and Approve Previous Minutes

  • {Slide 11}
  • Meeting #119, August 09 (draft circulated August 12)
    • Add Peter and Joel as notified absences.
    • Terry moved to approve as amended, Brad seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • None.

7. Discussion Topics

7 a) P2654 C4 Model perspectives

  • {Slide 14}
  • Brad described and demonstrated the methods for editing and extending C4 Model diagrams, and detailed where the PUML (Plant UML) files could be found on his GitHub site.
  • "Person" is really a role and essentially equivalent to UML's "Actor".
  • Discussions largely centred around "ATPG" and manual TPG and what terminology might be most appropriate for each category. This was not fully resolved.
  • The scope of "Automated/Automatic" in ATPG may be subject to interpretation.  Usual inference is that the test generation is automated, but could be read as implying that the tests are applied automatically.
  • Noted that "Cluster Tests" could not reasonably be taken to be only automatically generated or only manually generated: While some tests could be automatically generated based on CAD/device model data, other cluster tests may require design knowledge or intent that requires human input.
  • We're looking at board-level currently, system-level in on another diagram.
  • «System» doesn't equate to our view of what a system is and the term, like some others, is a carry-over from using Plant UML as the diagramming basis.
  • Reminder that the value of the C4 Models is the ability to tunnel down through the diagrams to increasingly finer detail.

8. Any Other Business

  • {Slide 15}
  • None.

9. Glossary: 

  • None
  • Carried over:
    • Better define structural test boundary vs functional test
    • Transfer module/library
    • Injection transfer module/library
    • RVF Message (to be refined)
    • RVF Command (to be refined)
    • "Tooling" - need to be clear on what is meant.
    • "True System".
    • Comment that "End-User" is subject to perspective and so needs to be qualified.
    • ModelPoint.
    • System Element.
    • System Resource.
    • 'System' needs the concept of a controller capability added.
    • "Filtering" may need to be defined.
    • "Translation" may need to be defined.
    • "Interface" is missing.
      • No obvious IEEE accepted definition.
      • 1687 has definitions for specialised forms: Device Interface and Instrument Interface.
      • We may need specialised forms for Software Interface and Hardware Interface.
      • "Interface" is overloaded and requires disambiguation.
    • 1687.1: Transformation.
    • IEEE 1856: Sense - "Sensor" done, Acquire, Analyze not really defined.
    • Device - do we mean a packaged device? May be many devices in a package. "Device" is often used as a modifier, e.g. "device package", "device identification".
    • Use Case Context, Application Context
    • Legacy Infrastructure, SJTAG Infrastructure (placeholders for now, really for working group to define).
    • "Generators": May need to be qualified as "Test Generators" (used by the integrator/tester) and "Model Generators" (used by IP providers, interface designers, etc.).
    • AccessLink and DataLink descriptions will need to be revised.
    • See P1687.1's definitions on Slide 31 of the pack presented by Jeff Rearick on Jan 14, 2019.
    • "State", "Vector", "Sequence" and "Pattern" as proposed at April 8, 2019 meeting.
    • "Event", "Access Interface" as proposed at April 15, 2019 meeting.
    • 'Port' needs to be developed.

10. Takeaways:

  • None. 

11. Schedule next meeting

  • August 30, 2021
    • No meeting on August 23 as Ian will be out.

12. Topic for next meeting

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

  • Brad moved to adjourn, seconded by Brian.
  • Meeting adjourned at 12:00 Noon EDT

Respectfully submitted,
Ian McIntosh