Requirements Management

14,000,000 Leading Edge Experts on the ideXlab platform

Scan Science and Technology

Contact Leading Edge Experts & Companies

Scan Science and Technology

Contact Leading Edge Experts & Companies

The Experts below are selected from a list of 442035 Experts worldwide ranked by ideXlab platform

Björn Regnell - One of the best experts on this subject based on the ideXlab platform.

  • Requirements are slipping through the gaps a case study on causes effects of communication gaps in large scale software development
    IEEE International Conference on Requirements Engineering, 2011
    Co-Authors: Elizabeth Bjarnason, Krzysztof Wnuk, Björn Regnell
    Abstract:

    Communication is essential for software development as its efficiency throughout the entire project life-cycle is a key factor in developing and releasing successful software products to the market. This paper reports on findings from an explanatory case study aiming at a deeper understanding of the causes and effects of communication gaps in a large-scale industrial set up. Based on an assumption of what causes gaps in communication of Requirements and what effects such gaps have, a semi-structured interview study was performed with nine practitioners at a large market-driven software company. We found four main factors that affect the Requirements communication, namely scale, temporal aspects, common views and decision structures. The results also show that communication gaps lead to failure to meet the customers' expectations, quality issues and wasted effort. An increased awareness of these factors is a help in identifying what to address to achieve a more efficient Requirements Management, and ultimately more efficient and successful software development. By closing the communication gaps the Requirements may continue all the way through the project life-cycle and be more likely to result in software that meets the customers' expectations.

  • what decision characteristics influence decision making in market driven large scale software product line development
    Requirements Engineering: Foundation for Software Quality, 2010
    Co-Authors: Jaap Kabbedijk, Björn Regnell, Krzysztof Wnuk, Sjaak Brinkkemper
    Abstract:

    Time efficiency is crucial for decision making in large scale market driven software product line development. In order to identify what factors influence the decision lead time and outcome, we conducted a retrospective case study at a large product software manufacturer and statistically analyzed seven possible relationships among decision characteristics. A large Requirements engineering decision log was used to statistically test all hypotheses. The results show that the number of products affected by a decision has a positive relationship with the time needed to take a decision. Furthermore, more products imply a longer decision lead time. Results also show that when a change request originates from an important customer, the request is sooner accepted than changes requested internally. For efficient Requirements Management, our findings support that decision making activities can be carefully refined in large scale Requirements engineering processes. Our findings, may be useful for Product Managers to understand the consequences of making certain types of decisions and planning actions in order to avoid their negative effects.

  • an experiment on linguistic tool support for consolidation of Requirements from multiple sources in market driven product development
    Empirical Software Engineering, 2006
    Co-Authors: Johan Natt Och Dag, Thomas Thelin, Björn Regnell
    Abstract:

    This paper presents an experiment with a linguistic support tool for consolidation of Requirements sets. The experiment is designed based on the Requirements Management process at a large market-driven software development company that develops generic solutions to satisfy many different customers. New Requirements and requests for information are continuously issued, which must be analyzed and responded to. The new Requirements should first be consolidated with the old to avoid reanalysis of previously elicited Requirements and to complement existing Requirements with new information. In the presented experiment, a new open-source tool is evaluated in a laboratory setting. The tool uses linguistic engineering techniques to calculate similarities between Requirements and presents a ranked list of suggested similar Requirements, between which links may be assigned. It is hypothesized that the proposed technique for finding and linking similar Requirements makes the consolidation more efficient. The results show that subjects that are given the support provided by the tool are significantly more efficient and more correct in consolidating two Requirements sets, than are subjects that do not get the support. The results suggest that the proposed techniques may give valuable support and save time in an industrial Requirements consolidation process.

  • a linguistic engineering approach to large scale Requirements Management
    IEEE Software, 2005
    Co-Authors: Björn Regnell, Vincenzo Gervasi
    Abstract:

    For large software companies, the sheer number of textual Requirements presents specific challenges. To find market opportunities, organizations must continuously elicit new Requirements and reevaluate old ones as market needs evolve. Developing large, complex software products aimed at broad markets involves identifying and maintaining the link between product Requirements and the massive inflow of customers' wishes. Automating this support through linguistic engineering could save considerable time and improve software quality.

  • speeding up Requirements Management in a product software company linking customer wishes to product Requirements through linguistic engineering
    IEEE International Conference on Requirements Engineering, 2004
    Co-Authors: Vincenzo Gervasi, Sjaak Brinkkemper, Björn Regnell
    Abstract:

    Developing large complex software products aimed for a broad market involves a great flow of wishes and Requirements. The former are elicited from customers while the latter are brought forth by the developing organization. These are preferably kept separated to preserve the different perspectives. The interrelationships should however be identified and maintained to enable well-founded decisions. Unfortunately, the current manual linkage is cumbersome, time-consuming, and error-prone. This work presents a pragmatic linguistic engineering approach to how statistical natural language processing may be used to support the manual linkage between customer wishes and product Requirements by suggesting potential links. An evaluation with real Requirements from industry is presented. It shows that in a realistic setting, automatic support could make linkage faster for at least 50% of the links. An estimation based on our evaluation also shows that considerable time savings are possible. The results, together with the identified enhancement, are promising for improving software quality and saving time in industrial Requirements engineering.

