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
Recorded activities
The protocol is always based on an activity, and the purpose of the protocol is to document the findings of that activity. The activity should therefore be attached to the protocol to make it easy to trace.
Activities, not objects, can be attached to the protocol. It is therefore possible to create the protocol for a task, but not, for example, for a test. The test is a document – a guide to how to test, but the testing itself is based on an activity. For the same reason, the protocol never refers to a person, but always to the activities he or she performs or the areas for which he or she is responsible.
Protocols that arise in projects always refer to the activities in a given project or area; the protocol should never be attached to a task from another project.
Protocols from activities performed at the level of the organization take place within the area of controlling or quality control. Typically, they also refer to objects that do not belong to controlling (the department does not primarily control itself in this way). For example, it may be related to a project that is not directly related to controlling within the organizational links.