h1. UBPL Introduction
通用的商业处理文库介绍
h4. Why a Universal Business Process Library?
为什么需要通用的商业处理文库？
The general idea is to create something like the "Universal Data Model", and that will continue to provide the basic business information concepts that we all use on a daily basis. Instead of for data structures, this would be for business processes.
通常的观点是建立一些像通用数据模型的东西，并且将会继续提供一些在我们日常生活中用到的基本的商业知识概念。不是为了数据结构，而是为了商业处理过程。
I've spent some time over the years, and others I work work have spent some time more recently, trying to find some sort of business process library we could base this on, but with no real luck. The closest things I've found are some semi-helpful books about business best practices, and documents created as a part of a number of business related specifications. I've started a page with those here:
[Resources with Information about General Business Processes]
我已经花了超过数年，除此之外在工作中也花费一些时间，试图去找到某种我们可以基于此的商业数量文件，但是，不幸的是。我已经找到的最接近的事情是一些几乎没用用的商业实战书籍，与特定商业相关的文档，所以我开始了这些页面的书写。
【通用商业处理过程的资源信息】
Still, these are not adequate for our needs, and even if they were I think we would want something that the community could get behind to maintain and expand, and also tie these artifacts to actual things that exist in Mantle. So, here we are, a few things I've thrown together to start assembling a Universal Business Process Library:
尽管如此，这也不能满足我们日常的需求，尽管如此我认为我们可以从中获取一些东西通过团体的维护和扩展，并且将这些人工产品与Mantlezhong中真实存在的联系起来。我们，我们开始组装一些通用商业处理文库。
[Universal Business Process Library Index]
【通用商业网处理文库索引】
This isn't meant to include everything that every business might do, but to be a library of general business activities that make up common processes that are shared by a wide variety of businesses. Some may of course be less commonly used, but the general intent will be similar to that of the rest of Mantle, ie things that can be customized and reused or used as-is for a wide variety of businesses to help with their process automation efforts.
这些。并不意味着包含所有的可能存在的商业，而是一个通用的由普通的处理过程构成的商业行为文库，这些通用的商业处理过程是由很多的企业分享的。一些可能很少使用，但是普通的意义是与mantle中一样的，是通用的在大部分企业中，可以帮助他们处理一些自动流程。
h4. What is in this Library?
在文库里有什么？
This library will consist of Business Process Stories. These stories are basically a series of sentences, each one consisting of an actor and an action. Just keep that in mind, it's _always_ actor and action, actor and action, actor and action. Hopefully that's clear... ;) All sentences need both, and may have conditions on them and other things as well, but always need an actor and an action. One basic rule based on that is no actions with actors.
文库将会包含商业处理故事。这些故事是一些基本的系列句子，每一个句子包含一个行为和一个动作。请记住这些，它总是行为者和行为，行为者和行为。希望这是清晰的，所有的句子都需要两个，可能存在条件或者别的事情，但是总是需要一个行为者和动作的。一个基本的原则是没有行为者就没有动作。
The top level document has 3 main parts:
最开始的文档含有3个主要的部分：
1. Actor Definitions
行为者定义
2. General Business Process Stories
通常的商业流程故事
3. Stories for Specific Types of Organizations
一些特殊组织的故事
In part #2 we'll create the library of smaller stories that make up parts of the higher level stories that are in #3. For example, look at the Story of Retail Company:
在第二部分里我么将要创建一些比较小的故事这些小的故事将会组成在第三部分中更高等级的故事。比如，零售公司的故事。
[Story of Online Retail Company]
在线零售公司的故事
There are a lot of high level steps in that story that describe general business activities. These are assembled in a way that makes sense for a retail company, but many of the individual activities are just as applicable in different parts of the high level stories for other types of organizations.
这里有很多的用于描述通常的商业行为的高级步骤。它们组装起来是的一个零售公司有意义，但是很多的个体行为仅仅是适用于别的类型的组织的高级故事的一部分。
Again, part #2 has smaller scoped processes that can be reused in many different types of companies, and based on writing stories for specific types of organizations we'll flesh that out to include a wide variety of business activities organized according to yet higher level business concepts, like the Marketing, Sales, Warehouse Management, etc that are currently in there.
在第二部分中有一些小的可以用于许多不同类型的公司的范围处理过程，他们的基础是书写一些特殊类型的组织包括根据更高商业概念的商业行为组织，比如市场营销，销售，仓库管理等等。
In part #2 each of these process names should also include both actor and action, and for higher level things like this the actor should be the "primary" actor for the story, there will certainly be other actors involved in most of them.
在第二部分中，每一个行为都应该包含行为者和动作，在更高等级的时候行为者应该是故事中主要的部分，将会包含别的行为者在其中。
h4. Concepts Behind This, and "HEMP"
这些之后的概念
The idea of using stories (aka "narratives") like this is a common one. Part of the reason for writing them specifically in the way I've described here is to make them a good starting point for further UI and system design efforts.
For those interested, this is based on a lot of research I've done over the years while trying to work more effectively with clients, and have written a book on that topic called "HEMP: An agile approach to analysis and design". HEMP stands for "Holistic Enterprise Mechanization Process".
On a side note, a better word for "mechanization" is "automation", but I thought HEMP would make a more colourful and interesting title than "HEAP".
像这样使用故事的观点是很普通的一种方式。以这种特别的方式去书写的一部分原因是使他成为一个未来UI和系统设计流程的起点，:一个冥敏捷的分析和设计方法，：HEMP:企业整体自动化处理。
另一方面，一个更号的描述机械化的词是自动化。但是为认为HEMP可能会比HEAP更多彩和有趣。
The book and other details are available at: [http://www.dejc.com/HEMP]
因为这些兴趣，这是基于我这几年使用客户端试图使得工作更加有效的的研究，并且写了一本关于此观点的书叫HEMP：
h4. A Special Note on Testing
测试的特别标注
The requirements and designs that come out of this effort will also help drive automated and manual testing efforts. Sometimes a problem with testing is we don't know what to test, or what the business activities the software is trying to support. This will help with the problem.
Along with these business process stories we may want test scenarios based on them, that are linked to from the stories. There may be many things linked to from these stories actually....
从这一流程里粗变的需求和设计同样会帮助驱使自动化测试流程。有些时候测试的问题是我们不知道去测试什么，或者软件支持什么样的商业行为。这将会帮助我们解决这些问题。
连同这些商业流程故事一起我们可能需要一些基于他们的测试脚本，实际上与这些故事有关的还有跟多的事情。