System architecture team – what we have been done by now.

 As you remember, as part of the enterprise architecture process we formed teams to deal with system architecture (and development methodology). Until now we went over business and information architecture outcomes and kind of approve them. I think this process is important for 2 reasons:

1)      Those are the foundations of the team products so team members should be as much as possible familiar with those foundations. Discussing and proving helps team members to be much more familiar with those foundations.

2)      Approving process make team members more loyal to them. It’s not set of decision that made by others and they must follow it’s their work outcome.

If there are point in the business and information architecture that the group wouldn’t accepted I went back to the relevant team and trying to found compromise that both team agreed on (yes I can run to the congress, diplomacy and politics are my second name those days :- )) .

We already finished approving business and information points and now we discussing system architecture subjects (such as system structure, system type, communication between systems and system components, etc’). the process involved  attempt to find out which one of the suggestion subjects solutions, that put on the table, has better match business and information foundations.