Category Archives: All

Information that is interest to all visitors – typically it will be of a general nature and not hold too many gems of knowledge

eaForms – a few new features that make my life easier

We have just released a new version of eaForms which, apart from a few maintenance items, has added 2 functions that I wanted to make my life a little easier, and hence I think could be of use to you.

The first relates to the use of the Genfile element field and the element linked files collection. The Genfile field is mainly used in class elements to store the source file which is linked to the class for example through a code import or code generation.  When you press F12  the filename in this field is used to select the file that is opened in an editor window.

Whereas the linked files is an element collection that can contain details of local files and web addresses.  Although we should aim to keep as much stuff as possible in the model this isn’t possible for all items, so having a reference that we can use to access the relevant item is useful.  So for these “file references” we have added the ability, within eaForms, to double click on the item whether it be a textbox containing the Genfile field or a listview of linked files, and using either the default windows associated program or an application configured in settings open the file (this can also be used to execute files if required). You can also use the context menu for textbox items as shown in the screenshot below.

Open file specified in Genfile from context menu

Open file specified in Genfile from context menu

The great thing is the ability to use a stereotyped element e.g. which contains details of the item plus the relevant filename so that you can directly open the file from within EA.

The second addition is really an experiment based on our observations of the increasing use of scripts.  We have added action buttons that will execute scripts either to

  • Save the element and then run a script
  • Run a script, and conditionally, on the result of the script, save the element or leave the form open

Furthermore, to avoid the risk that the script may not be available to the user we have embedded the script within the eaForm definition, and importantly it is the form designer who is responsible for checking it out!  As with any script related operations the uses are possibly myriad, although there are some restrictions.

Now, although these features only save seconds they can enhance the user experience or it may ensure important checks are made without the user needing to think.

If you’re new to eaForms then go to EA Workplace to download a copy to try

Do you have seemingly simple tasks you perform repeatedly that could be included as an eaForm capability?  Let us know what you need.

Adrian

Advertisements

Your use of EA – feedback from survey

Thank you to all those who have taken the time to complete my survey.

I have now closed the survey (see my previous post) which was completed by nearly 20 people.  To some extent the level of response is no surprise as anybody looking at the forums and blogs will tend to see the same interested people.  I had hoped to get a few more to improve the statistical integrity but trust it will paint a useful, if rough picture.  In this post when I’ve added my own comments I put them in italics, so hopefully they are clear.

I found the results have been very interesting and personally I was surprised to see how much use was made of EA other than want I tend to call the front end stuff – “requirements and modelling”.  If we start by looking at the roles of the respondants, we do it is skewed towards the front end with no users who I would describe in the more downstream roles, although that may only be a reflection of their job name rather than their true role.  I guess there are many “Jack of all trades

Respondants roles

Respondants roles

Then we looked at use of EA within the organisation.

Use of EA within our team and organisation

Use of EA within our team and organisation

What we see is that it is usually more than a single person using EA and where used, its use is moderate.  My interpretation is that in those organisations who have committed to use EA, we see some use beyond the team although this is not the case for all and it is purely just for the team.

When we look at the key deliverables, this started to surprise me as not only did it include those expected:

  • Requirements
  • Business and functional analysis
  • Architecture
  • Designs
  • Reporting  – both HTML and Word

But some interesting items that implied serious technical use downstream

  • Database design
  • Desktop applications
  • Embedded software

When we look at our level of EA expertise we see that it is higher than those within their teams and organisation.  No surpise as I guess those reading the blogs and seeing this survery are those most interested EA.

EA Expertise

EA Expertise

Now the survey gets in a more specific.  The next question related to learning EA and getting information.

How do we learn about EA?

How do we learn about EA?

The responses were interesting in that indicate that stuff is OK, but from the comments there is clearly scope for improvement.  One problem I see is that EA is big, really big, and it’s potential use is so great it is a hard nut to crack.  To gain valuable use of EA requires either true committment from one or more users in a team, or well designed training and guidance – or probably both.    The comments also highlighted a lack of resources.  I know if you look around the forums it is the same few individuals (probably you) who contribute (which I trust you enjoy doing!). In fact, EXploringEA probably wouldn’t exist if EA was well documented with tutorials, examples, and other readily available training material covering all topics of potential interest.

