No description available.

The diploma thesis focuses on analysis of software tools used in a softwarehouse company. It contains detailed assessment of a used project management information system, business process design and information system modification. The thesis also includes complete implementation of a module for cost calculation of software projects. The module is based on Use Case Points method.

Call number: LD2668 .T4 1985 S642 / Master of Landscape Architecture

<p>Systems development projects and their documents are more or less standardized and can mainly be applied on systems that are supposed to be built from scratch, or updated. In pace with the number of IT-systems are increasing worldwide there is no need for every organization to build their own IT-system. Nowadays it is also possible to purchase licenses which allow the purchaser to modify or add functions to the system. Along with those changes, there have been an increased amount of “rapid development methods” such as Agile and “Quick and Dirty” solutions, but these methods and perspectives are mainly focusing on entire systems development processes, as the old ones, but quicker.</p><p>If a company purchases an off-the-shelf system with source code available, there is no real need to go through a proper systems development process. During interviews with a small company that has acquired a system as mentioned above, the researcher realized that only one single document is needed, the requirements specification. Today’s requirements specifications can be either well detailed or less, but a project still needs the details specified. Combining a known agile development process with IEEE’s standardized requirements specification, a new way to proceed with projects based on one single document (the requirements specification) has been made. This document also has a focus on simplicity for the inexperienced readers, but with the depth that every developer has got a use for.</p>

Over the last decade, software has become an integral part of many products with which it is not traditionally associated (e.g., automobiles, medical equipment, home appliances, etc.). This has led to problems in many organizations, since it has proved difficult to integrate software engineering processes with other engineering processes. To address the increased complexity and to coordinate their engineering efforts, many organizations working in such domains have therefore introduced systems engineering into their business processes. Systems engineering is an interdisciplinary approach to system development. Teamwork is essential in developing complex systems, and systems engineering orchestrates this process throughout the lifespan of a system. The focus of systems engineering is on defining customer needs and required functionality, documenting requirements, synthesizing a design and validating the system. A problem with the traditional techniques of systems engineering is, however, that they provide inadequate support for achieving high levels of reuse between different projects. In this dissertation, methods and tools with the overall purpose of providing an improved reuse infrastructure for systems engineering artifacts and their resulting detailed design artifacts are proposed. The proposed methods and tools are based on the software product-line approach, a reuse strategy which focuses on families of related systems that address particular market segments. Studies have shown that if an empirical study does not report experiences from that which practitioners consider a “real” situation, results are likely to be ignored. Even though case studies cannot achieve the scientific rigor of formal experiments, case studies can provide enough information to decide if a specific technology will benefit a particular organization. To ensure industry-relevant research results, case studies on real development projects were chosen as the main vehicle for performing research. This dissertation reports experiences from four empirical studies which were performed within the Swedish defense industry. The studies indicate that the proposed methods and tools indeed provide an improved reuse infrastructure, compared to the previously used methods and tools.

<p>Software metrics are a useful tool for assessing software quality and for making predictions. But currently the interpretation of the measured values is based on personal experience and gut feeling. Not much information is available about thresholds and possible ranges of the metric values. In order to be able to define thresholds on which general recommendations could be based, quantitative data has to be obtain for allowing statistical evaluations and further investigations. So far the collection of test projects requires significant manual interaction for downloading and describing metadata.</p><p>This thesis describes a process for automatically obtaining, storing and maintaining a large number of open software projects from SourceForge.NET [1]. The projects are stored in a local folder structure; the meta-data is stored in a local database. The process is automated as far as possible, repeatable, transparent, extendible and flexible.</p>

