Submitted by CARLA MARIA GOULART DE MORAES (carlagm) on 2015-04-06T17:18:33Z No. of bitstreams: 1 VilsonGartnerComputacao.pdf: 9068377 bytes, checksum: 6ace07d8901f11d83ef8a8c13f4f62c7 (MD5) / Made available in DSpace on 2015-04-06T17:18:33Z (GMT). No. of bitstreams: 1 VilsonGartnerComputacao.pdf: 9068377 bytes, checksum: 6ace07d8901f11d83ef8a8c13f4f62c7 (MD5) Previous issue date: 2011 / CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / O Desenvolvimento Distribuído de Software (DDS) é um modelo de desenvolvimento que vem se intensificando nos últimos anos. Também conhecido como Desenvolvimento Global de Software (DGS), esse modelo de desenvolvimento é realizado por equipes em diferentes localizações geográficas. Entre os fatores que contribuem para esse aumento, está a necessidade de negócio das corporações, que buscam redução de custos, recursos qualificados e necessidade de uma presença global. Em outros casos, se deve ao surgimento de novos movimentos de desenvolvimento de software, como a comunidade de software livre, um exemplo bem sucedido de DDS. Apesar da necessidade ou mesmo da conveniência de desenvolver o software de forma distribuída, é extremamente difícil fazê-lo com sucesso. A separação física traz uma série de problemas e desafios interessantes que recém estão começando a ser compreendidas: questões estratégicas, questões culturais, comunicação inadequada, gestão do conhecimento, alocação de tarefas, confiança, questões técnicas, entre outros. Desde que surgiu, o DDS mudou grande parte da tradição do desenvolvimento de software e, para manter o seu mercado, as organizações não podem depender das mesmas competências e tecnologias de engenharia de software utilizadas no desenvolvimento interno. Nesse sentido, o presente trabalho tem por objetivo auxiliar na redução dos problemas e dificuldades trazidos por esse modelo de desenvolvimento, através da implementação de um ambiente de desenvolvimento cujas ferramentas foram definidas com base em estudos e trabalhos relacionados ao tema. / The Distributed Software Development (DSD) is a development model that has been intensified in recent years. Also known as Global Software Development (GSD), this development model is done by teams in different geographical locations. Among the factors that have contributed to this increase, there is the corporations business need of seeking ways to reduce costs, seeking skilled resources and having a global presence. In other cases, it is due to the emergence of new movements in software development, such as the free software community, a successful example of DSD. Despite the need or even desirability of developing software in a distributed way, it is extremely difficult to do this successfully. Physical separation has a number of interesting problems and challenges that are just beginning to be understood: strategic issues, cultural issues, inadequate communication, knowledge management, task allocation, trust, technical issues, among others. DSD has changed much of the tradition of software development since it appeared. Organizations cannot rely on the same skills and software engineering technologies used internally to maintain this new market. In this way, this work aims to help to reduce the problems and difficulties brought by this type of development, through the implementation of a software development environment whose tools were defined based on studies related to the topic.

This project included the development of a multi-user game that takes place in a 3 dimensional world of the computer science department. Basically, the game allows prospective students to meet existing students and faculty in a virtual open house that takes place within the third floor of Jack Brown Hall. Users can walk around Jack Brown Hall and type text messages to chat with each other.

