The purpose of this study was to understand the meaning of change through therapeutic enactment in psychodrama. Existential and hermeneutic phenomenology conducted from the perspective of a dialectic between storied narrative and thematic analysis was used to investigate the essential meaning of the experience. Eight co-researchers who had experienced significant change through therapeutic enactment in psychodrama were interviewed in depth. Transcripts from these interviews were transposed into narrative form in order to straighten the story of change through enactment in a before, during, and after sequence. These eight individual narratives were validated by the co-researchers. An independent reviewer checked each narrative against the original transcript, video tapes of the enactments, and comments of each co-researcher for trustworthiness. Each validated narrative provided a rich description of the lived experience of change through therapeutic enactment. In addition, fifty-nine (59) essential themes were formulated from the individual narratives: Fourteen (14) in the planning stage, twenty-four (24) in the enactive stage, and twenty-one (21) in the reflective, or integrative stage, of the enactment process. These themes were then woven into a common story representing the pattern and meaning of change through therapeutic enactment for this group of co-researchers. Finally, notations made during the transposing of the transcripts into personal narratives, formulation of the essential themes, and construction of the common story were used to develop a theoretical story of change through therapeutic enactment, as a final level of hermeneutic interpretation. This theoretical story was then presented in summary form as a thematic sequence of multi-modal change processes representing a model of change through therapeutic enactment. The results of this study suggested numerous theoretical and technical implications. Foremost among theoretical implications was the suggestion that Tomkins (1992) script theory of affect may best illuminate the effects and processes of psychodrama and enactment. This study also had implications for interactional theories of development, contemporary psychoanalytic theories of interpersonal functioning, theories of moral development, theories of dream functioning, and ethological theories of myth and ritual. The results of this study also suggested a number of additional qualitative and comparative outcome studies for future research.

No description available.

Use Case modeling has been constantly gaining popularity as the technique of choice for eliciting and documenting functional requirements. The deployment of Use Case models in industry has resulted in many positive experience reports being published. The inclusion of Use Case modeling into the Unified Modeling Language (UML) (OMG 2005) has aided its widespread use in industry, especially within the object-oriented community. One of the most attractive aspects of Use Case modeling is its technical simplicity, allowing stakeholders with differing backgrounds, to have a common understanding of the requirements. This technical simplicity can be deceptive, as many modelers create models that are incorrect, inconsistent, and ambiguous and contain restrictive design decisions. In Use Case driven development processes, Use Case models are used to drive the design and test phases. While a number of techniques have been proposed to develop test cases from Use Case models, these techniques tend to suffer from two major shortcomings. The techniques are technically too complex to be effectively used by its potential users (business analysts and customers); and the inability to use these techniques in the early stages of development. This thesis describes work tackling these deficiencies. Support for developing higher quality Use Case models is achieved by developing a modeling syntax that ensures consistency when constructing Use Case models. A controlled experiment was performed to empirically evaluate the effectiveness of using the modeling syntax. In addition, a technique based on utilizing antipatterns to detect potentially defective areas in Use Case models was developed. The technique prompts modelers to revise and remedy poor design decisions, yielding superior quality models. Finally, a framework was developed, which utilizes Use Case models, to develop acceptance tests. The framework was designed to account for the technical abilities of its potential users. / Software Engineering

How effective is a notation in conveying the writer's intent correctly? This paper identifies understandability of design notations as an important aspect which calls for an experimental comparison. We compare the success of university students in interpreting business process descriptions, for an established graphical notation (BPMN) and for an alternative textual notation (based on written use-cases). Because a design must be read by diverse communities, including technically-trained professionals such as developers and business analysts, as well as end-users and stakeholders from a wider business setting, we used different types of participants in our experiment. Specifically, we included those who had formal training in process description, and others who had not. Our experiments showed significant increases by both groups in their understanding of the process from reading the textual model. This was not so for the graphical model, where only the trained readers showed significant increases. This finding points at the value of educating readers of graphical descriptions in that particular notation when they become exposed to such models in their daily work.

