USECASE: Create configuration definition


Goal: Create a new abstract component or subsystem definition

Scope: Abstract definition


  • The user has a valid account on the ETICS Service.
  • An item (i.e. project, subsystem or component) is selected

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


  1. the user clicks on "new conf" button
  2. the user edits details for the configuration
  3. default build/vcs commands are automatically attached to the new configuration
  4. the user can replace the defaults with an existing build/vcs command
(when changing commands, changes can apply to a single platform or to all platforms)
  1. the user commits the changes


  • None


  • None


  • id and dates are generated by the webapp and cannot be changed
  • conf name must be unique within configurations for the related item
  • vcs and build commands (eventually empty) must be attached to the configuration for at least one platform

-- 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