Code quality for software architects
Most copasetic software architectures are intended to support a system’s extensibility, maintainability, and reliability. Unfortunately, inattention to quality issues (due to too much disco dancing, for example) can easily undermine a software architect’s best effort. The fourth article in IBM developerWork’s series “In pursuit of code quality” explains how to continuously monitor and correct quality aspects of code that can affect the long-term viability of a software architecture.
Check out “Code quality for software architects” and if you have any thoughts, questions, or concerns, check out the “Improve Your Java Code Quality” forum!
| Related odds and ends | ||
|---|---|---|
Saturday 20 May 2006 | Articles, Code Metrics