Backlog

As with all product developments, not everything we thought about has made it into the current release.

We now have a policy of not re-implementing all features from release to release, where we think features are not used very often. That way, eaTeamWorks might avoid becoming bloatware.

Here are some items on our backlog. Note that this does not represent a commitment to ever implement these features. They are just on our ‘to-do’ list.

They are in no particular order of important, usefulness or difficulty.

eaTeamWorks

eaDocX

1. Changing the UI theme. (Whole eaTeamWorks application)
   EA has this, as do many application with a large UI. The code for this is mostly done, but just didn’t make it into the current release.
2. Document Management. 
   This has been a feature of eaDocX for a long time, but we were never sure how people actually used it. Users who have a need for strict version control and tracking of versions seem to use separate document management systems, so we will wait for feedback before we re-implement DM. It’s also one of the more complicated it of eaDocX, and, if we do re-implement it, it will be made much simpler.
3. Diagram Filters and Scripted formatting.
   These planned for the next eaTeamWorks release.
4. HTML Generator
   Also part of eaDocX for a few years. Also not sure how many people use this. DONE
5. Generating a group of documents
   This was in previous EA versions, but didn’t seem to get used very much
6. Time-triggered document generation.
   Idea here is to have an un-attended EA machine, which is woken-up at a specific time, generates some documents, then goes back to sleep.
   Possibly available in v1.4
7. eaDocX without MS Word. 
   This idea is wafting for new functions in the Telerik framework Rich Text Editor control, to re-implement some bits of MS Word which we absolutely must have, such as hidden text.
   Researched -can’t be done.

Revision Manager

1. Make this into a separate top-level menu, like all other eaTeamWorks apps

eaSheets

1. Better support for containment hierarchies.
   Sheets is mostly about maintaining lists of elements, and connections between elements. It would be good if it also supported parent/child relationships as well.
   Maybe have a new set of (optional) columns, to show the children of the element in each row. Each type of child would have it’s own column, so it behaves the same way as other relationship columns. This will then allow for adding of new children of the correct type (exactly as with a regular connection relationship). What to so about deletion? For a regular related element, ‘delete’ of the text in a cell means deleting the connector. ‘Delete’ in a parent/child cell means….what? Maybe park the ‘deleted’ item somewhere? Certainly NOT a delete of the child element.
2. Add an un-do / redo function.
3. Allow for editing of method parameter lists.

Model Expert

1. When saving the results of a meta-model snapshot, if you have a remote or cloud repository, saving the classes and all their attributes can be quite slow. Maybe we should implement a fast save, when we create an XMI of all the data, then import all of it at the same time.
2. Add another quality check to the list of checks in the dashboard, to check that all the classifiers for all the elements are actually present somewhere in the model. We thought that the EA Project Integrity Checker did this, but it doesn’t.

If you have strong feelings about any of these, please contact support eaTeamworks support.