Challenges in balancing the amount of solution information in requirement specifications for embedded products

Juha Savolainen, Dagny Hauksdottir, Mike Mannion

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Requirements are traditionally viewed as being free of the details of an envisioned solution and specified using purely problem domain entities. Preventing premature design in the requirements permits the available design space not to be restricted too early which might inhibit innovative designs. In practice, on many industrial projects, separating the problem and solution domain entities can be difficult, and arguably there are benefits for not doing so. Many customers feel more confident describing their requirements, often as the difference between the existing products and their needs, some customers have such intimate knowledge of their products that their requirements tend to be very specific, and if the customer knows the exact solution needed that naturally will reduce the cost of the requirements elicitation as well as design activities. Practitioners are challenged to understand when having solution information in requirements is sensible and when it should be avoided. In this research challenge paper, we advocate that researchers should identify different contexts and corresponding criteria that practitioners can use to evaluate when requirements specifications may include design information. To understand the research challenge we present experiences from real projects and suggest possible factors that affect when design information may be viable in requirements specifications.
Original languageEnglish
Title of host publication21st IEEE International Requirements Engineering Conference (RE)
Subtitle of host publicationProceedings
Place of PublicationPassau, Germany
PublisherIEEE
Pages256-260
Number of pages5
ISBN (Electronic)978-1-4673-5765-4
DOIs
Publication statusPublished - 2013

Fingerprint

Specifications
Costs

Keywords

  • inverters
  • companies
  • standards
  • transportation
  • assembly
  • complexity theory
  • context

Cite this

Savolainen, J., Hauksdottir, D., & Mannion, M. (2013). Challenges in balancing the amount of solution information in requirement specifications for embedded products. In 21st IEEE International Requirements Engineering Conference (RE): Proceedings (pp. 256-260). Passau, Germany: IEEE. https://doi.org/10.1109/RE.2013.6636726
Savolainen, Juha ; Hauksdottir, Dagny ; Mannion, Mike. / Challenges in balancing the amount of solution information in requirement specifications for embedded products. 21st IEEE International Requirements Engineering Conference (RE): Proceedings. Passau, Germany : IEEE, 2013. pp. 256-260
@inproceedings{86ebf91665b24fac9128a98763301cd9,
title = "Challenges in balancing the amount of solution information in requirement specifications for embedded products",
abstract = "Requirements are traditionally viewed as being free of the details of an envisioned solution and specified using purely problem domain entities. Preventing premature design in the requirements permits the available design space not to be restricted too early which might inhibit innovative designs. In practice, on many industrial projects, separating the problem and solution domain entities can be difficult, and arguably there are benefits for not doing so. Many customers feel more confident describing their requirements, often as the difference between the existing products and their needs, some customers have such intimate knowledge of their products that their requirements tend to be very specific, and if the customer knows the exact solution needed that naturally will reduce the cost of the requirements elicitation as well as design activities. Practitioners are challenged to understand when having solution information in requirements is sensible and when it should be avoided. In this research challenge paper, we advocate that researchers should identify different contexts and corresponding criteria that practitioners can use to evaluate when requirements specifications may include design information. To understand the research challenge we present experiences from real projects and suggest possible factors that affect when design information may be viable in requirements specifications.",
keywords = "inverters, companies, standards, transportation, assembly, complexity theory, context",
author = "Juha Savolainen and Dagny Hauksdottir and Mike Mannion",
year = "2013",
doi = "10.1109/RE.2013.6636726",
language = "English",
pages = "256--260",
booktitle = "21st IEEE International Requirements Engineering Conference (RE)",
publisher = "IEEE",

}

Savolainen, J, Hauksdottir, D & Mannion, M 2013, Challenges in balancing the amount of solution information in requirement specifications for embedded products. in 21st IEEE International Requirements Engineering Conference (RE): Proceedings. IEEE, Passau, Germany, pp. 256-260. https://doi.org/10.1109/RE.2013.6636726

Challenges in balancing the amount of solution information in requirement specifications for embedded products. / Savolainen, Juha ; Hauksdottir, Dagny; Mannion, Mike.

21st IEEE International Requirements Engineering Conference (RE): Proceedings. Passau, Germany : IEEE, 2013. p. 256-260.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

TY - GEN

T1 - Challenges in balancing the amount of solution information in requirement specifications for embedded products

AU - Savolainen, Juha

AU - Hauksdottir, Dagny

AU - Mannion, Mike

PY - 2013

Y1 - 2013

N2 - Requirements are traditionally viewed as being free of the details of an envisioned solution and specified using purely problem domain entities. Preventing premature design in the requirements permits the available design space not to be restricted too early which might inhibit innovative designs. In practice, on many industrial projects, separating the problem and solution domain entities can be difficult, and arguably there are benefits for not doing so. Many customers feel more confident describing their requirements, often as the difference between the existing products and their needs, some customers have such intimate knowledge of their products that their requirements tend to be very specific, and if the customer knows the exact solution needed that naturally will reduce the cost of the requirements elicitation as well as design activities. Practitioners are challenged to understand when having solution information in requirements is sensible and when it should be avoided. In this research challenge paper, we advocate that researchers should identify different contexts and corresponding criteria that practitioners can use to evaluate when requirements specifications may include design information. To understand the research challenge we present experiences from real projects and suggest possible factors that affect when design information may be viable in requirements specifications.

AB - Requirements are traditionally viewed as being free of the details of an envisioned solution and specified using purely problem domain entities. Preventing premature design in the requirements permits the available design space not to be restricted too early which might inhibit innovative designs. In practice, on many industrial projects, separating the problem and solution domain entities can be difficult, and arguably there are benefits for not doing so. Many customers feel more confident describing their requirements, often as the difference between the existing products and their needs, some customers have such intimate knowledge of their products that their requirements tend to be very specific, and if the customer knows the exact solution needed that naturally will reduce the cost of the requirements elicitation as well as design activities. Practitioners are challenged to understand when having solution information in requirements is sensible and when it should be avoided. In this research challenge paper, we advocate that researchers should identify different contexts and corresponding criteria that practitioners can use to evaluate when requirements specifications may include design information. To understand the research challenge we present experiences from real projects and suggest possible factors that affect when design information may be viable in requirements specifications.

KW - inverters

KW - companies

KW - standards

KW - transportation

KW - assembly

KW - complexity theory

KW - context

U2 - 10.1109/RE.2013.6636726

DO - 10.1109/RE.2013.6636726

M3 - Conference contribution

SP - 256

EP - 260

BT - 21st IEEE International Requirements Engineering Conference (RE)

PB - IEEE

CY - Passau, Germany

ER -

Savolainen J, Hauksdottir D, Mannion M. Challenges in balancing the amount of solution information in requirement specifications for embedded products. In 21st IEEE International Requirements Engineering Conference (RE): Proceedings. Passau, Germany: IEEE. 2013. p. 256-260 https://doi.org/10.1109/RE.2013.6636726