BPM - The Promise And Challenges
•Transferir como PPS, PDF•
4 gostaram•2,321 visualizações
This presentation provides a high-level overview of BPM and where it is today. It also touches on some of the core technologies and standards. Its focus is on the four specific “Challenges” facing BPM and they are aligned to the four phases of the typical application development life cycle. 1. Discovery 2. Design 3. Development 4. Deployment
![How did we get here? ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (19)
Semelhante a BPM - The Promise And Challenges
Semelhante a BPM - The Promise And Challenges (20)
Mais de Jerald Burget
Último
Último (20)
BPM - The Promise And Challenges
- 1. BPM Promises and Challenges
- 22. To make this more concrete, let’s consider a stock broker interacting with a stock exchange (Stock Broker Process).
- 43. This figure summarizes this life-cycle concept.
Notas do Editor
- Hammer and Champy - They advised a deep and radical redesign of the business to root out waste and increase the focus on the customer.
- The private sector’s fiduciary responsibility to maximize shareholder’s return on investment
- i.e., Oracle BPMS
- This presentation provides a high-level overview of BPM and where it is today. It also touches on some of the core technologies and standards.
- Discovery refers to having an understanding about the current environment Design involves the analysis of the current processes and the definition of future state processes. In the development phase the future state is implemented in technology, which may involve process automation using a BPMS (business process management system). The new processes are put into production in the deployment phase.
- WfMC promotes the use of workflow by helping to establish standards for terminology, interoperability, and connectivity between workflow products. It has created XPDL, an XML-based definition for business processes. The mission of BPMI is to promote and develop Business Process Management by establishing standards for process design, deployment, execution, control, and optimization. BPMI has developed three standards: Business Processing Modeling Language, Business Process Modeling Notation, and Business Process Query Language. Founded by Tim Berners-Lee, W3C has published the key standards for XML, HTTP, HTML, SOAP (Simple Object Access Protocol), and Web services. All W3C standards must be royalty free. OASIS (Organization for the Advancement of Structured Information Standards) is a not-for-profit, global consortium that drives the development, convergence, and adoption of e-business standards. OASIS has defined standards for e-business applications (ebXML) and is working on other high-level Web services standards. In contrast to the W3C, standards published by OASIS may have royalties attached to them.
- In this example: When the Stock Broker Process invokes the stock exchange’s buy service operation, it is actually using a service link, which we have called the “ buyerLink .” The role: of the process in buyerLink is buy requestor and its port type is stock transaction . The role: of the stock exchange “partner” is buy service and its port type is stock order .
- In our example, when the stock broker process invokes the stock exchange’s buy service operation, it is actually using a service link, which we have called the “ buyerLink .” The role of the stock broker process in buyerLink is buy requestor and its port type is stock transaction . The role of the exchange partner is buy service and its port type is stock order .
- The first approach is inherited from Microsoft’s XLANG, and the second is inherited from IBM’s WSDL.
- They are intimidated by code, which tends to obscure the business issues. Also, non-developers need to see processes from multiple perspectives, to determine inter-process dependencies, and to extract system requirements from processes. This lies outside the scope of BPEL. Because BPEL has no graphical rendering, the business analyst would have to code XML. This is not likely to happen.
- Once this is done, how will the process then be automated? It would be desirable to export the process to the BPMS for execution, perhaps using BPEL as the lingua 3. It is not usable for “legacy processes” that comprise package applications, custom applications, or manual activities. This excludes 95 percent of all existing business processes.
- Standish Group - In its research into the success rate of application development projects The Standish Group. The Chaos Report (1994), http://www.standishgroup.com/sample_research/chaos_1994_1.php. The Standish Group notes that a key cause of such failures is the lack of clarity in capturing and communicating user requirements.
- 1. Software misses the mark, making scrap and rework inevitable.
- It defines BAM as providing “real-time access to critical business performance indicators to improve the speed and effectiveness of business operations.”
- 2. For example , it is necessary to evaluate the cost of each process instance. Moreover, it is necessary to aggregate process instance information based on various criteria.
- 2. Process languages, such as BPEL, while key elements in a process laboratory, need to be enhanced with graphical capabilities that link them with process discovery. 3. BPEL may play a key role in this integration.