Model-driven software development (MDSD) and component-based software development are both paradigms for reducing complexity and for increasing abstraction and reuse in software development. In this thesis, we aim at combining the advantages of each by introducing methods from component-based development into MDSD. In MDSD, all artefacts that describe a software system are regarded as models of the system and are treated as the central development artefacts. To obtain a system implementation from such models, they are transformed and integrated until implementation code can be generated from them. Models in MDSD can have very different forms: they can be documents, diagrams, or textual specifications defined in different modelling languages. Integrating these models of different formats and abstraction in a consistent way is a central challenge in MDSD. We propose to tackle this challenge by explicitly separating the tasks of defining model components and composing model components, which is also known as distinguishing programming-in-the-small and programming-in-the-large. That is, we promote a separation of models into models for modelling-in-the-small (models that are components) and models for modelling-in-the-large (models that describe compositions of model components). To perform such component-based modelling, we introduce two architectural styles for developing systems with component-based MDSD (CB-MDSD). For CB-MDSD, we require a universal composition technique that can handle models defined in arbitrary modelling languages. A technique that can handle arbitrary textual languages is universal invasive software composition for code fragment composition. We extend this technique to universal invasive software composition for graph fragments (U-ISC/Graph) which can handle arbitrary models, including graphical and textual ones, as components. Such components are called graph fragments, because we treat each model as a typed graph and support reuse of partial models. To put the composition technique into practice, we developed the tool Reuseware that implements U-ISC/Graph. The tool is based on the Eclipse Modelling Framework and can therefore be integrated into existing MDSD development environments based on the framework. To evaluate the applicability of CB-MDSD, we realised for each of our two architectural styles a model-driven architecture with Reuseware. The first style, which we name ModelSoC, is based on the component-based development paradigm of multi-dimensional separation of concerns. The architecture we realised with that style shows how a system that involves multiple modelling languages can be developed with CB-MDSD. The second style, which we name ModelHiC, is based on hierarchical composition. With this style, we developed abstraction and reuse support for a large modelling language for telecommunication networks that implements the Common Information Model industry standard.

Made available in DSpace on 2014-12-17T15:47:47Z (GMT). No. of bitstreams: 1 AnaLFM.pdf: 903790 bytes, checksum: 70d26a43bc5418b76d2ecdc1716d862c (MD5) Previous issue date: 2008-06-09 / Aspect Oriented approaches associated to different activities of the software development process are, in general, independent and their models and artifacts are not aligned and inserted in a coherent process. In the model driven development, the various models and the correspondence between them are rigorously specified. With the integration of aspect oriented software development (DSOA) and model driven development (MDD) it is possible to automatically propagate models from one activity to another, avoiding the loss of information and important decisions established in each activity. This work presents MARISA-MDD, a strategy based on models that integrate aspect-oriented requirements, architecture and detailed design, using the languages AOV-graph, AspectualACME and aSideML, respectively. MARISA-MDD defines, for each activity, representative models (and corresponding metamodels) and a number of transformations between the models of each language. These transformations have been specified and implemented in ATL (Atlas Definition Language), in the Eclipse environment. MARISA-MDD allows the automatic propagation between AOV-graph, AspectualACME, and aSideML models. To validate the proposed approach two case studies, the Health Watcher and the Mobile Media have been used in the MARISA-MDD environment for the automatic generation of AspectualACME and aSideML models, from the AOV-graph model / As abordagens orientadas a aspectos relacionadas a diferentes atividades do processo de desenvolvimento de software s?o, em geral, independentes e os seus modelos e artefatos n?o est?o alinhados ou inseridos em um processo coerente. No desenvolvimento orientado a, modelos, os diversos modelos e a correspond?ncia entre eles s?o especificados com rigor. Com a integra??o do desenvolvimento orientado a aspectos (DSOA) e o desenvolvimento baseado em modelos (MDD) pode-se automaticamente propagar modelos de uma atividade para outra atividade, evitando a perda de informa??es e de decis?es importantes estabelecidas em cada atividade. Este trabalho apresenta MARISA-MDD, uma estrat?gia baseada em modelos que integra as atividades de requisitos, arquitetura e projeto detalhado orientado a aspectos, usando as linguagens AOV-graph, AspectualACME e aSideML, respectivamente. MARISA-MDD define, para cada atividade, modelos representativos (e metamodelos correspondentes) e um conjunto de transforma??es entre os modelos de cada linguagem. Tais transforma??es foram especificadas e implementadas em ATL (Atlas Definition Language), no ambiente Eclipse. MARISA-MDD permite a propaga??o autom?tica entre modelos AOV-graph, AspectualACME e aSideML. Para validar a abordagem proposta dois estudos de caso, o Health Watcher e o Mobile Media foram usados no ambienteMARISA-MDD para gera??o autom?tica dos modelos AspectualACME e aSideML, a partir do modelo AOV-graph

