Hey, where's the option for 'a legally binding document that requires the architecture team to deliver something amazing... or else'? Now that would be a real architecture contract!
I think Option C hits the nail on the head. The contract is about establishing the guidelines and ground rules for developing the enterprise architecture. Keeps everyone on the same page.
Haha, Option D is totally off base. A timeline? That's not what an architecture contract is all about. Maybe the test writer was having a bit of fun with that one.
I was leaning towards Option B, but after reading it again, I'm not so sure. Communicating the architecture info is important, but I don't think that's the primary role of the contract.
Option A sounds about right. The architecture contract is an agreement between the key stakeholders on what the architecture deliverables will be. Seems pretty straightforward to me.
Val
16 days agoDahlia
2 days agoAleta
26 days agoGlendora
29 days agoMona
4 days agoAlise
1 months agoAmmie
9 days agoDoyle
21 days agoLeslee
2 months agoBoris
2 months agoRoyce
2 months agoAnthony
2 days agoCristina
3 days agoMarta
14 days agoFrankie
16 days agoKarma
19 days agoClorinda
1 months agoMelissia
1 months agoWilford
1 months agoLeslee
2 months agoDick
2 months agoCarmen
2 months agoDick
2 months ago