USECASE: Edit configuration's properties/environment/commands

CHARACTERISTIC INFORMATION

Goal: Edit (change) the properties/environment/commands of a configurations

Scope: Abstract definition

Preconditions:

  • The user has a valid account on the ETICS Service.

Success End Condition: the modified properties/environment/commands are saved in the data backend

Failed End Condition: no modification is made to the properties/environment/commands in the ETICS data backend

Primary Actor: developer

Trigger: This usecase is triggered via the web application


MAIN SUCCESS SCENARIO

  1. user selects a configuration
  2. user selects a platform
  3. user can either change the values of propss/envt/cmds or replace them with existing props/envt/cmds
  4. the user commits the changes

EXTENSIONS

  • None


NOTES

  • Property inheritance across configuration trees. Are properties inherited from parent configuration? probably not as you cannot always know what's the parent configuration (TBD)


CONSTRAINTS REQUIREMENTS

  • None

-- MebSter - 07 Mar 2006

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2006-03-07 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    ETICS All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback