Kdo je to “software architect”?
Otázku poněkud rozvláčně rozebírá esej Magnuse Mårtenssona, naštěstí se dá ale zjednodušit na 4 body:
- User experience: na konci našeho snažení je vždycky uživatel (jasně, kritérium je trochu slabší u low-level programování)
- Komunikace: !!!
- Technologie: na tom se asi všichni architekti shodnou
- Umění: … a na tomhle taky, a zálibně si přitom pomlasknou
K té - často podceňované - komunikaci:
The architect can never sit behind closed doors and expect to succeed. The architect must be out there every day, communicating with stakeholders, in order to perform the job function with excellence. Wait, isn’t this the project manager that I am writing about now? No. The day-to-day tasks of the person who is doing the architecture quite often cross over into the realm of the manager. Also, I am a firm believer that each person on any team has to do everything possible to further the project. If that means the lines between roles become fuzzy, then so be it. The exact line is hard to define and is based on the needs of the organization.
A odkaz na Cockburnův článek The end of software engineering and the start of economic-cooperative gaming taky potěšil.
Možná by se Mårtenssonovo pojednání dalo zjednodušit na jednu větu: softwarová architektura je o komunikaci. Zbytek je tak nějak jasný.
