USECASE: Clone configuration

CHARACTERISTIC INFORMATION

Goal: Clone an existing configuration, with the intention of modifying it

Scope: Abstract definition

Preconditions:

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

Success End Condition: the new configuration is created in the data backend

Failed End Condition: no new configuration is created in the ETICS data backend

Primary Actor: developer

Trigger: This usecase is triggered via the web application


MAIN SUCCESS SCENARIO

  1. the user selects a configuration
  2. a new configuration is created with the same details values
  3. new relations with shared sub-objects (commands, props, subconfs, etc..) are created
  4. the user commits the changes

EXTENSIONS

  • None


NOTES

  • None


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