The service librarian role is no different than a real librarian. It's the person who knows what services are available to the enterprise and is able to help projects identify what services will meet their needs. It is not the same person as the provider. This role may not be necessary if the enterprise has a very good repository and the appropriate processes to make sure it's used appropriately. Odds are, some form of governance board will act in this capacity.
The schema librarian role is very similar, but it's more focused on XML schemas and ensuring consistency. This role is also responsible for industry standard schemas that may be appropriate to the enterprise. Finally, the business process analyst should be self explanatory. Rather than traditional project analyst, the role of the business process analyst is to identify business processes. -tb --- In [email protected], Hitoshi Ozawa <[EMAIL PROTECTED]> wrote: > > Todd, > Would appreciate if you'll provide a simple explanation and duties of > the roles you've mentioned. > > H.Ozawa > > Todd Biske wrote: > > > The first ones that came to mind are: > > > > > > Service Librarian > > Schema Librarian > > Business Process Analyst > > > > -tb > > > > On Aug 23, 2006, at 7:51 PM, jeffrschneider wrote: > > > >> What new roles are people identifying in a SOA-centric I.T. > >> organization? > >> Jeff > >> > > > > > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
