Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Cosmos Architecture Meeting 27-Sept-07"

(UI for the CMDBf end-to-end use case)
 
Line 17: Line 17:
 
== UI for the CMDBf end-to-end use case ==
 
== UI for the CMDBf end-to-end use case ==
 
*What is the scope of the UI?  
 
*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?  
+
**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?  
+
**Or does it something do more?  
*If it does something more, do we use BIRT?
+
**If it does something more, do we use BIRT?
*[[CosmosDataReportingDesign]]
+
**[[CosmosDataReportingDesign]]
 
+
* We need to explain the relationship b/t CMDBf and the data visualization fw-->add to cmdbf deliverables document
+
* [[COSMOS_Design_Interaction_Model]]
+
  
 +
Sheldon has started to explain the relationship b/t CMDBf and the data visualization fw-->add to cmdbf deliverables document
 +
* [[COSMOS_Design_Interaction_Model]].  That said, we still, need to be clear on how the broker stores it's information internally to support the kind of queries that will come from the UI.  This continued to be a source of confusion b/c of the user interface.  Joel inidicated that he thought we closed on this when we had the instance data in the broker question.  We should clarify this on the [[Leveraging CMDBf]] page.
 
* What is the starting point for the graphical part of this UI? Is it the current COSMOS GUI?
 
* 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
+
**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.
+

Latest revision as of 12:16, 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

Sheldon has started to explain the relationship b/t CMDBf and the data visualization fw-->add to cmdbf deliverables document

  • COSMOS_Design_Interaction_Model. That said, we still, need to be clear on how the broker stores it's information internally to support the kind of queries that will come from the UI. This continued to be a source of confusion b/c of the user interface. Joel inidicated that he thought we closed on this when we had the instance data in the broker question. We should clarify this on the Leveraging CMDBf page.
  • What is the starting point for the graphical part of this UI? Is it the current COSMOS GUI?
    • Add this to the use cases for CMDBf

Back to the top