Applying the service-orientation model to building communities
rawn 100000R0P5 821 Views
I came across an interesting article in the current issue of THE FUTURIST magazine titled Extra-Preneurship: Reinventing Enterprise for the Information Age. The article by David Pearce Snyder, former CIO of the US Internal Revenue Service, starts out:
"Information technologies are toppling traditional hierarchical business-management systems. The new model for twenty-first-century management will be extra-preneurship--virtual networks based on collaboration and self-actualization that will add value to all current and future jobs. THE FUTURIST's Lifestyles Editor describes what this shift will mean for individuals, corporations, and the world economy."
What I found interesting was not the expounding on Linux, the open-source model, etc., that we have all heard before but the need to consider that the nature of how people work is changing. In particular the idea of "extra-preneurship" where the traditional structure of businesses are transforming into virtual collaborative networks.
I gainsay, this has relevance to one of my other continuing interests of service-orientation in business (and technical models).
Think of it: consider the specialization of work functions into specific tasks or task areas, each as a type of service. On the pure software level, services are very strictly defined, but on a business level, they exist as well. A combination of services therefore becomes a process flow (in business and in software).
A virtual collaboration can also be thought of as a workflow of processes and services, from simple levels such as consulting, to more complex multi-organization workgroups (e.g., standards organizations).
These collaborations are specific communities and uses of a community model. In fact, they integrate their human element services (thoughts, interactions, communications, contracts,
expertise, etc.), with software services (blogs, forums, instant messaging, wikis, etc.)
From a high-level, these services blend across each other into useful workflows that are arranged and rearranged per the needs of the users themselves. This is the same process that applies service-orientation to business and IT operations.
What may be missing is a development environment to build such communities with such workflows. Just like we have tools for business analysts to define process flows, and developer tools to define sequence diagrams, we need tools that allow a user to build such workflows out of the available members of a community, the available software services of the community, and the necessary means to arrange them together and define rules of behavior.