BA defines the "problem"; architect defines the "solution".
-cca(不归的如来佛);
2010-7-29{327}(#6201883@0)
BA and architect can be a same person, but still different roles.
"A problem well stated is a problem half solved." -- so BA is important.
Nonetheless, it's dangerous to dictate solution in problem definition. Some tech savvy BAs tend to do that. It's better for BAs to be tech-idiots -- but not always possible.:-)
I though a BA is to analyze the business processes, procedures,org structures etc. in order to identify problems, needs and determine solutions...
-thornthorn(Holy Moly);
2010-7-29(#6202010@0)
+1
-catia(No Comments);
2010-7-29(#6202022@0)
BA defines "What", doesn't define "How".
-cca(不归的如来佛);
2010-7-29{261}(#6202890@0)
For example: "Go to North Pole" is a requirement, or a "What", or a "Problem".
"Fly to Calgory, take a train to Yellow Knife, chat with a native girl and get her to give you a ride to the North Pole on a dog sled." -- This is "How", or a Solution.
Define and identify have very different meanings.
-thornthorn(Holy Moly);
2010-7-29(#6203000@0)
Geniuses get it from the spirit; dummies take it to the letter. :-)
-cca(不归的如来佛);
2010-8-7{80}(#6216120@0)
Even Holy the Smart can occasionally be dumb:-). No offence -- don't be upset.