Identificando interesses transversais em modelos de requisitos PL-AOVgraph

The occurrence of problems related to the scattering and tangling phenomenon, such as the difficulty to do system maintenance, increasingly frequent. One way to solve this problem is related to the crosscutting concerns identification. To maximize its benefits, the identification must be performed from early stages of development process, but some works have reported that this has not been done in most of cases, making the system development susceptible to the errors incidence and prone to the refactoring later. This situation affects directly to the quality and cost of the system. PL-AOVgraph is a goal-oriented requirements modeling language which offers support to the relationships representation among requirements and provides separation of crosscutting concerns by crosscutting relationships representation. Therefore, this work presents a semi-automatic method to crosscutting concern identification in requirements specifications written in PL-AOVgraph. An adjacency matrix is used to identify the contributions relationships among the elements. The crosscutting concern identification is based in fan-out analysis of contribution relationships from the informations of adjacency matrix. When identified, the crosscutting relationships are created. And also, this method is implemented as a new module of ReqSys-MDD tool

Support Tool to the Validation Process of Functional Requirements

The activity of validating identified requirements for an information system helps to improve the quality of a requirements specification document and, consequently, the success of a project. Although various different support tools to requirements engineering exist in the market, there is still a lack of automated support for validation activity. In this context, the purpose of this paper is to make up for that deficiency, with the use of an automated tool, to provide the resources for the execution of an adequate validation activity. The contribution of this study is to enable an agile and effective follow-up of the scope established for the requirements, so as to lead the development to a solution which would satisfy the real necessities of the users, as well as to supply project managers with relevant information about the maturity of the analysts involved in requirements specification.

Apoio à gerência de requisitos de software utilizando Design Rationale

Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES)

A systematic mapping study on the open source software development process.

Abstract?Background: There is no globally accepted open source software development process to define how open source software is developed in practice. A process description is important for coordinating all the software development activities involving both people and technology. Aim: The research question that this study sets out to answer is: What activities do open source software process models contain? The activity groups on which it focuses are Concept Exploration, Software Requirements, Design, Maintenance and Evaluation. Method: We conduct a systematic mapping study (SMS). A SMS is a form of systematic literature review that aims to identify and classify available research papers concerning a particular issue. Results: We located a total of 29 primary studies, which we categorized by the open source software project that they examine and by activity types (Concept Exploration, Software Requirements, Design, Maintenance and Evaluation). The activities present in most of the open source software development processes were Execute Tests and Conduct Reviews, which belong to the Evaluation activities group. Maintenance is the only group that has primary studies addressing all the activities that it contains. Conclusions: The primary studies located by the SMS are the starting point for analyzing the open source software development process and proposing a process model for this community. The papers in our paper pool that describe a specific open source software project provide more regarding our research question than the papers that talk about open source software development without referring to a specific open source software project.

It's all in the game: Teaching software process concepts

A major challenge in teaching software engineering to undergraduates is that most students have limited industry experience, so the problems addressed are unknown and hence unappreciated. Issues of scope prevent a realistic software engineering experience, and students often graduate with a simplistic view of software engineering’s challenges. Problems and Programmers (PnP) is a competitive, physical card game that simulates the software engineering process from requirements specification to product delivery. Deliverables are abstracted, allowing a focus on process issues and for lessons to be learned in a relatively short time. The rules are easy to understand and the game’s physical nature allows for face-to-face interaction between players. The game’s developers have described PnP in previous publications, but this paper reports the game’s use within a larger educational scheme. Students learn and play PnP, and then are required to create a software requirements specification based on the game. Finally, students reflect on the game’s strengths and weaknesses and their experiences in an individual essay. The paper discusses this approach, students’ experiences and overall outcomes, and offers an independent, critical look at the game, its use, and potential improvements.

Mitigating the obsolescence of quality specifications models in service-based systems