When we look at the most important features  of EA we see that at the top of the list are the front end stuff reflecting the roles of the respondants.

Most important feature

Most important feature

Then if we look at allthe features that are used.

Use of EA features

Use of EA features

If we look at those areas that are only sometimes or never used we would start to take out:

  • Team management tools
  • Model simulation
  • Execution analyser
  • QA
  • Maintenance

Now if this was a true reflection of EA usage it would be a concern.  The ability to have a single repository of information throughout the project, tracking from the requirements and design to the implementation and testing is highly desirable.  Furthermore, having accurate information downstream to support ongoing maintenance is essential.  I can only guess that a some stage of the project information is moved to other tools which are then used moving forward to support the product during it’s lifecycle – let’s hope!

What I can gather from comments is that there are some really useful features of EA.  There were comments for most areas, especially those in the areas where there is not a high use. Here is a subset:

  • Database – “Great for quick re-engineering “
  • Automation  – – “deploying and operating something in addition to EA is something they usually do not want.” Reflecting the challenge associated with using AddIns.
  • Project management – “I think it can be a good alternative to never-updated projects created in Microsoft Project, but its UI is too technical for the minds of PMs, and therefore may never gain popularity”.    No surpise that PM’s don’t want to change.  I developed an EA addin for MS Project but found that project managers weren’t really interested in using EA, so a I then produced an addIn for MS Project that accesses EA but still not much interest.  If I was in their shoes why would I change, what more am can I gain. One further point is that the project management capabilities within EA look great for managing say a development team but do not cater for the broader business project management, planning and reporting; nor should they!
  • Team management – “I haven’t or hardly found any well-developed use case and user story scenarios models at my clients. Because of this, testing features are of no value for them, until they understand why an up-to-date model with detailed requirements and scenarios are important” Interesting in that I think a lack of real detailed examples really is a limiter.  If there were real world examples which were well crafted and could be mapped to current working practices it would be great.  I guess that the problem here is that this would be valuable intellectual property and hence nobody is able to provided… Anybody have ideas on what could be done?
  • Maintenance – “Roadmapping works well. Trick is to have as-is and to be changes at the start end end of change dependency diagram.” It was great to see this comment as it really implies somebody is doing the right thing and managing the work from requirements to deployment and ongoing maintenance.

What is missing from EA?

The comments included:

  • Better Excel support – I will start with this as I have a personal investment in eaXL and see that this can do a lot – perhaps we haven’t communicated enough detail (!), so let us know what is needed and you never known.  And, now Sparx have their own Excel tools.
  • Intergration with other tools – notably publishing tools to make information available to a wider audience.  Although HTML is available organisations how their own preferred tools.
  • “Stop changing the UI in every release”
  • “A streamlined report/template editing facility, which enables manual editing, with a great UI, such as those you can find in visual query builders.”

Final feedback

I think I can summarise a sense of the feedback from one of the final comments:

“Great tool – but I think it tries to expand its scope too much”

Also in trying to do so much “some features need to be sharpened” – which apparently comes from a domain expert indicating that in adding some features they were not accurate in meeting the real need.

So there we have it.  For me, I’ve had some interesting reading which has generated some ideas for furture exploring and posts.  In the meantime, I’d like to thank those who took the time to contribute to the survey, and trust that you find this feedback useful.

Adrian

 

 

Let me know about your use of EA

In EXploringEA I’m always keen to look into stuff that may be useful.  I have a view that there is so much in EA that I really don’t know about or fully understand (and this could be the same for you).  Of course, it is difficult to document such a powerful tool in a way that makes the product fully accessible to all (I have some ideas, but not the mandate or resource!). I know I’ve suffered many times from some small detail being missed, or inferred from a previous topic that I may have skipped, in my eagerness to play and subsequently spend hours trying to get something working!

