<p>Software engineering tools are being used in the industry in order to improve the productivity and the quality of the software development process. The properties of those tools are being perceived to be unsatisfactory. For example, researchers have found that some problems are due to deficient integration among the tools. Furthermore, a continuing problem is that there is a gap between the IT education and real demand of tool-skills form IT industry. Consequently, knowledge is needed of the properties of software development tools as well an understanding of demanded tool-skill from the industry. </p><p>The purpose of this study is to survey commercial software development environment (SDEs) that are used today in professional software engineering and discuss their advantages adn disadvantages. A secondary goal of the study is to identify the actual requirements from the industry on the IT-education. </p><p>A questionnaire was sent out to 90 software developers and IT managers of 30 IT companies in Sweden. The results of the survey show that IT companies, for most part, use SDEs from commercial software vendors. Respondents report that common problems of the SDEs are the following: bad integration among the tools, problems to trace software artifacts in the different phases of the programming cycle, and deficient support for version control and system configuration. Furthermore, some tools are difficult to use which results in a time-consuming development process. </p><p>We conclude that future software development environments need to provide better support for integration, automation, and configuration management. Regarding the required tool-skills, we believe that the IT education would gain from including commercial tools that cover the whole software product lifecycle in the curriculum.</p>

Software engineering tools are being used in the industry in order to improve the productivity and the quality of the software development process. The properties of those tools are being perceived to be unsatisfactory. For example, researchers have found that some problems are due to deficient integration among the tools. Furthermore, a continuing problem is that there is a gap between the IT education and real demand of tool-skills form IT industry. Consequently, knowledge is needed of the properties of software development tools as well an understanding of demanded tool-skill from the industry. The purpose of this study is to survey commercial software development environment (SDEs) that are used today in professional software engineering and discuss their advantages adn disadvantages. A secondary goal of the study is to identify the actual requirements from the industry on the IT-education. A questionnaire was sent out to 90 software developers and IT managers of 30 IT companies in Sweden. The results of the survey show that IT companies, for most part, use SDEs from commercial software vendors. Respondents report that common problems of the SDEs are the following: bad integration among the tools, problems to trace software artifacts in the different phases of the programming cycle, and deficient support for version control and system configuration. Furthermore, some tools are difficult to use which results in a time-consuming development process. We conclude that future software development environments need to provide better support for integration, automation, and configuration management. Regarding the required tool-skills, we believe that the IT education would gain from including commercial tools that cover the whole software product lifecycle in the curriculum.

