This project is read-only.


0001 Database Capability (Phase 1) - 04 Determine a list of needed events for AbstraXProviderExtension to handle


·         Research MVVM Tree to determine list.  Submit for review.  (MVVMTreeView handles real events and forwards to classes that implement ITreeView via methods.
Related requirements:
• Provided by AbstraX Provider.
  1. The Base AbstraXProvider will provide a shared interface that must be implemented by all AbstraX Extensions.
  2. The EntityProvider will have a shared class (i.e. EntityProviderExtension.shared.cs) that will provide functionality to the front-end.
  3. The Base AbstraXProvider will provide the definition of an Attribute that will be acquired by the Silverlight front-end code generator (AbstraXGenerator) to instantiate and provide an instance of the extension.
  4. A method will be added to the IBase server and client interfaces for returning an extension.
  5. The EntityProvider back-end Entities will be refactored to provide the interface method
  6. The back-end implementation of the interface method will be decorated with the Attribute as described above and will return null by default.
  7. The AbstraXGenerator will read the Attribute from this method to instantiate and return the AbstraXExtension via a Unity IoC container.
    • Provides custom menu items
  8. The AbstraXProvider Extension will provide all custom menu items.
    • Handles Tree View events.
  9. The Base AbstraXProvider tree view node classes will query each internal node for an AbstraX Extension interface.
  10. The Base AbstraXProvider tree view node classes forward all necessary fired events to the extension.
    • Handles Tree View events - Create New
  11. AbstraX Provider extension will handle the following events:
    o Delete
    o Rename
    o Drag & Drop Copy & Paste (out-of-scope)
    o Greater than keyboard event.
    o “Shift-N” keystrokes to create a new node by default.
    • Provides User Interface for schema changes.
  12. AbstraX Provider extension will provide all necessary front-end user interfaces.
  13. All front-end user interfaces will conform to the MVVM design pattern.
    • Can be swapped out.
  14. AbstraX Provider extension as provided by the Unity IoC container will allow for unit testing of both the extension itself as well as the Base AbstraX Provider front-end tree nodes.
    Reproduction Steps
  15. Open the file "Abstrax provider extension events.doc" which is attached to this work item.
  16. Each method listed will represent an action in the project and will be followed by parenthesis. Example: MyNewMethod()
  17. Review each method to determine if:
    -The method is part of the requirements documents.
    -The method is within the scope of the project.
    -The method is implemented in the project.
    NOTE: Some of the methods in the list are grouped together in a particular way, but may not be grouped this way in the implementation.

file attachments


dezrtluver wrote Sep 21, 2012 at 3:03 AM

No Repro steps.

wrote Sep 21, 2012 at 3:56 AM

wrote Sep 21, 2012 at 3:57 AM

wrote Sep 21, 2012 at 4:00 AM

wrote Sep 25, 2012 at 2:38 AM

bowser4848 wrote Sep 25, 2012 at 2:39 AM

Added Repro steps.

shravya wrote Sep 29, 2012 at 10:03 PM

The method Change Multiplicity() is not listed under navigation property

shravya wrote Oct 22, 2012 at 11:46 PM

All methods are defined and this test case works

wrote Feb 13, 2013 at 11:51 PM

wrote May 16, 2013 at 10:30 AM

wrote May 16, 2013 at 10:30 AM

wrote Jun 14, 2013 at 7:53 AM