Telemarketers make use of a telescript - a guideline for a telephone conversation. This script creates an imbalance in the conversation between the marketer and the consumer. It is this imbalance, most of all, that makes telemarketing successful. The EGBG Counterscript attempts to redress that balance.
http://www.xs4all.nl/~egbg/counterscript.html
MOF is designed as a four-layered architecture. It provides a meta-meta model at the top layer, aka the M3 layer. This M3-model is the language used by MOF to build meta-models, called M2-models. The most prominent example of a Layer 2 MOF model is the UML meta-model, the model that describes the UML itself. These M2-models describe elements of the M1-layer, and thus M1-models. These would be, for example, models written in UML. The last layer is the M0-layer or data layer. It is used to describe real-world data.
I plan to include references to all standards that I review, so here is the list of links related to MOF and the MDA.
| |  |
Jack explains that "Not only is he using the wiki as a repository, but he's also integrating other tools to share information between the wiki and those other tools. This is one of the central ideas of knowledge and content management: the ability to reuse the same stuff in many different ways."
I always like solutions that are simple, easy to implement and get started, scalable, easy to change, etc... even if you have to renounce more sophisticated aspects, such as security, e-mail integration, etc...
]]>First, let's look at why there is a need for process management in the first place. Whether a company sells a product or service, all of its business processes exist for one primary reason, which is to drive the sale. In other words, the cost of any sale is the cumulative effect of all the business processes in the organization. For instance, if the cost of hiring an employee is high, then the cost of the sale goes up.
http://www.bpminstitute.org/articles/article/article/backwards-bpm-start-with-the-end.html
Even if almost two and a half years have passed lots of the ideas explained in it (once again by Paul Harmon) are still valid. Specially interesting is the BP Trends Enterprise Architecture Pyramid.
In metoCube we conceive a process as a set of tasks in which a role (maybe using one system) creates or modifies one or more objects.
Two major families of approaches can be distinguished: activity-centric and business object- centric. These approaches correspond to complementary viewpoints. We see great potential in creating a level of integration between them.
]]>