Business Use Scenarios
mConsole
ID | Scenario | Description | Data Assets Involved |
|---|---|---|---|
US_01 | Log into mConsole | The user is able to log into mConsole. |
|
US_02 | Change account password | The user is able to change their account password. | User account data |
US_03 | Update company information | The user is able to update their company information. | Company information data |
US_04 | Add user to customer account | The user is able to add new users to their customer account. | Customer info |
US_05 | Remove user from customer account | The user is able to remove users from their customer account. | Customer info |
US_06 | Manage user permissions | The user is able to change permissions for users in their customer account. |
|
US_07 | Manage encryption keys | The user is able to generate keys for mMC output encryption. | Customer private keys |
US_08 | Edit scores | The user is able to add, remove, or edit complexity scores. | Complexity score data |
US_09 | Edit collected size metrics | The user is able to manually edit metrics collected from databases (currently supported for PostgreSQL, MySQL, and Oracle). | Customer database metadata |
US_10 | View Demo dashboard | The user is able to observe migVisor capabilities using the Demo account. | migVisor sample database metadata |
US_11 | Download mMC | The user is able to download mMC. | Customer metadata collector archive |
US_12 | Remove user metadata | The user is able to remove uploaded databases. | Customer database metadata |
US_13 | Upload database metadata | The user is able to upload their scanned database metadata. | Customer database metadata |
US_14 | Download database metadata | The user is able to download their scanned database metadata. | Customer database metadata |
US_15 | Remove database metadata | The user is able to delete their uploaded database metadata from the account. | Customer database metadata |
US_16 | View uploaded database scan results | The user is able to view detailed results of scanned databases, including general details, workload, and sizing metrics. | Customer database metadata |
US_17 | Manage features for databases | The user is able to exclude or include features for databases. | Customer database feature metadata |
US_18 | Manage features for schemas | The user is able to exclude or include features for schemas. | Customer database schema feature metadata |
US_19 | Manage schemas for databases | The user is able to exclude or include schemas for databases. | Customer database schema metadata |
US_20 | Manage tags for databases | The user is able to assign or remove tags for databases to optimize search and database management. | Customer database metadata |
US_21 | View migration insights | The user is able to view migration insights for uploaded databases. | Customer database metadata |
US_22 | Generate technical reports
| The user is able to generate database reports. | Customer database metadata |
US_23 | Generate statistical reports
| The user is able to generate vendor-wide statistical reports. | Customer database metadata |
US_24 | Generate executive deck | The user is able to generate a specialized presentation report. | Customer database metadata |
US_25 | Select targets for complexity calculation | The user is able to choose various targets for uploaded databases for complexity calculation. |
|
US_26 | Configure focus period | The user is able to set the focus period for uploaded databases (currently supported for Oracle). |
|
US_27 | Select algorithms for target sizing metrics | The user is able to choose algorithms for calculating key target sizing metrics (currently supported for Oracle and SQL Server). | Customer database metadata |
US_28 | Declare application | The user is able to manually declare application details. | Customer application metadata |
US_29 | Upload application metadata | The user is able to upload their scanned application metadata. | Customer application metadata |
US_30 | Download application metadata | The user is able to download their scanned application metadata. | Customer application metadata |
US_31 | Remove application metadata | The user is able to delete their uploaded application metadata from the account. | Customer application metadata |
US_32 | View uploaded application scan results | The user is able to view detailed results of scanned applications, including general details and features. | Customer application metadata |
US_33 | Manage features for applications | The user is able to exclude or include features for applications. | Customer application feature metadata |
US_34 | Manage tags for applications | The user is able to assign or remove tags for applications to optimize search and application management. | Customer database metadata |
US_35 | Edit application | The user is able to manually edit scanned application data. | Customer application metadata |
US_36 | Select targets for complexity calculation | The user is able to choose various targets for uploaded applications for complexity calculation. |
|
US_37 | Create TCO projects | The user is able to create projects in TCO and view their summary and calculations. |
|
US_38 | Create cloud instances in TCO | The user is able to create cloud instances in TCO with calculated cloud costs based on the selected target platform. |
|
US_39 | Create instance groups in TCO | The user is able to create instance groups in the scope of a TCO project. |
|
US_40 | Choose database projected pathway in TCO | The user is able to select the sources that will or will not be migrated. |
|
US_41 | Manage TCO questionnaire data | The user is able to update questionnaire data for future costs calculation in TCO. | Customer TCO questionnaire data |
mMC
ID | Scenario | Description | Data Assets Involved |
|---|---|---|---|
US_01 | Log into mMC | The user is able to log into mMC. |
|
US_02 | Manage encryption keys | The user is able to update keys for mMC output encryption. | Customer private keys |
US_03 | Scan all or selected databases in an instance | The user is able to scan all or selected databases in an instance (currently supported for SQL Server, PostgreSQL, and MySQL). | Customer database metadata |
US_04 | Scan databases | The user is able to scan their databases to collect metadata. | Customer database metadata |
US_05 | Configure collection period | The user is able to set the collection period for database scanning (currently supported for Oracle). | Customer metadata collector settings |
US_06 | Archive databases configurations | The user is able to archive databases configurations to re-scan them later. | Customer database metadata |
US_07 | Import databases | The user is able to import databases from a configuration file for subsequent scanning. |
|
US_08 | Download configuration file | The user is able to download a configuration file with added databases. | Configuration file data |
US_09 | Scan applications | The user is able to scan applications to collect metadata. | Customer application metadata |
US_10 | Archive applications configurations | The user is able to archive applications configurations to re-scan them later. | Customer application metadata |
US_11 | Import applications | The user is able to import applications from a configuration file for subsequent scanning. |
|
US_12 | Download configuration file | The user is able to download a configuration file with added applications. | Configuration file data |