Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-975

Appealing, connected dashboards for CSP devices

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
    • Hide

      Demonstrate achievement of the PI7 goal  for Webjive which is

      Goal for PI7

      To have a handful of dashboards (between 2 and 5)  that cover complex systems (several devices, at different levels of hierarchy). These dashboards can be used by engineers that need to monitor the behavior of those devices and in part control them (by issuing commands and sending configurations).

      A primary key result is that we have those dashboards that have been defined for the specific needs and are used. Another key result is that several improvements in Webjive have occurred, to enable development of those dashboards.

      An expected outcome is that by using these dashboards engineers can more easily use the CSP and its sub-elements software, understand its behavior and therefore become more effective in their development activity.

      Another expected outcome is that SKA team members realize that Webjive is mature enough for defining non trivial dashboards, in terms of content, in terms of visual appeal and in terms of interaction structure. Other stakeholders, such as members of the Tango community, become easily convinced that Webjive is going to become "the" reference tool for GUIs for Tango. 

       

      A secondary goal is a process goal: members of the CREAM TEAM become more proficient in Lean UX practices such as developing and using mockups of the UI to gather useful feedback in terms of usability that inform the design process. The CREAM TEAM should also become proactive with respect to understanding what is needed by Webjive users and understanding their priorities and values.

      Show
      Demonstrate achievement of the PI7 goal  for Webjive which is Goal for PI7 To have a handful of dashboards (between 2 and 5)  that cover complex systems (several devices, at different levels of hierarchy). These dashboards can be used by engineers that need to monitor the behavior of those devices and in part control them (by issuing commands and sending configurations). A primary key result is that we have those dashboards that have been defined for the specific needs and are used. Another key result is that several improvements in Webjive have occurred, to enable development of those dashboards. An expected outcome is that by using these dashboards engineers can more easily use the CSP and its sub-elements software, understand its behavior and therefore become more effective in their development activity. Another expected outcome is that SKA team members realize that Webjive is mature enough for defining non trivial dashboards, in terms of content, in terms of visual appeal and in terms of interaction structure. Other stakeholders, such as members of the Tango community, become easily convinced that Webjive is going to become "the" reference tool for GUIs for Tango.    A secondary goal is a process goal: members of the CREAM TEAM become more proficient in Lean UX practices such as developing and using mockups of the UI to gather useful feedback in terms of usability that inform the design process. The CREAM TEAM should also become proactive with respect to understanding what is needed by Webjive users and understanding their priorities and values.
    • 3
    • 3
    • 11
    • Team_CREAM
    • Sprint 5
    • 7.6
    • PI22 - UNCOVERED

    • SYSTEM_DEMO_5 Team_CREAM webjive
    • SPO-561

    Description

      Develop a handful of dashboards (between 2 and 5) that cover complex systems (several devices, at different levels of hierarchy). These dashboards can be used by engineers that need to monitor the behavior of those devices and in part control them (by issuing commands and sending configurations).
      Dashboards are visually appealing and use images, colors, colored boxes and margins, colors and images may change depending on device values (attributes or states). The user can navigate between dashboards in a drill-down/move-up fashion. The user can launch commands and specify json strings for their arguments using things like dropdown menus.
      The "complex systems" mentioned above are components of the CSP that the CREAM TEAM is working on and include the CSP.LMC devices/classes: CSP.LMC Element Master, CSP.LMC Element Subarray. I expect that the created dashboards will cover no more than 15 devices. These devices are not necessarily part of the MVP (ie. the dashboards will work also for isolated CSP devices).

      Acceptance criteria

      • a system of dashboards for CSP-related devices are completed to allow engineers to monitor the behavior of their devices and to control them 
      • the dashboards are visually more appealing than existing ones and functionally richer 
      • target devices are TBD

      Attachments

        Issue Links

          Structure

            Activity

              People

                g.brajnik Brajnik, Giorgio
                g.brajnik Brajnik, Giorgio
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1017.5
                  Total1017.5

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel