Minutes of Weekly Meeting, 2016-10-26

Meeting called to order: 11:11 AM EDT

1. Roll Call

Ian McIntosh
Brad Van Treuren
Brian Erickson
Heiko Ehrenberg
Bill Eklow (joined 11:38)

By Proxy:
---

Excused:
Carl Walker
Eric Cormack
Adam Ley

2. Review and approve previous minutes:

  • Approval of October 19 minutes (Updated draft circulated on 10/24/2016)
    • Ian noted that the joining time for Peter should be 11:13.
    • Approval deferred until Bill had joined the call.
    • Brad moved to approve as amended, seconded by Brian. No objections or abstentions.

3. Review old action items

  • All: do we feel SJTAG is requiring a new test language to obtain the information needed for diagnostics or is STAPL/SVF sufficient? See also Gunnar's presentation, in particular the new information he'd be looking for in a test language (http://files.sjtag.org/Ericsson-Nov2006/STAPL-Ideas.pdf)
  • Ian: Add the previously discussed lists to the 'master' template. Ongoing.
    • Some sections need further expansion that may take time to develop.
  • Ian: Make sure that Bill has the text before ITC (Nov. 15). Ongoing.
    • Ian hadn't been able to put this into a form like the PAR template, but felt that the Scope, Purpose and Need texts were the "meat" and what was of most interest. Brad noted that Al Crouch seemed to be able to amend the details after having raised the draft PAR up to a certain point. Ian recalled that you could do this in MyProjects until the PAR is sent to the Sponsor.  

4. Reminders

  • Consider Adam's three points (from the action from the first weekly meeting) and suggest what is preventing us from answering those questions:
    • Establish consensus on goals and constraints
    • What are we trying to achieve?
    • What restrictions are we faced with?
  • Forum thread for discussion: http://forums.sjtag.org/viewtopic.php?f=3&t=172
  • The Newsletter was due at the end of July 2015.

5. Discussion Topics

a. Enumerate our requirements
- What are we trying to implement?
- Review previous Key Takeaways for relevant ideas - continue from row 51

  • The intent was to continue with the breakdown of the Key Takeaways started last week.
  • {Brad shared the Key Takeaways and the Requirements worksheets}
  • After trying to explore the takeaways listed on row 51, it was realised that the minutes of that meeting had erroneously carried over these points from the previous meeting. There were, however, new takeaways identified in the post-meeting proxy comments that were not recorded as such in the "Key Takeaways" section.
  • One question that stood out in reviewing the minutes was whether bridges were considered to be an Accesslink. Brad felt that depended on circumstances and that they were really a special purpose instrument.  However, that probably generates a requirement. Brian suggested that rather than considering "bridges" we should think of a more general class of "hybrid", to encompass other devices such as BIST controllers, etc.
  • For row 53 (relevant minutes are http://www.sjtag.org/minutes/weekly-minutes-2015/378-meeting-minutes-2015-08-03) it was difficult to pin down what had been meant by 'Multiplicity can be described by additional "edges" on the existing diagram' since "edges" did not appear in the notes. This could have referred to "0 or more", "1 or more" notation on the "AccessLink Postcondition (without NOP states)" diagram, although Ian felt it might also refer to iteration of the data transfers between Precondition and Postcondition operations.
  • The group reached Row 54 of Ian's sheet before time ran out.
  • The updated version of Brad's Requirement Excel file is available here: http://files.sjtag.org/Brad/SJTAG%20Requirement%20List%2020161026.xlsx.

6. Topic for next meeting

  • Enumerate our requirements - continued
    • What are we trying to implement?
    • Review previous Key Takeaways for relevant ideas - continue from row 57.

7. Key Takeaway for today's meeting

  • None.

8. Glossary terms from this meeting

  • None.
  • Carried over:
    • Definition of "interchangeability" required.
    • 'Instance' (or a more specific version of the term) may require definition in future.
    • 'Master through Slave Mode'
    • 'Master to Master Mode'
    • Need a refined definition of "system" for the purposes of the PAR.

9. Schedule next meeting

  • Next meeting November 2. Note that this meeting will be one hour earlier for Europeans, due the end of Daylight Saving.  Heiko will be out, and probably the following two weeks as well.
  • November schedule:
    • 9, 16, 23, 30.

10. Any other business

  • The US English language pack for the latest forum software has still not been released, but Ian has hand edited the current version to incorporate the latest changes from the British English pack. The forums will be upgraded at a convenient point.
  • Ian hopes Michele will be able to provide a fuller report on the TESTA tutorial in due course.

11. Review new action items

  • None.
  • Bill agreed that the Scope Purpose and Need were what he expected to see, and would try to sound out other TTSC members at ITC and so they would have better knowledge of the proposal when it does come before them.

12. Adjourn

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

Respectfully submitted,
Ian McIntosh