| [hyades-dev] Meeting minutes for 4/22 Hyades Execution Team Meeting |
I've attached the meeting notes for this week's meeting.
Kent Siefkes
<<Hyades Execution Group Meeting Notes - Apr 22.txt>>
Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, Apr 22, 2003
Attending
---------
Kent Siefkes, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Anthony Miguel, Scapa
Kim Coleman, IBM Rational Cupertino
Kris Kobylinski, IBM Toronto
Proposed Agenda
-------------------------
1. Review execution group plan of record (web published)
2. Identify blocking issues Inside and Outsidet he group, e.g. what's prevent us from making progress, especially
coding.
3. Enumerate components we own (workbench + remote) and assign implementation ownership for available resources
4. Discuss execution of Test Suites, and what we deliver for Rel. 1 (deferred one wek)
5. Review outstanding action items from 4/15 weekly meeting
Recorded discussion
-------------------
1. Reviewed plan of record (** indicates progress or status update)
1. Scope execution use cases for Release 1 (Eclipse release 2.1.1) completed April 8, 2003
2. Share and align/confirm use cases for Release 1 with User Interface group completed April 11, 2003
3. Participate in overall Hyades schedule/planning for first release ongoing
4. Complete and review remaining use case realizations, interfaces, and java doc for use cases scoped in
for first release: UC1 and UC2 already dropped, UC4, UC1.1, and UC2.1 remain.
** UC4 reviewed once, ready for a second review
** UC1.1 reviewed last week, Antony provided an updated version, and the group approved the update for
drop next week.
** UC2.1 not submitted yet for review
5. Specify control events for controlling execution (UC1.1) and monitoring/profiling (UC2.1)
** Kris ready for review of control events from WSAD Component test
6. Identify APIs for components that run on the remote machines, in conjunction with the Data Collection
& Communication group.
** Richard's group is taking the first shot at this and should be ready soon.
7. Add to our use case realizations interactions with the remote side components
** Yet to be done, pending #6.
8. Build reference implementation (integrating with the UI group and Data Collection & Communication group)
to realize the Release 1 execution use cases (UC1, UC2, UC4, UC1.1, UC2.1), including the implementation
of the associated execution interfaces (workbench side).
Execution Use Case Headlines:
UC1 - Launch a single test instance from workbench on a single specified node
UC1.1 - Show control events to running test
UC2 - Monitor a running application on a specified node
UC2.1 - Show control events to monitored app
UC4 - Launch a test for immediate reporting/monitoring
2. Identify blocking issues
A. Inside group
* disemminate internal understanding of programming to the RAC [Kim will share what she has learned]
B. Outside group
* #6 above from Richard's team: remote APIs for control and collecting data (via logging) -- some is
already done so Kris will follow up with Richard on this (i.e. this may not truly be blocking)
* Need delegate assigned from Richard's team to work closely with execution team to get coding traction
(not truly blocking, but needed)
* Need communication infrastructure Interface(s) from Richard's team that will be available in Release 1
3. Enumerated components & programming tasks we own (workbench + remote) and assign implementation ownership for
known available resources for Rel 1 (currently Joe, Kris, and Antony). TBA means To Be Assigned.
"test tool" on workbench side - Joe [need to colloborate with UI group]
listener on workbench side [that feeds model loader(s)] - or is UI or DataCollection team doing the
listener and loaders ? [it is expected that there is a common listener, but vendors could plug-in
their own]
session on workbench side - Antony [confirm with Richard's team that they are not providing this]
remote skeleton/proxy of Session - Antony [confirm with Richard's team that they are not providing this]
remote Session (that does real work) - Richard's team
[per test case type] Define Executable_object on workbench side (collaborate with UI team)
- Generic Support - Joe
- Manual - Joe
- Java/JUnit - Joe
- HTTP - Joe
- Arbitrary Command Line - Joe
[per test case type, but likely to share common] workbench side of IExecutionEnvironment & IExecutor
- Generic/Common Support - TBA
- Manual - TBA
- Java/JUnit - TBA
- HTTP - TBA
- Arbitrary Command Line - TBA
[per test case type, but likely to share common] remote skeleton/proxy of IExecutor (&IExecutionEnvironment?)
- Generic/Common Support - Kris
- Manual - Kris
- Java/JUnit - Kris
- HTTP - TBA
- Arbitrary Command Line - TBA
[per test case type, perhaps can share common] remote Executor (that does real work):
- Generic/Common Support - Richard's team [Confrm if listener that communicates with Agent(s) is included]
- Manual - Kris
- Java/JUnit - Kris
- HTTP - Kris
- Arbitrary Command Line - TBA
* Issue noted about the current RAC requirement to pre-registering the command associated with a
particular test case type (originally required for security reasons) in order to invoke it.
There was multiple voices that this was very user unfriendly as a general requirement since it would
require manual configuration prepping of each remote Agent before use, and we'd like to
see it removed as a general requirement.
4. Discuss execution of Test Suites, and what we deliver for Rel. 1 - DEFERRED UNTIL NEXT WEEK
5. Review outstanding action items from 4/15 week:
- Enumerate set of events that can occur in response to a sent message [Antony] - DONE
- Update UC1.1 [Antony] - DONE
- Update existing UCs to show the interactions between entities on workbench side and remote side [Joe]
- Identify existing control events within Component Test [Kris] - READY, Kris will send out email
- Determine the status of UC4, 2.1 (approved, more discussion?) [Joe] - DISCUSSED, These are approved.
6. New Action Items
Joe - attend weekly communication group meetings as a rep from our Execution Group
Kent - discuss blocking issues with external group leaders