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
Customer Service Response Generation
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
More about how the system works
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
Risk Pattern
The purpose of model risks is to facilitate the creation of risks for projects and activities.
The model risks can be used to describe common risks or even exceptional risks. In the case of exceptional risks, their inclusion in the methodology is particularly useful to ensure that their possible occurrence is not forgotten, even if they do not occur frequently.
Description of the sample risk
A sample risk has the same description as a project or area risk. The probability and threat classification can be filled in for the sample risk – these values also serve as a sample and can be adjusted within the project to suit the situation.
Risk description
For sample risks, a description should also be included to make the risk easier to evaluate. The description should include guidance for assessing whether or not the risk is relevant to a particular project.
The detail of the description depends on the experience of the people who will be evaluating the risks in the projects. It is therefore not possible to make a general recommendation on the level of detail to which risks should be analysed.
Methodological note
The sample risks are a fulfilment of the requirement of standards that require the definition of common risks as part of process assets (e.g. ASPICE, ISO 26262, ISO 270000 but also others).