USECASE: Create a new subsystem or component definition


Goal: Create a new abstract component or subsystem definition

Scope: Abstract definition

Preconditions: The user has a valid account on the ETICS Service.

Success End Condition: the new component or subsystem is created in the data backend

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

Primary Actor: developer

Trigger: This usecase is triggered via the web application


  1. user selects the parent module (project or subsystem)
  2. the user edit the subsystem/component details
  3. the webapp creates a default configuration for the subsys/comp
  4. the user commits the changes


  • None


  • None


  • id and dates are generated by the webapp and cannot be changed
  • module name needs to be unique within a project (to be discussed)

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