Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[hyades-dev] Meeting minutes for July 22nd Hyades Execution Team Meeting

I've attached the meeting notes from Tuesday's meeting.

 

Kent Siefkes

 

 

Execution Team Group Weekly Meeting, 11AM Eastern, Tuesday, July 22nd, 2003

Attending
---------
Kent Siefkes, IBM Rational Raleigh
Joe Toomey, IBM Rational Lexington
Ashish Mathur, IBM Rational Raleigh
Kim Coleman, IBM Rational Cupertino
Antony Miguel, Scapatech
Stephane Leroy, IBM Rational Toulouse
Kris Kobylinski, IBM Toronto
Richard Duggan, IBM Toronto


Proposed Agenda
---------------
1.	Hyades 1.0 Design Documentation
	A. Status/review JavaDoc updates (if any were needed)
		- Richard(execution components), Ashish(loader)

2.	Review action item status from last week

3.	Hyades Sept. Release
	A. Review UC1.1 use case realization (workbench side only, and including remote side interactions)
	B. Additional requirements gathering, if anything new since last week's submission

4.	Others ?


Recorded Discussion/Decisons
----------------------------
1.	Hyades 1.0 Design Documentation
	A. Status/review JavaDoc updates (if any were needed)
		- Richard(execution components)

			> Accurate.  Some could be enhanced to be more thorough.  Richard will do so at his next opportunity.

		- Ashish(loader)

			> A few are missing. Ashish will complete (day's work), and may need assist for checking it in (or Joe will check in for him)

2.	Review action item status from last week
	* Joe DROP the approved Use Case Realizations with mods noted above

		Ready, but needs to hook up with Sheldon to drop it.

	* Joe - Prepare UC1.1 for next week

		Done.

	* Joe - update test harness java doc (if time)

		Yet to do.

	* Richard/Ashish - See 1B) above, from last time

		See above.

	* Kent - forward new requirements to Harm

		Done.

3.	Hyades Sept. Release
	A. Review UC1.1 use case realization (workbench side only, and including remote side interactions)

		* Change example of Stop test to Suspend test (since stop test probably will use the kill method)
		* Add note that user gesture is on the Execution Results Editor/Viewer
			- Ashish had concerns about responsiveness based on 1.0 experience if we put it there
			- UI Group - please weigh in on where user control (suspend, resume, stop, etc.) gestures should originate in the UI
	
	B. Additional requirements gathering, if anything new since last week's submission

		* 

4.	Others ?	

New Action Items
----------------
* Joe - update test harness java doc
* Ashish - update loader java doc
* Richard - update execution components java doc 

Back to the top