There are several critical success factors suggested for why agile software development projects succeed, including organisational and process factors. Although there are an increasing number of identified critical success factors, IT professionals lack the modelling techniques and the theoretical framework to help them meaningfully understand their influences. To solve this problem, this study developed a model by employing the following theories: Theory of Reasoned Action (TRA), Theory of Planned Behaviour (TPB), and Unified Theory of Acceptance and Use of Technology (UTAUT) to create a fit model for agile software development projects. The research sought to answer the question: What are the critical success factors that influence the success of agile software development projects? The literature review considers the continued failure of agile and traditional software development projects which have led to the consideration of, and dispute over, critical success factors — the aspects most vital to a methodology’s success. Though TRA, TPB and UTAUT have previously been applied to agile methodologies, empirical models have not been completely integrated to develop a fit model. This research sought to fill this gap. Data was collected in South Africa through a web-based survey using structured questionnaires and an interview guide. Face-to-face interviews were done to identify the critical success factors in agile projects. The data was captured and analysed for descriptive statistics, convergent and discriminant validity, composite and internal reliability, and correlation in order to inform the structural equation modelling (SEM). SEM was used to test the research model and hypotheses to answer the research questions. The results informed development of a comprehensive model that could provide guidelines to the agile community. The study contributes towards understanding the critical success factors for agile projects. It examined direct, indirect and moderating effects, and the findings contribute towards developing a framework to be used by agile professionals. These key result shows that organisational factors have a great influence on performance expectancy characteristics. To ensure success of agile projects, managers are advised to focus on the effect of the organisation’s environment, culture and policies on performance and effort expectancy. / School of Computing / Ph. D. (Computer Science)

The research is conducted in the area of software methodologies with the emphasis on the integration of legacy systems with the client/server environment. The investigation starts with identifying the characteristics of legacy systems in order to determine the features and technical characteristics required of an integration methodology. A number of existing methodologies are evaluated with respect to their features and technical characteristics in order to derive a synthesis for a generic methodology. This evaluation yields the meta primitives of a generic methodology. The revised spiral model (Boehm,1986; DuPlessis & Vander Wah,1992) is customised to arrive at a software process model which provides a framework for the integration of legacy systems with the client/server environment. The integration methodology is based on this process model. / Computing / M. Sc. (Information Systems)

Dentre as práticas da Programação Extrema, ou eXtreme Programming (XP), destaca-se a Programação em Par, ou Pair Programming (PP). Nesta prática duas pessoas trabalham de forma colaborativa na mesma tarefa – projeto, algoritmo, código ou teste – e em um único computador. O objetivo geral deste trabalho é investigar a eficácia da Programação em Par versus Programação individual perante tarefas de modelagem e construção de software orientado a objetos. A eficácia da prática é avaliada por meio de atributos relacionados à qualidade de software, são eles: (i) tamanho dos métodos, (ii) complexidade estrutural dos métodos, (iii) acoplamento/dependência entre pacotes e, por fim, (iv) falta de coesão dos métodos por classe. Para isso, foi realizada uma pesquisa experimental envolvendo atividades práticas e aplicação de questionários junto a alunos voluntários de três instituições de ensino superior da cidade de Curitiba. A partir dessa pesquisa, conclui-se que Programação em Par mostrou-se mais eficaz perante tarefas de modelagem e construção de software que a programação individual, isso considerando tamanho e complexidade dos métodos. E mais, os alunos perceberam mais benefícios do que desafios (ou desvantagens) quando se adota a PP para realizar tais tarefas. / Among eXtreme Programming (XP) practices, Pair Programming(PP) stands out from the rest. It consists of two individuals cooperating, working in the same task - design, algorithm, code or test - in the same computer. The general objective of this study is to scrutinize the efficacy of Pair Programming versus individual programming relating to modeling tasks and object oriented software development. The efficacy of the process is evaluated through the following software quality related attributes: (i) method size, (ii) structural complexity of the methods, (iii) linkage/dependency among packages and finally (iv) lack of cohesion of the methods by class. Therefore, an experimental research was performed, involving practical activities and surveys answered by volunteer students from three different higher education institutions in Curitiba. This research showed that pair programming is more efficient when working with modeling tasks and software development than individual programming, taking into account size and complexity of methods. Furthermore, more pros than cons were found by students when pair programming was chosen to accomplish such tasks.

