Added by Thor Henning Hetland, last edited by Thor Henning Hetland on Nov 20, 2008  (view change)

Labels:

glossary glossary Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

Human 2 Application Services

Human 2 Application Services

Human 2 Application Services is services involving key user interaction components with one or more humans to fulfill some activity/workflow. For example a booking process or a manual shipment process,
Suggestion for a more precise definition

A H2A service is an implementation of a use-case/user story

  • which implements one, and only one human actor

Characteristics

Workflow-oriented Services which require human interaction

  • Long running transactions
  • Most services start as H2A Services
  • Automated on a ROI basis
  • Non-trivial decisions points that require 'human touch'
  • Starting-point/front-end of externalized processes

Patterns for Human 2 Application Services

Human 2 Application Services

Technology/Implementation strategy (Java)

Technology, Implementation and products

  • Buy specialized product if close match to requirements
    • (K2.NET)-alike products
  • Build portal upon best-of breed (JSR 168/286)
    • SiteVision, Vertical Site, CorePortal (Norwegian CMS and JSR 168 products)

Technology/Implementation strategy (.NET)

Technology, Implementation and products

  • Windows Forms
  • Microsoft Office (as smart client)
  • Pure ASP.NET
  • MOSS (Sharepoint platform) incl. Sharepoint Designer for H2A workflow
  • Enterprise Human Workflow with K2.NET / Skelta/ Captaris++
  • Portal connectors useful

Design rules

P1. A service shall have one named owner
P1. A service shall have one named owner
P2. A service shall provide documented business value
P2. A service shall provide documented business value
P20. All services shall be in the service universe
P21. A service shall be categorized (OW SOA category)
P3. A service shall do one only thing, and one thing well
P3. A service shall do one only thing, and one thing well
P4. A H2A service (webpart or portlet) shall be an independent component
P4. A H2A service (webpart or portlet) shall be an independent component
P41. A service shall provide heartbeat and traffic monitoring
P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services
P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services
P6. A H2A service shall not have internal workflow
P6. A H2A service shall not have internal workflow
P7. Too generic webparts or portlets shall be avoided
P7. Too generic webparts or portlets shall be avoided
P90. A service shall have a documented coupling to the contractual and requirement for service usage
P90. A service shall have a documented coupling to the contractual and requirement for service usage

Other technical details