There is plenty to discover, for example from the various forums, however there must be people out there doing some interesting stuff that is never reported and could go well beyond my expectations. Of course, the problem for anybody,especially under time pressures, is getting to know about stuff that may be useful to them when it is needed.

Having focused on scripting for a few months (not finished as I’m still exploring a few areas) I’ve been thinking about some other areas that I don’t fully understand, with a view to putting together some experiments to look into more stuff that I hope is potentially useful. I have my candidates list but, following a couple of recent posts I’ve had some useful feedback which has pointed me into some interesting, but not conclusive, directions.

In thinking about some of the areas to explore I get a sense that I am missing something.  Much of my experience of using EA has been with the front end tasks – requirements capture, modelling, analysis and design; if I look at user guide I’ve not even  got half way through!

So I am curious to get a fuller understanding of what and how EA is really used.  And, with this in mind, there is no better way than to ask you, EA users.  So my idea is to conduct a short survey, where you can help let me know how you use EA, what you think it does well, and probably most importantly areas that you would expect it to do better.

I’ve tried to make it easy with tick boxes.  I am not asking for detail,  but have provided space if you wish to add any comments that you think would highlight the value or issues with EA, so that I can just get a better understanding of what is being achieved with EA – what it does as doesn’t do this could be a help to me and others.

This anonymous survey is now available at How to use EA survey.   I’ll leave it there for about a few weeks, to give an opportunity to as many as possible.  Then I’ll consolidate the data and share a summary of the result in a future post, so you can see what our little world is doing with this great tool.

I am sorry that I cannot offer any incentives other than I will share a summary of the results in a future post, and the hope that I will continue to post information that may be useful to somebody.

And, of course, hopefully be inspired by you to explore other areas and application of EA.

Thanks for your help.

Adrian

What are the hot EA topics?

I’m taking a few weeks off, so I’m in holiday mode enjoying the sun and reducing my time in a dark room of computers, but although I won’t be doing many experiments I had it in mind that one job I should do is to review my list of candidate experiments ready for me return.

Every time I look at my list (infrequently), I get a sense that there is so much in EA and however much I explore there will always be more.  I guess this is no surprise as the tool evolves to meet users needs faster than I can explore, so my candidate list is just a guide to some of the areas I could explore when I next get idle.

Hot topics

I would guess that there are 3 hot topics:

  • Scripting _ If I look back over the last 6 months I’ve spend at lot of time looking at scripting. And judging by what seems to me an increasing number of queries on scripting on the Sparx automation forum I guess this could be considered a hot topic.
  • AddIns – There continues to be a steady stream of issues with AddIns and from the questions raised indicate more people are developing their own AddIns (my advert – we can help with AddIn developments!) as well as more being added to Sparx own list.
  • Documentation and reporting –  I have noted an increasing number of questions relating to producing documentation/reports in a variety of formats.

How accurate my observations is unclear so I may have missed a major topic; it would be interesting if there were statistics available (Sparx are there?).  What do you think I have missed?

Some of the topics that I don’t see much (or I’ve just missed) that were on my list are:

  • Application development
  • Model transformations

Perhaps that’s because those using fully understand.

What else for my list?

In starting to review my candidate list what came to mind was a post on the Sparx forum on testing AddIns last week.  It prompted me to think about what we use EA for?

We know that EA could be used throughout the development cycle whether modelling, analysis, design, coding, testing and maintenance. (I could possibly add project management but I guess that this will be a small number of users, not least based on the level of interest we have received for our MS Project and TeamPulse AddIns!)

From my experience the majority of users fall into the first 3 categories – modelling, analysis and design.  I think this observation is further supported by the topics covered at EA user Group meetings I have attended. Yes, there are a few well documented exceptions such as embedded code development but not much else.

Does this mean that like other tools I can think of such as Microsoft Word, EA is positioned by a few key features, and even though it continues to evolve the major use remains the same.  If we think about Word most users only use a small number of the product features; there are power users who can demonstrate some amazing stuff that can be done, however this requires awareness and knowledge of how to perform the task, and all too often users don’t go looking. It was this thinking that was part of the reasoning behind EXploringEA, the opportunity to go where others have not gone before…

So are there parts of EA that we are failing to use that could make our developments easier? better? quicker? cleaner? more maintainable? ….

It was the post on testing AddIns that reminded me that one of my goals with EXploringEA was to be able to fully understand the viability of managing the whole software lifecycle from product concept to its ongoing maintenance within EA. I had a vision that one tool containing the “knowledge” would help the overall process and its management.

Yes, there will be a need to call other tools – compilers, linkers, database tools, documentation tools … but no major distraction and if EA could truly be the kingpin to manage our world, would our developments be better?  or am I just trying to push all into a “box” which is just not the right size for the problem in hand?  And if there are too many other tools with which we need to interact are we just complicating the process?

So is my desire to manage and orchestrate the development in a clear and clean way getting in the way of a realistic development process? I hold my hand up and say I don’t use EA for the majority of my coding but somehow wish I could, and maintenance that’s another story.

So imagine that EA were the primary tool for our developments, with a few associated specialist programmes to do the detail, how would each of us feel whether we be business analysts, project managers, developers, coders, testers, supporters?

This approach raises a lot of issues, but for the moment here are a few questions:

  • Is EA only suitable for the modelling, analysis, design?
    • Is it sufficient and able to perform these tasks?
    • Is it viable to use EA in other areas such coding, testing, maintenance and if so what reliance is there on other tools? (Just seen the draft agenda for the EA User group meeting in London – with a talk on using EA for Full Project Lifecycle,  which could shed some more light on this)
    • Can we use it to produce all the documentation that we need, not only for our up front design activities but documents that meet the needs of testers, supporters and maintainers?
  • In  what areas are there are good case studies? (I need to look out for some, and if you have one let me know if I can add a link to it to help others?)
  • What additional tools are needed to support general purpose windows development?
  • And always – what questions should I be asking and I haven’t?

I also mustn’t forget to ask again – what are the hot EA topics?

I hope that is thought provoking – it has got me thinking – but then with the sun on the terrace …

I’ll be back soon.

Adrian

 

 

eaForms – is there a need for a simple EA client to help get people on board?

You may have seen, if you’ve reviewed information about our eaForms product, that one of the key reasons for the AddIn was to help overcome some of the issues we have experienced when trying to get people to use EA.  We have found that there are a set of people that I refer to as “reluctant users”, and from whom you may want them to contribute to the project by:

  • Providing Information – adding new packages/elements
  • Reviewing, editing or generally providing feedback
  • Approving items in the project

Needless to say, some of these people are just not be interested, whilst some may be willing to provide this information in a document or spreadsheet.  The former is the biggest challenge whilst the second will involve potentially time consuming, error prone work in harvesting the required content. Furthermore, if I’m the person doing the work, and not gaining any real insights into the project, I really don’t feel it’s good use of my time.  Yes there are tools to help (here’s a plug for eaDocX – it can readily import information from Excel; I wrote the Excel part following years of using VBA to get Excel content into EA – and it really does help!), but although a great help wouldn’t it be better if the creator of the information was able to work directly with EA?

When trying to introduce EA into a project I am sure we have all witnessed a mixed range of responses from those who:

  • see it, understand what EA offers and just can’t wait to get started

to those who:

  • aren’t interested, don’t understand why “another tool” and certainly don’t want to have to learn a new tool, and don’t have the time and will find any excuse to avoid meetings/trainings – the worst of the “reluctant users”. And unless remaining in their job depends explicitly on using EA they won’t, and it’s yours truly who will be picking up the pieces to ensure the completeness of the project.

So with eaForms we aim to help by reducing the perceived complexity of using EA, making it easier for users to get on board by reducing barriers to entry, and importantly, with the help of the local project experts, ensure that the editing forms meet the specific needs for the project and its users.

