Requirement patterns: an approach for streamlining requirements engineering in software product families

Reusable structure is essential in all reuse-based software development processes. This provides a solid foundation for seamless management of reusable artefacts especially in software product line engineering (SPLE). One of the potential benefits provided by a well-defined structure is systematic reuse of these artefacts. Requirements pattern approach provides guidelines for requirement engineers to reuse and specify requirements. Although a plethora of research on requirements pattern have been reported in the literature, no research available focuses on requirement engineering (RE) activities of SPLE. In this paper, we present an anatomy of software requirement pattern (SRP) for SPLE with a structured example from e-learning domain. To enable practitioners, understand the concept of requirement pattern more, we present a meta-model for the SRP concepts and their relationships. In addition, we describe how the requirement pattern approach, streamlines RE activities, design for and with reuse in both domain and application engineering processes of SPLE. The requirement pattern approach thus helps in achieving systematic requirements reuse (RR) and generation of structured software requirement specification (SRS) for individual applications

Separating Agent-Functioning and Inter-Agent Coordination by Activated Modules: The DECOMAS Architecture

The embedding of self-organizing inter-agent processes in distributed software applications enables the decentralized coordination system elements, solely based on concerted, localized interactions. The separation and encapsulation of the activities that are conceptually related to the coordination, is a crucial concern for systematic development practices in order to prepare the reuse and systematic integration of coordination processes in software systems. Here, we discuss a programming model that is based on the externalization of processes prescriptions and their embedding in Multi-Agent Systems (MAS). One fundamental design concern for a corresponding execution middleware is the minimal-invasive augmentation of the activities that affect coordination. This design challenge is approached by the activation of agent modules. Modules are converted to software elements that reason about and modify their host agent. We discuss and formalize this extension within the context of a generic coordination architecture and exemplify the proposed programming model with the decentralized management of (web) service infrastructures

Requirements patterns structure for specifying and reusing software product line requirements

A well-defined structure is essential in all software development, thus providing an avenue for smooth execution of the processes involved during various software development phases. One of the potential benefits provided by a well-defined structure is systematic reuse of software artifacts. Requirements pattern approach provides guidelines and modality that enables a systematic way of specifying and documenting requirements, which in turn supports a systematic reuse. Although there is a great deal of research concerning requirements pattern in the literature, the research focuses are not on requirement engineering (RE) activities of SPLE. In this paper, we proposed a software requirement pattern (SRP) structure based on RePa Requirements Pattern Template, which was adapted to best suit RE activities in SPLE. With this requirement pattern structure, RE activities such as elicitation and identification of common and variable requirements as well as the specification, documentation, and reuse in SPLE could be substantially improved

Business Family Engineering. Managing the Evolution of Business Driven Systems

Nowadays most companies in whichever field have a software system that helps managing all the aspects of the company, from the strategic management to daily activities. Companies are in continuous evolution to adapt to market changes, and consequently, the Information Technology (IT) infrastructure that supports it must also evolve. Thus, software companies are currently supporting this evolution with ad hoc techniques. We think that, as it is being done for traditional software systems (non-oriented to business process) in the software product line (SPL) field, institutionalized techniques for performing a systematic reuse of business processes across different businesses can be introduced. in this paper, we propose to adapt SPL techniques, oriented to reuse software, to Business-Driven Development (BDD), oriented to reuse processes, across different businesses; we call this proposal Business Family Engineering (BFE). We present a first approach to build a SPL of BDD systems that evolves at runtim

Business Family Engineering. Does It Make Sense ?

Nowadays most companies in whichever field have a software system that helps managing all the aspects of the company, from the strategic management to daily activities. Companies are in continuous evolution to adapt to market changes, and consequently, the Information Technology (IT) infrastructure that supports it must also evolve. Thus, software companies are currently supporting this evolution with ad hoc techniques. We think that, as it is being done for traditional software systems (non-oriented to business process) in the software product line (SPL) field, institutionalized techniques for performing a systematic reuse of business processes across different businesses can be introduced. in this paper, we explore the feasibility of adapting SPL techniques, oriented to reuse software, to Business-Driven Development (BDD), oriented to reuse processes, across different businesses; we call this approach Business Family Engineering (BFE). As a result of our study, we show some of the problems we have identified and some of the key aspects needed to enable this new field

Validation of RP-SPF framework: a systematic method for requirements reuse in software product lines

Reuse of requirements is crucial activity in software development especially across software product line engineering (SPLE), which involves two main processes known as domain engineering and application engineering. With these two processes SPLE enables systematic reuse of requirements through proper planning and development. This paper presents methodology and result of survey of experts for validating a proposed systematic requirement reuse approach named requirements pattern for software product families (RP-SPF) framework. During the survey, 14 experts in requirements engineering (RE), SPLE and software development responded and gave their opinions on RP-SPF framework. The result of the survey shows that RP-SPF approach is suitable and can effectively improve requirements engineering activities of SPLE. © BEIESP

Model driven product line engineering : core asset and process implications