Sjaak Brinkkemper - One of the best experts on this subject based on the ideXlab platform.

  • specification of Requirements and software architecture for the customisation of enterprise software a multi case study based on the re4sa model
    2019 IEEE 27th International Requirements Engineering Conference Workshops (REW), 2019
    Co-Authors: Tjerk Spijkman, Sjaak Brinkkemper, Fabiano Dalpiaz, Annefleur Hemmer, Richard Van De Bospoort
    Abstract:

    Many failed software projects can be traced to bad Requirements Management. Additionally, there is a big gap be-tween state of the art and practice in software architecture. For enterprise software customisation, not only do these issues apply, but additional challenges exist too. Instead of one standard soft-ware product, vendors often have to deal with customised ver-sions with additional maintenance challenges. In this research, we apply the Requirements Engineering for Software Architecture (RE4SA) model via a multi-case study to show how the require-ments engineering and software architecture disciplines can be linked, and in doing so provide improvements to both areas. Our multi-case study regards enterprise software customisation and shows improvements in Requirements Management and higher alignment between the software architecture and Requirements.

  • what decision characteristics influence decision making in market driven large scale software product line development
    Requirements Engineering: Foundation for Software Quality, 2010
    Co-Authors: Jaap Kabbedijk, Björn Regnell, Krzysztof Wnuk, Sjaak Brinkkemper
    Abstract:

    Time efficiency is crucial for decision making in large scale market driven software product line development. In order to identify what factors influence the decision lead time and outcome, we conducted a retrospective case study at a large product software manufacturer and statistically analyzed seven possible relationships among decision characteristics. A large Requirements engineering decision log was used to statistically test all hypotheses. The results show that the number of products affected by a decision has a positive relationship with the time needed to take a decision. Furthermore, more products imply a longer decision lead time. Results also show that when a change request originates from an important customer, the request is sooner accepted than changes requested internally. For efficient Requirements Management, our findings support that decision making activities can be carefully refined in large scale Requirements engineering processes. Our findings, may be useful for Product Managers to understand the consequences of making certain types of decisions and planning actions in order to avoid their negative effects.

  • Software Product Manager: A Mechanism to manage software products in small and medium ISVs
    2009
    Co-Authors: R. Katchow, Sjaak Brinkkemper, I. Van De Weerd, A. Rooswinkel
    Abstract:

    In this paper, we present SP Manager as an innovative tool for managing software products in small and medium independent software vendors (ISVs). This tool incorporates the operational software product Management (SPM) processes focused on Requirements Management and release planning. By using situational method engineering techniques, the tool is easy to adapt to a specific company context. In addition, by making it possible to integrate the tool with the development platform, the tool is easy to deploy and adopt. The expert validation of this tool indicates that the included development concepts, such as the integration of SPM with system defect Management, provide additional advantages to other SPM tools in the market.

  • becoming responsive to service usage and performance changes by applying service feedback metrics to software maintenance
    Automated Software Engineering, 2008
    Co-Authors: H W Van Der Schuur, Slinger Jansen, Sjaak Brinkkemper
    Abstract:

    Software vendors are unaware of how their software performs in the field. They do not know what parts of their software are used and appreciated most and have little knowledge about the behavior of the software and its environment. In this paper we present a metrics-based approach that is used by software vendors to create real-time usage reports, based on data gathered by leveraging aspect-oriented programming techniques. This approach enables software vendors to respond quickly to performance and usage changes in their service software, both at specific customers and concerning the service software in general. We show that by using this approach, vendors can make informed decisions with respect to software Requirements Management and maintenance. The metrics and usage reports are validated by way of a case study at a Dutch software vendor. While validation shows high potential of the approach, a successful implementation will require change Management at the software vendor.

  • speeding up Requirements Management in a product software company linking customer wishes to product Requirements through linguistic engineering
    IEEE International Conference on Requirements Engineering, 2004
    Co-Authors: Vincenzo Gervasi, Sjaak Brinkkemper, Björn Regnell
    Abstract:

    Developing large complex software products aimed for a broad market involves a great flow of wishes and Requirements. The former are elicited from customers while the latter are brought forth by the developing organization. These are preferably kept separated to preserve the different perspectives. The interrelationships should however be identified and maintained to enable well-founded decisions. Unfortunately, the current manual linkage is cumbersome, time-consuming, and error-prone. This work presents a pragmatic linguistic engineering approach to how statistical natural language processing may be used to support the manual linkage between customer wishes and product Requirements by suggesting potential links. An evaluation with real Requirements from industry is presented. It shows that in a realistic setting, automatic support could make linkage faster for at least 50% of the links. An estimation based on our evaluation also shows that considerable time savings are possible. The results, together with the identified enhancement, are promising for improving software quality and saving time in industrial Requirements engineering.