Made available in DSpace on 2016-08-17T14:52:48Z (GMT). No. of bitstreams: 1 alisson lindoso2.pdf: 6722921 bytes, checksum: 2f55fa8a7f109106c015f0307cb7582c (MD5) Previous issue date: 2006-03-10 / The increasing demand of software applications constructed conciliating productivity, low cost and high quality, even in complex and changeable domains, turns necessary the elaboration of techniques and methodologies focusing on development paradigms more suitable for approaching these conflicting features, like the multiagent one. On the other hand, the sotware reuse process promotes the creation of new applications employing reusable software artifacts previously developed. This work introduces MAAEM, an ontology-driven methodology for analysis, design and implementation of multi-agent applications through the reuse of models and components that represent the requirements of a family of applications in a domain as well as the corresponding agent-oriented solutions to these ones. ONTORMAS, an ontology whose instantiation is useful for modeling and representing specific applications developed with MAAEM methodology, is also presented. Two case studies elaborated in order to evaluate the methodology and ontology are also described, exploring the cases with and without reuse, respectively, in the touristic and juridical domains. / A crescente demanda por aplicações de software cuja construção concilie produtividade, baixo custo e alta qualidade, mesmo em domínios complexos e mutáveis, torna necessária a elaboração de técnicas e metodologias que foquem paradigmas de desenvolvimento mais adequados para abordar aquelas características conflitantes, tal como o paradigma multiagente. Por outro lado, o processo de reutilização de software permite promover a criação de novas aplicações empregando artefatos de software reutilizáveis previamente desenvolvidos. Esse trabalho introduz a MAAEM, uma metodologia baseada em ontologias para a análise, o projeto e a implementação de aplicações multiagente através do reuso de modelos e componentes que representam os requisitos de uma família de aplicações em um domínio, assim como as correspondentes soluções orientadas a agentes para tais requisitos. É também apresentada a ONTORMAS, uma ontologia cuja instanciação é útil para modelar e representar aplicações específicas desenvolvidas com a metodologia MAAEM. São descritos ainda dois estudos de caso elaborados no sentido de avaliar a metodologia e a ontologia, explorando os casos com e sem reuso, respectivamente, nos domínios turístico e jurídico.

The Advising Module: Graduate Application System is a Web-based application system that provides quality advice on coursework for prospective as well as continuing graduate students. It also serves as an improved tracking system for the graduate coordinator. Authorized parties may obtain access to status evaluations, master's options, and permitted course waivers, course listings, personal data, various advisement forms, application usage statistics, and automatic data updating process reports.

The agile manifesto has certainly changed the way software is produced in the Information Communications Technology (ICT) industry. However, many persistent challenges cripple agile software development. One challenge is that the constant change in technology makes the requirements hard to implement. Another is that issues of the agile requirements engineering (ARE) process are abundant and pervasive throughout software projects. The aim of this study is to determine common issues in agile requirements engineering in the South African software industry and identify tools and frameworks to mitigate risks emanating from such problems. This includes finding out how much value software practitioners put in the agile principles. This study was essentially quantitative, based on a cross-sectional survey. Self-administered questionnaires were used to collect required data which was then subjected to exploratory data analysis using SPSS (Statistical Package for the Social Sciences), a tool for statistical analysis. The results show that software practitioners have a strong penchant for principles of the Agile Manifesto. Major issues in agile requirements engineering include lack of proper validation tools and techniques, scope problems, lack of proper documentation, issues of prioritisation, as well as unavailability of customer representative. A detailed baseline of issues in agile requirements engineering was created along with a set of recommended tools and techniques used in the software industry. As for the recommendation, it is suggested that companies invest more on validation tools and techniques and consider non-functional requirements integration during software development. / School of Computing / M. Sc. (Computing)