It’s Monday and I am starting a new weekly series on BPM 2.0. Every Monday, I will pick one item in my BPM 2.0 checklist and provide more details about it. I will go through the items of the list in the order they appear in today, then circle back once I have covered all 18 items. Three passes should keep us busy for the rest of the year.
오늘은 월요일이고 나는 매주 월요일 BPM2.0이라는 시리즈로 새로운 한주를 시작한다.
나는 나의 BPM2.0 체크리스트 안에서 새로운 아이템을 골라 잡을 것이다. 그리고, 그것에 대해서 보다 상세하게 제공할 것이다. 목록 중에 하나의 아이템을 통해 오늘 표현할 것이고, 18개 아이템에 전체에 걸쳐 볼것이다.
The first item on the list is about process analysts, who I believe are the target users for BPM 2.0.
리스트에 있는 첫번째 아이템은 BPM2.0의 타켓 유저인 "프로세스 분석가"에 대한 것이다.
The question then becomes: how can you identify them? A simple test is to ask a candidate if she understands the differences between a do-while, a while-do, and a for-each loop. If she does — and can explain it to a business analyst who could not explain what a loop is at the first place — you found the person you were looking for. You will find her among the 8 million Visual Basic programmers, the 3 million PHP fans, the million PL/SQL folks, and the half a million or so ABAP guys and gals. If you compare that to the 2 million people who can write Java code today, that’s a pretty big group. If you add to the mix the folks who understand HTML, you’ve got a pool of more than 20 million people you can draw from.
And if you want to understand why the mastery of Java and J2EE should not be a pre-requisite to the use of a BPMS, just read the syllabus for the course on jBPM offered by JBoss:
“The student must have previous experience developing an Hibernate application. The student must know how to configure a simple SessionFactory for Hibernate, utilize a Hibernate Session and transactional demarcation and how to perform basic queries on Hibernate objects.”
To me, it’s pretty much a show stopper. BPM 2.0 does not stop there though
<출처: http://itredux.com/blog/2006/03/13/who-is-a-process-analyst/>
