Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Glassboy

Pages: [1] 2 3 ... 69
General Board / Re: Mind map connectors
« on: June 21, 2018, 01:29:36 pm »
The shape script for the mind map is horrible.

General Board / Re: Windows Authentication & User Principal Name
« on: June 20, 2018, 07:12:00 am »
the usual Domain\Username


General Board / Re: Notes and Shapescript
« on: June 18, 2018, 07:14:29 am »
What do you mean by "convert note to pin"?

A note has the following appearances
  • Standard
  • memo
  • memo style 2
  • pin
  • sticky
  • paperclip

Bugs and Issues / Re: Files on Sharepoint
« on: June 15, 2018, 07:16:47 am »
I know it's an access file, however my company has a standard that we need to follow, and SharePoint is the way to go until we get to deploy EA as an Enterprise solution. The long term plan is to go Pro Cloud on premise, but before I get there I have to demonstrate it works...

It doesn't.  Access databases don't even synchronise for offline folders.

General Board / Re: Client Verification by Certificate
« on: June 13, 2018, 09:44:06 am »
I presume you mean user authentication, and user certs.  No.

If you mean the actual client, it is a signed executable. 

Suggestions and Requests / Re: Support LDAP within WebEA
« on: June 12, 2018, 06:50:28 am »
To reuse the security defined in a model which uses Windows authentication, WebEA shall provide a interface to such an LDAP server.

My employer sells a number of services that offer LDAP as standard for identity management and authentication.  Increasingly we're finding that customers are declining to use LDAP.  For web apps they're asking for SAML.

Suggestions and Requests / Re: New standard element property: ID
« on: June 08, 2018, 06:53:32 am »
Now *this* is a much more interesting conversation.  Certainly I'm aware of much similar criticism of Archimate, and I'm far more interested in the Strategy, Business & Motivatioon layers, a little bit with Implementation (which is light anyway) and not as much in Application and Technology.  I'm also not especially wedded to Archimate, however it does have the advantage of being a 'standard'.
So - are you doing anything like this (or know of anyone who is) and/or do you have any suggestions on where I might look for inspiration ?
Or are you more coming from a general modelling perspective - ie, if the notation isn't representing the ideas well enough then work with one that does (?)

At least two posters here have extensively reworked or custom ArchiMate MDGs.  Every couple of weeks to a month someone asks a question on extending ArchiMate.  I stick to vanilla ArchiMate so as not to cause problems for my customers who struggle with the basics.  For most of the real crunchy things I do, I use other notations such as UML, Sequence Diagram, DFDs et al as it's easier to be correct.

While ArchiMate is a standard, it is a standard from a consortium of tool vendors, it's certainly not an "open" standard.

Suggestions and Requests / Re: New standard element property: ID
« on: June 07, 2018, 11:27:19 am »
Even if Sparx did what you ask your property wouldn't be displayed on any ArchiMate shape.  I suggest you look at the Language Customization Mechanisms section of the ArchiMate notation.

I understand your perspective on the purity of Archimate and I do agree, however as you have pointed out Archimate, by specification, allow customisation.  I'm happy to be corrected, but I don't see how the specification dictates the format and display of the text in the shape ... ?
Specifically - what would be the difference between an element with the name "5.2 Lorem Ipsum" and an element with an ID "5.2" and a name "Lorem Ipsum" displayed on the shape as "5.2 Lorem Ipsum".
Or am I missing your point here ?

The customisation that ArchiMate allows is the extension you are not wanting to do, namely defining a profile of tagged values.  However ArchiMate - as far as I can see - does not provide a mechanism for you to display these things visually as UML and other notations do.  You'll also see that each element generally has some notes on naming that doesn't include any kind of classification scheme.

Sparx's ArchiMate representation is already more UMLised than it should be.  There are frequent posts here asking how to UMLise it more.  This is just putting lipstick on a pig.  The reasons people want to do it is valid, but the logical conclusion is not to bastardise ArchiMate, it's to create your own UML meta-model containing the concepts you want to use from ArchiMate and leaving all the brain death and 70s IT concepts behind.

