This paper presents a method for visualizing the scoping process in platform-based development of embedded systems. The proposed visualization shows the decision process of including or excluding features that are candidates for the next release. The presented visualization charts are evaluated in a large-size embedded system platform project. The evaluation indicates that the visualization of feature survival and scope dynamics can improve the understanding of the decision process of platform scoping in real industrial projects. Future work includes dealing with the relations between features and system requirements, improving user interaction as well as visualizing statistical measures of efficiency of the scoping process.
{"title":"Visualization of Feature Survival in Platform-Based Embedded Systems Development for Improved Understanding of Scope Dynamics","authors":"Krzysztof Wnuk, B. Regnell, Lena Karlsson","doi":"10.1109/REV.2008.6","DOIUrl":"https://doi.org/10.1109/REV.2008.6","url":null,"abstract":"This paper presents a method for visualizing the scoping process in platform-based development of embedded systems. The proposed visualization shows the decision process of including or excluding features that are candidates for the next release. The presented visualization charts are evaluated in a large-size embedded system platform project. The evaluation indicates that the visualization of feature survival and scope dynamics can improve the understanding of the decision process of platform scoping in real industrial projects. Future work includes dealing with the relations between features and system requirements, improving user interaction as well as visualizing statistical measures of efficiency of the scoping process.","PeriodicalId":429417,"journal":{"name":"2008 Requirements Engineering Visualization","volume":"40 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127785060","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}
Requirements Engineering (RE) of a program is closely related to that of the projects within the program. The relationships dictate timelines of the program and related projects. Further, the relationships determine the effect of Change on the program, and the intensity of risk management required to reduce program failures. Inherent complexity of RE phase forces the relationships intricate thus making program management a difficult exercise. Familiar methods to represent relationships are descriptive alphanumeric data and gantt charts. These methods are inadequate to present the Program and Project phases with their relationships in a single paradigm. Further, with the existing methods, it is difficult to present Desired and Actual states of Program and Project phases in one model. This paper presents a tested visualization technique to connect a program RE with its projects. The technique provides an easy way to represent association of program RE to project RE.
{"title":"Visual Strawman to Relate Program RE to Project RE","authors":"B. Palyagar, P. Shanthakumar, A. Kishore","doi":"10.1109/REV.2008.5","DOIUrl":"https://doi.org/10.1109/REV.2008.5","url":null,"abstract":"Requirements Engineering (RE) of a program is closely related to that of the projects within the program. The relationships dictate timelines of the program and related projects. Further, the relationships determine the effect of Change on the program, and the intensity of risk management required to reduce program failures. Inherent complexity of RE phase forces the relationships intricate thus making program management a difficult exercise. Familiar methods to represent relationships are descriptive alphanumeric data and gantt charts. These methods are inadequate to present the Program and Project phases with their relationships in a single paradigm. Further, with the existing methods, it is difficult to present Desired and Actual states of Program and Project phases in one model. This paper presents a tested visualization technique to connect a program RE with its projects. The technique provides an easy way to represent association of program RE to project RE.","PeriodicalId":429417,"journal":{"name":"2008 Requirements Engineering Visualization","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126014446","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}
Requirements engineering heavily relies on oral and informal communication like meetings, phone calls, and e-mails. Some requirements are traditionally communicated outside formal documents in many companies. Considering document-based communication only is, therefore, not sufficient. Communication beyond documents should be taken into account when a company wants to improve its requirements engineering practices. We present a notation for visualizing the flow of requirements, explicitly including both informal and document-based communication. An example illustrates the notation by applying it to eliciting and validating security requirements. We compare our visualization approach for flows of requirements to related notations. The comparison shows how differences in notations affect the ability to model essential concepts of our approach. Explicitly modeling flows beyond documents provides new opportunities for requirement awareness, process improvement and innovation of tools and techniques.
{"title":"Beyond Documents: Visualizing Informal Communication","authors":"Kurt Schneider, Kai Stapel, Eric Knauss","doi":"10.1109/REV.2008.1","DOIUrl":"https://doi.org/10.1109/REV.2008.1","url":null,"abstract":"Requirements engineering heavily relies on oral and informal communication like meetings, phone calls, and e-mails. Some requirements are traditionally communicated outside formal documents in many companies. Considering document-based communication only is, therefore, not sufficient. Communication beyond documents should be taken into account when a company wants to improve its requirements engineering practices. We present a notation for visualizing the flow of requirements, explicitly including both informal and document-based communication. An example illustrates the notation by applying it to eliciting and validating security requirements. We compare our visualization approach for flows of requirements to related notations. The comparison shows how differences in notations affect the ability to model essential concepts of our approach. Explicitly modeling flows beyond documents provides new opportunities for requirement awareness, process improvement and innovation of tools and techniques.","PeriodicalId":429417,"journal":{"name":"2008 Requirements Engineering Visualization","volume":"53 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127575717","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}
Philipp Heim, Steffen Lohmann, Kim Lauenroth, Jürgen Ziegler
Understanding the relationships between requirements is important in order to understand the requirements themselves. Existing requirements management tools mainly use lists, tables, trees, and matrices to visualize requirements and their interrelations. However, all these visualization forms have a limited capability to show multiple relationships of different types. In this paper, we propose to extend traditional requirements analysis and management by a graph-based visualization that allows to represent multidimensional relations in a direct and flexible way. In particular, we propose a special presentation form that enables the exploration of requirements along their relationships and facilitates understanding of dependencies between requirements.
{"title":"Graph-based Visualization of Requirements Relationships","authors":"Philipp Heim, Steffen Lohmann, Kim Lauenroth, Jürgen Ziegler","doi":"10.1109/REV.2008.2","DOIUrl":"https://doi.org/10.1109/REV.2008.2","url":null,"abstract":"Understanding the relationships between requirements is important in order to understand the requirements themselves. Existing requirements management tools mainly use lists, tables, trees, and matrices to visualize requirements and their interrelations. However, all these visualization forms have a limited capability to show multiple relationships of different types. In this paper, we propose to extend traditional requirements analysis and management by a graph-based visualization that allows to represent multidimensional relations in a direct and flexible way. In particular, we propose a special presentation form that enables the exploration of requirements along their relationships and facilitates understanding of dependencies between requirements.","PeriodicalId":429417,"journal":{"name":"2008 Requirements Engineering Visualization","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114333003","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}
Little effort has been put into understanding how trust can be modelled and reasoned when developing information systems. Equally little effort has been put into developing visual languages to support trust modelling. Our motivation comes from this situation and we aim to develop a visualization language for trust related requirements elicitation. In this paper we highlight the lack of substantial work in this area and we describe the foundation for such a visualization language.
{"title":"Modelling Trust Requirements by Means of a Visualization Language","authors":"K. K. Bimrah, H. Mouratidis, D. Preston","doi":"10.1109/REV.2008.3","DOIUrl":"https://doi.org/10.1109/REV.2008.3","url":null,"abstract":"Little effort has been put into understanding how trust can be modelled and reasoned when developing information systems. Equally little effort has been put into developing visual languages to support trust modelling. Our motivation comes from this situation and we aim to develop a visualization language for trust related requirements elicitation. In this paper we highlight the lack of substantial work in this area and we describe the foundation for such a visualization language.","PeriodicalId":429417,"journal":{"name":"2008 Requirements Engineering Visualization","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124938913","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}
The goal of many software projects is the support of business processes. A typical business process spans multiple Use Cases. This poses the difficulty of making the set of encompassing Use Cases consistent with each other and functionality-wise complete with regards to the overall business process. Manual arrangements and reviews of Use Cases are burdensome and time-intensive. Therefore, an automatic approach is needed that restores an overview of the Use Cases and visualizes the control-flow of the resulting business process. Our approach uses pre-conditions, post-conditions, and triggers of Use Cases to automatically assemble business processes in BPMN notation in order to solve this problem.
{"title":"Visualizing Use Case Sets as BPMN Processes","authors":"D. Lubke, K. Schneider, M. Weidlich","doi":"10.1109/REV.2008.8","DOIUrl":"https://doi.org/10.1109/REV.2008.8","url":null,"abstract":"The goal of many software projects is the support of business processes. A typical business process spans multiple Use Cases. This poses the difficulty of making the set of encompassing Use Cases consistent with each other and functionality-wise complete with regards to the overall business process. Manual arrangements and reviews of Use Cases are burdensome and time-intensive. Therefore, an automatic approach is needed that restores an overview of the Use Cases and visualizes the control-flow of the resulting business process. Our approach uses pre-conditions, post-conditions, and triggers of Use Cases to automatically assemble business processes in BPMN notation in order to solve this problem.","PeriodicalId":429417,"journal":{"name":"2008 Requirements Engineering Visualization","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127753135","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}
This paper defines a framework of three dimensions which influence usability of trace visualizations: tasks, user roles, and information access. Based on this framework, we survey existing visualizations and conclude that future visualizations should focus more on users and tasks.
{"title":"On Usability in Requirements Trace Visualizations","authors":"Stefan Winkler","doi":"10.1109/REV.2008.4","DOIUrl":"https://doi.org/10.1109/REV.2008.4","url":null,"abstract":"This paper defines a framework of three dimensions which influence usability of trace visualizations: tasks, user roles, and information access. Based on this framework, we survey existing visualizations and conclude that future visualizations should focus more on users and tasks.","PeriodicalId":429417,"journal":{"name":"2008 Requirements Engineering Visualization","volume":"2003 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-09-08","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127329561","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}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：