{"title":"Invented requirements and imagined customers: requirements engineering for off-the-shelf software","authors":"C. Potts","doi":"10.1109/ISRE.1995.512553","DOIUrl":null,"url":null,"abstract":"The requirements engineering research and consulting communities are not serving the interests of software developers who build off-the-shelf application software. Most of our models and methods evolved with the aid of funding from organizations interested in obtaining unique systems under contract and in which there is a clear interface between \"customer\" and \"developer\". These origins have spawned many assumptions about what requirements are. Through several design scenarios I illustrate how these assumptions break down in the case of off-the-shelf software. I then suggest some alternative priorities that would address these shortcomings. My aim is to provoke and stimulate thought, not to propose a developed solution.","PeriodicalId":354711,"journal":{"name":"Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95)","volume":"16 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1995-03-27","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"140","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ISRE.1995.512553","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 140
Abstract
The requirements engineering research and consulting communities are not serving the interests of software developers who build off-the-shelf application software. Most of our models and methods evolved with the aid of funding from organizations interested in obtaining unique systems under contract and in which there is a clear interface between "customer" and "developer". These origins have spawned many assumptions about what requirements are. Through several design scenarios I illustrate how these assumptions break down in the case of off-the-shelf software. I then suggest some alternative priorities that would address these shortcomings. My aim is to provoke and stimulate thought, not to propose a developed solution.