Towards developing software from a description of the business processes they support

组织构建软件系统来支持业务流程。因此，可以合理地期望软件的模型将以这样或那样的形式体现它应该支持的业务过程的模型。将业务建模工件映射到软件工件的想法很吸引人，在过去的三十年左右的时间里，人们一直在以不同的形式追求这个想法。管理信息系统的先驱们已经以高层业务功能和粗粒度信息系统块之间映射的形式将这种关系形式化（参见[CARL 79]）。虽然这种映射对高级别系统规划很有用，但对信息系统的实际开发帮助不大。业务流程管理和面向服务的体系结构的最新发展已经在相当大程度上弥合了业务分析师可以开发的流程模型与其在软件中的实际实现之间的差距（参见[OUYA 09]）。假设各种流程任务已经作为服务实现。如果他们不是，以及如何建立这些服务，摆在首位？我们认为，这是可能的，以开发分析模型的软件，从业务流程的描述，它的目的是支持[MILI 07]。这取决于我们解决两个挑战的能力，1）使业务分析师能够开发详细的流程模型，而不是将他们变成“BPMN程序员”，2）充分了解早期的系统分析决策，以实现它们作为模型转换。我们建议通过为业务分析师提供流程建模辅助工具来解决第一个挑战，这些工具可以帮助他们使用通用业务流程模型的目录和业务友好的流程定制/专业化操作符来指定详细的组织特定流程[MILI 09]。我们建议通过构建（过程->软件）模型映射辅助来解决第二个挑战，该模型映射辅助：a）将早期系统分析决策（软件的范围、目的和过程自动化的期望水平）编入法典，以及B）为最常见的选择提出软件模式[MILI 07]。

Organizations build sofware systems to support business processes. It is thus reasonable to expect that a model of the software would incarnate, in one form or another, a model of the business process it is supposed to support. The idea of mapping business modeling artifacts to software artifacts is an appealing one, and has been pursuded, in different forms, for the past thirty or so years. MIS pioneers have formalized this relationship in the form of a mapping between high-level business functions and coarse-grained information system blocks (see e.g. [CARL79]). While such a mapping was useful for high-level system planning, it provided little help in the actual development of the information system. Recent developments in business process management and service-oriented architectures have considerably bridged the gap between a process model that a business analyst could develop, and its actual realization in software (see e.g. [OUYA09])... provided that the various process tasks are already implemented as services. What if they aren't, and how to build those services, in the first place? We argue that it is possible to develop analysis models of a software from a description of the business processes it is designed to support [MILI07]. This depends on our ability to address two challenges, 1) enable business analysts to develop detailed process models, without turning them into 'BPMN programmers', and 2) understand enough about the early system analysis decisions to implement them as model transformations. We propose to address the first challenge by providing business analysts with process modeling aids that help them specify detailed organization-specific processes using a catalog of generic business process models, and business-friendly process customization/specialization operators [MILI09]. We propose to address the second challenge by, building a (process -> software) model mapping aid that, a) codifies the early systems analysis decisions (scope of software, its purpose, and the desired level of process automation), and b) proposes software patterns for the most common choices [MILI07].