业务流程建模有哪些技术？
我不确定这是否是问这个问题的正确地方，但就这样吧。
我目前正在研究一些不同的技术来建模业务流程。我需要为我的公司找到一个合适的选择，该公司开发各种网络应用程序。
到目前为止我发现了什么：
UML，特别是活动图
流程图
Windows 工作流基础
业务流程建模
我深入研究了工作流程的世界，但它主要是关于公司流程的自动化，而这不是我想要的。我的重点是软件及其内部流程。
如果其他人知道其他一些技术或者可以告诉我我已经发现的技术的优点或缺点，我将非常感激，因为我现在有点陷入困境。
I'm not sure if this is the right place to ask this question but here goes.
I'm currently looking into some different techniques to model a business proces. I need to find a suitable option for my company which develops all kind of web applications.
What i have found so far:
UML, specificly the activity diagrams
Flow charts
Windows workflow foundation
Business process modeling
I had a dive into the world of workflows but it's mainly about automating a process of a company and thats not what I'm looking for. My focus is on software and the process within.
If anyone else knows some other technique or can tell me the advantages or disadvanteges of the techniques I allready found that would be much appreciated because I'm a little stuck right now.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
目前，BPMN（业务流程建模符号）和 UML 活动图是两个最流行的选择。
我认为，当您对组织的业务方面进行建模并在深入研究软件系统的技术设计时立即转向活动图（作为 UML 语言的核心组件，活动图是当必须将工作流信息与系统的其他视图（也表示为 UML 图（如类图或序列图）时）更适合。
请注意，现在正在创建 BPMN 的 UML 配置文件 这意味着您将能够在同一个项目中混合使用 BPMN 和 UML 图
Right now BPMN (Business Process Modeling Notation) and UML activity diagrams are the two most popular options for that.
I think of BPMN as the right choice when you are modeling the business aspects of the organization and move to Activity Diagrams as soon as you drill down to the technical design of the software system (as a core component of the UML language, activity diagrams are a better fit when having to combine workflow information with other views of the system, expressed also as UML diagrams like class diagrams or sequence diagrams).
Note that now a UML profile for BPMN is being created which means that you will be able to mix BPMN and UML diagrams in the same project
我建议您考虑 ISO/IEC 24744。它会给您一个非常不同的视角，因为它没有使用无处不在的“组织作为机器”的比喻，而是寻求一种更加机会主义、以人为本的观点。
换句话说，ISO/IEC 24744 并不将业务流程表示为工作流程，其中要遵循的流程是驱动程序。相反，业务流程通过所涉及的工作产品和对这些工作产品采取行动的人员来表示。所执行的过程起着重要但次要的作用。
如果您对为什么会这样或有什么优点感兴趣，请告诉我，我很乐意详细说明。
I suggest you consider ISO/IEC 24744. It will give you a very different perspective, since it does not use the ubiquitous "organisation as machine" metaphor, going for a more opportunistic, people-oriented viewpoint.
In other words, ISO/IEC 24744 does not represent a business process as a workflow where the process to follow is the driver. Instead, a business process is represented through the work products that are involved and the people that act upon them. The process performed plays an important but secondary role.
If you are interested in why this is so, or what the advantages are, let me know and I'll be happy to elaborate.
我认为您是在问将业务需求/规则转化为技术需求，然后转化为设计？之后，您将将此设计实现为代码。
我不确定这是否是您要问的..
I think you are asking about transforming your business requirements/rules into technical requirements and then into a design? After that you will implement this design into code.
Am not sure if this is what you are asking about..