[KP FRaMED] Meeting Protocols
This page helps to keep everyone up to date according to the development process done during the complex lab Software Technology/FRaMED. Every meeting protocol should be uploaded here.
#Do. January-26 2017 ##Assigned Tasks ###Kevin Kassin
- Create Wikipage about requirements used to generate configurations
- Complete dokumentation in code
- Add corner cases and one additional requirement for relationships
- Analyse 3 processes for the selection of test case configuration
#Do. January-12 2017 ##Assigned Tasks ###Kevin Kassin
- Continue implementing model manipulation test generator
- Change links of created file, to work on travis
- Add CompartmentInheritance to baseTest
- Implement RoleInheritance correctly and add it to baseTest
- Analyse 3 processes for the selection of test case configuration
#Do. January-05 2017 ##Assigned Tasks ###Kevin Kassin
- Refactoring
- Rename packet testgeneration
- Check validity of configurations with featureIDE
- Use a BitSet instead of a String to save configurations
- Change base of links (. to platform...)
- Change string manipulation to model manipulation to create test cases
- Trigger test case creation before load directory
- Upload crom_dia file of BaseTest
#Do. December-15 2016 ##Assigned Tasks ###Kevin Kassin
- Read literature to find out how to automate tests for the transformation dependant on features
- Start to implement solution for tests
- Testgenerator
- Create feature configurations
#Do. December-8 2016 ##Assigned Tasks ###Kevin Kassin
- Refactor transformations Fulfillment, Compartment Type und Group Constraint
- Implement features in transformations Group Constraint und Relationship
- Read literature to find out how to test the transformation dependant on features
#Do. December-1 2016 ##Assigned Tasks ###Kevin Kassin
- Refactor dead code "RoleImpl.etl"
- Finish wikipage to show influence of feature model to transformation
- Realize some influences of feature to transformation
#Do. November-24 2016 ##Assigned Tasks ###Kevin Kassin
- Refactor manually putting (key, value) in Map in ORM2CROM transformation
- Elaborate wikipage to show influence of feature model to transformation
#Do. November-17 2016 ##Assigned Tasks ###Kevin Kassin
Programming
- Name of compartment type should be kept even if compartment type feature is not choosen.
- Change Strings in code to avoid blanks.
- Refactor name setting in factories and createShapeCommand (using shape.getName()==null)
- change variable ~features in Tranformations from set to a map (feature->boolean)
Theory/ Preparation for programming
- Create and elaborate wikipage to show influence of feature model to transformation
##Assigned/ Remaining/ Changed Tasks ###Kevin Kassin Talked about problems concerning the second and third task determined at last meeting. Talked about implementation of create Rolemodel.
- Function to create Rolemodels (Compartment with different name)
- Change transformation for Compartmenttypes when !compartment (ignore attributes and operations)
##Assigned Tasks ###Kevin Kassin
- Add SmallIcon for PaletteEntry "Role Model"
- Function to create Rolemodels
- Change transformation for Compartmenttypes when !compartment (ignore attributes and operations)
##Assigned Tasks ###Kevin Kassin
- Add paletteEntry "Role Model", visible when !compartment_type
##Assigned Tasks
- Introduce a label showing the current status (valid/invalid) of the configuration
- Implement Load&Store functionality for the crom_dia file with embedded feature list
- Find out if there are exclusion-constraints in the feature model
- Refactor
- Ask FeatureIDE Dev on how to integrated the FeatureIDE Update site into Travis/Maven
- Adjust Feature attributes in the Ecore file (selected/automated)
- Read-only page for crom and crom_dia
Next meeting: 28.06.16 10:00 am
##Assigned Tasks
-
Create prototype feature-selection page
-
Try to integrate FeatureIDE functionality into FRaMED
-
Read-only page for crom and crom_dia
-
Find out how to create singleton elements in ecore file
Next meeting: 14.06.16 10:00 am
##Assigned Tasks
- Create prototype feature-selection page
- Try to integrate FeatureIDE functionality into FRaMED
- Find out how to create singleton elements in ecore file
- Create new plugin-Project for feature model
- Read-only page for crom and crom_dia
- Play around!
Next meeting: 07.06.16 10:00 am
##Assigned Tasks
- Export to Eclipse-Product
- Create new plugin-Project for feature model
- Think about how a configuration (*.config) can be stored within FRaMED
- Make a list of pros and cons
##Assigned Tasks
- Create issues for each unimplemented Feature
- Gray out RelationshipConstraints, if no Relationship is selected (Improvement)
- It is possible to create unjustifiable constraints (e.g., reflexive and irreflexive) (Bug)
- Make release v2.0.3 (hints)
- Check release on a clean Eclipse instance
- Check javadoc completeness
- Generate corresponding javadoc for the version (v2.0.3) in gh-pages
- Create your own feature model only including the above features
- Mon. May-19 2016, 9:30, APB/2094
##Assigned Tasks
- Fix RelationshipConstraint Bug
- Test the Editor, e.g. RelationshipConstraints
- Create/delete constraint onClick palette entry
- Fix icons
- Fix file save
- Install RoSI_CROM
- Inspect Feature Model and Feature Mapping
- Identify the features used in the mapping
- Create your own feature model only including the above features
- Think about how a configuration (*.config) can be stored within FRaMED
- Mon. May-2 2016, 9:00, APB/2094
- GitHub update (Meeting protocol, Doku, push to developer branch, Transformations)
- Create TestcaseGenerator (Generate testcases for Relationships and RelationshipConstraints)
- Add comments to past implemented code
- Adapt palette: Adding constraints by selection in palette
Tue. Apr-26 2016, 09:30, INF/2078
- Manual transformation test
- Create testcases for multiple relationships
- Create testcases of multiple relationships with constraints
- Adapt palette: Adding constraints by selection in palette
Tue. Apr-19 2016, 09:30, INF/2078
- Add constraint label to relationships
- Adapt create constraint dialog for relationships connection (multiple polyline)
- Solve mupltiple polyline bug
- Adapt relationship/constraint handling for creating/deleting
- Disable drawing additional constraint connection line
- Enable multiple relationships between same compartments
Tue. Apr-12 2016, 09:30, INF/2078
- Add constraint label to relationships
- Create multiple line for relationship description
- Add drag and drop for constraints
- Add drag and drop for figures
- Create rule for adding multiple relations
- Standalone release
Tue. Apr-05 2016, 10:00, INF/2078
After a break, we met each other to discuss our further approach.
Mo. Mar-22 2016, 10:00, INF/2078
- Update Wiki and Meetings Protocols
- Study GEF Notation
- Investigate EditPolicies for dynamic usage
- Check where and when patterns (Editor.ORMDDirectEditManager) are used and how to rework
Fr. Dec-18 2015, 10:00, INF/2078
- Update Wiki and Meetings Protocols
- Move getRelationshipConstraints to Util
- Change order of connections in ORMGraphicalEditorPalette
- Add new icons for connections
- Add rest of RelationshipExclusion Implementation
- Add RelationshipExclusion to Wiki (NEED TO UPDATE IMAGE!!!)
- Study GEF Notation
- Rework EditPolicy for dynamical usage
Fr. Dec-11 2015, 12:30, INF/2078
After first steps we are starting to get into FRaMED. For that we are getting specific tasks.
- Investigate ConstraintDialog Bugs
- Update Wiki and Meetings Protocols
- Change Type.getConstraints to Type.getRelationshipConstraints
- Add RelationshipExclusion to FRaMED
- Add tests for the transformation of Reflexive, Acyclic and RelationshipExclusion in "transformation.test"
- Study /org.framed.orm.ui/src/org/framed/orm/ui/editPolicy
Fri. Nov-20 2015, 14:00, INF/2094
In this first meeting we met each other to talk in general about the project. We came up with several introductory tasks.
- incorporation of FRaMED, GEF etc.
- add constraints (Acyclic, Reflexive) to graphical model
- implement handling of added constraints in editor
- extend transformations with added constraints
Wed. Nov-11 2015, 14:00, INF/2094
Today, we finished up our project by stating that all due tasks were fulfilled yet. There are only minor changes to make:
- Update Wiki images to show FRaMED 2
- Correct Wiki link to Bank example (fix file extension)
- Perform a final merge and create a release (mail Thomas when it's done)
- Push committed changes from David
We met the last time to state the current progress of the project and to discuss the final steps to take to finish up the project.
- [Tobias] Generate JavaDoc after final To-Master-Merge
- [David] Fix Input Validation (has to be integrated later on)
- [David] Editor testing
- [Tobias] Final Merge and Release when all changes are made
- [Kay] Close deprecated issues in the issue tracker
- [Kay] Slightly update the former created presentation slides
- [Johannes] Change ORM to CROM_DIA extension
- [Kay] Implement Relationship name label
- [all] Notify Tobias once all changes on the project are done and the final merge+release can be performed.
Mo. Feb-9 2015, 14:00, INF/2078
We met today to discuss the final steps of the project. According to our schedule, there are two weeks left for finalizing the project. We seem to surpass that goal.
- [all] Write and improve JavaDoc (documentation)
- [all] Update Wiki, i.e. presentation slides (documentation)
- [Johannes] Change
.ormfile extension to.crom_dia - [Tobias+Johannes] Provide the bank example in the user section of the wiki
- [David] Editor testing (Edit policies and public methods)
- [David] Finalize input validation
- [Kay] Realize RelationshipImplication (Optional)
- Merge project into
masterbranch, update versions - generate and push JavaDoc to gh-pages
- review existing issues
- release "FRaMED v2"
Mo. Jan-26 2015, 14:00, INF/2078
We met today to update ourselves about the current state of the project and re-assign some tasks to keep up the schedule properly. Nothing fundamental has changed. ;-) The project should be ready to start working within the next two weeks, and the next meeting shall be the first with a running editor.
- Finalize transformation (as before) [Johannes+Tobias]
- Work in Relations [Kay]
- Test Relations [David]
- Input validation for entered Strings (i.e. Attributes) [David]
Mo. Jan-19 2015, 14:00, INF/2078
We met to communicate the current state of the project, especially with the presence of Thomas. The editor has to be finalized as soon as possible which should be discussed with Kay during the next week. Tests according to the editor have to be written, too. The transformation part is going forward as planned. For better building purposes, the project should be transformed to Maven managed projects. This allows a proper building automatization respecting the dependencies.
Goal should be a major finalization of the project implementation itself till end of January (better: Jan-25).
- Finalize editor (David and Kay)
- Finalize transformation (Tobias and Johannes)
- Looking for Maven project transformation possibilities (Thomas)
- When Maven is set up, the Maven support should be enabled in each Eclipse environment in use (all)
Mo. Jan-12 2015, 14:00, INF/2078
We met to talk about the current state of the project. There are no new tasks to assign. Just one remark: The shape related tasks will be fulfilled by Kay now.
Tu. Jan-6 2015, 14:00, INF/2078
We met to give us a brief status report and planned the creation of a time schedule. The schedule will be elaborated until the next meeting based on the end of January as major goal to finalize the project. Ultimate goal will be the end of February as after that date not all team members are available in Dresden anymore for this winter term.
One design decision that has been done by the transformation team: The transformation will be based on the Epsilon-Transformation Framework.
- [Balint] Continue the shape development for the editor
- [Johannes+Tobias] Continue the transformation functionality development
- [David] Continue the relation development for the editor (refactoring, tests)
- [David] Create work plan/schedule for the rest of the project
- [Kay] Create tests for the editor (+ documentation work)
We. Dec-17 2014, 13:30, INF/2078
We met to give us a brief status report. The editor needs further implementation effort, but generally the project including the editor is executable. There are no new task assignments as the work can be continued as usual. The version numbering should be corrected, so that the master branch gets version 1.0 and the develop branch gets version 2.0.
Mo. Dec-8 2014, 14:00, INF/2078
We elaborated a work plan for the next two weeks (as can be seen in the assigned tasks section below) and fixed some project responsibilities as follows.
- Kay - contact person regarding the graphical model
- Johannes - test supervisor
- Tobias - documentation responsibility
- David - project and team structuring
- Team "Editor" (Balint+Kay+David) - responsible to renovate the graphical editor
- Team "Transformation" (Johannes+Tobias) - responsible to develop the transformation algorithm
Furthermore, we decided to communicate more flexible by means of Skype to become more flexible.
- [all] Send Skype user name to David
- [David] Distribute all Skype user names among the team
- [David] Import diagrams into project wiki
- [Johannes+Kay] Finalize the new graphical model and distribute a presentation on this model among the team
- [Balint+Kay+David] Renovate the editor based on the new graphical model
- [Tobias+Johannes] Elaborate a transformation algorithm for getting from a graphical notation to a semantic model
Mo. Dec-01 2014, 14:00, INF/2078
We already decided to separate the graphical model from the semantic model. An open question was, whether the sync between these models should be made instantly (with each change in the graph. model) or on demand (with a single transformation algorithm). We decided to implement the single transformation algorithm.
We want to make sure that there is no manual modification in the generated code.
We identified 4 steps to go through next:
- Create the graphical model (this week)
- Make the Editor run again (apprx. 2 weeks)
- Develop a transformation algorithm (in parallel to step 2, but needs more time)
- Testing, Bug Fixing, Stabilization
- [all] We want to assign task responsibilities to each team member. To do this during the next meeting, everyone should make up his mind about which kind of task would fit to him. And: Think about Ecore model transformation, SWT testing and jUnit testing.
- [Kay+Johannes] are now responsible for the graphical model.
- [David] will generate class diagrams for documentation purposes.
- [Balint+Tobias] will upload the generated JavaDoc and continue the documentation.
Mo. Nov-17 2014, 14:00, INF/2078
We mainly decided today that we will separate the semantic and editor model in our implementation. This leads to consistency issues that shall get resolved by introducing a consistency layer - a bidirectional mapping between the two models.
- [David] Evaluate yED + Doclet in terms of automatic diagram generation out of the existing 1.0 code base
- [Johannes+Kay] Implement the initial Editor Model
- [Tobias+Balint+David] Identify solutions of how to modify the EditParts
Tu. Nov-11 2014, 13:00, INF/2078
We decided to continue developing the existing implementation of FRaMED instead of a complete re-implementation from scratch. This decision may change during the next few weeks, as it is hard to evaluate the efford objectively and correctly and if the changes to be made are overwhelmingly much so that a re-implementation becomes more sensible.
- [Kay] Branching FRaMED to a "development branch" that can be merged to the master later on (just because the branch will consist of errors and the master should be kept stable and executable)
- [Kay] Integration of the new CROM model into FRaMED (which will initially cause errors that should be resolved step by step later on)
- [Team] Update and completion of the documentation of the existing FRaMED implementation, i.e. creating easy to read and understand diagrams for describing the FRaMED structure and behavior.
Mo. Nov-03 2014, 14:50, INF/2078
Mo. Oct-27 2014, 14:50, INF/2078