Difference between revisions of "Extra meeting 17.1.2012"

From Developer Documents
Jump to navigation Jump to search
Line 151: Line 151:
 
* '''(Toni)''' Developer documentation
 
* '''(Toni)''' Developer documentation
 
* '''(Tuukka)''' Model Browser (multi-selections, dnd)
 
* '''(Tuukka)''' Model Browser (multi-selections, dnd)
* '''()''' 3D
+
* '''(Marko)''' 3D
  
 
Future topics:
 
Future topics:
  
* Databoard
+
* '''(Toni)''' Databoard
 
* History data management
 
* History data management
 
* Charts
 
* Charts
Line 163: Line 163:
 
* Model event management
 
* Model event management
 
* Access control
 
* Access control
 +
 +
;Work practices
  
 
During H1/2012, all of these topics shall be covered 1-2 topics/meeting. For each meeting, a presentation shall be prepared by the responsible person.
 
During H1/2012, all of these topics shall be covered 1-2 topics/meeting. For each meeting, a presentation shall be prepared by the responsible person.
 +
 +
Topics are divided into two categories: core technologies and application areas. All persons responsible for application areas need to be aware of core technologies.
 +
 +
The target is to hold 1 meeting per week.
  
 
;2. Other issues
 
;2. Other issues

Revision as of 08:33, 17 January 2012

Previous Up Next

Agenda

1. Discussion on development areas
  • Create a list of most important epic stories in Simantics development.
  • Agree responsibilities for development topics and allocate time for processing of the first topics
2. Other issues
  • Organization of documentation

Minutes

1. Discussion on development areas

Choose five topics that we should start processing first.

Topics Hannu Tuukka Tommi Harri Antti
(Harri) Scrum and SVN process - - - - -
(Hannu) Layer0 (Inverses, ConsistsOf, Export/Import, Adapters vs. SCL values) X X - - X
(Hannu) SCL (Function library design and development rules, Contexts in getRelatedValue2, Technical details on using ReadGraph and indices) X - - - X
(Antti) DB client (Interface cleanup and improvements, Implementation improvements, Persistent requests, Documentation) (issue:3075) - X - - X
(Antti) Variable (Interface improvements, Standard property specification, Standard implementation of graph-based variables, Standard implementation of simulator variables?) - - - - -
(Antti) Modelled Selection view (Model improvement) - - - - -
(Hannu) Experiment control (Interfaces, Interplay with Variable) - - - - -
(Hannu) Commands - - - - -
(Antti) Sheets - - - - -
(Hannu) Structural (Interface variables, Standard implementation?) X X - - X
(Antti) Scenegraph (Loaders, Refactoring needs, Diagram) X X - - -
(Tuukka) Diagram (Refactoring towards Scenegraph, Layers, Testing) - - - - -
(Hannu) Mapping framework (SCL-based definition) - - - - -
(Tuukka) Testing (Increasing automatic testing, Squish) X X - - X
(Antti) Team features (Implementation strategy) - - - - -
(Tuukka) Migration (Tool development) - - - - -
(Hannu) Developer tools (IDE integration, Graph Debugging, SCL support, migration support?) - - - - -
  • (Antti) Views
  • (Antti) Interactive model documentation
  • (Toni) Developer documentation
  • (Tuukka) Model Browser (multi-selections, dnd)
  • (Marko) 3D

Future topics:

  • (Toni) Databoard
  • History data management
  • Charts
  • SPM
  • Ontology development environment
  • Model issue management
  • Model event management
  • Access control
Work practices

During H1/2012, all of these topics shall be covered 1-2 topics/meeting. For each meeting, a presentation shall be prepared by the responsible person.

Topics are divided into two categories: core technologies and application areas. All persons responsible for application areas need to be aware of core technologies.

The target is to hold 1 meeting per week.

2. Other issues