Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History
Policy Advisory Board is a specialized Center of Excellence organ, focusing on the round trip of keeping the design-time governance policies aligned with the company goals, people and competences.

See also [Governance] for more details on Governance. This content is build on content from http://wiki.community.objectware.no

P.A.B. Meeting

Participants

  • IT Manager
  • Company Chief Architect
  • Service Owner
  • Project Lead Architect
  • Central PAB-issue stakeholders

PAB Meeting Agenda

  • Intro PAB
  • Presentation of the PAB issue
  • Stakeholder analysis

Example Service Policy QA meeting

Agenda

  • Presentation of the H2A Services [MyCustomer H2A Services]
  • Policy QA of each of the services
    • [Design-Time Governance for H2A Services]
    • [Design-Time Governance for A2A Services]
    • [Design-Time Governance for ACS Services]
    • [Design-Time Governance for CS Services]
    • If non conformance
      • if the team challenges the policy
        • register issue i Jira PAB project
      • if the team accepts the non-conformance as a design/implementation flaw
        • create plan for compliance
  • New policy suggestions
    • Document as Jira PAB issue
    • New rules is documented with the terms from RFC2119 (MUST/SHOULD/CAN etc)
  • Aggregated conclusion from the QA process

SOA Design rules

Policy Rules for Human to Application Services (H2A)

Policy Rules for Application to Application Services (A2A)

Policy Rules for Aggregated Core Services (ACS)

Policy Rules for Core Services (CS)

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.