Requirements-aware systems address the need to reason about uncertainty at runtime to support adaptation decisions, by representing quality of services (QoS) requirements for service-based systems (SBS) with precise values in run-time queryable model specification. However, current approaches do not support updating of the specification to reflect changes in the service market, like newly available services or improved QoS of existing ones. Thus, even if the specification models reflect design-time acceptable requirements they may become obsolete and miss opportunities for system improvement by self-adaptation. This articles proposes to distinguish "abstract" and "concrete" specification models: the former consists of linguistic variables (e.g. "fast") agreed upon at design time, and the latter consists of precise numeric values (e.g. "2ms") that are dynamically calculated at run-time, thus incorporating up-to-date QoS information. If and when freshly calculated concrete specifications are not satisfied anymore by the current service configuration, an adaptation is triggered. The approach was validated using four simulated SBS that use services from a previously published, real-world dataset; in all cases, the system was able to detect unsatisfied requirements at run-time and trigger suitable adaptations. Ongoing work focuses on policies to determine recalculation of specifications. This approach will allow engineers to build SBS that can be protected against market-caused obsolescence of their requirements specifications. © 2012 IEEE.

Personalized public transportation information

Thesis to obtain the Master of Science Degree in Computer Science and Engineering

Information systems for water resources management improvement in developing countries

Water resources management, as also water service provision projects in developing countries have difficulties to take adequate decisions due to scarce reliable information, and a lack of proper information managing. Some appropriate tools need to be developed in order to improve decision making to improve water management and access of the poorest, through the design of Decision Support Systems (DSS). On the one side, a DSS for developing co-operation projects on water access improvement has been developed. Such a tool has specific context constrains (structure of the system, software requirements) and needs (Logical Framework Approach monitoring, organizational-learning, accountability and evaluation) that shall be considered for its design. Key aspects for its successful implementation have appeared to be a participatory design of the system and support of the managerial positions at the inception phase. A case study in Tanzania was conducted, together with the Spanish NGO ONGAWA – Ingeniería para el Desarrollo. On the other side, DSS are required also to improve decision making on water management resources in order to achieve a sustainable development that not only improves the living conditions of the population in developing countries, but that also does not hinder opportunities of the poorest on those context. A DSS made to fulfil these requirements shall be using information from water resources modelling, as also on the environment and the social context. Through the research, a case study has been conducted in the Central Rift Valley of Ethiopia, an endhorreic basin 160 km south of Addis Ababa. There, water has been modelled using ArcSWAT, a physically based model which can assess the impact of land management practices on large complex watersheds with varying soils, land use and management conditions over long periods of time. Moreover, governance on water and environment as also the socioeconomic context have been studied.

European society of hypertension position paper on ambulatory blood pressure monitoring.

Ambulatory blood pressure monitoring (ABPM) is being used increasingly in both clinical practice and hypertension research. Although there are many guidelines that emphasize the indications for ABPM, there is no comprehensive guideline dealing with all aspects of the technique. It was agreed at a consensus meeting on ABPM in Milan in 2011 that the 34 attendees should prepare a comprehensive position paper on the scientific evidence for ABPM.This position paper considers the historical background, the advantages and limitations of ABPM, the threshold levels for practice, and the cost-effectiveness of the technique. It examines the need for selecting an appropriate device, the accuracy of devices, the additional information and indices that ABPM devices may provide, and the software requirements.At a practical level, the paper details the requirements for using ABPM in clinical practice, editing considerations, the number of measurements required, and the circumstances, such as obesity and arrhythmias, when particular care needs to be taken when using ABPM.The clinical indications for ABPM, among which white-coat phenomena, masked hypertension, and nocturnal hypertension appear to be prominent, are outlined in detail along with special considerations that apply in certain clinical circumstances, such as childhood, the elderly and pregnancy, and in cardiovascular illness, examples being stroke and chronic renal disease, and the place of home measurement of blood pressure in relation to ABPM is appraised.The role of ABPM in research circumstances, such as pharmacological trials and in the prediction of outcome in epidemiological studies is examined and finally the implementation of ABPM in practice is considered in relation to the issue of reimbursement in different countries, the provision of the technique by primary care practices, hospital clinics and pharmacies, and the growing role of registries of ABPM in many countries.

Developing a user-centric event management system

