Jamie's stag do

-- Posted from my iPhone

Eriksson-Penker Business Extensions to UML - Reference Card

 

 

http://amor.fri.uni-lj.si/dejan/delo/studenti/id/UML%20(Eriksson-Penker%20Business%20Extensions).pdf

 

SOA and BPM Exception Handling - Links

Implementing Exceptions in SOA

http://www.infoq.com/articles/lublinsky-soa-exception

 

Managing Exceptions in a SOA World

http://74.125.77.132/search?q=cache:pEOS_Pbb5xIJ:hosteddocs.ittoolbox.com/RR091605.pdf+soa+exception+handling&hl=en&ct=clnk&cd=3&gl=uk&client=firefox-a

 

BPM Exception Handling

http://www.workflowpatterns.com/patterns/exception/introduction.php

 

BPM Exception Types

http://www.workflowpatterns.com/patterns/exception/exceptiontypes.php

 

 

TDA - Technical Design Authority

 

What are the responsibilities of the TDA?

• Review the Solution Architecture
• Review the Architecturally Significant Scenarios
• Review the Architecture Quality Attributes
• Review any Architectural Risks and Issues

 

Why does the TDA need to do this?

• Validate Solution Architecture (Quality, Business Architecture Alignment and Requirements Compliance etc.)
• Validate Architecture Progress
• Resolve Architecture Issues
• Lead Architecture Direction
• Manage Technical Risks

 

Who is in the TDA?

• CTO
• Enterprise Architect (Lead)
• Solution Architect
• Business Architect
• Third Party Architecture Leads
• Key Business Stakeholders
• Programme/Solution Delivery Manager

 

When will the TDA meet?

 

·         A regular TDA Review Meeting will take place (frequency depending on programme size - fortnightly is suggested). 

 

How will the TDA Review Meeting function?

 

Two business days before the before the meeting the following will take place:

• TDA Lead to publish the TDA Review Agenda
• TDA Lead to publish Solution Architecture Document and related artefacts

Before the meeting begins:

• TDA Members to read TDA Review Agenda and prepare where appropriate
• TDA Members to read Solution Architecture Document and related artefacts

And during the meeting:

• TDA Lead to go through the agenda items, risks and issues
• TDA to discuss Solution Architecture, issues etc.
• TDA Lead to capture issues

 

service naming conventions

PPS - Portlet Presentation Service
APS - Ajax Presentation Service

BAS - Business Activity (/Process/Orchestrated) Service
FBS - Functional Business Service
UBS - Utility Business Service

LDS - Application Data Service
LDS - Logical Data Service
CDS - Canonical Data Service
PDS - Physical Data Service