General Board / Re: Reusing a Use Case, generic or template?
« on: June 07, 2018, 07:48:41 am »
What request is sent?  What classes are impacted by that message? What objects sent, what operations invoked?  How does that change your class diagram?  How about the validation?  That's where things get interesting.

I suspect it is something like OAUTH or SAML (or even Kerberos) and there is a lack of good available sequence diagrams for those protocols, which is odd given that they are fairly well understood.

Suggestions and Requests / Re: New standard element property: ID
« on: June 06, 2018, 10:25:59 pm »
- It felt to me like a general property that would be useful and valuable to many people as a global element standard property (and presumably the existing numbering features have been added for that reason, just the implementation doesn't quite work as well as I believe it could)

You've suggested an arbitrary use property.  Which is the opposite of a standard property.  With everyone using it in different ways it would drive confusion into models.

- A tagged value would not be displayed on shapes and in the project browser, ie alongside the element name (even a standard property wouldn't be without core EA changes like the ones that have been made to support display of the Alias property)

I'm not sure the relevance of this comment.  It sounds like you actually need to organise your workspace differently so you see more information when browsing the project browser.

- I'm trying to avoid extending and customising (albeit I'm happy to admit that EA is designed for this type of extension)

I'm not sure how adding a poorly defined global property is better for anyone than a properly defined extension.

- I'm not really familiar with how tagged values are best implemented (so maybe this would be easier than I think it would be). In particular I'm working with the Archimate MDG and stereotypes which adds another level of confusion / complexity

Even if Sparx did what you ask your property wouldn't be displayed on any ArchiMate shape.  I suggest you look at the Language Customization Mechanisms section of the ArchiMate notation.

Suggestions and Requests / Re: New standard element property: ID
« on: June 06, 2018, 01:42:21 pm »
Want to raise a thought here before I raise a feature request - in case there is already a way of doing this.

I'd like to have an element ID as a genuine separate element property (ie not text embedded in the name field).  This being a field that can contain an alphanumeric ID for the element, that is (perhaps optionally) displayed wherever the name is displayed - ie in the browser, on shapes and in selections.

This field could be filled automatically or manually, and could be used as a shorthand to identify the element and perhaps refer to some concept or identity outside the model.  For example:
- Project ID to external PMO listing
- Server ID from CMDB

What is your reasoning for this not being a tagged value?

Bugs and Issues / Re: EA14: Archimate shapescript / rendering issues
« on: June 06, 2018, 08:00:05 am »
You DO mean that the Sparx ArchiMate 3 scripts are the 3rd Worst, yes?  What are the other two?   :-\

Mind mapping and DFD.

BPMN would seem to be the best, but I haven't used all of the MDGs.

Bugs and Issues / Re: EA14: Archimate shapescript / rendering issues
« on: June 05, 2018, 08:32:54 am »
There are several renedering issues withe Archimate3 shapes in EA14 (many / most of which trace back through earlier EA versions and Archimate MDGs).  From what I can tell many people are accepting these or working around the (eg by creating their own shapes) - I can't find any mention of bugs or issues being explicitly raised in this forum.  However givan that Archimate is obne of the major reasons why we are using EA I thought I would formalise the issues we are encountering.  I will raise a formal bug report for these also.

3rd worst shapescript in the product :-)

I usually take the approach teach them the modelling notation as I teach how to do various diagrams with various notations. Examples seem to be the best way to get them up the learning curve quickly. For enterprise architecture using archimate I start off with motivations then move through the various domains such as business, application, infrastructure etc. Each time introducing something new that Sparx EA can do.

I get people to start modelling and tell them not to worry about being correct.  Then I read their model back to them and get them to confirm whether what I read is what they intended to convey.  ArchiMate especially should break down into a series of statements, and be able to be read like a story.  Story telling is a fundamentally human activity and we train children to do it in schools so I find that people pick up how to improve their modelling this way.

EA can' parse DDL. Since it internally seems to have a SQL parser (the SQL you send from EA to a DB are mangled in the one or other way) there should be ways to get EA eating a DDL. However, times for seeing feature requests being implemented are no longer in the range of a couple of weeks.

I think that this sort of functionality would be best community produced.  Sparx should be responsible for the parser and documentation about it and the community could craft for the particular database technology.

Pages: [1] 2 3 ... 69