Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

The definition of an Information Architect's responsibilities seems to fit neatly with the definition of 'model' in the MVC pattern. But I've never heard the two concepts discussed together.

In a large project that has a dedicated Information Architect as well as a team of developers, does the Information Architect actually say "Model A has properties x, y, and z and has foreign keys to Models B and C..." etc, or do they just express the concepts more vaguely and let the development team translate this into MVC models?

Just wondering what is the most common practice.

share|improve this question

closed as primarily opinion-based by MichaelT, GlenH7, Kilian Foth, Dan Pichelman, gnat Mar 14 at 21:09

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

Can whoever downvoted please let me know why this is a bad question? –  callum Feb 9 '12 at 15:01
I didn't downvote, but given organizational variations, it's hard to imagine a correct answer. In my experience, few organizations agree on titles. If they do, they don't agree on the title's responsibility. Wikipedia's information architecture article acknowledges the "difficulty in establishing a common definition." This is complicated further because organizations can't even agree on what, exactly, MVC entails. Maybe state your definitions explicitly to eliminate any confusion? –  Corbin March Feb 9 '12 at 16:13

2 Answers 2

up vote 6 down vote accepted

Your instinct isn't incorrect, in that on paper some roles played by an Information Architect would seem to benefit technical development using MVC. But in reality this isn't the case, as the IA typically plays a role at a much more abstract level (relative to the technical details): gathering and organizing data to convey meaning, usually in the form of requirements handed off to other parties for technical implementation (front-end, back-end, etc).

There may be times when you have someone playing the role of IA who is also a programmer (it happens -- I am one of those weirdos). In that case, you may find yourself having fruitful discussions regarding the definitions of models within an IA context, but ultimately that work falls within the purview of the technical development team.

share|improve this answer

No, information architecture should stay at a much higher level. Their role is to define how the pages logically lay out and how things interact with each other which probably drives the design of the model and the application as a whole. But specifying what properties a certain model has is way too granular for the IA, if they even understand development on that level.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.