[hyades-dev] Meeting minutes for July 8th Hyades Execution Team Meeting

["Siefkes, Kent" <KSiefkes@xxxxxxxxxxxx>]

I've attached the meeting notes for yesterday's meeting.

 

Kent Siefkes

 

 

 

Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, July 8th, 2003

Attending
---------
Kent Siefkes, IBM Rational Raleigh
Ashish Mathur, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Anthony Miguel, Scapa
Richard Duggan, IBM Toronto
Kris Kobylinski, IBM Toronto
Dwayne Dreakford, IBM Rational Raleigh


Proposed Agenda
---------------
1.	Hyades 1.0 - Joe, Kris
	a.	Review status of what was dropped in Hyades 1.0 for Execution, and what was held back.
	b.	Review upcoming plans for incremental 1.0 work
	c.	Design documentation status/plans - use case realizations, other
2.	Hyades Sept. Release
	a.	Process suggestions for gathering execution requirements for Sept. release
	b.	Execution team membership
	c.	Suggested changes from 1.0 operating procedures


Recorded Discussion/Decisons
----------------------------
1.	Hyades 1.0 - Joe, Kris
	a.	Review status of what was dropped in Hyades 1.0 for Execution, and what was held back.
		IN: Execution for JUnit tests only
		HELD BACK: Execution for HTTP and Manual Test (from WSAD Component Test)
		
		Use Cases:
   		IN: UC4 - Launch a test for immediate reporting/monitoring
		HELD BACK(Execution): UC2 - Monitor a running application on a specified node (Profiling is there, but not for a running test)
		HELD BACK: UC1 - Launch a single test instance from workbench on a single specified node, (functionality implicit in UC4, but not possible from Hyades UI)
	    	HELD BACK: UC1.1 - Show control events to running test (Start, not Stop)
	    	HELD BACK: UC2.1 - Show control events to monitored app


	b.	Review upcoming plans for incremental 1.0 execution-related work:

		Hyades 1.01 (this week)
		A. Fix Severity 1 defects in execution area

		Hyades 1.0x driver additions
		A. HTTP
		B. Manual Test
		
		Potential additional incremental drops (such as Stop test, etc. that were held back from 1.0)

		Discussion about branches to separate 1.0x work from Sept. release work, potential transition to CVS
	
		Recommend Monday mgmt. meeting discusses branch and incremental drop strategy between 1.01 and sept. Release

	c.	Design documentation status/plans - use case realizations, other

		1. Update existing use case realizations
			A. Correct per 1.0 implementation
			B. Add detail now available based on 1.0 implementation (possibly in separate diagram)
			C. Add remote side (possibly in separate diagram)

			Priority:
			Do UC4 first (Joe)
			Remove existing UC2 from web site (Joe)
			Do UC1 (Joe)
			Do UC1.1 (Joe)
		
		2. Publish Execution infrastructure block diagram (Joe to send out for review by next week)

		3. Review and make any necessary corrections to JavaDoc (believed to be close to up-to-date) - Richard(execution components),
			Dwayne(marshalling framework), Joe(execution harness), Ashish(loader)
		
2.	Hyades Sept. Release
	a.	Process suggestions for gathering execution requirements for Sept. release
		- Mgmt. meeting agreed that a more structured process is needed than 1.0 (we'll wait for guidance on that process)
		
	b.	Execution team membership
		- Dwayne and Ashish will not likely be able to participate in Sept. release development
		- Antony and Kris will get back on this later

	c.	Suggested changes from 1.0 operating procedures
		- Discussed some organizational efficiency issues (beyond execution group)
		- Group to think over how the execution group meetings can be improved (effectiveness, efficiency, content, etc.), for next week.

New Action Items
----------------
* See design doc assignments under 1c above (goal is to complete by next Tuesday, subject to 1.01 work)