Re: Workbench

a orth <pwht@...>

Exactly, and agile will help us get there.


From: Ian C <ian@...>
Sent: Saturday, February 20, 2021 12:58 AM
To: a orth <pwht@...>
Subject: Re: [GeneraERS] Workbench


Hi Andrea,

Looks like email came to just me.


And re agile, or any process for that matter, will not work unless we have a clear idea/definition of where we are headed.



Ian C



On Sat, Feb 20, 2021 at 2:49 PM a orth <pwht@...> wrote:

So the scrum master hat is on. And I admit if you haven't worked under agile, it may not be clear. It's also easier to takea reflective look at things sometimes via email


First, a consideration are the outcomes of what we want to achieve which, in this case, is the workbench but would apply to PE, documentation,etc


When I say outcomes, it's not technology being referencd because that's a solution. Just off the top off my head, we want to allow for flexible front ends. How do we efficiently get there? Not buy making big bang architectural decisions.


Instead, we decide what our outcomes are (this would be easier to visualize and determine with what is called a product canvas).


Then we decide what are Most Valuable Prototype (MVP). The MVP is what bit of coding will help us determine if we are headed to a solution that meets are outcomes.


I'm a little uneasy, and I'm quilty of it, of going straight to a technology solution and I'm a bit concerned we're waterfalling, when you really can't make waterfall work for greenfield work and when work is done in bits outside of most contributors day jobs

From: genevaers-discussion@... <genevaers-discussion@...> on behalf of Ian C <ian@...>
Sent: Friday, February 19, 2021 2:37:53 AM
To: genevaers-discussion@... <genevaers-discussion@...>
Subject: [GeneraERS] Workbench


Hi All,


reviewing an issue re management of passwords led me to think about the workbench in a more general sense.


We currently do not manage our passwords in a way that will comply with the CII best practices.

We keep that passwords locally in a less than acceptable encrypted form.


I partially understand how to fix the issue.


But let's stand back and think about what the workbench is and where we want to go with it.

It is a temporary beast. We want to move to a language based approach.


As a step towards that I propose we think of the workbench as an editor. Nothing more.

An editor that produces say WB XML files. That can then be processed on the mainframe to generate the run control files and run the performance engine.


As such I think we should remove any password storage from the workbench system.

The database behind the workbench should be thought of as nothing more than a clever scratch pad.

It remembers stuff.


Similarly the business of logging into the workbench is not really needed. The whole user account and management of internal permissions is pretty pointless.

Simple connect to the database and a given environment. Do what you want and export the xml.

It can then be stored in source control and re imported at a later date.


Share an environment with others. But treat the workbench just as an editor.

Agree how you are going to work together. Do not rely on the tool to sort it for you.


Or maybe just use a local database.... that is then much more like an editor?


This will greatly simplify it and the need for management of accounts etc,

All we need is to provide a login screen that makes a connection to the database and takes you to the desired environment.


What about someone accidently deleting things?  Yep, a valid concern. Open to suggestions on that one.

If whatever is stored in a source control system then it can be restored.


Reply to the group with comments etc. And we can maybe discuss in our coming meetings.

Though I think things like this should be sorted outside of a meeting and merely confirmed in the meeting.


Looking forward to hearing from you. We need to figure out what we are going to do pretty soon.



Ian C

Join to automatically receive all group messages.