Mūsų dienomis informacinės sistemos tampa vis sudėtingesnės ir verslo procesams aprašyti seniai nebeužtenka paprastų tekstų ar schemų. Kompiuterizuotų IS reikalavimams aprašyti ir modeliuoti geriausiai tinka specialiai tam skirti modeliai. Modeliavimas tapo būtinas kuriant dideles, sudėtingas ar su kitomis sistemomis sąveikaujančias informacines sistemas, nors daugelis programuotojų siekia minimizuoti modeliavimo pastangas. Modeliuojami ne tik vartotojo poreikiai, dalykinė sritis, programinė įranga, bet ir organizacijos veikla - pastaraisiais metais ši modeliavimo fazė tapo daugelio projektavimo procesų dalimi. Todėl specialūs kompiuterizuoti modeliavimo įrankiai tapo neatskiriama sudėtingų IS kūrimo ir projektavimo dalimi. Modernėjant technologijoms vis labiau orientuojamasi į reikalavimų specifikavimo fazę IS kūrimo projektuose – reikalavimai turi lemiamą reikšmę projektuojant modernias ir sudėtingas informacines sistemas. Todėl vis didėja projektavimo įrankių įtaka IS kūrimo procese, jų pagalba kartais generuojant ir kodą. Taigi, kad tinkamai būtų sukurta ir vystoma nauja sistema, būtina tinkamai apsibrėžti viziją, veiklos modelį ir tiksliai specifikuoti reikalavimus. Šis procesas, bei veiklos modelio transformavimas į vartotojo reikalavimų sistemai modelį aptariamas šiame darbe. / In nowadays information systems are becoming more and more sophisticated and for business process definition it is not enough to use simple schemas and text. For information systems requirements there are created special models. Systems modeling became a must for creating big, sophisticated, difficult systems. User’s requirements, subject matter and specialty domain, software architecture and even organizations activities are being modeled in modern software development companies during systems design process. Special modeling tools are used to create information systems. During last few years software and business developers are focusing more to requirements specification phase. In information systems development projects strict and simply understandable requirements have critical meaning creating big sophisticated information systems. So usage of design and modeling tools is more and more popular. Using such tools sometimes program code is generated to. To develop stable system is crucial to have a vision, make good activity model and specify requirements for future system. This work covers the method of the formation of transformation between activity and use-case models. This transformation is based developing business vision and requirements to future system. The algorithm of transformation described is this work, formally defines the described models elements relations between each other. Solution, based on described algorithm was made on MagicDraw UML tool platform... [to full text]