Liam Peyton - One of the best experts on this subject based on the ideXlab platform.

  • a systematic review of goal oriented Requirements Management frameworks for business process compliance
    International Workshop on Requirements Engineering and Law, 2011
    Co-Authors: Sepideh Ghanavati, Daniel Amyot, Liam Peyton
    Abstract:

    Legal compliance has been an active topic in Software Engineering and Information Systems for many years. However, business analysts and others recently started exploiting Requirements Engineering techniques, and in particular goal-oriented approaches, to model and reason about legal documents in system design and business process Management. Many contributions involve extracting legal Requirements, providing law-compliant business processes, as well as managing and maintaining compliance. In this paper, we report on a systematic literature review focusing on goal-oriented legal compliance of business processes. 88 papers were selected out of nearly 800 unique papers extracted from five search engines, with manual additions from the Requirements Engineering Journal and four relevant conferences. We grouped these papers in eight categories based on a set of criteria and then highlight their main contributions. We found that the main areas for contributions have been in extracting legal Requirements, modeling them with goal modeling languages, and integrating them with business processes. We identify gaps and opportunities for future work in areas related to prioritization to improve compliance, templates for generating law-compliant processes, general links between legal Requirements, goal models, and business processes, and semi-automation of legal compliance and analysis.

  • a systematic review of goal oriented Requirements Management frameworks for business process compliance
    International Workshop on Requirements Engineering and Law, 2011
    Co-Authors: Sepideh Ghanavati, Daniel Amyot, Liam Peyton
    Abstract:

    Legal compliance has been an active topic in Software Engineering and Information Systems for many years. However, business analysts and others recently started exploiting Requirements Engineering techniques, and in particular goal-oriented approaches, to model and reason about legal documents in system design and business process Management. Many contributions involve extracting legal Requirements, providing law-compliant business processes, as well as managing and maintaining compliance. In this paper, we report on a systematic literature review focusing on goal-oriented legal compliance of business processes. 88 papers were selected out of nearly 800 unique papers extracted from five search engines, with manual additions from the Requirements Engineering Journal and four relevant conferences. We grouped these papers in eight categories based on a set of criteria and then highlight their main contributions. We found that the main areas for contributions have been in extracting legal Requirements, modeling them with goal modeling languages, and integrating them with business processes. We identify gaps and opportunities for future work in areas related to prioritization to improve compliance, templates for generating law-compliant processes, general links between legal Requirements, goal models, and business processes, and semi-automation of legal compliance and analysis.

  • a Requirements Management framework for privacy compliance
    WER, 2007
    Co-Authors: Sepideh Ghanavati, Daniel Amyot, Liam Peyton
    Abstract:

    Compliance with privacy legislation is a primary concern for health care institutions that are building information systems support for their business processes. This paper describes a Requirements Management framework that enables health information custodians (HIC) to document and track compliance with privacy legislation. A metamodel is defined for our framework to define compliance tracking links between separate User Requirements Notation models of the HIC and privacy legislation. Using examples from a case study at a major teaching hospital, we show how this framework can be used to manage change and ensure compliance when privacy legislation is amended or the business processes evolved.

