Differences between revisions 3 and 5 (spanning 2 versions)
Revision 3 as of 2009-11-02 13:11:03
Size: 2911
Editor: pko
Comment:
Revision 5 as of 2010-03-17 13:09:34
Size: 2460
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:

Steps to be taken:

 1. Decide on PLANETS. Do we use PLANETS or not. The following steps assume that we do.
 1. Design Workflow
  1. Input - How do we provide input for the characterization tools.
  2. Output - How do we receive output from said characterization tools, and how do we use said output.
  3. Multiple Tools - We will most likely use multiple tools to achieve a better characterization. How dod we do this
 1. Choose interfaces.
Line 46: Line 36:
 * [:Tasks/6/1/AnalysisDocument:Analysis Document]
 * [:Tasks/6/1/DesignDocument:Design Document]
 * [:Tasks/6/1/SystemMaintenanceDocument:System Set-up and Maintenance Document]
 * [[Tasks/6/1/AnalysisDocument|Analysis Document]]
 * [[Tasks/6/1/DesignDocument|Design Document]]
 * [[Tasks/6/1/SystemMaintenanceDocument|System Set-up and Maintenance Document]]
Line 51: Line 41:
[[PageDicts(Actions/,Iteration,Time used,Status,Notes,Tasks adressed,Tasks adressed ~= Tasks/6/1)]] <<PageDicts(Actions/,Iteration,Time used,Status,Notes,Tasks adressed,Tasks adressed ~= Tasks/6/1)>>

Task Review Interface

Title
Review Interface

State
Not started

Time used

Time estimated
5md

Description

Review and approve the interface for the charac service. This include the soap interface, the java interface, the possible rest interface and the return values. These must all be of such a nature that this interface can be used to wrap many different tools. Look at the planets interfaces for this.

Documentation

Progress history

Iteration Time used Status Notes Tasks adressed
Actions/Review characterisation interface 23 In progress [[Tasks/6/1]]

Tasks/6/1 (last edited 2010-03-17 13:09:34 by localhost)