This thesis describes the development of a software requirements specification for a user-centric event management system. The system is set to satisfy three goals: adding value for the event attendees, adding value for the event organizer, and reducing the costs of arranging and running an event. The requirements are identified by researching the prescriptive traits of event business and the current state of the case company and its environment. First the professional and human needs for events are scrutinized. Second, some recent reports about the current trends in the event business are reviewed. Then the event life cycle is presented using the model of new service development, and online promotion of events and especially word-of-mouth marketing receive special attention. Events are also regarded from the perspective of social networks and social media. The case company’s current state and its competitors are reviewed to formulate the needs which the system should fulfil. Then the currently available solutions for social media oriented event management are reviewed. The result is a set of functional and non-functional requirements. The functional requirements are categorized into social media, social networking, event personalization, event management, and system administration features. The specified features and non-functional requirements satisfy the three goals set for the system.

Toiminnanohjausjärjestelmän käyttöönoton onnistuminen ja siihen vaikuttavat tekijät Pyrollsack Oy:ssä

Tämä diplomityö käsittelee toiminnanohjausjärjestelmän käyttöönottoa ja käyttöönoton kriittisten menestystekijöiden toteutumista. Työn tavoitteena oli tutkia kirjallisuudessa esiintyviä käyttöönoton kriittisiä menestystekijöitä ja verrata niitä Pyrollsack Oy:n käyttöönottoprosessista saatuihin kokemuksiin. Tuloksena voidaan havaita menestystekijät sekä esittää parannusehdotuksia havaittuihin heikkouksiin. Käyttöönottoprojektissa vahvuuksina nähtiin huolellinen valmistautuminen projektiin, uuden toiminnanohjausjärjestelmän strategisen merkityksen ymmärtäminen, nopea päätöksenteko sekä operatiivisen käyttöönoton ajoitus ja vaiheistus. Heikkouksina nähtiin liiallinen viive suunnittelun ja toteutuksen välillä, riittämättömät henkilöresurssit, ohjausryhmän toimimattomuus, viestintä, muutosjohtaminen, puutteellinen tietojen konversio, koulutus sekä toimittajan puutteellinen ymmärrys tehdystä vaatimusmäärittelystä. Käyttöönotto tulisi nähdä laajana projektina, joka koskee koko organisaatiota. Pienissä ja keskisuurissa yrityksissä erityistä huomiota tulee kiinnittää henkilöresurssien riittävyyteen. Uusi toiminnanohjausjärjestelmä saattaa aiheuttaa hetkellisen taantuman toiminnan sujuvuudessa. Toiminnanohjausjärjestelmän hyödyt toiminnalle ovat vaikeasti mitattavissa ja usein positiiviset vaikutukset havaitaan vasta vuosien päästä.

Tuotehallinnan tietoprosessin haasteet ja kehittäminen ohjelmistoyrityksessä

Diplomityössä tutustuttiin ohjelmistoyrityksen tuotteiden asiakastarpeiden ja vaatimusten käsittelyyn tuotehallinnan tietoprosessin näkökulmasta. Työssä kuvattiin yrityksen nykyinen prosessi sekä analysoitiin erityisesti sen haasteita. Teoriatiedon sekä yrityksen asiantuntijalausuntojen pohjalta laadittiin tuotehallinnan tietoprosessin kehitysehdotuksia. Kvalitatiivinen tapaustutkimus toteutettiin käytännönläheisesti esittämällä kohdeyrityksen asiantuntijoille avoimia kysymyksiä sekä heidän kanssaan keskustellen. Tutkimus tehtiin neljässä vaiheessa ja sen päätavoitteena oli selvittää, millä keinoilla voidaan tukea kohdeyrityksen tuotekehitystarpeisiin ja tuotekehitysehdotuksiin liittyvän tiedon hallintaa sekä tuotantopäätöksiä. Tutkimuksen teoreettinen viitekehys koostui organisaation tietoprosessista, organisaation päätöksentekoprosessista, ohjelmistotuotteen erityispiirteistä sekä ohjelmiston tuotehallinnasta. Kohdeyrityksen tuotehallinnan tietoprosessin kehittämisen keskeisiksi tekijöiksi nousivat tuotehallinnan tukena käytettävän tietojärjestelmän ominaisuudet, tiedon hakeminen, tiedon löytäminen ja tulkinta. Kehityskohteiksi nousivat lisäksi prosessin kulku, perustuotekehityksen ja asiakastoimituksien rinnakkainen hallinta sekä asiakasarvon tuottaminen tuotehallinnan keinoin. Tutkimuksen lopputuloksena toteutettiin kohdeyrityksen tuotehallinnan tietoprosessin tavoitetilan kuvaus. Tavoitetilan elementtejä olivat tuotteiden pidemmän tähtäimen suunnitelmat (roadmap), tuotehallinnan organisointi tiimeille sekä sensemaking-prosessin hyödyntäminen osapuolien yhteisen ymmärryksen luomiseksi kehitystarpeille. Käytössä olevan tietojärjestelmän kehitysehdotukset perustuivat näiden tuotehallinnan elementtien tukemiseen.