For an example Use Case form we only included the information our BA required using simple controls to help with the data input.  Also in hiding tagged values and using dropdown lists to limit input values to a pre-defined list we made it clearer what information was needed and any choice restrictions that should be applied.

eaForms AddIn Use Case form for our Business Analyst

eaForms AddIn Use Case form for our Business Analyst

We were thinking about our reluctant user’s and wondered whether it was possible to use the same form definitions we create with eaForms, but instead of within an AddIn use them within a simple standalone client that would.  In taking this approach, we could remove the need for the user to open EA and potentially, further reduce the barriers to using EA.

To test the idea we have produced a simple prototype client (illustrated below), with minimal menu options; we only offer – open and close an EA project, edit an existing element selected from a project browser and add/delete elements using editing forms defined to meet your project needs.

eaForms prototype client with same Use Case form

eaForms prototype client with same Use Case form

Using this client the user sees a much simplified interface and no longer needs to open EA and potential be confused or intimidated by the great range of options.  Remember our aim is to get users on-board quickly, so we hope that our eaForms client will provide either the new or reluctant user with a means to be included directly in the project work within minutes.  To be clear this is not a substitute for most EA users and is certainly not a powerful feature rich client but provides a simple means to capture important information into our EA projects without the existing EA users having to convert documents (Yippee!).

With the flexibility of eaForms the element editing forms can be tailored to meet users needs by project users.  They may include simple or complex controls, richer “gadgets” and action buttons to perform project specific task plus the ability to drive consistency of data input through value selection rather than free data text.

NB: Before I continue, there will be many, including myself, who feel users need to overcome their resistance to learning some UML and get to grips with EA.  But as we all know we don’t live in an ideal world, and have to adapt. So if our client provides a means to ensure that those that should be involved with our projects are, then we must surely increase the likelihood that we will have better projects.

Now it is my turn to ask you a question. We have a very small sample set of customers and hence we are interested your views. As a reader of this post it is more than likely that you are a committed EA user, so no need for this client, you are not the target audience (although eaForms may be of interest), however you may work with people that you would like to be users.

  • Who are they? What are their roles?  What tools do they use when they should be using EA?
  • What would they need for a tool?
  • Would providing them with a simpler client help them better understand the value of EA and hopefully lead them down the path to becoming a real committed EA user? Would having a simple client help you, if only to reduce all the harvesting that you may have to do!
  • Does the concept of a simple client make sense?

These are just some of the questions we are asking ourselves, there are many more we should probably be looking at and with that in mind are keen to get your feedback on this idea.  Please add a comment to this post or send us an email at eaforms(at)exploringea.co.uk

I look forward to hearing from you.

Many thanks

Adrian

 

eaForms – using lists to access element and related information

Each EA element has a range of collections which contains information about the element or related “things”.  Just a quick look and you will see a range of collections associated with each element, for example:

  • Attributes
  • Methods
  • Connectors
  • Diagrams
  • Elements
  • EmbeddedElements
  • Requirements
  • TaggedValues
  • Files
  • Metrics
  • Realizes
  • Resources
  • Efforts
  • Risks
  • Issues
  • Tests

Depending on your role and/or stage in a project you may be interested in some or none of these bits of information.  But as a collection of relevant information it can be useful to have a view of them during your work.  To access most of these items with EA you will often need to make a menu selection.   However, as we may use some of them frequently wouldn’t it be useful if we could see them without this need for additional user input.  When developing eaForms it was our view that having visibility of the required information at the same time would be useful when adding or editing elements;   the ability to see the information at a glance plus the ability to add a new item using an action button was our vision.

So with eaForms we have provided a list control whose data source can be set to display a wide range of collections.  Furthermore, within these lists we have added the ability to select and open the related item for example with Use Cases (Actors, Pre/Post conditions), Classes(Attributes and operations) as well as requirements and other related items for which we can interpret the target item (at present we have added what we see as the useful stuff).  This allows the user to work within the context of the current opened element to view and edit the related information.

As an example, let us start with a look at a simple requirements form were we have included a list of linked items:

