发布求助
文献互助 智能选刊 最新文献

Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.最新文献

筛选
英文 中文
Software requirements for architectured systems 架构系统的软件需求
Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. Pub Date : 2003-09-23 DOI: 10.1109/ICRE.2003.1232788
Elena Navarro, I. Ramos, Jennifer Pérez
{"title":"Software requirements for architectured systems","authors":"Elena Navarro, I. Ramos, Jennifer Pérez","doi":"10.1109/ICRE.2003.1232788","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232788","url":null,"abstract":"Recently, increased attention has been paid to how to establish and strengthen the relationships between requirements and architectural design. In particular, how the process must encompass changes to requirements over time and their effects upon a system's architecture. We sketch our work-in-progress in this field, which we concern about a methodology to guide the architecture development from the inception.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131105029","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 18
The journey toward secure systems: achieving assurance 迈向安全系统的旅程:获得保证
Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. Pub Date : 2003-09-08 DOI: 10.1109/ICRE.2003.1232731
S. Lipner
{"title":"The journey toward secure systems: achieving assurance","authors":"S. Lipner","doi":"10.1109/ICRE.2003.1232731","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232731","url":null,"abstract":"","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"50 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126767741","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 1
One approach to the metric baselining imperative for requirements processes 一种对需求过程进行度量基线化的方法
Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. Pub Date : 2003-09-08 DOI: 10.1109/ICRE.2003.1232767
Roy Chardon, M. Dorfman
{"title":"One approach to the metric baselining imperative for requirements processes","authors":"Roy Chardon, M. Dorfman","doi":"10.1109/ICRE.2003.1232767","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232767","url":null,"abstract":"The success of development projects in customer-oriented industries depends on reliable processes for the definition and maintenance of requirements. With the sustained, severe reduction in the rush to new technology, this widely accepted fact has become increasingly evident in the networking industry. Customers now focus on high product quality as they strive for economy of operation. Enhancing product quality necessitates enhancing processes, which in turn can necessitate applying more accurate (and precise) measures. Finding process deviations and identifying patterns of product deficiencies are critical steps to achieving high quality products. We describe the application of quantitative process control (QPC) during early development phases to establish and maintain baseline distributions characterizing RMCM&T processes, and to monitor their evolutions. Metric baselining as described includes key metric identification, and data normalization, filtering, and categorization. Empirical baselining provides the statistical sensitivity to detect requirements process problems, and to support targeted identification of particular requirements-related patterns in defects.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"120 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122473508","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 0
Integrating RE methods to support use case based requirements specification 集成可重构方法以支持基于用例的需求规范
Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. Pub Date : 2003-09-08 DOI: 10.1109/ICRE.2003.1232790
N. Maiden, S. Jones, M. Flynn
{"title":"Integrating RE methods to support use case based requirements specification","authors":"N. Maiden, S. Jones, M. Flynn","doi":"10.1109/ICRE.2003.1232790","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232790","url":null,"abstract":"There has recently been a trend in requirements engineering towards combining techniques in order to complement the deficiencies of one with the strengths of another. RESCUE is a process that continues this tradition and combines human activity modelling and i* system goal modelling in a concurrent engineering approach to support the generation of more complete and correct use case models and descriptions, and hence better requirements. The process is aimed at developing large socio-technical systems where confidence in the correctness and completeness of use cases, and hence requirements, is important. The RESCUE process has been applied and tested in the specification of requirements for CORA-2, a real and large-scale socio-technical system in which computerised assistance will be provided to air traffic controllers.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117103393","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 10
Determining socio-technical systems requirements: experiences with generating and walking through scenarios 确定社会技术系统需求:生成和遍历场景的经验
Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. Pub Date : 2003-09-08 DOI: 10.1109/ICRE.2003.1232752
Alistair Mavin, N. Maiden
{"title":"Determining socio-technical systems requirements: experiences with generating and walking through scenarios","authors":"Alistair Mavin, N. Maiden","doi":"10.1109/ICRE.2003.1232752","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232752","url":null,"abstract":"Scenarios are effective for discovering requirements, but we still do not understand what types of scenario and which walkthrough techniques are most effective. We report the application of one scenario approach - CREWS-SAVRE - to discover requirements for naval and air traffic management systems with BAE Systems and Eurocontrol respectively. Results from these experiences are used to investigate important questions about the effectiveness of structured scenario walkthroughs and the level of domain-specificity most beneficial to the discovery of requirements. Lessons learned suggest that systematic walkthroughs of simple scenarios that do not contain excessive domain knowledge are more effective for discovering system requirements. This provides the reader with simple-to-use guidelines for scenario-based requirements discovery.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130584884","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 72
Understanding and comparing model-based specification notations 理解和比较基于模型的规范符号
Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. Pub Date : 2003-09-08 DOI: 10.1109/ICRE.2003.1232750
Jianwei Niu, J. Atlee, N. Day
{"title":"Understanding and comparing model-based specification notations","authors":"Jianwei Niu, J. Atlee, N. Day","doi":"10.1109/ICRE.2003.1232750","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232750","url":null,"abstract":"Specifiers must be able to understand and compare the specification notations that they use. Traditional means for describing notations' semantics (e.g., operational semantics, logic, natural language) do not help users to identify the essential differences among notations. Previously, we presented a template-based approach defining model-based notations, in which semantics that are common among notations (e.g., the concept of an enabled transition) are captured in the template and a notation's distinct semantics (e.g., which states can enable transitions) are specified as parameters. We demonstrate the template's generality by using it to document the semantics of SCR, SDL, and Petri nets. We also show how the template can be used to compare notation variants. We believe template definitions of notations ease a user's effort in understanding and comparing model-based notations.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121152889","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 16
Evaluating the quality of a UML business model 评估UML业务模型的质量
Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. Pub Date : 2003-09-08 DOI: 10.1109/ICRE.2003.1232760
B. Berenbach
{"title":"Evaluating the quality of a UML business model","authors":"B. Berenbach","doi":"10.1109/ICRE.2003.1232760","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232760","url":null,"abstract":"Many Siemens operating companies build software products or products with a high software content (e.g. embedded software). Siemens Corporate Research has had the unique opportunity over the last few years to look at the analysis models from which the software products were derived, analyze them, and recommend changes. All the models investigated define commercial products that are or will be in the marketplace in the near future. Because of the size and complexity of the models (some running over a thousand use cases) the internal analysis tool design advisor was created to facilitate their inspection. An analysis was then performed on several models with interesting results.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"86 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114731857","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 5
Measuring requirements traceability from multiple angles at multiple lifecycle entry points 从多个生命周期入口点的多个角度度量需求可追溯性
Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. Pub Date : 2003-09-08 DOI: 10.1109/ICRE.2003.1232766
D. Becker
{"title":"Measuring requirements traceability from multiple angles at multiple lifecycle entry points","authors":"D. Becker","doi":"10.1109/ICRE.2003.1232766","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232766","url":null,"abstract":"Ideally, requirements traceability metrics are started at the beginning of a project. The initial statement of work or request for proposal form the root of the requirements tree and the traditional requirements metrics (requirements added, modified, deleted) are baselined from those documents. The collecting of requirements metrics at various stages of the lifecycle $from architecture to testing to help desk support - based on work with a number of government and commercial clients is discussed. Similar to the costs of fixing defects, the challenges of starting requirements metrics collection substantially increase the later in the lifecycle one starts but the return on investment can still be significant at each stage.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124268177","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 8
The automated extraction of requirements from UML models 从UML模型中自动提取需求
Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. Pub Date : 2003-09-08 DOI: 10.1109/ICRE.2003.1232764
B. Berenbach
{"title":"The automated extraction of requirements from UML models","authors":"B. Berenbach","doi":"10.1109/ICRE.2003.1232764","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232764","url":null,"abstract":"We have observed that often there is a disconnect between a UML model and the requirements of the modeled processes. This gap tends to widen as models become more complex and the extraction of detailed requirements becomes more difficult. The process by which detailed requirements are extracted from a model is fairly straightforward. Not only can the technique be used to extract requirements, but, interestingly enough, the same information that is extracted can be used to generate the task list part of a project plan, as the concrete use cases identify the pieces of software that need to be implemented. The use case model is basically an acyclic directed graph, with dependencies as vertices and use cases as nodes. In order for the extraction process to work, the use case model needs to be built following certain guidelines. For example: No dependency cycles and model continuity (e.g. a single continuous directed graph).","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"31 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130002510","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 22
Requirement tracking: a streamlined approach 需求跟踪:一种流线型的方法
Proceedings. 11th IEEE International Requirements Engineering Conference, 2003. Pub Date : 2003-09-08 DOI: 10.1109/ICRE.2003.1232774
J. Archer
{"title":"Requirement tracking: a streamlined approach","authors":"J. Archer","doi":"10.1109/ICRE.2003.1232774","DOIUrl":"https://doi.org/10.1109/ICRE.2003.1232774","url":null,"abstract":"The streamlined approach is a midrange approach to requirement tracking that rejects both a high degree of formality (such as requirements matrices) and informal techniques (such as \"user stories\"). The basic requirement unit is the requirement statement, not the document, or the use case. Typically, requirements statements are from one to four sentences long. The key concept of the streamlined approach is that of the concrete software requirement. The two primary characteristics are: 1) The requirement is linked to a single software deliverable which it specifies. 2) There exists a well defined completion criterion for determining when the deliverable satisfies the requirement.","PeriodicalId":243621,"journal":{"name":"Proceedings. 11th IEEE International Requirements Engineering Conference, 2003.","volume":"37 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2003-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132853695","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
引用次数: 5
下一页 尾页
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整，为了账户安全，请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
现在去查看 取消
×
提示
确定
请完成安全验证×
相关产品
×
本文献相关产品
联系我们：info@booksci.cn Book学术提供免费学术资源搜索服务，方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号：481959085
Book学术官方微信