A process model for requirements engineering of CCOTS

Deifel, Bernhard

doi:10.1109/dexa.1999.795186

Cited by 7 publications

(5 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Nevertheless, in order to keep, or increase, market shares, the requirements that satisfy most customers need to be selected. This further emphasises the role of marketing in the market-driven development situation [10].…”

Section: Market-driven Requirements Engineeringmentioning

confidence: 99%

“…There are mainly potential users, an imagined group of people who may fit into the profile of an intended product user. Eliciting requirements from this group of users and customers is one of the major distinguishing characteristics between market-driven and customer-specific RE [10,30,33]. This is mainly managed through marketing, technical support, user groups and trade publication reviewers [4].…”

Section: Market-driven Requirements Engineeringmentioning

confidence: 99%

See 1 more Smart Citation

Requirements engineering challenges in market-driven software development – An interview study with practitioners

Karlsson

Dahlstedt

Regnell

et al. 2007

Information and Software Technology

131

127

View full text Add to dashboard Cite

Section: Market-driven Requirements Engineeringmentioning

confidence: 99%

Section: Market-driven Requirements Engineeringmentioning

confidence: 99%

Requirements engineering challenges in market-driven software development – An interview study with practitioners

Karlsson

Dahlstedt

Regnell

et al. 2007

Information and Software Technology

131

127

View full text Add to dashboard Cite

“…Requirements validation is traditionally performed in close cooperation with the customer (bespoke RE), but in MDRE this is complicated for obvious reasons. There is the possibility to cooperate with key customers but their input may be hard to obtain, and in addition they may not be representative of all requirements in a release 44, 69. This is further complicated by the fact that some requirements are invented to suit an imaginary customer 39.…”

Section: Background and Related Workmentioning

confidence: 99%

Introduction of a process maturity model for market‐driven product management and requirements engineering

Gorschek

Gomes²,

Pettersson³

et al. 2011

J Software Evolu Process

View full text Add to dashboard Cite

SUMMARY The area of software product development of software intensive products has received much attention, especially in the area of requirements engineering and product management. Many companies are faced with new challenges when operating in an environment where potential requirements number in thousands or even tens of thousands, and where a product does not have a customer, but any number of customers or markets. The development organization carries not only all the costs of development, but also takes all the risks. In this environment traditional bespoke requirements engineering, together with traditional process assessment and improvement models fall short as they do not address the unique challenges of a market‐driven environment. This paper introduces the Market‐driven Requirements Engineering Process Model, aimed at enabling process improvement and process assurance for organizations faced with these new challenges. The model is also validated in the industry through three case studies where the model is used for process assessment and improvement suggestion. Initial results show that the model is appropriate for process improvement for organizations operating in a market‐driven environment. In addition, the model was designed to be light weight in terms of low cost and thus adapted not only for large organizations but suitable for small and medium enterprises as well. Copyright © 2011 John Wiley & Sons, Ltd.

show abstract

“…However, there is no concrete process or techniques to generate the service capabilities and implementation needed in the marketplace that the supplier is targeting. There is related work in supplierside requirements, for example Deifel [6], but this work is not specific to the unique and flexible nature of web software services.…”

Section: Introductionmentioning

confidence: 98%

Using Requirements to Define Services for Service-Centric Food Traceability Information Systems

Lockerbie

Karlsen

Puccio

et al. 2008

2008 International Workshop on Service-Oriented Computing: Consequences for Engineering Requirements

View full text Add to dashboard Cite

This paper reports empirical research on our requirements processes and methods for engineering service-centric food traceability information systems. We address the need for providing requirements for the service provider and service integrator by developing new structures, architectures and techniques needed to derive services from a requirements specification. Our results are demonstrated by addressing four specific challenges that we currently lack process and method advice for.

show abstract

A process model for requirements engineering of CCOTS

Cited by 7 publications

References 8 publications

Requirements engineering challenges in market-driven software development – An interview study with practitioners

Requirements engineering challenges in market-driven software development – An interview study with practitioners

Introduction of a process maturity model for market‐driven product management and requirements engineering

Using Requirements to Define Services for Service-Centric Food Traceability Information Systems

Contact Info

Product

Resources

About