Uso de modelos i* para enriquecer requisitos em métodos ágeis

The activity of requirements engineering is seen in agile methods as bureaucratic activity making the process less agile. However, the lack of documentation in agile development environment is identified as one of the main challenges of the methodology. Thus, it is observed that there is a contradiction between what agile methodology claims and the result, which occurs in the real environment. For example, in agile methods the user stories are widely used to describe requirements. However, this way of describing requirements is still not enough, because the user stories is an artifact too narrow to represent and detail the requirements. The activities of verifying issues like software context and dependencies between stories are also limited with the use of only this artifact. In the context of requirements engineering there are goal oriented approaches that bring benefits to the requirements documentation, including, completeness of requirements, analysis of alternatives and support to the rationalization of requirements. Among these approaches, it excels the i * modeling technique that provides a graphical view of the actors involved in the system and their dependencies. This work is in the context of proposing an additional resource that aims to reduce this lack of existing documentation in agile methods. Therefore, the objective of this work is to provide a graphical view of the software requirements and their relationships through i * models, thus enriching the requirements in agile methods. In order to do so, we propose a set of heuristics to perform the mapping of the requirements presented as user stories in i * models. These models can be used as a form of documentation in agile environment, because by mapping to i * models, the requirements will be viewed more broadly and with their proper relationships according to the business environment that they will meet

The 3C cooperation model applied to the classical requirement analysis

Aspects related to the users' cooperative work are not considered in the traditional approach of software engineering, since the user is viewed independently of his/her workplace environment or group, with the individual model generalized to the study of collective behavior of all users. This work proposes a process for software requirements to address issues involving cooperative work in information systems that provide distributed coordination in the users' actions and the communication among them occurs indirectly through the data entered while using the software. To achieve this goal, this research uses ergonomics, the 3C cooperation model, awareness and software engineering concepts. Action-research is used as a research methodology applied in three cycles during the development of a corporate workflow system in a technological research company. This article discusses the third cycle, which corresponds to the process that deals with the refinement of the cooperative work requirements with the software in actual use in the workplace, where the inclusion of a computer system changes the users' workplace, from the face to face interaction to the interaction mediated by the software. The results showed that the highest degree of users' awareness about their activities and other system users contribute to a decrease in their errors and in the inappropriate use of the system.

Lightweight compilation of (C)LP to JavaScript

We present and evaluate a compiler from Prolog (and extensions) to JavaScript which makes it possible to use (constraint) logic programming to develop the client side of web applications while being compliant with current industry standards. Targeting JavaScript makes (C)LP programs executable in virtually every modern computing device with no additional software requirements from the point of view of the user. In turn, the use of a very high-level language facilitates the development of high-quality, complex software. The compiler is a back end of the Ciao system and supports most of its features, including its module system and its rich language extension mechanism based on packages. We present an overview of the compilation process and a detailed description of the run-time system, including the support for modular compilation into separate JavaScript code. We demonstrate the maturity of the compiler by testing it with complex code such as a CLP(FD) library written in Prolog with attributed variables. Finally, we validate our proposal by measuring the performance of some LP and CLP(FD) benchmarks running on top of major JavaScript engines.