In advance of the launch of the formal SABSA Institute Working Group for Modelling SABSA with ArchiMate (MSA), an update to the Tools & Techniques White Paper T100 – Modelling SABSA with ArchiMate has been published.
In addition, SABSA Institute Members can download an ArchiMateSE Model of an open-source control framework – the CSA Cloud Controls Matrix. Members can access the file at Resources > Working Groups.
A Project Charter and Call for Participants will be launched by the end of April.
6 thoughts on “SABSA Modelling in ArchiMate – Updated Paper & Cloud Controls Matrix Model”
Hello,
I’ve been reviewing this document and noticed in the SABSA attributes section it makes reference to Data Attributes. I can’t find any catalog describing this set of attributes and I am wondering what the source for it was? I know there has been a call for new attributes but I don’t see any published work. Were the data attributes included in the whitepaper drawn from something published by SABSA or on the website? Thanks.
I see now they are defined in the taxonomy file provided.
I’ve been reviewing this revision of the whitepaper and trying to adjust a template I made based on the initial version. I’ve noticed on the Business Attributes diagram provided in the SABSA example file that there appear to be some cut & paste errors with regard to the descriptions of the attributes. Also, I’ve noticed that there are in my opinion some inconsistencies in how the model was built, specifically with the use of properties, that are not consistent with the provided XML schema. I’m trying to build a template that will hopefully more closely align to the XML schema if/when I get to the point of exporting and trying to transform the export into a document for validation against the provided XML schema. I’m actually curious to know if there is an existing transform template available that might shed some light on why particular choices were made in the supplied model (e.g. attributes do not appear to have a domain property as specified in the XML schema). Would be interested in sharing how I am trying to implement what is described in the whitepaper and in the XML schema to see if I am on the right track towards getting a template that will be exportable and when transformed conforms to the XML schema. I recall a video I saw on YouTube a few years back where the model was eventually transformed and loaded into a node database which enabled the use of queries to validate business rules regarding how the model was constructed. I’m very interested in getting to that level of capability when using this proposed approach.
Another item I’ve noticed. “Opportunity” appears in the general description of the Motivation Aspect of the full security overlay, however that specialization is never further defined in the whitepaper nor does it appear in the XML schema. Is this an error of inclusion from a previous version?
Another item I’ve noticed. For Article/Mandate the whitepaper calls out that they are synonyms with the same structure, the XML Schema doesn’t appear to list Mandate as a valid entry. Not sure if this is an omission or if models containing Mandate should fail XML Schema validation.
Hi Christopher,
First of all, thanks for taking the trouble to have reviewed these artefacts in such detail and fed your comments back into the process.
Your contribution is also timely as the paper is about to undergo a review and update, in conjunction with the team at The Open Group. If you would be willing, I’d like to bring you into this process via a call so that I can properly understand and address your feedback – easier than a review cycle via the Blog.
If this is OK for you, pls contact me via DM (steven.bradley@sabsainstitute.org) and we can set something up 🙂