Requirements Analysis and Management for Benefiting Openness

Journal of Industrial Information Integration, 2018

Just-in-time (JIT) requirements are characterized as not following the traditional requirement engineering approach, instead focusing on elaboration when the implementation begins. In this experience report, which is an invited extension of a recently published work [1], we first analyze both functional and nonfunctional JIT requirements from three successful open source software (OSS) projects, including Firefox, Lucene, and Mylyn, to explore the common activities that shaped those requirements. We identify a novel refinement and resolution process that all studied requirements followed from their inception to complete realization and subsequent release. Noticing some interesting phenomena more specific to non-functional requirements (NFRs), we conduct a second study examining 50 NFRs from the aforementioned three subject systems. This study reveals a slightly different process followed in the refinement and resolution of NFRs. It also provides further evidence that NFR refinement and resolution activities focus more on implementation refinement rather than requirement elaboration in the studied systems. Our research provides new insights into how OSS project teams create quality features from simple initial descriptions of JIT requirements, uncovers activities more particular to JIT requirements engineering (RE) for NFRs, and opens new avenues for further research in the emerging JIT RE field.

International Journal of Advanced Computer Science and Applications, 2018

The trend of Open Source Software development has been increased from the past few years. It has gained much attention of developers in the industry. The development of open source software systems is slightly different from traditional software development. In open source software development, requirement elicitation is a very complex and critical process as developers from different regions of the world develop the system so it’s really difficult to gather requirements for such systems. A variety of available tools, techniques, and approaches are used to perform the process of requirement elicitation. The purpose of this study is to focus on how the process of requirement elicitation is carried out for open source software and the different ways which are used to simplify the process of requirement elicitation. This paper comprehensively describes the techniques which are available and are used for requirement elicitation in open source software development. To do so, a literature...

IFIP Advances in Information and Communication Technology, 2015

Open source software ecosystem modelling has emerged as an important research area in software engineering. Several models have been proposed to identify and analyse the complex relationships in OSSecosystems. However, there is a lack of formal models, methodologies, tool support, and standard notations for OSS-ecosystems. In this paper we propose a general framework for support the OSS-ecosystems modelling process. This framework will allow the representation, synthesis, analysis, evaluation, and evolution of OSS-ecosystems. Design science methodology is proposed to create several artefacts and investigating the suitability of these artefacts in the OSS-ecosystem context.

2015

This Study is result of searching from study of configuration of technical system, organizational context, study of social process and growing relationship for rising in open source software. Main thing include is understanding the requirements for open software development efforts, and how the development of these requirements differs from those traditional to software engineering and requirements engineering. Open source software now plays vital role in development field of technical areas. Here some development communities are described, examined, and compared to help discover use of OSS in research field. Some kind of software are mentioned here for growth in development of open source in replace of close operating system platform. Subsequently, implementation of this kind of software for better result is the objective of this study.

IT Professional, 2019

Moving toward the open innovation (OI) model requires multifaceted transformations within companies. It often involves giving away the tools for product development or sharing future product directions with open tools ecosystems. Moving from the traditional closed innovation model toward an OI model for software development tools shows the potential to increase software development competence and efficiency of organizations. We report a case study in software-intensive company developing embedded devices (e.g., smartphones) followed by a survey in OSS communities such as Gerrit, Git, and Jenkins. The studied branch focuses on developing Android phones. This paper presents contribution strategies and triggers for openness. These strategies include avoid forking OSS tools, empower developers to participate in the ecosystem, steer ecosystems through contributions, create business through differentiation, and create new ecosystems. The triggers of openness are from 30 different companies with examples. Finally, openness requires a cultural change aligned with strategies and business models. & OPEN INNOVATION PENETRATES several industries such as manufacturing, finance, automotive, mining and construction, telecommunication, and software engineering. 1,9 Companies have discovered that their business may benefit from sharing knowledge with other companies (e.g., Sony Mobile, Intel, Ericsson, IBM etc.). 2,3 In OI, the knowledge may flow both inside-out and outside-in and be attached to monetary transactions, or not. 1 Tools for software engineering is an area to which companies apply OI principles. For example, in the Jenkins and Gerrit

2016

