Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Teaching software architecture principles in CS1/CS2
ISAW '98 Proceedings of the third international workshop on Software architecture
Objects, components, and frameworks with UML: the catalysis approach
Objects, components, and frameworks with UML: the catalysis approach
UML distilled (2nd ed.): a brief guide to the standard object modeling language
UML distilled (2nd ed.): a brief guide to the standard object modeling language
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
UML components: a simple process for specifying component-based software
UML components: a simple process for specifying component-based software
Software product lines: practices and patterns
Software product lines: practices and patterns
Experience with a Course on Architectures for Software Systems
Proceedings of the SEI Conference on Software Engineering Education
Software architecture at a large financial firm
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications
Best practice for grooming critical mid-level roles
Proceedings of the 2007 ACM SIGMIS CPR conference on Computer personnel research: The global information technology workforce
Question framework for architectural description quality evaluation
Software Quality Control
| Hi-index | 0.00 |
A large financial company, struggling with legacy systems that did not interoperate, performed a pilot project to teach software architecture to an enthusiastic application development team. Experienced mentors, including the author, worked with the application team for seven months to complete their engineering goal successfully. However, the mentors were unsuccessful in their attempt to train any of the six members of the application team to create architecture models on their own, though they were able to create them collaboratively with the mentors. This surprising result is due to the application team's strong preference for concrete artifacts over abstract ones. Even more surprising, an application developer from a different project, "Developer X", read the architecture modeling documentation on an internal website and, without mentoring, created architecture models within a few days. In light of this failure to teach software architecture, two short-term strategies are suggested for the use of software architecture in companies.