Minutes of P2654 Working Group Meeting No.129, 2021-11-01

 Meeting called to order:  11:10 AM EDT

The slide references relate to the pack used during this meeting, located here: 
http://files.sjtag.org/P2654WG/P2654_Meeting_129.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)
Eric Cormack (DFT Solutions) (joined 11:30)
Terry Duepner (National Instruments)
Brian Erickson (JTAG Technologies)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Louis Ungar (A.T.E. Solutions)

Guests:
Tom Thompson (for IEEE)

Excused:
Bill Huynh (Marvell Inc.)
Heiko Ehrenberg (GOEPEL Electronics)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco)

2. Agenda

  • Brian moved to accept the agenda, seconded by Joel, 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 #128, October 25 (draft circulated October 25)
    • No correction noted.
    • Jon moved to approve, seconded by Terry, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • 1149.7 has started re-circulation ballot.

7. Discussion Topics

7 a) Continue Review of Standard Draft

  • {Slide 14}
  • Continuing review of clause 4.3 and representation of a system.
  • Ian has posed three questions regarding this:
    • Does this, or some it, belong much earlier, e.g. in the Introduction?
    • Should we have some text to the effect that nothing in the standard is intended to imply any limitation on what is considered a system?
    • We’ve considered properties of a system – should we instead think about properties of the constituent parts of a “system”?
  • We currently define a system in the glossary on our wiki - http://wiki.sjtag.org/index.php?title=Glossary:System.  Arguably, this may be too abstract for many readers. It describes properties of the system but with regard to the third question above, is perhaps more relevant to talk about the properties of the components that would allow P2654 to be applied to those parts?
  • Remainder of the discussion centered around the Introduction to the Standard.  This does not form part of the standard itself but may be the first thing people read.  How would the standards show up in a Google search?  Would the way it is shown draw the target audience in? Similarly, how might it appear in IEEE Xplore?  1149.7 looked up in Xplore for reference: Presents a (truncated) Abstract, Scope and Purpose. Scope and Purpose obviously come from the PAR (and standard) but where does Abstract come from? For 1149.7 it is similar, but not identical to the Introduction. {Post Meeting Note: Abstract, along with Keywords is part of the standard template - these are on the second page, but have not yet been filled out in our draft, so are easily missed} 
  • We want to make the "pitch" more accessible and since what is shown in Xplore gets truncated to the first 4 or 5 lines of each section, it would seem to be important for the Abstract to get the key messages over in the first couple of sentences.
  • What we currently have in the Introduction hints at what a system is and who the target audience is but could possibly be more direct.  Maybe need to say why you should use the standard and give some direction to other relevant standards.  Can't address them all but some will be more directly pertinent than others.  We do intend to have a clause on relationships to other standards. Possibly show a matrix? Might that then presume there are standards we would say we don't support?  
  • Show what P2654 is and what it isn't.  Why it's not e.g. 1687, what makes it different, what it let's me do that I can't already do.  How do you make it appear to the non-technical manager (e.g. prospect of using off-the-shelf- tooling rather than hand crafting your own in-house/ad hoc solutions)?
  • Working up an Abstract might be a useful exercise.
  • The draft was unedited and remains as IEEESTD-P2654_Draft_D01_BGVT_20211018.docm in the Drafts/Group Submissions folder.

8. Any Other Business

  • {Slide 15}
  • None.

9. Glossary: 

  • None.
  • Carried over:
    • Network will need to be defined
    • PTPG - Programmable Test Pattern Generator/Generation
    • 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:

  • Abstract/Introduction needs to be more accessible, have "management appeal". 

11. Schedule next meeting

  • November 8, 2021
    • NOTE: Daylight saving ends in US so meeting time returns to normal for Europe.

12. Topic for next meeting

  • Continue review of standard draft
    • IEEESTD-P2654_Draft_D01_BGVT_20211018.docm
    • Continue with clause 4.3 and representation of a system.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

  • Brian moved to adjourn, seconded by Terry.
  • Meeting adjourned at 12:01 PM EDT

Respectfully submitted,
Ian McIntosh