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

toggeable features

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

Details

    • Feature
    • Won't have (this time)
    • None
    • None
    • Obs Mgt & Controls
    • Hide

      Decoupling of deployment from release.

      • features can be tested in production without affecting real users
      • features that are "private" to SKA can be enabled by us, but not by other institutions
      Show
      Decoupling of deployment from release. features can be tested in production without affecting real users features that are "private" to SKA can be enabled by us, but not by other institutions
    • Hide

      As a user of webjive I can operate on its configuration and

      • see what features can be turned on or off; see what is being turned on; 
      • swap state on each of these features
      • if there are dependencies between features, then webjive has built-in tests that are run when webjive is launched that clearly explain what dependent-on features need also to be enabled.
      • Dependencies between features should be documented in the user documentation of webjive. 
      • Once this mechanism is in place, all new features being developed need to be configurable.
      • (It is actually part of the DoD) Appropriate testing needs to be done when developing each feature so that webjive works fine when it is enabled and when it is disabled, in combinations with many of the previosuly developed features turned on or off.
      Show
      As a user of webjive I can operate on its configuration and see what features can be turned on or off; see what is being turned on;  swap state on each of these features if there are dependencies between features, then webjive has built-in tests that are run when webjive is launched that clearly explain what dependent-on features need also to be enabled. Dependencies between features should be documented in the user documentation of webjive.  Once this mechanism is in place, all new features being developed need to be configurable. (It is actually part of the DoD) Appropriate testing needs to be done when developing each feature so that webjive works fine when it is enabled and when it is disabled, in combinations with many of the previosuly developed features turned on or off.
    • 3
    • 3

    • PI22 - UNCOVERED

    Description

      The architecture of WebJive Suite (Frontend + TangoGQL) needs to be made parametric to enable continuous deployment (a-là SAFe): implemented features need to be deployable in the production system, but necessarily released to the public. In this way features can be tested in production by selected beta-testers. This is also needed so that we at SKA deploy certain features that are specific for us (like themes, skins, logos) and MaxIV can avoid using those features; and viceversa.

      This can be achieved by having some sort of configuration switch that can turn-on/turn-off a feature (1 switch <–> 1 feature).

       

      Attachments

        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: (0%)

                Feature Estimate: 3.0

                IssuesStory Points
                To Do00.0
                In Progress   00.0
                Complete00.0
                Total00.0

                Dates

                  Created:
                  Updated:

                  Structure Helper Panel