Information systems can be visualized with many tools. Typically these tools present functional artifacts from various phases of the development life-cycle; these include requirements models, architecture and design diagrams, and implementation code. The syntactic structures of these artifacts are often presented in a textual language using symbols, or a graphical one using nodes and edges. In this paper, we propose a quality-based visualization scheme. Such a scheme is layered on top of these functional artifacts for presenting non-functional aspects of the system. To do this, we use quantified quality attributes. As an example, we visualize the quality attributes of trust and performance among various nonfunctional requirements of information systems.
{"title":"Visualizing non-functional requirements","authors":"Neil A. Ernst, Yijun Yu, J. Mylopoulos","doi":"10.1109/REV.2006.10","DOIUrl":"https://doi.org/10.1109/REV.2006.10","url":null,"abstract":"Information systems can be visualized with many tools. Typically these tools present functional artifacts from various phases of the development life-cycle; these include requirements models, architecture and design diagrams, and implementation code. The syntactic structures of these artifacts are often presented in a textual language using symbols, or a graphical one using nodes and edges. In this paper, we propose a quality-based visualization scheme. Such a scheme is layered on top of these functional artifacts for presenting non-functional aspects of the system. To do this, we use quantified quality attributes. As an example, we visualize the quality attributes of trust and performance among various nonfunctional requirements of information systems.","PeriodicalId":355652,"journal":{"name":"2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop)","volume":"17 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121021011","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}
Capturing structural relationships between requirements is essential for effective visualization. Existing techniques such as UML, SysML, and goaloriented requirement engineering present a relationship focused approach in visualization; however, a commonly shared understanding of requirement-based relationships has not yet emerged. Considerations in structural and visual representation of requirement relationships are discussed in the paper, drawing issues from commercial tools, UML, SysML requirements diagram and goal-oriented requirement engineering. Lessons learned from author's own experience of developing requirement engineering tool support with graph-based techniques are summarized. Suggestions for areas of investigation for practical and better use of requirement relationships via visualization are provided.
{"title":"Representing Requirement Relationships","authors":"I. Ozkaya","doi":"10.1109/REV.2006.4","DOIUrl":"https://doi.org/10.1109/REV.2006.4","url":null,"abstract":"Capturing structural relationships between requirements is essential for effective visualization. Existing techniques such as UML, SysML, and goaloriented requirement engineering present a relationship focused approach in visualization; however, a commonly shared understanding of requirement-based relationships has not yet emerged. Considerations in structural and visual representation of requirement relationships are discussed in the paper, drawing issues from commercial tools, UML, SysML requirements diagram and goal-oriented requirement engineering. Lessons learned from author's own experience of developing requirement engineering tool support with graph-based techniques are summarized. Suggestions for areas of investigation for practical and better use of requirement relationships via visualization are provided.","PeriodicalId":355652,"journal":{"name":"2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop)","volume":"84 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115786034","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}
As the Unified Modeling Language (UML) and modeldriven development (MDD) become increasingly common in industry, many developers are faced with the difficult task of understanding how an existing UML model realizes system requirements. Essentially, developers are required to understand the structure and behavior of UML models that they may have not created. Understanding these relationships is non-trivial, because the interactions in the model are not readily apparent. Commonly, the only means to elicit these relationships is visual inspection and guided simulation. This paper describes an alternative approach termed REVU (Requirements Visualization of UML), a process for visualizing functional requirements in terms of behavioral interactions in a UML model. We illustrate the use of this process with the visualization of scenarios for an adaptive light control system.
{"title":"Visualizing Requirements in UML Models","authors":"S. Konrad, H. Goldsby, Karli Lopez, B. Cheng","doi":"10.1109/REV.2006.11","DOIUrl":"https://doi.org/10.1109/REV.2006.11","url":null,"abstract":"As the Unified Modeling Language (UML) and modeldriven development (MDD) become increasingly common in industry, many developers are faced with the difficult task of understanding how an existing UML model realizes system requirements. Essentially, developers are required to understand the structure and behavior of UML models that they may have not created. Understanding these relationships is non-trivial, because the interactions in the model are not readily apparent. Commonly, the only means to elicit these relationships is visual inspection and guided simulation. This paper describes an alternative approach termed REVU (Requirements Visualization of UML), a process for visualizing functional requirements in terms of behavioral interactions in a UML model. We illustrate the use of this process with the visualization of scenarios for an adaptive light control system.","PeriodicalId":355652,"journal":{"name":"2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop)","volume":"13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125482791","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}
Software release planning is a complex task, as many different factors must be considered. Project managers can't cope with the complexity of release planning. Project managers need a tool support in release planning. Existing tools for release planning are not appropriate or are one tool in a set of specialized tools in a project. Using more tools leads to inconsistent data among this set of tools. This paper proposes a decision support tool for release planning: Basis of the tool is the Sysiphus framework, which stores all the information related to a software project in a single repository. Knowledge nuggets are introduced as a concept to aggregate and develop knowledge that belongs to a specific release. The paper shows a prototypically implemented visualization for planning multiple releases.
{"title":"Visualization of Release Planning","authors":"K. Herrmann","doi":"10.1109/REV.2006.7","DOIUrl":"https://doi.org/10.1109/REV.2006.7","url":null,"abstract":"Software release planning is a complex task, as many different factors must be considered. Project managers can't cope with the complexity of release planning. Project managers need a tool support in release planning. Existing tools for release planning are not appropriate or are one tool in a set of specialized tools in a project. Using more tools leads to inconsistent data among this set of tools. This paper proposes a decision support tool for release planning: Basis of the tool is the Sysiphus framework, which stores all the information related to a software project in a single repository. Knowledge nuggets are introduced as a concept to aggregate and develop knowledge that belongs to a specific release. The paper shows a prototypically implemented visualization for planning multiple releases.","PeriodicalId":355652,"journal":{"name":"2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop)","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134353560","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}
In this paper, we are emphasizing our perfect appreciation of using visualization means in requirements engineering as key success factor in any complex (software) development project. We are discussing our experiences with requirements engineering visualization, in the large part gained in the course of a three years multidisciplinary software development project in the insurance domain. A business process-based requirements modeling and management approach that has been developed and employed within this project is described. In order to overcome some process-related and tool integration issues to refine this approach, we investigated a recently released requirements engineering software of a prominent vendor. Experiences using this tool, tool integration for requirements engineering visualization, and suggestions for future research are discussed extensively.
{"title":"Business Process-based Requirements Modeling and Management","authors":"Mario Pichler, H. Rumetshofer","doi":"10.1109/REV.2006.1","DOIUrl":"https://doi.org/10.1109/REV.2006.1","url":null,"abstract":"In this paper, we are emphasizing our perfect appreciation of using visualization means in requirements engineering as key success factor in any complex (software) development project. We are discussing our experiences with requirements engineering visualization, in the large part gained in the course of a three years multidisciplinary software development project in the insurance domain. A business process-based requirements modeling and management approach that has been developed and employed within this project is described. In order to overcome some process-related and tool integration issues to refine this approach, we investigated a recently released requirements engineering software of a prominent vendor. Experiences using this tool, tool integration for requirements engineering visualization, and suggestions for future research are discussed extensively.","PeriodicalId":355652,"journal":{"name":"2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130066380","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}
For several years we have been employing a riskbased decision process to guide development and application of advanced technologies, and for research and technology portfolio planning. The process is supported by custom software, in which visualization plays an important role. During requirements gathering, visualization is used to help scrutinize the status (completeness, extent) of the information. During decision making based on the gathered information, visualization is used to help decisionmakers understand the space of options and their consequences. In this paper we summarize the visualization capabilities that we have employed, indicating when and how they have proven useful.
{"title":"Experiences using Visualization Techniques to Present Requirements, Risks to Them, and Options for Risk Mitigation","authors":"M. Feather, S. Cornford, J. Kiper, T. Menzies","doi":"10.1109/REV.2006.2","DOIUrl":"https://doi.org/10.1109/REV.2006.2","url":null,"abstract":"For several years we have been employing a riskbased decision process to guide development and application of advanced technologies, and for research and technology portfolio planning. The process is supported by custom software, in which visualization plays an important role. During requirements gathering, visualization is used to help scrutinize the status (completeness, extent) of the information. During decision making based on the gathered information, visualization is used to help decisionmakers understand the space of options and their consequences. In this paper we summarize the visualization capabilities that we have employed, indicating when and how they have proven useful.","PeriodicalId":355652,"journal":{"name":"2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop)","volume":"40 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127033879","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 quality of the Requirements Engineering (RE) process plays a critical role in successfully developing software systems. Often, in software organizations, RE processes are assessed and improvements are applied to overcome their deficiency. However, such improvements may not yield desired results for two reasons. First, the assessed deficiency may be inaccurate because of ambiguities in measurement. Second, the improvements are not validated to ascertain their correctness to overcome the process deficiency. Therefore, a Requirements Engineering Process Improvement (REPI) exercise may fail to establish its purpose. A major shortfall in validating RE processes is the difficulty in representing process parameters in some cognitive form. We address this issue with an REPI framework that has both measurement and visual validation properties. The REPI validation method presented is empirically tested based on a case study in a large software organization. The results are promising towards considering this REPI validation method in practice by organizations.
{"title":"Validating Requirements Engineering Process Improvements - A Case Study","authors":"B. Palyagar, F. Moisiadis","doi":"10.1109/REV.2006.5","DOIUrl":"https://doi.org/10.1109/REV.2006.5","url":null,"abstract":"The quality of the Requirements Engineering (RE) process plays a critical role in successfully developing software systems. Often, in software organizations, RE processes are assessed and improvements are applied to overcome their deficiency. However, such improvements may not yield desired results for two reasons. First, the assessed deficiency may be inaccurate because of ambiguities in measurement. Second, the improvements are not validated to ascertain their correctness to overcome the process deficiency. Therefore, a Requirements Engineering Process Improvement (REPI) exercise may fail to establish its purpose. A major shortfall in validating RE processes is the difficulty in representing process parameters in some cognitive form. We address this issue with an REPI framework that has both measurement and visual validation properties. The REPI validation method presented is empirically tested based on a case study in a large software organization. The results are promising towards considering this REPI validation method in practice by organizations.","PeriodicalId":355652,"journal":{"name":"2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop)","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130955959","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}
When the requirements in a software system change, we should notify every contributor who participates in the analysis, design, implementation, and testing of the requirement to reduce rework. However, the network of contributors working on a requirement is constantly changing, making it not only difficult to seek expertise from other team members, but also difficult to send requirements-change information to team members. To promote communication and improve awareness among contributors working on the same requirement, in this position paper we suggest using a visual representation called a requirements-centred-social-network diagram. Using the social-network diagram, a contributor can learn about another contributor¿s communication patterns around the development of a requirement, or send requirements-change-awareness notifications to every member of a team working on the same requirement. This social network can automatically expand to include contributors who work on a requirement but may not have been included in a project plan. The requirements-centred social network therefore captures not only the relationships among an initial team, but also emergent relationships among peripheral contributors. We believe that, by providing visual feedback of communication patterns within a contributor¿s expanding social network and promoting communication among team members, we can improve awareness of the work done by other contributors and maintain awareness of requirements change.
{"title":"Visualizing a Requirements-centred Social Network to Maintain Awareness Within Development Teams","authors":"Irwin Kwan, D. Damian, M. Storey","doi":"10.1109/REV.2006.8","DOIUrl":"https://doi.org/10.1109/REV.2006.8","url":null,"abstract":"When the requirements in a software system change, we should notify every contributor who participates in the analysis, design, implementation, and testing of the requirement to reduce rework. However, the network of contributors working on a requirement is constantly changing, making it not only difficult to seek expertise from other team members, but also difficult to send requirements-change information to team members. To promote communication and improve awareness among contributors working on the same requirement, in this position paper we suggest using a visual representation called a requirements-centred-social-network diagram. Using the social-network diagram, a contributor can learn about another contributor¿s communication patterns around the development of a requirement, or send requirements-change-awareness notifications to every member of a team working on the same requirement. This social network can automatically expand to include contributors who work on a requirement but may not have been included in a project plan. The requirements-centred social network therefore captures not only the relationships among an initial team, but also emergent relationships among peripheral contributors. We believe that, by providing visual feedback of communication patterns within a contributor¿s expanding social network and promoting communication among team members, we can improve awareness of the work done by other contributors and maintain awareness of requirements change.","PeriodicalId":355652,"journal":{"name":"2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop)","volume":"123 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126102403","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 benefits of aspects and aspect-oriented modelling are beginning to be recognized for requirements engineering activities. However, once aspects have been identified, the behaviour, structure, and pointcut expressions of aspects need to be modeled unobtrusively at the requirements level, allowing the engineer to seamlessly focus either on the behaviour and structure of the system without aspects or on the combined behaviour and structure. Furthermore, the modeling techniques for aspects should be the same as for the base system, ensuring that the engineer continues to work with familiar models. This position paper describes how, with the help of Use Case Maps, scenario- based aspects can be modeled visually and unobtrusively at the requirements level and with the same techniques as for non-aspectual systems. With Use Case Maps, aspects including pointcut expressions are modeled in a visual way which is generally considered the preferred choice for models of a high level of abstraction.
{"title":"Visualizing Aspect-Oriented Requirements Scenarios with Use Case Maps","authors":"G. Mussbacher, Daniel Amyot, M. Weiss","doi":"10.1109/REV.2006.9","DOIUrl":"https://doi.org/10.1109/REV.2006.9","url":null,"abstract":"The benefits of aspects and aspect-oriented modelling are beginning to be recognized for requirements engineering activities. However, once aspects have been identified, the behaviour, structure, and pointcut expressions of aspects need to be modeled unobtrusively at the requirements level, allowing the engineer to seamlessly focus either on the behaviour and structure of the system without aspects or on the combined behaviour and structure. Furthermore, the modeling techniques for aspects should be the same as for the base system, ensuring that the engineer continues to work with familiar models. This position paper describes how, with the help of Use Case Maps, scenario- based aspects can be modeled visually and unobtrusively at the requirements level and with the same techniques as for non-aspectual systems. With Use Case Maps, aspects including pointcut expressions are modeled in a visual way which is generally considered the preferred choice for models of a high level of abstraction.","PeriodicalId":355652,"journal":{"name":"2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop)","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127237677","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 describes a new visualization technique for helping analysts to understand the potential impact of changing requirements, and for providing valuable early feedback on the quality of a software design. Based on the candidate links that are automatically generated by a trace retrieval tool, VisMatrix creates a graphical representation of the requirements trace matrix showing not only where candidate links exist, but also the strength of those links. New metrics derived from the trace visualization, and its underlying trace matrix, are introduced. These include 'trace clustering' for evaluating modularity, and 'trace scope' for analyzing fan-in and fan-out behavior of traces, where fan-in represents the number of requirements influencing a design artifact, and fan-out represents the degree of influence a single requirement has on the set of design artifacts. Examples are drawn from the automatically generated trace matrices of four different data sets to illustrate the visualization techniques and analyze the proposed metrics.
{"title":"Visualization and Analysis in Automated Trace Retrieval","authors":"C. Duan, J. Cleland-Huang","doi":"10.1109/REV.2006.6","DOIUrl":"https://doi.org/10.1109/REV.2006.6","url":null,"abstract":"This paper describes a new visualization technique for helping analysts to understand the potential impact of changing requirements, and for providing valuable early feedback on the quality of a software design. Based on the candidate links that are automatically generated by a trace retrieval tool, VisMatrix creates a graphical representation of the requirements trace matrix showing not only where candidate links exist, but also the strength of those links. New metrics derived from the trace visualization, and its underlying trace matrix, are introduced. These include 'trace clustering' for evaluating modularity, and 'trace scope' for analyzing fan-in and fan-out behavior of traces, where fan-in represents the number of requirements influencing a design artifact, and fan-out represents the degree of influence a single requirement has on the set of design artifacts. Examples are drawn from the automatically generated trace matrices of four different data sets to illustrate the visualization techniques and analyze the proposed metrics.","PeriodicalId":355652,"journal":{"name":"2006 First International Workshop on Requirements Engineering Visualization (REV'06 - RE'06 Workshop)","volume":"69 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2006-09-11","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133730954","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
扫码关注我们
求助内容：
应助结果提醒方式：