patrickdlogan wrote:
I would interest to know whether people find it useful to talk about
processes and services as distinct concepts in an enterprise
architecture sense? Does it pay to make the distinction?
    
First, keep them distinct.

Second, define them because one person's definition of "process" is
likely to differ from another's.

We may need to make five or six things distinct, not just one or two.

-Patrick
+1.  We've already heard 2 completely different concept of process, haven't we.  Ash says, "The business people manage the processes, while the technology people manage the services", while Gregg says, "multiple services live in a single JVM process."

Mind you, this group's attempts at defining "service" have not been very successful to date, so we're just as likely to get mired down in definitions of "process".  Myself, I'd go for simplicity, and stay away from IT when thinking about it.  Something like:

service = work provided on a contract basis
process = a collection of related activities
-- 

All the best
Keith

http://keith.harrison-broninski.info


YAHOO! GROUPS LINKS




Reply via email to