Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AppGenerator: Update Pool of Available Application Names #6948

Open
TL41 opened this issue Jan 21, 2024 · 4 comments
Open

AppGenerator: Update Pool of Available Application Names #6948

TL41 opened this issue Jan 21, 2024 · 4 comments
Labels
noteworthy probably worth mentioning in release notes task Not directly feature related (i.e. dependency upgrade, docs, etc)

Comments

@TL41
Copy link
Contributor

TL41 commented Jan 21, 2024

Description

Currently, the list of application names used by AppGenerator are a generic list of words. We would like to update this list with a sampling of "generic, real-world" application names relevant to a variety of industries. There is a pool of 590 items today. We can add some prefixes and suffixes to make a longer list (i.e. (Legacy); replace 'System' with 'Software' or 'Application'; add locale like 'Global', 'UK', 'EMEA', etc)

waltz-jobs/src/main/resources/app-names.txt

suggestions (to be expanded):

Core Banking System
Retail Banking System
Corporate Banking System
Private Banking System
Digital Banking Platform
Risk Management Software
Credit Risk Management
Market Risk Management
Operational Risk Management
Compliance Risk Management
Cyber Risk Management
Anti-Money Laundering (AML) Software
Transaction Monitoring System
Customer Due Diligence (CDD) System
Watchlist Screening System
KYC (Know Your Customer) System
AML Analytics Platform

Resourcing

We intend to contribute this feature

@davidwatkins73
Copy link
Member

davidwatkins73 commented Jan 28, 2024

I've played around a bit with chatgpt to create some semi-realistic data sets.
Currently it's generating sample data for

  • capabilities
  • org units
  • data types
  • apps (linked to orgs)
  • ratings between apps and capabilities
  • flows between apps
  • data types on the flows

Its not perfect by any means, but it looks promising.
The chat transcipt is here: https://chat.openai.com/share/24883a64-920a-4211-a3f0-d145761de640

I've written a cheap n' cheerful loader that will be checked in on a branch on my clone (davidwatkins73/waltz-dev).
The programme to load the data is DemoDataLoader - however it will destroy all data currently in the database when it runs.

Example:
image

Ideas for enhancements:

  • add primary ratings (can just randomly select one mearuable rating per app)
  • add servers / technology (can re-use exsiting sample data loaders)
  • add people (can re-use existing sample data loader)
  • add assessments (may need something a bit more custom to be realistic)
    • be nice if these could be set in the spreadsheet, name and options with a frequency distribution for the options
  • add stats (DORA stats may be a good one)
    • as above, seee if we can define some in the spreadsheet with a ranges, oucomes and distributions

davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Jan 28, 2024
@davidwatkins73 davidwatkins73 added noteworthy probably worth mentioning in release notes task Not directly feature related (i.e. dependency upgrade, docs, etc) labels Jan 28, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Jan 29, 2024
@TL41
Copy link
Contributor Author

TL41 commented Feb 1, 2024

thanks for pulling this together! This is a great idea to get a full set of demo data.

We've also made a list of sample application data we can share, even if it serves as a short term update to app-names.txt and then we tackle the bigger bucket of work you've detailed above

Let us know if that's something we should contribute now or hold off as part of a bigger revamp

@davidwatkins73
Copy link
Member

davidwatkins73 commented Feb 1, 2024

Take a look at the list off apps in the xlsx which is part of the (draft) PR : #6971

I was thinking we could expand this xlsx (or split it) to contain a curated set of test data, then let the old data generation harnesses fill in the blanks (people, servers, databases etc).

It's self contained in the waltz-jobs sub project for now. Perhaps we should create a more specfic sub project for demo data where we can also collect other material useful for 'advertising' Waltz ?

Either way, its certainly something we could collaborate over. Ultimately people could tweak the data in the xlsx to skew to their specific demo needs.

@TL41
Copy link
Contributor Author

TL41 commented Feb 1, 2024

here's some additional applications, grouped together

Additional Application Names.xlsx

some may be similar to what you have already, but for demo purposes I think it's ok

davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Mar 17, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Mar 17, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Mar 17, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 7, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 7, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 7, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 7, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 7, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 7, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 7, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 7, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 14, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 14, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 14, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 14, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 14, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue Apr 14, 2024
davidwatkins73 added a commit to davidwatkins73/waltz-dev that referenced this issue May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
noteworthy probably worth mentioning in release notes task Not directly feature related (i.e. dependency upgrade, docs, etc)
Projects
None yet
Development

No branches or pull requests

2 participants