SANTOS, Ismayle de Sousa. Um ambiente para geração de cenários de testes para linhas de produtos de software sensíveis ao contexto. 2013. 135 f. : Dissertação (mestrado) - Universidade Federal do Ceará, Centro de Ciências, Departamento de Computação, Fortaleza-CE, 2013. / Submitted by guaracy araujo (guaraa3355@gmail.com) on 2016-07-01T19:23:59Z No. of bitstreams: 1 2013_dis_issantos.pdf: 3899116 bytes, checksum: 671b1907d9f723390441a5b8ed58142c (MD5) / Approved for entry into archive by guaracy araujo (guaraa3355@gmail.com) on 2016-07-01T19:25:01Z (GMT) No. of bitstreams: 1 2013_dis_issantos.pdf: 3899116 bytes, checksum: 671b1907d9f723390441a5b8ed58142c (MD5) / Made available in DSpace on 2016-07-01T19:25:01Z (GMT). No. of bitstreams: 1 2013_dis_issantos.pdf: 3899116 bytes, checksum: 671b1907d9f723390441a5b8ed58142c (MD5) Previous issue date: 2013 / A Context-Aware Software Product Line (CASPL) is a product line for developing context-aware applications, which dynamically change their behavior or provide services based on context information. With this kind of line, the productivity can be increased and the development costs of the context-aware application can be cut down. In this scenario, the testing activity needs to deal with the peculiarities of both context-aware applications and the product line development paradigm. Through the complexity involved in testing a CASPL is essential to have methods or tools for supporting this activity, especially with the goal of creating tests from requirements. The aim of this early testing generation is to identify and fix the defects in the early stages of development. Therefore, this work aims to propose an environment for generating test scenarios for a CASPL that takes into account the presence of context information and seeks to maximize the testing reuse. This environment consists of a testing scenario generation method, a template for textual use case specification and a support tool. The method uses as input textual use cases especifications with information about: funcionality, variability, and how the context afect the final products. The environment also has a use case template that supports the use of the method and a tool support, which allows the modeling of use cases according to this template and implements the proposed method. In order to verify the benefits of the environment as a way to testing generation for a Context-Aware Software Product Line, an assessment in the form of controlled experiment is conducted. Based on the collected results, it is observed that: the use of the template makes easy the understanding of a Context-Aware Software Product Line use case; the method favors the creation of a set of tests with higher coverage than a non-systematic testing generation; and the tool is the necessary support for the method / Uma Linha de Produto de Software Sensível ao Contexto (LPSSC) é uma linha de produto para o desenvolvimento de aplicações sensíveis ao contexto, que alteram dinamicamente o comportamento ou que proveem serviços com base em informações de contexto. Nesse cenário, a atividade de testes precisa lidar ao mesmo tempo com as peculiaridades das aplicações finais, que são sensíveis ao contexto, e com o paradigma de desenvolvimento em linha de produto. Mediante a complexidade envolvida nos testes de uma LPSSC, é fundamental a existência de métodos ou ferramentas de suporte a essa atividade, especialmente com a intenção de criar testes a partir dos requisitos da linha. O objetivo dessa geração precoce dos testes é permitir a identificação e correção dos defeitos nos estágios iniciais de desenvolvimento. Dessa forma, esta dissertação tem por objetivo propor um ambiente de geração de cenários de testes para uma LPSSC que utiliza especificações textuais de casos de uso com informações de contexto e que possibilita a reutilização dos testes. Este ambiente é constituído pela proposta de um método de geração de cenários de testes, de um template para especificação textual de casos de uso de uma LPSSC e de uma ferramenta de apoio. O método utiliza como base especificações textuais de casos de uso com informações sobre: funcionalidade, variabilidade da linha, e como o contexto afeta os produtos finais. O ambiente também contém o template para caso de uso que fornece suporte ao uso do método e a ferramenta de apoio, que permite a modelagem de casos de uso segundo esse template e implementa o método proposto. Com a intenção de verificar os benefícios do ambiente, proposto nesta dissertação, quanto a geração de cenários de testes para uma LPSSC, conduziu-se uma avaliação preliminar na forma de experimento controlado. Baseado nos resultados coletados nessa avaliação percebeu-se que: o template favorece o entendimento de um caso de uso de uma LPSSC; o método favorece a criação de um conjunto de testes com uma maior cobertura para uma LPSSC, se comparado a criação de testes de forma não sistemática; e a ferramenta representa um suporte necessário.

Systems development projects and their documents are more or less standardized and can mainly be applied on systems that are supposed to be built from scratch, or updated. In pace with the number of IT-systems are increasing worldwide there is no need for every organization to build their own IT-system. Nowadays it is also possible to purchase licenses which allow the purchaser to modify or add functions to the system. Along with those changes, there have been an increased amount of “rapid development methods” such as Agile and “Quick and Dirty” solutions, but these methods and perspectives are mainly focusing on entire systems development processes, as the old ones, but quicker. If a company purchases an off-the-shelf system with source code available, there is no real need to go through a proper systems development process. During interviews with a small company that has acquired a system as mentioned above, the researcher realized that only one single document is needed, the requirements specification. Today’s requirements specifications can be either well detailed or less, but a project still needs the details specified. Combining a known agile development process with IEEE’s standardized requirements specification, a new way to proceed with projects based on one single document (the requirements specification) has been made. This document also has a focus on simplicity for the inexperienced readers, but with the depth that every developer has got a use for.

Software metrics are a useful tool for assessing software quality and for making predictions. But currently the interpretation of the measured values is based on personal experience and gut feeling. Not much information is available about thresholds and possible ranges of the metric values. In order to be able to define thresholds on which general recommendations could be based, quantitative data has to be obtain for allowing statistical evaluations and further investigations. So far the collection of test projects requires significant manual interaction for downloading and describing metadata. This thesis describes a process for automatically obtaining, storing and maintaining a large number of open software projects from SourceForge.NET [1]. The projects are stored in a local folder structure; the meta-data is stored in a local database. The process is automated as far as possible, repeatable, transparent, extendible and flexible.