tag:blogger.com,1999:blog-45604631900324366922026-06-03T16:03:07.705+02:00This blog complements the support web site for my book "Improving enterprise business process management systems" about BPM, SOA and EA, which has just been published (see www.improving-BPM-systems.com/book ). © Copyright 2007-present by A. Samarin. All rights reserved. Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.comBlogger360125tag:blogger.com,1999:blog-4560463190032436692.post-8953849234612029022021-12-22T09:31:00.000+01:002021-12-22T09:31:23.197+01:00

Working with reference architectures, I met the new for me pattern or principle called “Anna Karenina”. The name of the principle derives from Leo Tolstoy's 1877 novel “Anna Karenina”, which begins: “All happy families are alike; each unhappy family is unhappy in its own way”.From https://en.wikipedia.org/wiki/Anna_Karenina_principle The “Anna Karenina” principle states that a deficiency in any

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-43736337511902184102020-07-29T00:15:00.003+02:002020-07-29T09:50:28.892+02:00

1 Executive summary CBDC implementation is a daunting task and its the most difficult feature is legality through CBDC life cycle. Let us architect CBDC as commonly agreed reference architecture which is available to everyone to move forward further (via improving the entire global economic position) and faster (via innovations). Although there are some attempts to outline CBDC

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-56443388374799793402019-05-07T21:41:00.002+02:002019-05-07T21:49:52.781+02:00

1 Smart Cities Reference Architecture Methodology The IEC System Committee “Smart Cities” is mandated to develop the Smart Cities Reference Architecture (SCRA) which is a template for various Smart Cities solution architectures.  Although there are many reference architectures for Smart Cities, those architecture have been developed under different and unknown methodologies. This made

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com3tag:blogger.com,1999:blog-4560463190032436692.post-46546279637982099202019-03-31T22:30:00.002+02:002019-03-31T22:58:56.540+02:00

1 Addressing crosscutting aspects by-design Various crosscutting aspects (also known as non-functional or quality characteristics) of systems are, actually, dependant on all the system elements and relationships between them. For example, the security design principle “weakest link” is saying that “in designing security for a system, focus should be put on the weakest components of the

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com1tag:blogger.com,1999:blog-4560463190032436692.post-87154641485049917542019-03-27T17:51:00.000+01:002019-03-27T17:51:03.145+01:00

