6.3 High-Level System Architecture - FIGURE 6

[martchcl]

COMMENT ON IMAGE

Allan Thomson
10:48 18 Aug

We discussed a new variant of this diagram to help highlight the Intermediary relationship.

Drummond Reed
02:16 25 Aug
Allan, can you remember what the specific suggestion(s) were? Then we can produce a revised version.

Drummond Reed
10:40 25 Aug
WENJING recalls that this diagram uses two Intermediary systems but shows only one Supporting System. Wenjing will update.

Darrell O'Donnell
10:40 25 Aug
@drummond.reed@avast.com or @wenjing.chu@futurewei.com this diagram isn't in the slide deck where we have consolidated the diagrams that are in use.

Drummond Reed
17:40 25 Aug
@darrell.odonnell@continuumloop.com None of Wenjing's diagrams are currently in that deck. That's one of his action items (as he goes through updating them) to place them in that deck.

Drummond Reed
03:18 26 Aug
@chu.wenjing@gmail.com to revise his diagram and place in the TAS Source Diagrams Google Slides deck.

[talltree]

This issue is about the same diagram being discussed in #31. @darrellodonnell & Allan Thomson, can we make a reference to this issue there and then close this issue?

[darrellodonnell]

I am good with that.

[talltree]

My mistake, @darrellodonnell. Issue #31 is about Figure 4, and this issue is about Figure 6. I am assigning to @wenjing who did the original (who can consult @allant0 about the suggested changes).

[talltree]

@wenjing will propose a revision to the figure.

[wenjing]

This issue was copied from the old Google doc. It had been fixed already during the moving to Github back in Sept. The relevant commit is: 00556f2.
@talltree @darrellodonnell please take a look. The change is about "Supporting Systems" - we now show two instances of supporting systems to be consistent with 2 instances of intermediary systems. I'll probably propose last call if there's no new comment.

[talltree]

We reviewed this together on the 2022-11-10 TATF NA/EU meeting and agreed with Wenjing that the figure had been updated to address the issue. Thus we are closing this issue as agreed on the call.