Welcome ...
… to the bpmWiki. This wiki is about BPM, EAM and a little bit ALM. It's a world full of acronyms. BPM stands for Business Process Management , EAM for Enterprise Architecture Management and ALM for Application Lifecycle Management. If you want to edit, comment, add or review something, please feel free to sign on.
Enterprise Engineering & Architecture Matrix v0.7.0
Our first (sub-)project: Build up a bpm-centric Enterprise Engineering & Architecture Matrix from
- features and
in the area of BPM[N|S|A|M] - with UML/MDA. Main approach is to collect, not to judge. We want to give handy attributes to assess the solutions, but we hope not to balance too much. For the personal sentence we found a user-namespace, where you can rank every attribute for yourself, and create your own assessment.
Our μ-Roadmap:
- Phase 1 - Brainstorming and Collecting ('till ca. October)
- Phase 2 - Structuring und Categorising, starting a beta ('till ca. November)
- Phase 3 - Lift-Off (end of 2011)
- Phase 4 - Every Week min. one Tool-Revision (2012 ff)
- Phase 5 - Live-Blogging from Conferences & Key-Notes, Producers updating there Product-Versions via Webservice.
- Phase 6 - Rank-o-meter?
Features
This section is the start of an ontology of BPM Product Features. We think about starting with 100-150 values, but can't garantee to reach 300-400 Product-Feature-Values. So an aggregation, grouping, categoriszing is essential. The first phase of this wiki will end with a first suggestion of a feature-ontology.
Common
Some easy, global informations about the product version.
Cross
Here a first, cluttered cross feature & group collection.
Hope we have a vital discussion, about structure, integrity and categorization of common features.
Customizing
Without customizing a BPM-Solution is just a bread without butter. Addons, API, Stencil-Sets, Styleguide & Pattern-Support could help to give your BPM-Initiative the rocket science.
Focus
The main product focus and focal point is the most important attribut to cluster the market of tools and solutions.
Infrastructure
What are the pre-requirements for installation? On the TCO-View could be the Maintance an important aspect. What's if you have success, and you have to scale your systems because of the traffic - no-brainer?
Lifecycle
There are a lot of BPM-Lifecycle theories, so it's a good idea to divide the whole story in eight lifecycle areas to have a good chance to cover mostly all feature aspects:
01 - Analyse, Discover & Mashup
02 - Design & Plan
03 - Development & Implemention
04 - Rules Engineering
05 - Simulation & Improvement
06 - Build, Test & Deployment
07 - Operations & Executions
08 - Monitoring & KPI/SLA Governance
Pattern
Pattern are more then only a product-feature. Pattern are boon and bane. For the creative corehead they seem like killing the cat. For the industrial thinker they are the building blocks for successfully time-to-market stories. What do you think about pattern?
Products
The long list of great BPM-Solutions should devide in some categories. Starting with the split in BP+MA (Modelling & Analyse) and BP+MS (Managing & System[operation]). Below this we differ as follow:
BPMA (Business Process Modelling & Analysing)
- Visio-Solution: From simple stencils to Enterprise Process Engine Integration.
- BPMN Client-Server: Modelling- & Analyse-Tool with Standard Client-GUI
- BPMN Web (SaaS): Webbased Modelling- & Analyse-Tool
- Allround Modeller w. BPMN 2.0: UML-, EPK-, ERD-Modeller with BPMN-Support
BPMS (Business Process Management System)
- Client-Server: Classical Client-Server Architecture
- Web (PaaS): BPMS in the Cloud mostly as PaaS, seldom only as SaaS.
- Embedded-BPM: BPM inside ECM, ERP, DMS, CRM, MDM …
- Mobile-App: Tracking, and some Human-Tasking on the Phone, why not. It's easy.
- Process-Mining: Mudracking with Process-Data on Logging-Level
- Process-Monitoring: Dashboarding with KPI- & SLA-Governance
- Rules-Engine: The Core of the Core, very fast very complex.
- Process-Engine: Just a core Process-Engine for running BPEL, PDX oder BPMN 2.0
- ESB: Enterprise Service Bus. Mediation-Layer with EI-Pattern.
- Testtools: And what's about automated BPM-testing?
Product-Focus and BPM-Lifecycle
In relation to the BPM Lifecycle, we consider the following constrains, with a smooth transition:
- 01: BPMA
- 02: BPMA
- 03: BPMA / BPMS
- 04: BPMA / BPMS
- 05: BPMA / BPMS
- 06: BPMS
- 07: BPMS
- 08: BPMS
You find our first wave of products, cluttered and only in alphabetic product order here.
Tools we have settled on our radar have become a namespace and can navigate direct through the sitemap. If a solution offers its features in the Cloud SaaS oder PaaS or Standalone or Server-Side or Client-Side is as Product-Feature. We want to collect tons of them. Find the first Brainstorm on this here.
User-Stories
Did you have some cool experience you want to share? Or why not defining a personal rank-o-meter? Perhaps you want to weight the License-Model higher then for eg. the visual smartness of a tool. Vice-versa also. Balancing, assessing, scoring is a personal task. So we think about a matrix corellation between product, feature, and user-ranking. .
It's all about BPM formerly known as Workflow Management
Access all Areas
Do you wanna have a VIP-Pass for the BPM(N|S|A|M) Backstage? You know your product like no other? You also amazed like me to see so many beautiful solutions grow in this complex area of computing? You have some great ideas to enhance the Enterprise Engineering Matrix? Oh, you find a typo or want to help gardening the big ballroom of information?
Just drop me a letter info@detlef-burkhardt.de