Krzysztof Wnuk - One of the best experts on this subject based on the ideXlab platform.

  • towards new ways of evaluating methods of supporting Requirements Management and traceability using signal to noise ratio
    International Conference on Evaluation of Novel Approaches to Software Engineering, 2019
    Co-Authors: Krzysztof Wnuk, Markus Borg, Tony Gorschek
    Abstract:

    Developing contemporary software solutions requires many processes and people working in synergy to achieve a common goal. Any misalignment between parts of the software production cycle can severe ...

  • Requirements are slipping through the gaps a case study on causes effects of communication gaps in large scale software development
    IEEE International Conference on Requirements Engineering, 2011
    Co-Authors: Elizabeth Bjarnason, Krzysztof Wnuk, Björn Regnell
    Abstract:

    Communication is essential for software development as its efficiency throughout the entire project life-cycle is a key factor in developing and releasing successful software products to the market. This paper reports on findings from an explanatory case study aiming at a deeper understanding of the causes and effects of communication gaps in a large-scale industrial set up. Based on an assumption of what causes gaps in communication of Requirements and what effects such gaps have, a semi-structured interview study was performed with nine practitioners at a large market-driven software company. We found four main factors that affect the Requirements communication, namely scale, temporal aspects, common views and decision structures. The results also show that communication gaps lead to failure to meet the customers' expectations, quality issues and wasted effort. An increased awareness of these factors is a help in identifying what to address to achieve a more efficient Requirements Management, and ultimately more efficient and successful software development. By closing the communication gaps the Requirements may continue all the way through the project life-cycle and be more likely to result in software that meets the customers' expectations.

  • what decision characteristics influence decision making in market driven large scale software product line development
    Requirements Engineering: Foundation for Software Quality, 2010
    Co-Authors: Jaap Kabbedijk, Björn Regnell, Krzysztof Wnuk, Sjaak Brinkkemper
    Abstract:

    Time efficiency is crucial for decision making in large scale market driven software product line development. In order to identify what factors influence the decision lead time and outcome, we conducted a retrospective case study at a large product software manufacturer and statistically analyzed seven possible relationships among decision characteristics. A large Requirements engineering decision log was used to statistically test all hypotheses. The results show that the number of products affected by a decision has a positive relationship with the time needed to take a decision. Furthermore, more products imply a longer decision lead time. Results also show that when a change request originates from an important customer, the request is sooner accepted than changes requested internally. For efficient Requirements Management, our findings support that decision making activities can be carefully refined in large scale Requirements engineering processes. Our findings, may be useful for Product Managers to understand the consequences of making certain types of decisions and planning actions in order to avoid their negative effects.

Wentao Wang - One of the best experts on this subject based on the ideXlab platform.

  • towards a security Requirements Management framework for open source software
    IEEE International Conference on Requirements Engineering, 2018
    Co-Authors: Wentao Wang
    Abstract:

    Security refers to a class of non-functional Requirements (NFRs) related to system confidentiality, integrity, and availability. It plays a critical role in many open source software (OSS) projects. Experience indicates that considering security early in the software life cycle can help address security problems, such as reducing information breach and unauthorized data access. However, unlike up-front Requirements engineering (RE), Requirements are fully discussed and become elaborated in OSS projects only after the implementation begins. Therefore, security Management approaches which based on up-front RE shall be modified or improved while applied to OSS projects. To make OSS projects more secure, this research extends existing security Requirements Management approaches and proposes a new security Management framework for OSS projects. I also describe obstacles for building our framework and formulate their conquering as research questions. Analysis and discussion of research questions will enable me to gain valuable insights, which I will use to improve the proposed framework.