1 Introduction Although the global success of software is unquestionable (“software is eating the world”, everyone wants to use agile, etc.), last year the agile guru and “father” of microservices Martin Fowler was talking "why are we struggling" (see https://martinfowler.com/articles/agile-aus-2018.html ). He pointed at three problems: Get rid of the Agile Industrial Complex and the idea of

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com1tag:blogger.com,1999:blog-4560463190032436692.post-13927269689513139002018-10-09T08:45:00.001+02:002018-10-09T08:45:27.983+02:00

Methodology, Architecture and Practice (MAP) for Digital Transformation is a series of blog posts about #DigitalTransformation. 1 Context At the beginning of October 2018, the www.africup.tn conference took place in Tunisia. The conference was focused on how to help start-ups. Currently, start-ups are the main “source” of jobs in many countries, especially, on the African continent, because

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-46996384005012981092018-09-24T09:32:00.001+02:002018-09-24T09:32:10.386+02:00

Methodology, Architecture and Practice (MAP) for Digital Transformation is a series of blogpost about #DigitalTransformation. This blogpost is about a Laboratory of Architectural and Technological Governance of “Smart Everything” 1 Why the laboratory is created (what is the reason for this?) The Laboratory of Architectural and Technological Governance of Smart Everything (LATGOSE) is

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-74767758422227310102018-07-24T11:40:00.002+02:002018-07-26T14:45:22.688+02:00

This blogpost is an example view based on the value viewpoint described in the series https://improving-bpm-systems.blogspot.com/search/label/%23BAW also it illustrates the blogpost http://egov-tm.blogspot.com/2018/07/blog-post.html The IEC System Committee (SyC) “Electrotechnical aspects of Smart Cities” has the following scope. To foster the development of standards in the field of

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com1tag:blogger.com,1999:blog-4560463190032436692.post-52721420650592804092018-06-30T19:25:00.001+02:002019-05-22T23:02:15.519+02:00

Post-platform enterprise pattern: Enterprise-Enterprise Yet Open Robotic Environment (EEYORE) With thanks to John Morris (@JohnHMorris) and Michael Poulin (@m3poulin) for their valuable comments. An updated version of the article is available at https://bpm.com/blogs/post-platform-enterprise-pattern-faster-and-cheaper-inter-enterprise-ecosystem-business WHY In the modern business world

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com4tag:blogger.com,1999:blog-4560463190032436692.post-40064054685500927802018-06-28T12:43:00.001+02:002018-06-28T12:43:19.136+02:00

Mini-course at VFU 1 Title Architecting modern digital systems 2 The problem to be addressed At present, there are many IT-related methodologies, technologies, tools and schools of thoughts which overlap and contradict each other. The best practices are actually the best only in particular situations. Often decisions about software-intensive solutions are taken on the in-complete and

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-66334387240534554402018-04-28T11:46:00.000+02:002018-04-28T12:02:04.565+02:00

1 The expression “all models are wrong” is wrong "All models are wrong" is a well-known aphorism from statistics (attributed statistician to George Box, 1976), which has been used in other disciplines. A modern book on system engineering claims that "The map is not the territory, the menu can’t be eaten, the drawings do not fly, the source code does not store the values of its variables

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-84927808857432546202018-03-11T11:31:00.001+01:002018-03-22T21:34:50.043+01:00

This blogpost is based on the several recent LI discussions about the concept “capability” (see their URLs at the end of this blogpost). Those endless discussions only confirm a well-known systemic observation – a complex concept is better understand via its relationships to other concepts. Thus, to define the concept “capability”, it is necessary to define together the several related

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-9766926753548573662018-01-15T21:20:00.000+01:002019-11-12T16:20:18.712+01:00

This blogpost continues the "Better Architecting With" series http://improving-bpm-systems.blogspot.bg/search/label/%23BAW 1 About Digital Systems A digital system is a system which builds life cycles of its primary artefacts on the primacy of explicit, formal, computer-readable and computer-executable presentation of those artefacts (in other words, digital presentation of those

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-43667044751814907462017-09-28T18:45:00.001+02:002017-12-31T09:57:37.113+01:00

Any blockchain-based solution is a virtual (invisible but real) intermediary (with its data, computing resources, workers, miners and decision makers) between people using this solution (the users). Actually, the users agreed to trust the goodwill of networked miners (not technology as claimed by many blockchain enthusiasts) to be able to work between themselves (e.g. carry out some transactions)

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-3489982818968249812017-09-15T14:40:00.000+02:002017-09-15T14:40:32.910+02:00

Just an illustration BTW, the idea "stolen" from the agile development methodology. Thanks, AS

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-8986149871543435802017-08-31T18:50:00.000+02:002017-09-10T11:25:07.811+02:00

As we know, the blockchain technology is actually a multi-user, centralised (logically) and distributed (physically) archive with excellent availability and integrity characteristics. Such an archive collects various records and packs them into chained and (practically) immutable blocks. Why is it centralised? Because of the single uniform code base and the consensus process, i.e. a combination

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com1tag:blogger.com,1999:blog-4560463190032436692.post-7181518212040098362017-08-23T20:01:00.000+02:002017-08-23T20:01:58.421+02:00

My presentation for BrightTalk { "channelId" : 679, "language": "en-US", "commId" : 268047, "displayMode" : "standalone", "height" : "auto" } And some feedback from the organisers. You had 362 pre-registered users and 122 views so far. 36 people downloaded your slides and you got 4.2/5 rating for your webinar. All users said it was a very useful presentation, but I would like to

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-88678300000946278202017-08-14T09:47:00.001+02:002018-04-24T09:15:37.338+02:00

As we all know, usage of MicroService Architecture (MSA) requires the very comprehensive operational practices and infrastructure. A microservice is a unit-of-functionality (or “class” in the informal IT terminology) within its own unit-of-deployment (or “component” in the informal IT terminology) acting as a unit-of-execution (or “computing process” in the informal IT terminology). Some

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-10000672285275476632017-07-27T21:42:00.000+02:002017-08-29T21:43:14.333+02:00

All blogposts on this topic are at the URL http://improving-bpm-systems.blogspot.ch/search/label/%23BAW  1 The systems approach basics The systems approach is a holistic approach to understanding a system and its elements in the context of their behaviour and their relationships to one another and to their environment. Use of the systems approach makes explicit the structure of a

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-82488712878409359632017-06-20T17:20:00.003+02:002017-07-03T11:53:30.759+02:00

{ "channelId" : 679, "language": "en-US", "commId" : 260541, "displayMode" : "standalone", "height" : "auto" } Thanks, AS

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-20220071377736182692017-06-17T21:17:00.000+02:002017-06-17T21:18:09.788+02:00

This blogpost continues the blogpost “#entarch frameworks are typical monoliths which have to be disassembled for better architecting” ( see http://improving-bpm-systems.blogspot.bg/2017/06/entarch-frameworks-are-typical.html ) and uses some feedback from a LinkedIn discussion https://www.linkedin.com/feed/update/urn:li:activity:6278239461654437888/ This blogpost outlines a “big picture”

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-587802030364408852017-06-07T17:17:00.001+02:002018-02-15T12:47:06.576+01:00

This blogpost starts the "Better Architecting With" series http://improving-bpm-systems.blogspot.bg/search/label/%23BAW#entarch frameworks are considered as a must for any serious #entarch work. There are about 1 000 #entarch frameworks on this planet. The most popular of them are typical monoliths – huge in size, contain a lot of overlaps, slow to evolve, difficult to adapt to particular needs,

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-44685091789988398872017-06-02T13:14:00.001+02:002017-06-02T18:28:31.728+02:00

This blogpost explains how to implement the EU General Data Protection Regulation (GDPR) by design and by default via Business Process Management (BPM). This blogpost describes only a reference solution architecture without much implementation details. It focuses, primarily, on the artefacts such as capabilities, rules, roles, data-structures, documents, explicit coordination and audit trails.

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-17832932610066280592017-05-31T15:26:00.002+02:002017-05-31T15:26:40.283+02:00

The classic definition of the microservice architectural style “as an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanism” creates a lot of fears and misunderstandings: Application monoliths are evils, but having too many microservices sounds like creating an (unknown) evil as well. Everything has

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0tag:blogger.com,1999:blog-4560463190032436692.post-23830504477122276162017-05-22T21:13:00.001+02:002018-04-24T09:16:13.666+02:00

Everyone heard about the DevOps culture which refers to a set of practices that emphasize the collaboration and communication of both software developers and IT professionals while automating the process of software delivery and infrastructure changes. Certainly, DevOps improves the time-to-market for digital solutions, but it spans only a down-stream part of the idea-to-solution value stream.

Alexhttp://www.blogger.com/profile/07571303538841911828noreply@blogger.com0