The purpose of this study was to understand the meaning of change through therapeutic enactment in psychodrama. Existential and hermeneutic phenomenology conducted from the perspective of a dialectic between storied narrative and thematic analysis was used to investigate the essential meaning of the experience. Eight co-researchers who had experienced significant change through therapeutic enactment in psychodrama were interviewed in depth. Transcripts from these interviews were transposed into narrative form in order to straighten the story of change through enactment in a before, during, and after sequence. These eight individual narratives were validated by the co-researchers. An independent reviewer checked each narrative against the original transcript, video tapes of the enactments, and comments of each co-researcher for trustworthiness. Each validated narrative provided a rich description of the lived experience of change through therapeutic enactment. In addition, fifty-nine (59) essential themes were formulated from the individual narratives: Fourteen (14) in the planning stage, twenty-four (24) in the enactive stage, and twenty-one (21) in the reflective, or integrative stage, of the enactment process. These themes were then woven into a common story representing the pattern and meaning of change through therapeutic enactment for this group of co-researchers. Finally, notations made during the transposing of the transcripts into personal narratives, formulation of the essential themes, and construction of the common story were used to develop a theoretical story of change through therapeutic enactment, as a final level of hermeneutic interpretation. This theoretical story was then presented in summary form as a thematic sequence of multi-modal change processes representing a model of change through therapeutic enactment. The results of this study suggested numerous theoretical and technical implications. Foremost among theoretical implications was the suggestion that Tomkins (1992) script theory of affect may best illuminate the effects and processes of psychodrama and enactment. This study also had implications for interactional theories of development, contemporary psychoanalytic theories of interpersonal functioning, theories of moral development, theories of dream functioning, and ethological theories of myth and ritual. The results of this study also suggested a number of additional qualitative and comparative outcome studies for future research. / Education, Faculty of / Educational and Counselling Psychology, and Special Education (ECPS), Department of / Graduate

<p>UML and use case modeling have the last few years received much attention. Use cases are used to describe the functional requirements of a system and a use case diagram shows the relationships among use cases and actors within a system. The semantics of use case diagrams are, however, often unclear. The aim of this dissertation is to point out ambiguities and limited expressiveness present in the current use case notation of UML and to indicate in which directions remedies to these deficiencies may be sought.</p><p>Problems reported by researchers were identified and presented to a set of use case practitioners. Then a proposal of possible improvements of the use case notation, which should reduce the ambiguities and increase the expressiveness in the notation, was developed. To place some measurements on the value the proposal can have in practice, it was also presented to a set of practitioners.</p><p>The proposal provides a suggestion of how to model various tricky situations in a use case diagram. Furthermore, the dissertation gives insight on how the use case technique is used in practice. Practitioners argue that the use case specifications are more important than the use case diagrams. They also argue that the purpose of use case diagrams is to describe a system's main functionalities and not details, and that as few use case relationships as possible should be used in use case diagrams.</p>

UML and use case modeling have the last few years received much attention. Use cases are used to describe the functional requirements of a system and a use case diagram shows the relationships among use cases and actors within a system. The semantics of use case diagrams are, however, often unclear. The aim of this dissertation is to point out ambiguities and limited expressiveness present in the current use case notation of UML and to indicate in which directions remedies to these deficiencies may be sought. Problems reported by researchers were identified and presented to a set of use case practitioners. Then a proposal of possible improvements of the use case notation, which should reduce the ambiguities and increase the expressiveness in the notation, was developed. To place some measurements on the value the proposal can have in practice, it was also presented to a set of practitioners. The proposal provides a suggestion of how to model various tricky situations in a use case diagram. Furthermore, the dissertation gives insight on how the use case technique is used in practice. Practitioners argue that the use case specifications are more important than the use case diagrams. They also argue that the purpose of use case diagrams is to describe a system's main functionalities and not details, and that as few use case relationships as possible should be used in use case diagrams.

A prática de reuso, apesar de ser universalmente e reconhecidamente aceita como uma boa prática, ainda não atingiu um estágio de maturidade satisfatório nas instituições. Em particular, a definição e a construção das interfaces com o usuário (IHC) ainda carecem de abordagens efetivas e sistemáticas de reuso, mesmo se comparadas com as práticas já existentes de reuso dos demais artefatos de software. O objetivo deste trabalho é duplo: investigar abordagens de reuso de interfaces do usuário (IHC), analisando-as do ponto de vista da sua aplicabilidade, adequação e integração em um processo de desenvolvimento de software baseado na UML e propor uma abordagem de reuso de artefatos de software interativo dirigida por casos de uso, integrando – por meio de alguns aspectos do ciclo de vida de casos de uso (da modelagem à implementação) – vários conceitos e técnicas de reuso bem conhecidos como padrões de casos de uso, padrões de interação e padrões de projeto. O foco principal é a definição de como promover o reuso de interface com o usuário baseado em padrões e de como usar e implementar esses padrões através do reuso de código e/ou de componentes. / Reuse practicing, although universally and recognizably accepted as good practice, hasn’t reached a fair maturity level in organizations. Specifically, the definition and construction of user interfaces (HCI) lack effective and systematic reuse approaches even when compared with other reuse practices used nowadays. This work has a dual-purpose: to make a survey of reuse approaches of user interfaces (HCI) and their applicability in a development process based on UML, and to present a use case driven software reuse approach for interactive systems, integrating – by means of some aspects of use case life cycle (from modeling to implementation) - several well-known reuse concepts and techniques like use case patterns, interaction patterns and design patterns. The approach focuses on how to promote user interface reuse based on patterns and how to use and implement them through code reuse and/or component reuse.

