我不是指每分钟的比特数，而是业务流程管理。
起初虽然 BPM 被高估了，因为该技术在某种程度上很容易解决，但我了解到 BPM 套件的价值在于让非技术的业务专家参与到软件设计中。
我知道，用户在分析过程中总是和我们在一起，但我们使用的工件对他们来说总是很陌生。无论UML图看起来多么友好，或者我们进行了多少敏捷迭代，最终用户和最终开发人员之间总是存在差距（通常由用户经理和IT经理覆盖：-S）
您（作为软件开发人员）如何看待 BPM？看起来很有趣吗？你会考虑学习其中之一吗？你认为5年后它会死吗？
我知道 BPM 根本不是灵丹妙药，但除非您有一个非常聪明的客户，他知道如何表达他们的要求让我们把它做好，否则分析和需求将永远是项目失败的地方。
I spent a couple years in the Content Management/Information Management circle using both FileNet and IBM BPM products. I would have to say I am incredibly unimpressed, and here is why:
1) BPM is one of those things I have not ever seen implemented intuitively. By that I mean (similar to what you say in your question) that a business user cannot sit down, and with 30 minutes create a process/workflow.
2) I have rarely seen a non-programmer be able to create acceptable solutions
3) The lack of ability to explain BPM to business users, the inability of business users to comprehend, and the amount of time and money spent on BPM seems ludicrous to me. From experience in everything I have been involved in, the company could hire 1 or 2 people (technical types) to work full time and create them a custom app for the time it takes a bunch of business types to have numerous meetings and hire consultants or train business people.
4) It is an incredibly niche market, and 90% of the outcome involves document routing and approvals. This is a VERY VERY simple concept, and one which a developer can usually code and implement a solution for much cheaper. If the developer is good, they can make it much more intuitive with less steps too.
5) It usually takes longer to have a coder talk with 10 people in management, a bunch of business users, learn to use a bad limited product and come up with a solution than it would be just to let normal development go on.
Don't get me wrong here - I know my experience, while quite deep compared to some, only deals with a couple products meaning I have only touched a little of what is out there. I am all in favor of innovation, but I haven't yet seen a halfway decent solution, and they all cost 20 times more than they are worth. I am sure COTS BPM type software will persist, but I hope I don't have to work with it for many more years. Hopefully then it will be halfway decent.
我认为 BPM 与“保持计算机运行”的传统 IT 单元正交，因为 BPM 是我们尝试通过添加这项技术或相应地更改流程来改进工作方式的地方。我觉得它在几个方面相当迷人。
对我来说另一个有趣的部分是，这往往涉及查看业务的不同部分，例如销售团队如何工作、营销、人力资源等，并试图了解他们的效率以及事情在哪里改善？
我认为它不会消亡，但名称的含义会发生变化和发展，我怀疑其中一个分支可能是自动化业务专家或其他名称。我也确实看到这与公司 IT 部门的应用程序组合的想法相结合。应用程序会定期进行改进或更换，以改进事物的工作方式，并具有持续改进的价值。
不要忘记，我们这些 IT 部门的人经常光顾这个网站。我可能是一名网络开发人员，但根据公司的不同，这可能有几个不同的角度：1）产品开发——在这里我帮助制造产品或促进公司销售的服务，2）信息技术——在这里我帮助公司通过了解公司的骨干来运营，公司的骨干是一组机器和各种软件，这些软件通过各种流程缝合在一起，以实现公司的运营。
The evolution of requirements and the technologies that can help meet those requirements are usually a couple of big things that can impact any large software integration like an ERP or CRM system. In taking years to get the software installed and the company using it correctly, there will likely be many changes as to how we thought it would work to this is how we actually use it, where not all changes are bad. It may be that by removing some part a company could save thousands of dollars on the man hours that would be spent on something that isn't really needed or useful but this wasn't known at the start and thus one of the requested features is removed from the list of things wanted at the end.