
doi: 10.1109/tse.2009.69
handle: 11562/1017639 , 11583/2281944 , 11567/284206 , 11582/6650
In recent years, several design notations have been proposed to model domain-specific applications or reference architectures. In particular, Conallen has proposed the UML Web Application Extension (WAE): a UML extension to model Web applications. The aim of our empirical investigation is to test whether the usage of the Conallen notation supports comprehension and maintenance activities with significant benefits, and whether such benefits depend on developers ability and experience. This paper reports and discusses the results of a series of four experiments performed in different locations and with subjects possessing different experience-namely, undergraduate students, graduate students, and research associates-and different ability levels. The experiments aim at comparing performances of subjects in comprehension tasks where they have the source code complemented either by standard UML diagrams or by diagrams stereotyped using the Conallen notation. Results indicate that, although, in general, it is not possible to observe any significant benefit associated with the usage of stereotyped diagrams, the availability of stereotypes reduces the gap between subjects with low skill or experience and highly skilled or experienced subjects. Results suggest that organizations employing developers with low experience can achieve a significant performance improvement by adopting stereotyped UML diagrams for Web applications.
Software/Software Engineering, Comprehension tasks Empirical investigation Graduate students Maintenance activity Maintenance software Model domains Performance improvements Reference architecture Software/software engineering Source codes UML diagrams UML extension UML stereotypes Undergraduate students WEB application, 150, Software Engineering, Documentation, Distribution Maintenance and Enhancement, Documentation; maintenance; and enhancement; software engineering; software/software engineering, 004
Software/Software Engineering, Comprehension tasks Empirical investigation Graduate students Maintenance activity Maintenance software Model domains Performance improvements Reference architecture Software/software engineering Source codes UML diagrams UML extension UML stereotypes Undergraduate students WEB application, 150, Software Engineering, Documentation, Distribution Maintenance and Enhancement, Documentation; maintenance; and enhancement; software engineering; software/software engineering, 004
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 68 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Top 10% | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Top 10% | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Top 10% |