Simple requirements form list related items

Simple requirements form list related items

We can double click on an item in this list to open the relevant  item – in our example another requirement (we can drop down into other elements as required)

Opening a related item

Opening a related item

As a more complex example let us look at the Use Case form below – which includes linked actors, pre-/post-conditions, tagged values and linked items

Use Case example with several lists

Use Case example with several lists

To this form we can add action buttons to this form – as modified below – where we also illustrate adding on a new post condition within the current element editing context

Use case example with action button - to add a new post-condition

Use case example with action button – to add a new post-condition

Of course, what you place on your eaForms is up to you, that was the core idea behind eaForms. The ability to adapt the editing forms to match both the needs of your project and the users working on the project is key.  With eaForms you not only select the content but also define the layout and its presentation (look and feel) to meet your specific needs.  Having lists is one of those features that can help present the information in a better way for you.

I hope they provide you with the information you need.  Feel free to let us have your wish lists of additions.

Adrian

 

More exploring scripts – running EA Scripts from your code

I promised it wouldn’t be too long before I returned to provide the results from my experiments into running EA scripts from an external application (or if you wish from an EA Add-In).  If you missed the previous post on scripting may be worth reading first so that the current post is read in context.

Moving forward within exploring scripting capabilities let me start by providing some background information I discovered that will be relevant to the task in hand with the focus on user scripts.  You will see below I have skipped stuff that I didn’t see necessary for the current experiments.

1. EA stores its scripts in t_script

When we want to run an EA script we need to know where they can be found.  If you look into the EA database, and my suggestion would be to open a local EAP file using Access, you can find a table called t_script as illustrated below.

t_script - contains a range of scripts

t_script – contains a range of scripts including user scripts

If you look through that table you see the following columns which as I interpret have the following meanings:

  • ScriptID – a unique integer
  • ScriptCategory – there are several categories with normal human readable names and some GUID looking numbers (!) which including user scripts(indicated by the category with the value 605A62F7-BCD0-4845-A8D0-7DC45B4D2E3F).  You can also see other scripts such as those used when building code
  • ScriptName – once again either a human string or a GUID looking number
  • ScriptAuthor – another GUID looking number – not sure where this points to yet.  I’ll have to add this in when I find it but didn’t seem important at the time.
  • Notes – specifies the script name, type and language e.g.”<Script Name=”myScript” Type=”Internal” Language=”VBScript”/>”
  • Script – contains the script code in plain text form for user scripts.  When necessary I’ll have to check out the use of this for other types of scripts.

2. Extracting the script

If we want to run any of the user scripts we need to read the t_scripts table and extract the required script.  The method I have used was to:

  • Read the rows from the table, filtering on script category
  • Get the script name
  • For the selected script, extract the text from the Script column

3. Checks before running scripts

INCLUDES – If you look at scripts in EA you will see that some will include other scripts (e.g. INC). If we are running scripts within EA this is not a problem provided they exist within the EA context, however as we will see below, if we are running them elsewhere we need to ensure that we include ALL the relevant code.

RUN TIME OBJECTS – when running scripts within EA use is often made of the following run time objects:

  • Repository – current EA repository
  • Maths – the Cephes maths library
  • Session – which provides functions to interact with the user through the EA UI

If you are executing your scripts in another environment then you will need to supply the relevant references if required; note that the session object is purely for use within the EA script running environment.

Running scripts from the outside

With that bit of background we are now ready to look at running an EA script under the control of our “external” application.  Why is this an issue?  Can we not just ask EA to run the script for us?  Well so far I cannot see a way to interact with the EA script engine via the automation interface.  Hence,  the solution I have used (and I believe used by many others) is to provide my own instance of the script engine, extract the relevant script code and execute.

This isn’t as difficult as it sounds, although my voyage of discovery was interesting – and as seen from various posts on the Sparx Forum and Stack Overflow shared!

Script engine

As far as I can determine EA uses the Microsoft windows scripting engine.  Which I believe is MSScriptControl – which means that VB Script and JScript scripts written for EA can be run by using this control.

