Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Business Proces...  Business view vs implementation considerations
Previous Previous
 
Next Next
New Post 10/29/2010 3:24 AM
User is offline Des
1 posts
No Ranking


Business view vs implementation considerations 

When modelling business processes (we use BPMN which will be executed via BPEL), to what extent should the analyst worry about implementation of that process vs capturing the business view. For example, I have a BPM which at a high-level: calculate payments for a period, create a schedule of instalments. Where I have multiple periods I could model my process as follows:

1a.1st pass through the process for year 1, creating a payment schedule
1b.2nd pass through for year 2, creating a 2nd payment schedule which may actually mean adjust the 1st schedule to add new payments and dates
OR
2. loop through the processing of both years and leave the activity 'create schedule' until all the processing is done so that only one schedule is actually created.
 
From a process view, option 2 seems 'neater' as it is only one activity of 'create schedule' (reviewers have looked at option 1 and ased why the need to go to that activity multiple times when the end result is you actually just want one output). From an implementation view though, option 2 may mean problems with managing state, as effectively the information from processing year 1 would need to be held in state until year 2 had been processed and all that information is then fed into the activity 'create schedule' which would need to work out which is the most recent and relevant info to use (there could be many periods worth). Option 1 allows for each subsequent period to build on /replace the previous period so that no matter how many loops through, each 'instance' of a schedule is effectively replaced with a subsequent one.
To what extent should the process analyst need to worry about implementation? Or is it actually just a process modelling style issue? Preference for one over the other?
Thoughts greatly appreciated.
 
New Post 10/31/2010 4:01 AM
User is offline Kimbo
454 posts
5th Level Poster


Re: Business view vs implementation considerations 
Modified By Kimbo  on 10/31/2010 6:05:53 AM)

 Hi Hetachapman,

It looks to me like option 1 is using business process mapping to design your solution. That isn't the purpose of BPM. Option 2 i.e. a "Create Schedule" activity only, is sufficient detail for a BPM diagram. I  think your reviewers have a very valid point in questioning option 1.

So, to answer your last question, a business process analyst should not really consider implementation at all. In fact when I model business processes I include both system and manual activities without regard to implementation, so that the full end to end process is captured. Business users see the full process and manual processes are opportunities for later computerisation.

As a last comment, the level of detail in option 1 is something to consider once you get around to designing your solution. You may well use a process map for this, but it won't be a "business" process map.

Kimbo

 
New Post 12/7/2010 12:11 AM
User is offline SteveBoulanger
38 posts
9th Level Poster


Re: Business view vs implementation considerations 

 Hi Hetachapman,

In my humble opinion, BPM is typically performed by business analysts and managers. It can be defined as a way of thinking and an approach which allows the organization to focus and manage its business processes with the aim of deriving efficiency and quality in its way of working across multiple levels of business to achieve defined corporate objectives.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Business Proces...  Business view vs implementation considerations

Community Blog - Latest Posts

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC