Markus Kelanti, Jari A. Lehto, Sanja Aaramaa, P. Kuvaja
{"title":"VLSRE中记录问题和解决方案领域需求的实践","authors":"Markus Kelanti, Jari A. Lehto, Sanja Aaramaa, P. Kuvaja","doi":"10.1109/SEAA.2012.52","DOIUrl":null,"url":null,"abstract":"Modern systems are becoming increasingly complex, and Requirements Engineering (RE) processes should be able to cope with thousands or tens of thousands of requirements presented by a wide variety of stakeholders. These requirements need to be analysed in order to ascertain what the actual problem is and how it should be solved. This paper describes a case in a large company in a telecommunication domain where the goal was to create a practice in order to differentiate Problem and Solution domain requirements quickly, early in Very Large Scale Requirements Engineering (VLSRE). As a result, a System-Stakeholder-Request/Requirement (SSR) practice was developed.","PeriodicalId":298734,"journal":{"name":"2012 38th Euromicro Conference on Software Engineering and Advanced Applications","volume":"68 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2012-09-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"A Practice for Recording Problem and Solution Domain Requirements in VLSRE\",\"authors\":\"Markus Kelanti, Jari A. Lehto, Sanja Aaramaa, P. Kuvaja\",\"doi\":\"10.1109/SEAA.2012.52\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Modern systems are becoming increasingly complex, and Requirements Engineering (RE) processes should be able to cope with thousands or tens of thousands of requirements presented by a wide variety of stakeholders. These requirements need to be analysed in order to ascertain what the actual problem is and how it should be solved. This paper describes a case in a large company in a telecommunication domain where the goal was to create a practice in order to differentiate Problem and Solution domain requirements quickly, early in Very Large Scale Requirements Engineering (VLSRE). As a result, a System-Stakeholder-Request/Requirement (SSR) practice was developed.\",\"PeriodicalId\":298734,\"journal\":{\"name\":\"2012 38th Euromicro Conference on Software Engineering and Advanced Applications\",\"volume\":\"68 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2012-09-05\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2012 38th Euromicro Conference on Software Engineering and Advanced Applications\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/SEAA.2012.52\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2012 38th Euromicro Conference on Software Engineering and Advanced Applications","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SEAA.2012.52","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
A Practice for Recording Problem and Solution Domain Requirements in VLSRE
Modern systems are becoming increasingly complex, and Requirements Engineering (RE) processes should be able to cope with thousands or tens of thousands of requirements presented by a wide variety of stakeholders. These requirements need to be analysed in order to ascertain what the actual problem is and how it should be solved. This paper describes a case in a large company in a telecommunication domain where the goal was to create a practice in order to differentiate Problem and Solution domain requirements quickly, early in Very Large Scale Requirements Engineering (VLSRE). As a result, a System-Stakeholder-Request/Requirement (SSR) practice was developed.