{"title":"Requirements capture and analysis prior to modeling","authors":"S. White","doi":"10.1109/ECBS.1997.581766","DOIUrl":null,"url":null,"abstract":"Numerous stakeholders collaborate to develop system requirements for a complex system. They conceive needs, evaluate risk, cost and benefits, identify tradeoffs, and negotiate priorities over a long period of time. Government and industry need a structured approach to requirements elicitation that supports this collaborative effort. Automated support is a long term goal of the author's research. The initial goal is to develop a firm foundation for capturing requirements, analyzing them, and supporting different views, including capture views (e.g. capabilities, constraints, operational environment), domain views (e.g. tracking, manufacturing, reliability), and stakeholder views (e.g. user, customer, designer, tester). These views help the analyst review specifications for errors and omissions. The paper identifies capture views and provides details concerning the system capabilities view, which includes functions, behavior, information entities, and non-functional requirements.","PeriodicalId":240356,"journal":{"name":"Proceedings International Conference and Workshop on Engineering of Computer-Based Systems","volume":"43 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1997-03-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings International Conference and Workshop on Engineering of Computer-Based Systems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ECBS.1997.581766","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 3
Abstract
Numerous stakeholders collaborate to develop system requirements for a complex system. They conceive needs, evaluate risk, cost and benefits, identify tradeoffs, and negotiate priorities over a long period of time. Government and industry need a structured approach to requirements elicitation that supports this collaborative effort. Automated support is a long term goal of the author's research. The initial goal is to develop a firm foundation for capturing requirements, analyzing them, and supporting different views, including capture views (e.g. capabilities, constraints, operational environment), domain views (e.g. tracking, manufacturing, reliability), and stakeholder views (e.g. user, customer, designer, tester). These views help the analyst review specifications for errors and omissions. The paper identifies capture views and provides details concerning the system capabilities view, which includes functions, behavior, information entities, and non-functional requirements.