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
Return project plan by baseline
Sample tasks and methodologies of the area
Effect of the task on the right to modify the attached object
The person responsible for the task
Working procedure – task definition
Objects related to the task pattern
Contacts and directories module (CRM)
Web management and automation
Receiving a message from the web
Human resources
Human Resources module security
Manage department / division data
Synchronizing staff and system users
Products, assets and sales
Received order for goods or services
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 Management
Additional functions with files
Copying and moving files between objects
Files (documents) linked to the object
Formatted texts in the application
Gateway settings for external messages
IMP gateway settings for email communication
Input requirements
The system input requirements overview shows an overview of the requirements that are input to the project, i.e. not derived. These are not necessarily just user requests. If the customer has specific requirements for e.g. the mechanical part of the system, the requirements can be entered directly as mechanical requirements. (Be careful if your methodology allows this.)
How to know the input requirements
Nowhere in the requirement do you fill in whether it is an input or derived requirement. A request is input unless it has a trace/trace binding from another request leading to it. So when you enter a request, it is automatically an input request. As part of the analysis, we recommend creating derived requests directly with the New Derived Request button. Use this button to directly create a derived request (i.e. with a link from the default request).
Want to learn more?
You can read a more complete description about requirements by opening the help in the requirements list. Click on the list and play the help in the window that opens.