We introduce a class of program editors that present a program using a rich set of transformations; we call these kinds of editors composable presentation editors. Proper use of these kinds of editors appears to lead to more expressive programs-programs whose structure are aligned with the problem they are trying to solve. By default, the composable presentation editor presents program elements textually as concrete syntax and enables typical editor commands on the program. Metadata on program elements control how the transformations are applied. Customized metadata can re-order, pictorialize, collapse, duplicate, or expand the displayed form of program elements and can additionally alter the available editor commands. We have developed a set of presentation techniques to be used by presentation designers (i.e., the programmers who design how a program is presented in the editor. These techniques relate to well-understood programming language design, editor design, and programming best-practices techniques including scoping, higher order functions, refactoring, prettyprinting, naming conventions, syntax highlighting, and text hovers. We introduce two implementations of composable presentation editors and a number of examples showing how programs can be made more expressive when presentation techniques are properly used. The first implementation is the ETMOP, an open editor, where a metaobject protocol is provided that allows language and editor designers to customize the way program elements are displayed. These customizations are called presenta- tion extensions and the corresponding presentation extension protocol acts in a way similar to the way that syntax macros extend the syntax of a language. The second implementation is Embedded CAL, a closed editor that uses these presentation techniques to embed one language (CAL) inside a host language (Java) through the use of presentation techniques, without changing the syntax or compiler of either language.

We introduce a class of program editors that present a program using a rich set of transformations; we call these kinds of editors composable presentation editors. Proper use of these kinds of editors appears to lead to more expressive programs-programs whose structure are aligned with the problem they are trying to solve. By default, the composable presentation editor presents program elements textually as concrete syntax and enables typical editor commands on the program. Metadata on program elements control how the transformations are applied. Customized metadata can re-order, pictorialize, collapse, duplicate, or expand the displayed form of program elements and can additionally alter the available editor commands. We have developed a set of presentation techniques to be used by presentation designers (i.e., the programmers who design how a program is presented in the editor. These techniques relate to well-understood programming language design, editor design, and programming best-practices techniques including scoping, higher order functions, refactoring, prettyprinting, naming conventions, syntax highlighting, and text hovers. We introduce two implementations of composable presentation editors and a number of examples showing how programs can be made more expressive when presentation techniques are properly used. The first implementation is the ETMOP, an open editor, where a metaobject protocol is provided that allows language and editor designers to customize the way program elements are displayed. These customizations are called presenta- tion extensions and the corresponding presentation extension protocol acts in a way similar to the way that syntax macros extend the syntax of a language. The second implementation is Embedded CAL, a closed editor that uses these presentation techniques to embed one language (CAL) inside a host language (Java) through the use of presentation techniques, without changing the syntax or compiler of either language.

We introduce a class of program editors that present a program using a rich set of transformations; we call these kinds of editors composable presentation editors. Proper use of these kinds of editors appears to lead to more expressive programs-programs whose structure are aligned with the problem they are trying to solve. By default, the composable presentation editor presents program elements textually as concrete syntax and enables typical editor commands on the program. Metadata on program elements control how the transformations are applied. Customized metadata can re-order, pictorialize, collapse, duplicate, or expand the displayed form of program elements and can additionally alter the available editor commands. We have developed a set of presentation techniques to be used by presentation designers (i.e., the programmers who design how a program is presented in the editor. These techniques relate to well-understood programming language design, editor design, and programming best-practices techniques including scoping, higher order functions, refactoring, prettyprinting, naming conventions, syntax highlighting, and text hovers. We introduce two implementations of composable presentation editors and a number of examples showing how programs can be made more expressive when presentation techniques are properly used. The first implementation is the ETMOP, an open editor, where a metaobject protocol is provided that allows language and editor designers to customize the way program elements are displayed. These customizations are called presenta- tion extensions and the corresponding presentation extension protocol acts in a way similar to the way that syntax macros extend the syntax of a language. The second implementation is Embedded CAL, a closed editor that uses these presentation techniques to embed one language (CAL) inside a host language (Java) through the use of presentation techniques, without changing the syntax or compiler of either language. / Science, Faculty of / Computer Science, Department of / Graduate

Made available in DSpace on 2016-12-23T14:33:36Z (GMT). No. of bitstreams: 1 dissertacao.pdf: 2123194 bytes, checksum: b9d4a5d39eaf88559d7055b13547ab8e (MD5) Previous issue date: 2006-11-27 / Due to the complexity and the high number of variables involved in the management activities, it is essential to the project manager to have some kind of automated support to perform her tasks. During the accomplishment of a software project, a high amount of knowledge is produced and used. Looking for the reuse of that knowledge in future projects, we need to provide means to retain and store the generated knowledge in a way to minimize the effort to obtain it in the future. In this context, knowledge management can be used to capture the knowledge and experience generated and accumulated during the software process and to promote the appearance of new knowledge. Experience constitutes a key factor in order to management activities can be accomplished with success. Thus, the benefits reached by the change of ideas during the accomplishment of those activities are evident. During this work, in order to support software project management using knowledge management in the software development environment ODE, we have developed and integrated to ODE an infrastructure to support software items characterization and search for similar items and an infrastructure to support group decision. To evaluate the potential of these infrastructures, we specialized them, respectively, to support project characterization and cooperative elaboration of risk plans. / Tendo em vista a complexidade das atividades de gerência e a quantidade de variáveis envolvidas nessas atividades, é essencial que o gerente de projetos conte com algum tipo de apoio automatizado para realizá-las. Durante a realização de um projeto de software, muito conhecimento é produzido e utilizado. Visando à reutilização desse conhecimento em projetos futuros, é fundamental que sejam providos meios de se reter e armazenar o conhecimento gerado, de forma a minimizar o esforço para obtê-lo no futuro. Neste contexto, a gerência de conhecimento pode ser usada para capturar o conhecimento e a experiência gerada e acumulada durante o processo de software e promover o surgimento de novo conhecimento. A experiência constitui um fator de fundamental importância para que as atividades de gerência sejam realizadas com sucesso. Assim, os benefícios alcançados pela troca de idéias durante a realização dessas atividades são evidentes. Durante este trabalho, visando ao apoio de gerência de conhecimento à gerência de projetos de software no ambiente de desenvolvimento de software ODE, foram desenvolvidas e integradas a ODE uma infra-estrutura para caracterização de itens de software e busca de itens similares e uma infra-estrutura de apoio à decisão em grupo. Para avaliar o potencial dessas infra-estruturas, foram conduzidas especializações das mesmas, respectivamente, para caracterização de projetos e para a elaboração cooperativa de planos de riscos.

Made available in DSpace on 2016-12-23T14:33:37Z (GMT). No. of bitstreams: 1 dissertacao.pdf: 8391728 bytes, checksum: 9bece3ebe6f8b8e7853c4336a5dd29f5 (MD5) Previous issue date: 2006-09-10 / Tendo em vista a complexidade das atividades de gerência e a quantidade de variáveis envolvidas nessas atividades, é essencial que o gerente de projetos conte com algum tipo de apoio automatizado para realizá-las. Durante a realização de um projeto de software, muito conhecimento é produzido e utilizado. Visando à reutilização desse conhecimento em projetos futuros, é fundamental que sejam providos meios de se reter e armazenar o conhecimento gerado, de forma a minimizar o esforço para obtê-lo no futuro. Neste contexto, a gerência de conhecimento pode ser usada para capturar o conhecimento e a experiência gerada e acumulada durante o processo de software e promover o surgimento de novo conhecimento. A experiência constitui um fator de fundamental importância para que as atividades de gerência sejam realizadas com sucesso. Assim, os benefícios alcançados pela troca de idéias durante a realização dessas atividades são evidentes. Durante este trabalho, visando ao apoio de gerência de conhecimento à gerência de projetos de software no ambiente de desenvolvimento de software ODE, foram desenvolvidas e integradas a ODE uma infra-estrutura para caracterização de itens de software e busca de itens similares e uma infra-estrutura de apoio à decisão em grupo. Para avaliar o potencial dessas infra-estruturas, foram conduzidas especializações das mesmas, respectivamente, para caracterização de projetos e para a elaboração cooperativa de planos de riscos. / Due to the complexity and the high number of variables involved in the management activities, it is essential to the project manager to have some kind of automated support to perform her tasks. During the accomplishment of a software project, a high amount of knowledge is produced and used. Looking for the reuse of that knowledge in future projects, we need to provide means to retain and store the generated knowledge in a way to minimize the effort to obtain it in the future. In this context, knowledge management can be used to capture the knowledge and experience generated and accumulated during the software process and to promote the appearance of new knowledge. Experience constitutes a key factor in order to management activities can be accomplished with success. Thus, the benefits reached by the change of ideas during the accomplishment of those activities are evident. During this work, in order to support software project management using knowledge management in the software development environment ODE, we have developed and integrated to ODE an infrastructure to support software items characterization and search for similar items and an infrastructure to support group decision. To evaluate the potential of these infrastructures, we specialized them, respectively, to support project characterization and cooperative elaboration of risk plans.

Made available in DSpace on 2016-08-17T14:53:06Z (GMT). No. of bitstreams: 1 UIRATAN ALVES DE SOUSA CAVALCANTE.pdf: 4868154 bytes, checksum: 71d6895bc849a94e0bac2dba2b713adf (MD5) Previous issue date: 2009-12-01 / The agent-oriented development paradigm has achieved a high maturity level over the last decade. However, integrated development environments supporting all phases of agent-oriented development are still missing. MADAE-Pro is a process for the development and reuse of family of multi-agent systems and integrates two complementary process. One is based on Domain Engineering concepts, aiming in creating artifacts of reusable software in the development of an application family in a particular domain problem, and the other is based on Application Engineering, which guides the construction of applications based on reusable software artifacts previously produced in the Domain Engineering process. The environment includes the ONTORMAS ontology and, through inference rules and semantic search over its instances, automates the modeling tasks of the MADAE-Pro process. These features allow for the developer productivity gains and for maintaining the consistence of the knowledge-base, ensuring the success of the reuse in future applications. / O paradigma de desenvolvimento orientado a agentes tem atingido um alto nível de maturidade na última década. Entretanto, ainda faltam ambientes integrados de desenvolvimento de software que suportem todas as fases do desenvolvimento orientado a agentes. MADAE-Pro é um processo para o desenvolvimento e reuso de famílias de sistemas multiagente e integra dois subprocessos complementares. Um é baseado nos conceitos da Engenharia de Domínio, isto é, visa construir artefatos reutilizáveis que representem uma família de aplicações e o outro, baseado na Engenharia de Aplicações, guia o desenvolvimento de uma aplicação específica reutilizando os produtos do primeiro subprocesso. Este trabalho propõe MADAEIDE, um ambiente integrado de desenvolvimento baseado no conhecimento que automatiza o processo desenvolvimento de software multiagente MADAE-Pro. O ambiente agrega a ontologia ONTORMAS e, através de regras de inferência e buscas semânticas diretamente sobre suas instâncias, automatiza as tarefas de modelagem do processo MADAE-Pro. Estas características levam a um ganho de produtividade por parte do desenvolvedor, além de manter uma base de conhecimento consistente, garantido o sucesso do reuso em futuras aplicações.