Climate change calls for action from all sectors of our global economy, including ICT. Therefore, it is important to change the way we develop software to address the challenges posed by sustainability. Our goal is to contribute with a reusable sustainability requirements catalogue that helps developers be aware of sustainability-related properties worth considering during software development. The information for this catalogue was gathered via a systematic mapping study, whose results were synthesised in feature models and then modelled using iStar for a more expressive and configurable representation. A qualitative evaluation of the catalogue’s readability, interest, utility, and usefulness by 50 participants from the domain, showed that around 79% of the respondents found the catalogue “Good” or “Very Good”. However, more than 5% of the expert participants found weaknesses regarding most of the evaluated questions and around 25% are neutral in their overall evaluation. This led us to evolve the initial version of the catalogue for the social and technical dimensions of sustainability to improve its completeness and usefulness. This is achieved by aligning the information gathered in the systematic mapping study with the well-established quality model of the ISO/IEC 25010:2011, as we expect most of the experts are familiar with those qualities and respective hierarchies. During this process, we found information that led us to propose two additional qualities that were not covered by the ISO standard: fairness and legislation. We applied this evolved version of the catalogue to the U-Bike project comparing the requirements elicited without the catalogue with those identified using the catalogue. The result suggests that new sustainability requirements were worth considering from a sustainability point of view, supporting the usefulness of the catalogue.

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.