Requirements elicitation is a fundamental process in software engineering, essential for aligning software products with user needs and project objectives. As software projects become more complex, effective elicitation methods are vital for capturing accurate and comprehensive requirements. Despite the variety of available elicitation methods, practitioners face persistent challenges such as capturing tacit knowledge, managing diverse stakeholder needs, and addressing ambiguities in requirements. Moreover, although elicitation is recognized as a core process for gathering and analyzing system objectives, there is a lack of a unified and systematic framework to guide practitioners—especially newcomers—through the activity. To address these challenges, we provide a comprehensive analysis of existing elicitation methods, aiming to contribute to better alignment between software products and project objectives, ultimately improving software engineering practices. We do so by performing a systematic literature review identifying crosscutting steps, common techniques, tools, and approaches that define the core activities of the elicitation process. We synthesize our findings into a metamodel that structures software elicitation processes. This review uncovers various elicitation methods—such as collaborative workshops, interviews, and prototyping—each demonstrating unique strengths in different project contexts. It also highlights significant limitations, including stakeholder misalignment and incomplete requirements capture, which continue to reduce the effectiveness of elicitation processes. Finally, our study seeks to contribute to understanding requirements elicitation methods by providing a comprehensive view of their current strengths and limitations through a metamodel enabling the structuring and optimization of elicitation processes.
Software architects play a crucial role in proposing system designs and technologies, providing guidelines for system construction and quality assessment, and facilitating communication among stakeholders. However, training software architects is known to be challenging, with no clear set of techniques available to effectively transfer and acquire the necessary knowledge, methods, and attitudes. This paper aims to address this issue by presenting an initial characterization of the learning styles of software architects using Kolb’s Learning Styles Inventory, a well-known assessment tool designed to provide a summary of an individual’s preferred learning style. To achieve this objective, we administered Kolb’s Learning Styles Test to seven mid-senior practitioners working as software architects. The analysis of the test results revealed that the primary learning mode of these software architects is a combination of Active Experimentation and Abstract Conceptualization, followed by Concrete Experience, and to a lesser extent, Reflective Observation. Understanding the learning styles of software architects has significant implications for software engineering education and the training of these professionals. It enables courses and instructors to tailor their approaches by emphasizing practice and experimentation to foster problem-solving skills. Furthermore, it facilitates the design of activities that promote decision-making and goal-setting in the field of software architecture.
The effective transfer and acquisition of necessary knowledge, methods, and attitudes pose significant challenges for Software Engineering Education. Furthermore, training in software development skills and knowledge currently lacks a clear set of techniques to link learning styles and preferences with development team roles. This paper characterizes the learning style of four traditional roles in software development (Analyst, Architect, Developer, and Project Manager) using Kolb's Learning Styles Inventory. Kolb's Learning Styles Test was administered to 110 software development practitioners (15 analysts, 18 architects, 50 developers, and 27 project managers). The test results show that, with some differences, architects and analysts have the Deciding style, while developers and project managers exhibit the Thinking style. Finally, in alignment with Kolb's learning strengths and challenges, this work provides a set of teaching strategies for each role based on their inferred learning styles.
In this work, we address the problem of locally estimating the size of a natural network using local information: fitting the sum of new neighbors discovered at step of a breadth-first search (BFS) with a logarithmic function we determined as a ln(Γ(i)) e + b. With rather little computation, we reach an estimation error of at most five percent, only allowing the BFS to visit at most ten percent of the whole network. The main contributions of this work are a new approach to estimate network size with a precision higher than 95%, an estimation algorithm that can be applied in an arbitrary natural network, and an example of the use of structural properties in optimizing network algorithms.