Notes from meeting 2-Oct-2002

 - Giuseppe apologises for having failed to announce the meeting room!


 - Session during TDAQ plenary (ATLAS week; tuesday 16:00 - 18:00): contents

	+ present the working group: summary of definition document, preliminary workplan
	+ where are we: preliminary work done up to now
	+ list of findings (present their scope)



 - Current issues: an initial list to which we are all invited to modify/add...

	+ stageable architecture (includes also ROD-ROB issues)

	+ Monitoring: what is being monitored, where and how much (matrix)

	+ COntrol Network: requirements

	+ Other networks... backend network? ROD monitoring network?

	+ Parameters: which ones, values, ...
	
	+ Errors: define, on a component by component basis, the sources of errors and their handling
		(pre-requisitie to address system wide use cases related to error handling)

	+ Single points of failure (DFM, RoIB)

	+ Compliance to partitioning (component by component basis)

	+ Common schemes for local control and supervision

	+ Interfaces between components


 - Volunteering for "presentations":

	Bob --> monitoring; networks we have got

	Giuseppe --> scaleable architecture; interfaces; partitioning

	Sergei --> errors, common schemes for control & monitorig

	Beniamino --> parameters

  short talks (5-10 mins) addressed at defining the issue


 - Calendar for open meetings: every second monday 16:00/18:00 (in alternative to data collection meeting). First
   one October 14. The role of the open meeting is that of, given an issue, to: agree on the issues, formulate the
   problem and the reccommendation to the mgt team.

 - Architecture document

   A reference document will be produced describing the existing architecture; the document will be updated
   consistently with the work of the wg. A proposed outline:


		- introduction etc.

		- Parameters chapter

		- Chapter with a list of components relevant to the architecture
		
		- Overall architectural "views":

			data flow view
			control view
			"location" view (where things are located physically)
			Size view (how many instances of each component)
			other views?

		- Components:
			a description of each architectural component:

				function, requirements, performance, error behaviour, ...


		- Interfaces

			a description of the interfaces between components



   (of course with plenty of pointers to existing and future technical documentation)

   Initially the document will be filled with the result of the informal discussions we (will) have with
   people from the different systems/sub-systems.