Citation Context

...s assignmentspublic class TestSuite provides role TestCreator;sACM SIGSOFT Software Engineering Notes Page 10 March 2008 Volume 33 Number 2 4.6sTestRun (Command Pattern)sFollowing the Command pattern =-=[4]-=- and according to [2], a Client calls run on a test to run that test. It provides a collecting parameter, asTestResult object, to track what’s happening as the test run progresses.spublic collaboratio...

Citation Context

...n Role modeling (in the context of object-oriented software design) was invented over 20 years ago [1]. It is related to the CRC (Class Responsibility Collaboration) cards approach to software design =-=[2]-=-. In recent years, role modeling has made its way into UML where it is called collaborations. My dissertation about role modeling for framework design [3] showed that role modeling makes designing, do...

Citation Context

...code composition and implementation. Ansearly exception is Johnson’s work on documenting frameworkssusing design patterns. He shows how a framework can be viewedsas a sequence of pattern applications =-=[6]-=-.sOn a level closer to implementation, Fairbanks et al. show howsframeworks can be decomposed into and then recomposed fromsdesign fragments that are closely linked to code fragments [3].sLike Johnson...

Citation Context

...ollaboration is VanHilst and Notkin’sswork of collaborations. Using C++ templates they show how tosbreak up a program into collaboration components and how toscreate new programs from these templates =-=[14]-=-. This paper doessnot prescribe a specific implementation mechanism.sAnother attempt at code composition, foreshadowing aspectoriented programming, was Ossher et al.’s work on subjectoriented programm...

Citation Context

...trieve information from a TestResult object. Errors and Failures are collected, and statistics about them are provided. The TestResult collaboration is an instance of the Collecting Parameter Pattern =-=[8]-=-. The TestResult object is passed through the test case hierarchy while running the tests. It is important to note that the Creator and the Client are typically different objects, as the Creator role ...

Citation Context

...laboration) cards approach to software design [2]. In recent years, role modeling has made its way into UML where it is called collaborations. My dissertation about role modeling for framework design =-=[3]-=- showed that role modeling makes designing, documenting, and using frameworks easier than possible with the traditional class-based approach alone. UML 2.0 provides support for developers to document ...

Citation Context

..., foreshadowing aspectoriented programming, was Ossher et al.’s work on subjectoriented programming. Subjects are functional slices through asprogram that can be used to explain and specify a program =-=[9]-=-.sOssher et al. followed up with detailed implementation support.sAspect-oriented programming (AOP) is related to collaborationbased design: A collaboration can be viewed as an aspect andshence subsum...

Citation Context

... applications [6].sOn a level closer to implementation, Fairbanks et al. show howsframeworks can be decomposed into and then recomposed fromsdesign fragments that are closely linked to code fragments =-=[3]-=-.sLike Johnson’s patterns, Fairbank et al.’s fragments are onlysloosely related to the notion of collaboration as used in this paper.sCloser to my notion of collaboration is VanHilst and Notkin’sswork...

Citation Context

...otion of collaborations as used insthis paper, the work of Lieberherr et al. on aspectual collaborationssuses AOP techniques and shows how programs can be composedsfrom these aspectual collaborations =-=[7]-=- [8].sACM SIGSOFT Software Engineering Notes Page 1 March 2008 Volume 33 Number 2 10.1145/1350802.1350812 The notion of collaboration used in this paper is based on my dissertation [11]. This paper us...

Citation Context

... and using frameworks easier than possible with the traditional class-based approach alone. UML 2.0 provides support for developers to document objects as playing roles and engaging in collaborations =-=[4]-=-. However, it is still an evolving specification and is limited when it comes to full-blown role modeling. For this reason, this document uses a lightweight UML-based approach to describe the JUnit 3....

Citation Context

...everal roles.) Free roles in Java are typically interfaces--otherwise the free assignment would not be possible. We discuss the importance of free roles for framework and component coupling elsewhere =-=[5, 3]-=-. The definition of role given above also implies that a collaboration specification can never have just one role; there must at least be two roles. If you can’t find that second role: It may well be ...

Citation Context

...te thatsthe top four classes in Figure 3 are classes defined in java.lang and presented here only for reasons of completeness. For another documentation of JUnit please see the original “cook’s tour” =-=[6]-=-. Figure 3: The class diagram of the JUnit 3.8 junit.framework classes. In a nutshell, JUnit works the following way. A complete test run has two phases: The first phase is configuration, second phase...