Gender-Inclusive Requirements Engineering

Publisher Copyright: © 2022 The Author(s)Gender inclusion is fundamental to a prosperous society, but inequality and exclusion persist in various sectors of it. One of them is the ICT field, which is still struggling to represent the diversity of those it serves. The lack of diversity and power imbalance in software development affects the produced systems, that, instead of advancing gender inclusion, create new barriers in achieving it. Although considered neutral, software does not equally serve everyone who depends on it, favoring characteristics that are statistically more observed in those that are represented during development. As software development teams are predominantly male, it is not surprising that existing systems favor characteristics that are statistically more observed in men over characteristics observed in other genders. As technologies rapidly evolve and revolutionize the way we live, addressing this problem becomes urgent to ensure that these systems benefit everyone, regardless of their gender. As a first step towards this goal, we performed a systematic mapping study on gender issues in software engineering whose results indicated that gender impacts development and systems, but there are limited approaches for addressing it in Requirements Engineering. This study served as the foundation for proposing a conceptual model for gender-inclusive requirements. Its main objective is to facilitate discussion and analysis of gender and related concepts in the elicitation process to include them in the specification of requirements. In this paper, we extend this work by illustrating the concepts with an example, by presenting a process for using the knowledge of the model and a prototype tool that implements it, and by discussing an evaluation with 31 participants of the conceptual model's usefulness, difficulty of understanding, strengths and weaknesses, use and recommendation, and finally, its components. The results were positive as both novices and experts in conceptual modeling considered the model useful, provided comprehensive feedback on its strengths but also suggestions for improvement, and most answered positively to the questions about whether they would use and recommend it.publishersversionpublishe

International conference on software engineering and knowledge engineering: Session chair

The Thirtieth International Conference on Software Engineering and Knowledge Engineering (SEKE 2018) will be held at the Hotel Pullman, San Francisco Bay, USA, from July 1 to July 3, 2018. SEKE2018 will also be dedicated in memory of Professor Lofti Zadeh, a great scholar, pioneer and leader in fuzzy sets theory and soft computing. The conference aims at bringing together experts in software engineering and knowledge engineering to discuss on relevant results in either software engineering or knowledge engineering or both. Special emphasis will be put on the transference of methods between both domains. The theme this year is soft computing in software engineering & knowledge engineering. Submission of papers and demos are both welcome

Modelling Requirements for Content Recommendation Systems

This paper addresses the modelling of requirements for a content Recommendation System (RS) for Online Social Networks (OSNs). On OSNs, a user switches roles constantly between content generator and content receiver. The goals and softgoals are different when the user is generating a post, as opposed as replying to a post. In other words, the user is generating instances of different entities, depending on the role she has: a generator generates instances of a "post", while the receiver generates instances of a "reply". Therefore, we believe that when addressing Requirements Engineering (RE) for RS, it is necessary to distinguish these roles clearly. We aim to model an essential dynamic on OSN, namely that when a user creates (posts) content, other users can ignore that content, or themselves start generating new content in reply, or react to the initial posting. This dynamic is key to designing OSNs, because it influences how active users are, and how attractive the OSN is for existing, and to new users. We apply a well-known Goal Oriented RE (GORE) technique, namely i-star, and show that this language fails to capture this dynamic, and thus cannot be used alone to model the problem domain. Hence, in order to represent this dynamic, its relationships to other OSNs' requirements, and to capture all relevant information, we suggest using another modelling language, namely Petri Nets, on top of i-star for the modelling of the problem domain. We use Petri Nets because it is a tool that is used to simulate the dynamic and concurrent activities of a system and can be used by both practitioners and theoreticians.Comment: 28 pages, 7 figure

An Entry Point for Formal Methods: Specification and Analysis of Event Logs

Formal specification languages have long languished, due to the grave scalability problems faced by complete verification methods. Runtime verification promises to use formal specifications to automate part of the more scalable art of testing, but has not been widely applied to real systems, and often falters due to the cost and complexity of instrumentation for online monitoring. In this paper we discuss work in progress to apply an event-based specification system to the logging mechanism of the Mars Science Laboratory mission at JPL. By focusing on log analysis, we exploit the "instrumentation" already implemented and required for communicating with the spacecraft. We argue that this work both shows a practical method for using formal specifications in testing and opens interesting research avenues, including a challenging specification learning problem

Mapping languages analysis of comparative characteristics

RDF generation processes are becoming more interoperable, reusable, and maintainable due to the increased usage of mapping languages: languages used to describe how to generate an RDF graph from (semi-)structured data. This gives rise to new mapping languages, each with different characteristics. However, it is not clear which mapping language is fit for a given task. Thus, a comparative framework is needed. In this paper, we investigate a set of mapping languages that inhibit complementary characteristics, and present an initial set of comparative characteristics based on requirements as put forward by the reference works of those mapping languages. Initial investigation found 9 broad characteristics, classified in 3 categories. To further formalize and complete the set of characteristics, further investigation is needed, requiring a joint effort of the community

Land use, urban, environmental, and cartographic applications, chapter 2, part D

Microwave data and its use in effective state, regional, and national land use planning are dealt with. Special attention was given to monitoring land use change, especially dynamic components, and the interaction between land use and dynamic features of the environment. Disaster and environmental monitoring are also discussed

A hierarchy of SPI activities for software SMEs: results from ISO/IEC 12207-based SPI assessments

In an assessment of software process improvement (SPI) in 15 software small- and –medium-sized enterprises (software SMEs), we applied the broad spectrum of software specific and system context processes in ISO/IEC 12207 to the task of examining SPI in practice. Using the data collected in the study, we developed a four-tiered pyramidal hierarchy of SPI for software SMEs, with processes in the higher tiers undergoing SPI in more companies than processes on lower level tiers. The development of the hierarchy of SPI activities for software SMEs can facilitate future evolutions of process maturity reference frameworks, such as ISO/IEC 15504, in better supporting software development in software SMEs. Furthermore, the findings extend our body of knowledge concerning the practice of SPI in software SMEs, a large and vital sector of the software development community that has largely avoided the implementation of established process maturity and software quality management standards