A prática de reuso, apesar de ser universalmente e reconhecidamente aceita como uma boa prática, ainda não atingiu um estágio de maturidade satisfatório nas instituições. Em particular, a definição e a construção das interfaces com o usuário (IHC) ainda carecem de abordagens efetivas e sistemáticas de reuso, mesmo se comparadas com as práticas já existentes de reuso dos demais artefatos de software. O objetivo deste trabalho é duplo: investigar abordagens de reuso de interfaces do usuário (IHC), analisando-as do ponto de vista da sua aplicabilidade, adequação e integração em um processo de desenvolvimento de software baseado na UML e propor uma abordagem de reuso de artefatos de software interativo dirigida por casos de uso, integrando – por meio de alguns aspectos do ciclo de vida de casos de uso (da modelagem à implementação) – vários conceitos e técnicas de reuso bem conhecidos como padrões de casos de uso, padrões de interação e padrões de projeto. O foco principal é a definição de como promover o reuso de interface com o usuário baseado em padrões e de como usar e implementar esses padrões através do reuso de código e/ou de componentes. / Reuse practicing, although universally and recognizably accepted as good practice, hasn’t reached a fair maturity level in organizations. Specifically, the definition and construction of user interfaces (HCI) lack effective and systematic reuse approaches even when compared with other reuse practices used nowadays. This work has a dual-purpose: to make a survey of reuse approaches of user interfaces (HCI) and their applicability in a development process based on UML, and to present a use case driven software reuse approach for interactive systems, integrating – by means of some aspects of use case life cycle (from modeling to implementation) - several well-known reuse concepts and techniques like use case patterns, interaction patterns and design patterns. The approach focuses on how to promote user interface reuse based on patterns and how to use and implement them through code reuse and/or component reuse.

A prática de reuso, apesar de ser universalmente e reconhecidamente aceita como uma boa prática, ainda não atingiu um estágio de maturidade satisfatório nas instituições. Em particular, a definição e a construção das interfaces com o usuário (IHC) ainda carecem de abordagens efetivas e sistemáticas de reuso, mesmo se comparadas com as práticas já existentes de reuso dos demais artefatos de software. O objetivo deste trabalho é duplo: investigar abordagens de reuso de interfaces do usuário (IHC), analisando-as do ponto de vista da sua aplicabilidade, adequação e integração em um processo de desenvolvimento de software baseado na UML e propor uma abordagem de reuso de artefatos de software interativo dirigida por casos de uso, integrando – por meio de alguns aspectos do ciclo de vida de casos de uso (da modelagem à implementação) – vários conceitos e técnicas de reuso bem conhecidos como padrões de casos de uso, padrões de interação e padrões de projeto. O foco principal é a definição de como promover o reuso de interface com o usuário baseado em padrões e de como usar e implementar esses padrões através do reuso de código e/ou de componentes. / Reuse practicing, although universally and recognizably accepted as good practice, hasn’t reached a fair maturity level in organizations. Specifically, the definition and construction of user interfaces (HCI) lack effective and systematic reuse approaches even when compared with other reuse practices used nowadays. This work has a dual-purpose: to make a survey of reuse approaches of user interfaces (HCI) and their applicability in a development process based on UML, and to present a use case driven software reuse approach for interactive systems, integrating – by means of some aspects of use case life cycle (from modeling to implementation) - several well-known reuse concepts and techniques like use case patterns, interaction patterns and design patterns. The approach focuses on how to promote user interface reuse based on patterns and how to use and implement them through code reuse and/or component reuse.