Background: Currently having a software ecosystem is vital for many technology businesses. For this reason, understanding of software ecosystem and its benefits and also the elements of each software ecosystem can help business and software communities to emerge and orchestrate the products ecosystem optimally. Moreover, an interesting phenomenon in computer science and information technology is open source software and systems which enable users to participate in developing and using the software at many scales, from a simple mobile application to large-scale business systems and ICT applications. Objective: Study of open source software ecosystem (OSS-Ecosystem) and its roles, impacts and actors in software engineering domain will reveal how practitioners and researchers encounter open source software ecosystem and the results will be applicable to other software technology products and ICT business. The main goal is to understand how open source ecosystem can promote the products in a competitive market. Methods: There is a handful of systematic literature reviews published on the concepts of the software ecosystem. This study is an attempt to bring out the relevance of open source phenomenon and software ecosystem through systematic literature review principles. This research method will show the quality of the combination of these two subjects. Results: The research strategy resulted in 462 kinds of literature, from which 93 articles were chosen as the set of primary studies. The state-of-the-art of OSS-ecosystem is clearer by its definition. Model's and actor's lists are presented to give a better overview of the functionality of ecosystem. Eventually, advantages and other challenges of OSSecosystem are cited to deliver business opportunities. Conclusion: Through out the literature definitions found for OSS-ecosystems and few of them customized for OSS-ecosystem the requirement for the definition of single open source ecosystem is required. However, various models have been proposed. To understand the models' functionality better, models are classified according to model purpose into five categories. Furthermore, important benefits and challenges extracted as a resource for decision-making process for projects or companies to make OSSecosystem foundation.

cs.bilgi.edu.tr

Open innovation, and particularly open source software is associateded with openness in terms of participation to the innovation process. Despite the prominent image of openness to participation, however, a variety of measures are taken in large scale innovation ecosystems to tame the potentially chaotic activity and growth in bottom-up innovation, and align contributions with the strategic priorities of major stakeholders. Such taming rests on the dual desires to unleash the proven power of bottom-up innovation on the one hand, and to ride it in certain directions on the other. It emerges in the form of a variety of governance mechanisms, licensing strategies, organizational practices, etc., but exhibit certain common themes. In this paper, by drawing on several examples of large scale open source software ecosystems, we demonstrate that methods employed for taming exhibit a considerable isomorphism. By drawing also on examples of failures, we further suggest that the computing industry is settling on what we call Pax Innova. It is a coherent set of practices which retain virtues of bottom-up innovation while allowing major stakeholders investing into the ecosystem to selectively support activities, and introduce top-down corporate discipline such as quality assurance measures. The choice of available practices depend on initial conditions (i.e. whether the ecosystem is led or only supported by private firms) but nevertheless shaped around the same set of requirements.

Information and Software Technology, 2017

Context: Open source software (OSS) and software ecosystems (SECOs) are two consolidated research areas in software engineering. OSS influences the way organizations develop, acquire, use and commercialize software. SECOs have emerged as a paradigm to understand dynamics and heterogeneity in collaborative software development. For this reason, SECOs appear as a valid instrument to analyze OSS systems. However, there are few studies that blend both topics together. Objective: The purpose of this study is to evaluate the current state of the art in OSS ecosystems (OSSECOs) research, specifically: (a) what the most relevant definitions related to OSSECOs are; (b) what the particularities of this type of SECO are; and (c) how the knowledge about OSSECO is represented. Method: We conducted a systematic mapping following recommended practices. We applied automatic and manual searches on different sources and used a rigorous method to elicit the keywords from the research questions and selection criteria to retrieve the final papers. As a result, 82 papers were selected and evaluated. Threats to validity were identified and mitigated whenever possible. Results: The analysis allowed us to answer the research questions. Most notably, we did the following: (a) identified 64 terms related to the OSSECO and arranged them into a taxonomy; (b) built a genealogical tree to understand the genesis of the OSSECO term from related definitions; (c) analyzed the available definitions of SECO in the context of OSS; and (d) classified the existing modelling and analysis techniques of OSSECOs. Conclusion: As a summary of the systematic mapping, we conclude that existing research on several topics related to OSSECOs is still scarce (e.g., modelling and analysis techniques, quality models, standard definitions, etc.). This situation calls for further investigation efforts on how organizations and OSS communities actually understand OSSECOs.

In large-scale open source software (OSS) innovation ecosystems that incorporate firms, a variety of measures are taken to tame the potentially chaotic activities and align the contributions of various participants with the strategic priorities of major stakeholders. Such taming rests on the dual desires of this emergent community of firms to unleash the innovation potential of OSS and to drive it to a certain direction, and it emerges in the form of various organizational activities. By drawing on a sample of large-scale OSS ecosystems, the authors discuss that methods employed for taming are isomorphic, and overview the emerging strategic pattern for establishing systems of innovation. This pattern involves a related set of practices to balance virtues of OSS community while introducing corporate discipline. In contrast to approaches such as open innovation, which favor isolated reasoning, they present a systemic and historical perspective to explain the continuum in emergence and...

2016

For many years, Requirements Engineering has been regarded as a crucial phase of software development, because it is responsible to collect from the stakeholders and model the purposes of the system to be. Consequently, lots of research results have been accumulated over the years concerning approaches to elicit and model requirements. However, eliciting and modeling requirements for innovative software, for which no determined stakeholder is defined, are still open research issues. This is due to the very nature of innovation, which asks for new ways of thinking and generating software products. This paper aims at presenting the RE process which led to the development of a web-based social network named ConecteIdeias. This social network is aimed at supporting people on creating new ideas and solutions to change social reality in the place where they live. Besides briefly presenting the social network and thoroughly describing the process, this paper also presents some lessons lear...