ArchJava is a descriptive architectural language that builds on top of Java. It ensures that anything written in its language does not violate the architecture, for example, communication modules is only possible where these points are defined.
This could be helpful as it builds on top of the type safety to prevent the programmer from violating the architecture, make it easy to diagram the architecture and easier to refactor.
However, as it stands now, it would need several improvements to be used commonly. The architect still has to write code in the language, or teach others how to. The graphing was not shown in the paper, and being able to visualize makes it much easier to understand architecture than looking at a definition in code.
Perhaps the biggest limitation is the inability to coordinate between multiple projects. This makes it impossible to use to describe the architecture for some projects, such as the Making Memories architecture described in the previous post. It could not describe the communication between the sides and the rendering farm, or between third party applications. Any comments?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment