|
|
|
|
|
|
|
|
|
|
|
|
|
|||||||||
|
|
|
|
|||||||
|
|
|||||||||
|
|
|
|
|
|
|
|
|
|
|
Why Can't They Create Architecture Models Like "Developer X"? An Experience ReportGeorge FairbanksThe 2003 International Conference on Software Engineering (ICSE'03), Portland, Oregon, USA, May 3-10, 2003.
|
|||||
| Abstract | |||||
| 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 who completed their engineering goal successfully. However, the mentors were unsuccessful in their attempt to train any of the six members of 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 good 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 and long-term strategies are discussed. | |||||
| Keywords | |||||
|
|
Last modified: 6/25/2003. For comments and problems, contact able-help@cs.cmu.edu.