A Model for Technology Transfer in Practice
IEEE Software
A controlled empirical evaluation of a requirements abstraction model
Information and Software Technology
Journal of Systems and Software
Requirements engineering: In search of the dependent variables
Information and Software Technology
A practitioner's guide to light weight software process assessment and improvement planning
Journal of Systems and Software
Journal of Systems and Software
When Product Managers Gamble with Requirements: Attitudes to Value and Risk
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
A Controlled Experiment of a Method for Early Requirements Triage Utilizing Product Strategies
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
A Requirements Reference Model for Model-Based Requirements Engineering in the Automotive Domain
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
A systematic review on strategic release planning models
Information and Software Technology
The impact of agile principles on market-driven software product development
Journal of Software Maintenance and Evolution: Research and Practice
Handshaking between software projects and stakeholders using implementation proposals
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
Framework for decisional business modeling and requirements modeling in data mining projects
IDEAL'09 Proceedings of the 10th international conference on Intelligent data engineering and automated learning
Software process improvement through the Lean Measurement (SPI-LEAM) method
Journal of Systems and Software
Reusing security requirements using an extended quality model
Proceedings of the 2010 ICSE Workshop on Software Engineering for Secure Systems
The agile requirements refinery: Applying SCRUM principles to software product management
Information and Software Technology
A meta model for artefact-orientation: fundamentals and lessons learned in requirements engineering
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part II
Requirements engineering process improvement: an industrial case study
REFSQ'11 Proceedings of the 17th international working conference on Requirements engineering: foundation for software quality
Assessing requirements compliance scenarios in system platform subcontracting
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement
Release planning with feature trees: industrial case
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
Information and Software Technology
Obsolete software requirements
Information and Software Technology
Analyzing an industrial strategic release planning process: a case study at roche diagnostics
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
A taxonomy for requirements engineering and software test alignment
ACM Transactions on Software Engineering and Methodology (TOSEM)
Guiding requirements engineering for software-intensive embedded systems in the automotive industry
Computer Science - Research and Development
Hi-index | 0.00 |
Software requirements arrive in different shapes and forms to development organizations. This is particularly the case in market-driven requirements engineering, where the requirements are on products rather than directed towards projects. This results in challenges related to making different requirements comparable. In particular, this situation was identified in a collaborative effort between academia and industry. A model, with four abstraction levels, was developed as a response to the industrial need. The model allows for placement of requirements on different levels and supports abstraction or break down of requirements to make them comparable to each other. The model was successfully validated in several steps at a company. The results from the industrial validation point to the usefulness of the model. The model will allow companies to ensure comparability between requirements, and hence it generates important input to activities such as prioritization and packaging of requirements before launching a development project.