AyMINE – Technical documentation
User Modules
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
Region / project / methodology
Change management process in a project
Qualification of user or contact
Right to Manage Qualifications
Methodology and Quality Management systems
What a methodology / QMS consists of
Objects affected by the problem
Sample tasks and methodologies of the area
Effect of the task on the right to modify the attached object
Objects related to the task pattern
Contacts and directories module (CRM)
Address book or people and companies
Web management and automation
Receiving a message from the web
Human resources
Asset management module
Technical Modules
Sabre plugin module
Enterprise Architect connector
Database link to Enterprise Architect database
System Modules
The AyMINE framework module
Configure how your system looks and works
Gestures and keyboard shortcuts
How the system works and how it protects data
Private notes and tags for objects
Filtering in the list of records
System services
Additional functions with files
Copying and moving files between objects
Relatios between objects
Relatios are used to document user-defined relations between object. They do not supply or alter regular relations, but allow deep documentation of the real world.
What to related
Relatios are typically used in accordance to the internal methodology. Methodology is important because without that relatios and espcially information stored in the relations easily confuse other users that might not understand relation or not foung information hidden in unexpected field – relation description.
In a nutshell: use relation in scope an in purpose that is ashared among users.
Relation documentation
Relations are always beteen two object and cannot exists without that.
Except object, relations should have name, to make clear, why they are there. Other feilds are optional.
Name You can put whatever name you want. Nevertheless – for better clarity it is important to use the same name for relation type everywhere. That's why you can set name from pre-defined list. If list does not fit your needs, contact your administration. It is easy to update the list, when it makes sense.
Version Version is used in case that you have updates of model like releases, change analysi etc. It allows prepare new version and change old and new versoin after analysis and decision about the change.
Lock
Lock allow lock the relations and prevents delete. You shall unlock relations before delete.