Reuse is at the heart of major improvements in productivity and quality in Software Engineering. Both Model Driven Engineering (MDE) and Software Product Line Engineering (SPLE) are software development paradigms that promote reuse. Specifically, they promote systematic reuse and a departure from craftsmanship towards an industrialization of the software development process. MDE and SPLE have established their benefits separately. Their combination, here called Model Driven Product Line Engineering (MDPLE), gathers together the advantages of both. Nevertheless, this blending requires MDE to be recasted in SPLE terms. This has implications on both the core assets and the software development process. The challenges are twofold: (i) models become central core assets from which products are obtained and (ii) the software development process needs to cater for the changes that SPLE and MDE introduce. This dissertation proposes a solution to the first challenge following a feature oriented approach, with an emphasis on reuse and early detection of inconsistencies. The second part is dedicated to assembly processes, a clear example of the complexity MDPLE introduces in software development processes. This work advocates for a new discipline inside the general software development process, i.e., the Assembly Plan Management, which raises the abstraction level and increases reuse in such processes. Different case studies illustrate the presented ideas.This work was hosted by the University of the Basque Country (Faculty of Computer Sciences). The author enjoyed a doctoral grant from the Basque Goverment under the “Researchers Training Program” during the years 2005 to 2009. The work was was co-supported by the Spanish Ministry of Education, and the European Social Fund under contracts WAPO (TIN2005-05610) and MODELINE (TIN2008-06507-C02-01)

Analysis of expert’s opinion on requirements patterns for software product families framework using GQM method

Software product line engineering (SPLE), provides an opportunity to improve reuse of software artifacts through domain engineering and application engineering processes. During the domain engineering process, reuse activities of the product line are well-planned and subsequently executed in the application engineering process. This paper presents an analysis of interview result with experts in requirements engineering (RE) and software development for validating requirements pattern for software product families (RP-SPF) framework. The interview was conducted using goal questions metrics (GQM) method to define a goal and formulate research questions for conducting the interview. During the interview, 6 experts compared RP-SPF approach (systematic) with ad hoc (conventional) approach of reuse and documentation of requirements in terms of suitability, efficiency, and effectiveness in SPLE. The experts also gave their feedback on the perception of the use of RP-SPF tool. The analysis of the interview result shows that RP-SPF approach is suitable in SPLE and more efficient and effective than ad hoc approach of reuse and documentation of requirements

Knowledge-related processes critical to the enabling of systematic software asset reuse in a global IT company

This research presents a case study on the knowledge management processes critical for achieving systematic software asset reuse in a global IT company. Reusing a software asset and its related artefacts at selected other business clients drives innovation, increases efficiency and can generate several million dollars in revenue from just one reuse. To date, known software asset reuse success is limited. Despite practical relevance, research has stagnated by mainly investigating technical reuse aspects. This thesis addresses three gaps in the literature by looking from a business perspective at the intellectual capital required for software asset reuse, presenting five real-life software asset reuses and detailing the knowledge management processes towards systematic software asset reuse. The answers to the research questions advance the academic literature in the fields of intellectual capital, circular economy and knowledge. Theoretical implications are: The intellectual capital required for systematic software asset reuse is a particular software asset, the reusable software asset, further defined here. The circular economy is enriched by adding a two-step distribution task to the reuse process. The thesis refines knowledge management concerning intangible reuse. A new finding is that software asset reuse requires a proactive decision to anticipate a scarcity of knowledge in space or time, which has been identified as the software asset reuse trigger. Reuse sets in before the life end of the software asset is reached. It creates parallel software instances via abstraction, repurposing and adaptation. These boost the asset lifetime as they are logically linked. They represent tailored solutions for a heterogeneous client base and, therefore, target business-to-business niche markets. This thesis makes an original contribution to knowledge by identifying that collaborative sharing of the change required for one client with existing reusers leads to improved software quality, surpassing that of other software constructs. Further, it claims that reusable software assets target a parallel market to software products. This research significantly contributes to practice: First, by demonstrating that reuse is only feasible if the software asset can be adapted. Second, one reason for being of some reusable software assets is to stop the flood of less funded individual software trying to serve the same need. Third, a managerial guide provides advice on building reuse capabilities in the IT organisation to support the change that drives software asset reuse

What Do We Know About Hugging Face? A Systematic Literature Review and Quantitative Validation of Qualitative Claims

Background: Collaborative Software Package Registries (SPRs) are an integral part of the software supply chain. Much engineering work synthesizes SPR package into applications. Prior research has examined SPRs for traditional software, such as NPM (JavaScript) and PyPI (Python). Pre-Trained Model (PTM) Registries are an emerging class of SPR of increasing importance, because they support the deep learning supply chain.Aims: Recent empirical research has examined PTM registries in ways such as vulnerabilities, reuse processes, and evolution. However, no existing research synthesizes them to provide a systematic understanding of the current knowledge. Some of the existing research includes qualitative claims lacking quantitative analysis. Our research fills these gaps by providing a knowledge synthesis and quantitative analyses.Methods: We first conduct a systematic literature review (SLR). We then observe that some of the claims are qualitative. We identify quantifiable metrics associated with those claims, and measure in order to substantiate these claims.Results: From our SLR, we identify 12 claims about PTM reuse on the HuggingFace platform, 4 of which lack quantitative validation. We successfully test 3 of these claims through a quantitative analysis, and directly compare one with traditional software. Our findings corroborate qualitative claims with quantitative measurements. Our findings are: (1) PTMs have a much higher turnover rate than traditional software, indicating a dynamic and rapidly evolving reuse environment within the PTM ecosystem; and (2) There is a strong correlation between documentation quality and PTM popularity.Conclusions: We confirm qualitative research claims with concrete metrics, supporting prior qualitative and case study research. Our measures show further dynamics of PTM reuse, inspiring research infrastructure and new measures