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

Analysis of minimal functional set of User Interfaces for AA0.5

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

Details

    • Obs Mgt & Controls
    • Hide

      A well defined minimal set of User Interfaces for the use at the ITFs and AA0.5 scenario, to identify where development is needed to avoid undue effort being spent on developing complex UIs when simple off the shelf UIs will initially suffice.

      Show
      A well defined  minimal  set of User Interfaces for the use at the ITFs and AA0.5 scenario, to identify where development is needed to avoid undue effort being spent on developing complex UIs when simple off the shelf UIs will  initially suffice.
    • Hide
      • considered roles should include AIV engineers, commissioning/system scientists, operators, maintenance engineers; 
      • the document should list all the use cases that are relevant for each role;
      • completeness is important, as well as validity (i.e. the stakeholders would agree that that a given use cases is indeed needed and important);
      • use cases should be described with no more than one paragraph of text (no need to provide a formal definition of them, with triggers, preconditions, flows, etc - this will be done later on if needed).

       

      AIV engineers (e.g ITF leads, POs from Atlas & Viola):

      • Review outcomes from Low ITF analysis in PI14
      • Discuss these outcomes with ITF leads, what is vitals, what is nice to have etc.

      Commissioning/System Scientists:

      • Commissioning Scientists written AA0.5 Scenarios <link> are broken down and sea-level uses cases extracted.
      • Follow-up interviews with Commissioning/System Scientists for confirmation.

      Operators (e.g Shari... as we wont hire operators in PI16):

      • Define ** operator responsibility/role/ day to day
      Show
      considered roles should include AIV engineers, commissioning/system scientists, operators, maintenance engineers;  the document should list all the use cases that are relevant for each role; completeness is important, as well as validity (i.e. the stakeholders would agree that that a given use cases is indeed needed and important); use cases should be described with no more than one paragraph of text (no need to provide a formal definition of them, with triggers, preconditions, flows, etc - this will be done later on if needed).   AIV engineers (e.g ITF leads, POs from Atlas & Viola): Review outcomes from Low ITF analysis in PI14 Discuss these outcomes with ITF leads, what is vitals, what is nice to have etc. Commissioning/System Scientists: Commissioning Scientists written AA0.5 Scenarios <link> are broken down and sea-level uses cases extracted. Follow-up interviews with Commissioning/System Scientists for confirmation. Operators (e.g Shari... as we wont hire operators in PI16): Define ** operator responsibility/role/ day to day
    • Inter Program
    • 2
    • 2
    • 13
    • 6.5

    • Spike SP-1808 Design for a Taranta dashboard that provides overview of the MVP

    • Team_OMCPT
    • Sprint 5
    • Hide

      As said in the slack channel, there's nothing more that we can do now other than discussing those findings, decide which actions to take, and do that.

      As expected at the beginning, this work raised a large number of questions and revealed several blind spots and gaps. 

      IMO, the other outcome is that the confluence page and corresponding miro board provides birds-eye view of what support UIs of the AA0.5 is needed. 

      Show
      As said in the slack channel, there's nothing more that we can do now other than discussing those findings, decide which actions to take, and do that. As expected at the beginning, this work raised a large number of questions and revealed several blind spots and gaps.  IMO, the other outcome is that the confluence page and corresponding miro board provides birds-eye view of what support UIs of the AA0.5 is needed. 
    • 16.6
    • Stories Completed, Solution Intent Updated, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    • Team_CREAM Team_MCCS Team_NALEDI Team_OMCPT Team_SST

    Description

      Analysis work to identify the minimum functional set of user interfaces required for the ITF and AA0.5. To answer the question "When I turn up to work at the ITF/AA0.5 facility, in week 1, what do I need in front of me?"

      Interfaces should include shell commands, python statements, Jupyter notebooks, Taranta dashboards, Grafana dashboards, and UIs provided by additional external tools (such as Kibana or database access tools).

      Ideally users (belonging to the SKA community) should be able to connect their laptop to a suitable network and  then be able to fire up the appropriate UI.

      This work is aimed at associating to the the job roles that are relevant (such as operator, commissioner, maintenance engineer) the collection of sea-level use cases that they need to fulfill, as well as the type of UI that could be used.

      A document should be delivered that describes the findings.

      This is work that should build upon https://jira.skatelescope.org/browse/SPO-1615. In fact it is expected that several of the use cases identified for the ITF will be valid for the AA0.5 as well.

       

      Note

      "Sea-level use case" is a term introduced by Alistair Cockburn that refers to use cases that an actor can carry out in a single session, in a short time span (10 minutes? half an hour?)  that provide enough value to let the actor happily walk away.
      In addition to Cockburn's book Writing Effective Use cases, see https://pjhobday.wordpress.com/2010/05/28/setting-use-case-goal-levels/.

       

      How to carry out this work

      Similarly to what was done for SP-1615:

      • identification of a number of key stakeholders to interview
      • define the skeleton of the interview
      • running each interview and writing up a summary of what was learned
      • (possibly) assembling a user story map
      • integrating what was learned for the ITF
      • integrating what can be gleaned from the science scenarios 
      • synthesizing the final report

       https://confluence.skatelescope.org/display/SE/Analysis+of+UI+needs+for+AA0.5

      Attachments

        Issue Links

          is informed by

          Spike - A time limited investigation to get some knowledge SP-1808 Design for a Taranta dashboard that provides overview of the MVP

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          relates to

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-3552 Produce Real-Time (per minute) Bandpass Spectra for SKA-LOW station antennas using MCCS

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Discarded

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-2773 Define and document required python control interface to the telescope

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          mentioned in

          Page Loading...

          Structure

            Activity

              People

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

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete34.0
                  Total34.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel