Register now or log in to join your professional community.
Mr. Mohammed Thiab has explained this Question properly
I believe it to be an application that instead of being based on procedures or objects, it is based on business processes
A process-driven application is any software application that enables users and data to interact within the context of a business process. In other words, a process-driven application is the software that runs the business process.
Process Based/driven application was popularized in2008 when describing applications driven by processes, and originally referred to applications driven by their business process management ("BPM")
A (Process Driven) application is a software application that is driven by an underlying process or workflow engine where the process can be exposed and reused.
It is the application which automates processes across the value chain, either downstream with suppliers (either material or service suppliers), or upstream with customers. It provides a single integrated environment for the development and deployment of business processes through the whole value chain.
This will allow users to ensure that the processes are aligned with the strategy, goals and business objectives of the company, and that these processes operate efficiently, and consequently eliminates the gap between what the business needs from IT and what IS technologies are capable of providing.
With this Business Process Application integrated with ERPs, it is now possible to add new functionalities to the ERP, and have streamlined the business processes cross the value chain. So we have created business value, making it easy for people to communicate and participate in the business process, facing the challenge of integrating heterogeneous IT software systems.
agreed with NADEEM MALIK
This take me to the different philosophies/approaches of "push" vs. "pull" , or "inside-out" vs. "outside-in" or "functiomality-driven vs need-driven" applicable to many things including our approach/mentality to software/business application development .
In the push/outside-in/functionality-driven school, business appications are designed, developed, marketed and pmroted based on an "external" view from someone outside the customer organization with focus on some functionality that is claimed to be useful/neneficial to the customer
Taking the other approch pull/inside-out/needs driven school, business applications are designed, developed and deployed according to an "internal" view from within the customer organization and reflecting its own needs.
In my approach (highly influenced by IBM school), I view business applications in three categories (the MUST have, the NICE to have, and the OK to have) .. from a pure business model viewpoint.
Furthermore, I take the MUST have category and differentuate between what we call " mission-critical business applications" without which the company will fail to fulfill its commitments/obligations, and the "value-add business applications " that give you your own distinguishing flavor (differentiator) in the marketplace
Dealing with these applciations from a "pull/inside-out" approach, I find using business process management (BPM) principles vital to bridge the needs/requirements gap based on thorough and comprehensive understanding of what goes inside the organization represented in clear and complete business process diagrams (much much much better than conventional flowchart diagrams)
I hope this sheds some light on the question !
i Agree with Salauddin
A gree with Mr. : Thiab
