Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Cosmos Architecture Meeting 27-Sept-07"
Line 29: | Line 29: | ||
* We have identified the GUI & programmatic interface aspects of this UI. We need to specify those in detail. Does someone have anything to start with or will these be addressed by new ERs? | * We have identified the GUI & programmatic interface aspects of this UI. We need to specify those in detail. Does someone have anything to start with or will these be addressed by new ERs? | ||
+ | |||
+ | * We need to be clear on how the broker stores it's information internally and the kind of queries. This continued to be a source of confusion b/c of the user interface. |
Revision as of 11:58, 27 September 2007
Attendees
- Ali Mehregani
- Mark Weitzel
- Bill Muldoon
- Hubert Leuyng
- Valentina Popescu
- Sheldon Leeloy
- David Whiteman
- Jimmy Mohsin
- Don Ebright
- Jack Devine
- Saraub
- Mau Shin
Minutes
UI for the CMDBf end-to-end use case
- What is the scope of the UI?
- Does the UI simply pull the data from the MDRs and present it to a live user or an application?
- Or does it something do more?
- If it does something more, do we use BIRT?
- CosmosDataReportingDesign
- We need to explain the relationship b/t CMDBf and the data visualization fw-->add to cmdbf deliverables document
- COSMOS_Design_Interaction_Model
- What is the starting point for the graphical part of this UI? Is it the current COSMOS GUI?
- We should add this to the use cases for CMDBf
- We have identified the GUI & programmatic interface aspects of this UI. We need to specify those in detail. Does someone have anything to start with or will these be addressed by new ERs?
- We need to be clear on how the broker stores it's information internally and the kind of queries. This continued to be a source of confusion b/c of the user interface.