MK
Howdy,
I have a process to design at hand. it is an application process that if it passes some initial assessment will go throuhg an entire SDLC until the solution is entirely developed. Any thoughts about how to present the SDLC within the process model without getting into a lot of details. My assumption is that the SDLC is a value stream-- and thus can not be triggered as one single subprocess.
The SDLC is already designed.
Thanks!
Hi Mohammed,
For me, without knowing much about the details, it sounds like a good use case for an Enterpise BPMN Collaboration diagram. I would use application system type lanes and add my tasks as service or scprit tasks (depending on the actual execution):
A Service Task is a Task that uses a Web service, an automated application, or other kinds of service in completing the task. / A Script Task is executed by a business process engine. The task defines a script that the engine can interpret. When the task begin, the engine will execute the script. The Task will be completed when the script is completed.
(see: BPMN Activity Types Explained (visual-paradigm.com).
Best,
Veronika
Thank you, Veronika, for the reply.
The process is about developing a dashboard. The request usually comes from an end user then it has to pass through some filtration activities such as demand mgmt., governance, etc. Before being authorized for development where the SDLC will be triggered as follows:
- Requirements gathering and syndication
-Development and testing
- Deployment and release
My understanding of the EBPMN is that it has several pools for the various parties within the enterprise. And the main activities within each process are listed within each pool. And that the interactions between these pools are done via messages flowing between them.
Would apprecaite your input- and if there are addtional resoruces to read more about this EBPMN.
Thanks again,
Mohammed
Hello Mohammed,
watch out for a misconception here: A BPMN Pool represents a process, not a department. You could use Lanes inside the pool to represent departments or roles. Only when different processes interact you need a second pool and they will communicate via message flows (between message events or Send/Receive tasks). So in your case the process from request to approval of the development project could be one pool, which upon approval ends with a message end event and sends a message (the development project approval) to the SDLC process (another Pool), where it will be received by a message start event.
In practice make one collaboration diagram for each of the two processes and use occurrence copies of the pools to show the message flow communication. I illustrated this in a comment to another post: https://www.ariscommunity.com/users/pennyb/2016-05-02-use-occurrence-copies-process-interfaces-signal-events
It works the same for start and end message events.
Hi Mohammed,
Still not sure that I get the full picture of what you want to do.
If you want do map the process on a really high level, then I would create a value-added chain diagram (I would actually create that anyways)
So, let me give you an example of what I mean- for the high-level, I would create something like this:
For the lower levels, it now depends a bit. If your processes describe mainly the system view on things, then I would chose the EBPMN. However, if you want to show roles (including responsibilities (RA[S]CI), IT systems, inputs, outputs, etc., then I would chose EPC as preferred notation. (For processes related to organizational stuff, I would always chose EPC over (E)BPMN.)
Just a brief visual comparison - for the BPMN diagram, I am lacking a bit of phantasy- so please excuse the brevity.
| EBPMN | ECP |
 |
 |
Those two diagrams would reflect the first object in the VAC. So, the process demand. For the next objects of the VAC, I would create a new diagram and assign/link them with interfaces.
Does that help?
Best,
Veronika
