This post originated from an RSS feed registered with Java Buzz
by Michael Cote.
Original Post: The Semiotics of Software Architecture:
Feed Title: Cote's Weblog: Coding, Austin, etc.
Feed URL: https://cote.io/feed/
Feed Description: Using Java to get to the ideal state.
Software architecture advocates, however, seldom speak about the social aspects, such as how the architecture can support discussions about the system, as well as between members of the development team, as between the team and the stakeholders. The architecture must be habitable; it must be a meaningful model of the problem domain; it must constitute a universe where every element conveys as much information about its role in the interactions with the other elements, in as small means as possible—where they are signs charged with information.
I have no idea what "semiotics" is, but I like the sound of the above.