USECASE: Create a new project definition

CHARACTERISTIC INFORMATION

Goal: Create a new abstract project definition

Scope: Abstract definition

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

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

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

Primary Actor: project administrator

Trigger: This usecase is triggered via the web application


MAIN SUCCESS SCENARIO

  1. clicks on "create new"
  2. the edit page for a <> is shown to the user
  3. the user edits the project details
  4. the webapp creates a default configuration for the project
  5. the user commits the changes

EXTENSIONS

  • None


NOTES

  • None


CONSTRAINTS REQUIREMENTS

  • None

USECASE: Create a new subsystem or component definition

CHARACTERISTIC INFORMATION

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


MAIN SUCCESS SCENARIO

  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

EXTENSIONS

  • None


NOTES

  • None


CONSTRAINTS REQUIREMENTS

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

USECASE: Create configuration definition

CHARACTERISTIC INFORMATION

Goal: Create a new abstract component or subsystem definition

Scope: Abstract definition

Preconditions:

  • 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


MAIN SUCCESS SCENARIO

  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

EXTENSIONS

  • None


NOTES

  • None


CONSTRAINTS REQUIREMENTS

  • 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

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

USECASE: Edit subconfigurations

CHARACTERISTIC INFORMATION

Goal: Edit (change) the children (and dependencies) configurations

Scope: Abstract definition

Preconditions:

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

Success End Condition: the modified list of children (and dependencies) configurations are saved in the data backend

Failed End Condition: no modification is made to the selected configuration 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. user search/browses configurations for project/subsystem sybsystems/components
  3. user selects and attaches an existing configuration for the subsystem/component
  4. the user commits the changes

EXTENSIONS

  • None


NOTES

  • None


CONSTRAINTS REQUIREMENTS

  • configurations for subparts must already exist. The user cannot add configurations created on-the-fly.
  • the same applies to dependencies

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

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