To run a script, we can use an instance of this class,  set the relevant attributes and call the run or execute function. So within our application we can:

  • Create an instance of MSScriptControl e.g. myScriptControl
  • Specify the script language e.g. myScriptControl.Language = “VBScript”
  • Set the script code using the relevant text (note: this will need to be complete with any includes expanded. e.g. myScriptControl.AddCode(ScriptCodeText)
  • If required pass objects that will be available to the script using the AddObject method e.g. myScriptControl.AddObject(“myObjectName”, myObjectValue, True) adds a name/value pair and sets this as a global value
  • If required pass parameters to the script.  This is done by setting up an object array containing the relevant arguments e.g. ArgumentObjects.  Remember that the scripting languages are loosely typed so they have no explicit knowledge of typing
  • We can then run the script and for functions capture the result e.g. myResult = myScriptControl.run(“myScriptName”, ArgumentObjects)

Pulling it all together

So with that background I put together a simple program to run a script.  The application provided a means to enter a script and run it.  This allowed me to verify that the mechanism worked fine without any interactions with EA.  However, I need to remember to do things link reset the scriptcontrol if I reuse it (myScriptControl.reset)!

It is also worth noting that I recently saw that there are some observed issues, for example – adding code will automatically execute code – I have only seen this issue when executing the script control within an EA Addin, it seemed to work fine when operating in a standalone program but that doesn’t mean there aren’t instances where this is not the case (the joys of software), hence I need to explore further!

But in the meantime, onto testing with EA – which involves the following steps:

  • Open an EA Repository
  • Get a list of user scripts
  • Select and run a script
  • View the result report

As it turned out I skipped writing a simple windows application as I was confident that would work, so went straight to writing a small Add-In that would perform these tasks. So no need to open the repository just the steps that followed.

My simple Add-In basically lists the available user scripts and provides a means to inspect and run the script.

Script Tester Menu

Script Tester Menu

The form that presents me with a list of scripts (as well as providing a option to refresh the list) is illustrated below.

Script tester list of scripts

Script tester addin displays a list of scripts that can be selected

The user can select a script from the list, and inspect the details:

Script Details

Details of selected script – script can be run by pressing run script button

And if they wish run the script, for example as below.

Results from running the simple script

Results from running the simple script

I am pleased to say that it presented the same result as when running the script natively within EA.

So using this approach there is a a means to run EA scripts under our control, demonstrated with this EA Add-In, and I’m confident it will work from the outside with a windows application, albeit with care regarding the objects that are being expected.

Points to note

Just to recap on the some points for running scripts using the script control.  You need to:

  • Ensure that the code provided is complete
  • Reset the script control before use
  • Pass any required object to the script – note that session is not available and if libraries are required you are responsible for ensuring that they are accessible
  • Provide any required arguments as objects – NOT typed
  • Capture the results

Nearly there or not!

If I refer back to my diagram in the last post (repeated here for reference), that illustrated all the tests I wanted to explore.

Overview of scripting scenarios to explore

Overview of scripting scenarios to explore

We have covered all cases 1 to 6 – albeit that there is ongoing work in checking some potential issues with case 6.

Case 7 – calling our Add-In from a script when working within EA

So what about the EA script control (not our own script control) calling an EA Add In. Just to be clear this is a normal EA script running within EA.  Is there a way?  Well I’m still working on this. I’ve posted and had some interesting observations which I have posted on the Sparx Forum.

This case has presented some interesting windows programming issue which has forced me to spend more time that planned looking into windows processes, but then that is the fun of exploring.

Overall for the most likely use cases all works as one would hope.  It is the edge cases that I thought I needed to explore that have raised some issues and I’ll be looking into:

  • Feedback I’ve received on how to resolve case 5
  • Unwanted code execution issues in case 6
  • Finding the correct reference for case 7

I hope to report back soon with my findings for these cases.

In the meantime, if you have some answers do join the dialogue here or on the forums.  For those happy with other scenarios I hope you have found this useful.

Adrian