Is Knowledge Management (KM) a problem that can be solved by a single application, or a collection of interfaced applications? These designed specifically to solve an individual Business Process (BP) task. In my opinion it is the latter choice.
KM is a collection of applications held together by SOA that is hooked tightly to a Workflow Process (WF). The WF is a collection of scheduled business rules and polices that drive a product to its completion. Along the way Data Repositories will be used to store and version data.
The product will be reviewed, tested, inspected and verified that is under budget and on time. That is the dream / goal.
Let's look at the buzzwords and see what kind of exercise this becomes:
1. KM - Potentially a single UI that delivers data at exactly the time needed
2. BP - Business Process, the well-known steps to build your widget.
2. SOA - Service Oriented Architecture. The rules, definitions, standards, interfaces that connect objects together. It is the processing lines in the flowchart.
3. WF - Work flow - All the required process steps to produce a product
4. Schedule - A time-line, calculated to offer the most profit, that a WF is tied into
5. Data Repository - A safe and secure area to keep either meta-data or physical files. Generally there will be security rules around the content.
Whew! I will start tackling some of these in future articles. Next I am going to do something fun and share a little code.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment