One of the goals of the integration of formal and graphical methods is to reuse tool support associated with formal methods. This paper reports on a combination of the Jaza Z animator with the RoZ tool. RoZ produces a Z specification from an annotated UML class diagram. It also generates the specification of basic operations associated to the diagram. The paper recalls the principles of the RoZ tool, gives a typical animation session, and discusses how RoZ and class diagrams must be adapted to support animation
{"title":"Using Jaza to Animate RoZ Specifications of UML Class Diagrams","authors":"Y. Ledru","doi":"10.1109/SEW.2006.39","DOIUrl":"https://doi.org/10.1109/SEW.2006.39","url":null,"abstract":"One of the goals of the integration of formal and graphical methods is to reuse tool support associated with formal methods. This paper reports on a combination of the Jaza Z animator with the RoZ tool. RoZ produces a Z specification from an annotated UML class diagram. It also generates the specification of basic operations associated to the diagram. The paper recalls the principles of the RoZ tool, gives a typical animation session, and discusses how RoZ and class diagrams must be adapted to support animation","PeriodicalId":127158,"journal":{"name":"2006 30th Annual IEEE/NASA Software Engineering Workshop","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2006-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122498407","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}
It is widely held that programming language extensions that support separation of concerns and that are also integrative benefit development, maintenance and reuse of software designs and code. Such is the intent of our synchronization units model (Szumo), which unifies new features for expressing synchronization in a multi-threaded program with existing features of an object-oriented language. However, to make effective use of a language extension, a programmer needs an accurate mental model of how new concepts affect and are affected by existing concepts. Moreover, good separation dictates that interactions between these concepts should be understandable at the level of the new concepts. This suggests that the semantics of Szumo should be specifiable as a self-contained partial specification, called a view, and the semantics of its integration with other language features should be specifiable by view composition. To our knowledge, however, view-based approaches have not been applied in specifying the semantics of language extensions. Moreover, devising separable views that serve to simplify comprehensibility of a complex specification is still more of an art than a science. This paper presents a case study in the use of views in structuring a Z specification of Szumo
{"title":"Using Views to Specify a Synchronization Aspect for Object-Oriented Languages","authors":"R. Stirewalt, L. Dillon, R. Behrends","doi":"10.1109/SEW.2006.41","DOIUrl":"https://doi.org/10.1109/SEW.2006.41","url":null,"abstract":"It is widely held that programming language extensions that support separation of concerns and that are also integrative benefit development, maintenance and reuse of software designs and code. Such is the intent of our synchronization units model (Szumo), which unifies new features for expressing synchronization in a multi-threaded program with existing features of an object-oriented language. However, to make effective use of a language extension, a programmer needs an accurate mental model of how new concepts affect and are affected by existing concepts. Moreover, good separation dictates that interactions between these concepts should be understandable at the level of the new concepts. This suggests that the semantics of Szumo should be specifiable as a self-contained partial specification, called a view, and the semantics of its integration with other language features should be specifiable by view composition. To our knowledge, however, view-based approaches have not been applied in specifying the semantics of language extensions. Moreover, devising separable views that serve to simplify comprehensibility of a complex specification is still more of an art than a science. This paper presents a case study in the use of views in structuring a Z specification of Szumo","PeriodicalId":127158,"journal":{"name":"2006 30th Annual IEEE/NASA Software Engineering Workshop","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2006-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132601009","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 aim of this work is to produce a traceability model to enhance processes and tasks, which make extensive use of traceability information such as, V&V, change management and impact analysis, under the roundtrip engineering approach. This paper analyzes several current traceability approaches, in order to obtain their relevant features, to identify overlaps and inconsistencies between them, and to select the best traceability practices. It was identified that, several issues still make difficult the adoption of a wide-scale traceability activity, in the software/system engineering practice, such as, there is a lack of a commonly accepted traceability definition, a standard way of specifying traceability between artifacts, and a traceability type classification. Basing on these findings, an approach for a "traceability schema specification" and a first implementation on a software/system engineering environment are provided. The schema attempts to systematize the definition, deployment and maintenance of a traceability implementation
{"title":"Analyzing and Systematizing Current Traceability Schemas","authors":"Angelina Espinoza, P. Alarcón, J. Garbajosa","doi":"10.1109/SEW.2006.12","DOIUrl":"https://doi.org/10.1109/SEW.2006.12","url":null,"abstract":"The aim of this work is to produce a traceability model to enhance processes and tasks, which make extensive use of traceability information such as, V&V, change management and impact analysis, under the roundtrip engineering approach. This paper analyzes several current traceability approaches, in order to obtain their relevant features, to identify overlaps and inconsistencies between them, and to select the best traceability practices. It was identified that, several issues still make difficult the adoption of a wide-scale traceability activity, in the software/system engineering practice, such as, there is a lack of a commonly accepted traceability definition, a standard way of specifying traceability between artifacts, and a traceability type classification. Basing on these findings, an approach for a \"traceability schema specification\" and a first implementation on a software/system engineering environment are provided. The schema attempts to systematize the definition, deployment and maintenance of a traceability implementation","PeriodicalId":127158,"journal":{"name":"2006 30th Annual IEEE/NASA Software Engineering Workshop","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2006-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116082909","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 design of software that is easy to port or deliberately targeted for multiple platforms is a neglected area of software engineering. A promising solution is to link components and toolkits through XML and reflection
{"title":"Cross-Platform Development: Software that Lasts","authors":"J. Bishop, R. Horspool","doi":"10.1109/MC.2006.337","DOIUrl":"https://doi.org/10.1109/MC.2006.337","url":null,"abstract":"The design of software that is easy to port or deliberately targeted for multiple platforms is a neglected area of software engineering. A promising solution is to link components and toolkits through XML and reflection","PeriodicalId":127158,"journal":{"name":"2006 30th Annual IEEE/NASA Software Engineering Workshop","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2006-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132006999","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}
Role-based access control (RBAC) is a high level authorization mechanism in which access decisions are based on the roles that users hold within an organization. Because RBAC offers scalability, consistency and ease of maintenance, it is very useful, particularly for large organizations. RBAC has been used to describe authorization in a wide variety of applications ranging from operating systems and databases to complex information systems. Despite its widespread adoption, however, there doesn't seem to be a common agreement on the semantics of even key RBAC concepts. For examples, the definitions of fundamental terms such as subject, principal, role, task, and permission have been open to many different and sometimes inconsistent interpretations. This paper attempts to clarify and define essential RBAC concepts. Based on these definitions, a variety of state-based flat role based access control models are developed. These models have increasing degrees of complexity and are formulated in the specification notation Z. The starting point is a core RBAC model which, in turn, is successively refined into a series of flat RBAC models with increasing levels of details. The semantics of each model is captured by giving a precise formulation of its corresponding reference monitor which makes access control decisions
{"title":"Formal Z Specifications of Several Flat Role-Based Access Control Models","authors":"A. Abdallah, E. Khayat","doi":"10.1109/SEW.2006.20","DOIUrl":"https://doi.org/10.1109/SEW.2006.20","url":null,"abstract":"Role-based access control (RBAC) is a high level authorization mechanism in which access decisions are based on the roles that users hold within an organization. Because RBAC offers scalability, consistency and ease of maintenance, it is very useful, particularly for large organizations. RBAC has been used to describe authorization in a wide variety of applications ranging from operating systems and databases to complex information systems. Despite its widespread adoption, however, there doesn't seem to be a common agreement on the semantics of even key RBAC concepts. For examples, the definitions of fundamental terms such as subject, principal, role, task, and permission have been open to many different and sometimes inconsistent interpretations. This paper attempts to clarify and define essential RBAC concepts. Based on these definitions, a variety of state-based flat role based access control models are developed. These models have increasing degrees of complexity and are formulated in the specification notation Z. The starting point is a core RBAC model which, in turn, is successively refined into a series of flat RBAC models with increasing levels of details. The semantics of each model is captured by giving a precise formulation of its corresponding reference monitor which makes access control decisions","PeriodicalId":127158,"journal":{"name":"2006 30th Annual IEEE/NASA Software Engineering Workshop","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2006-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127344956","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}
During its lifecycle, software experiences numerous changes that are either due to bug fixes or to the incorporation of new features. Implementing such changes is often more difficult than expected, which frequently leads to underestimation of the associated implementation effort. This paper describes work that aims to understand change impact based on the visualization of the characteristics of change requests using standard diagrams (e.g. UML diagrams). Each diagram depicts different aspects of a software system and can illustrate factors that might drive the implementation effort. Using examples, in which we analyze three change requests, we describe how we determined the characteristics of the change requests. We furthermore discuss how the impact of change requests on diagrams relates to the implementation effort. Our overall goal is to develop a new impact analysis approach that helps determine software change impact based on the use of specific diagrams
{"title":"Understanding Change Requests to Predict Software Impact","authors":"C. Ackermann, M. Lindvall","doi":"10.1109/SEW.2006.36","DOIUrl":"https://doi.org/10.1109/SEW.2006.36","url":null,"abstract":"During its lifecycle, software experiences numerous changes that are either due to bug fixes or to the incorporation of new features. Implementing such changes is often more difficult than expected, which frequently leads to underestimation of the associated implementation effort. This paper describes work that aims to understand change impact based on the visualization of the characteristics of change requests using standard diagrams (e.g. UML diagrams). Each diagram depicts different aspects of a software system and can illustrate factors that might drive the implementation effort. Using examples, in which we analyze three change requests, we describe how we determined the characteristics of the change requests. We furthermore discuss how the impact of change requests on diagrams relates to the implementation effort. Our overall goal is to develop a new impact analysis approach that helps determine software change impact based on the use of specific diagrams","PeriodicalId":127158,"journal":{"name":"2006 30th Annual IEEE/NASA Software Engineering Workshop","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2006-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122004488","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 run-time quality properties of software architecture, such as reliability and performance, are fundamental to telecom systems, but they are very hard to be precisely specified and evaluated with conventional methods. In our contribution we focus on modeling and analysis of architectural level run-time quality properties using formal methods. Colored Petri nets (CPN) is used to create specific system behavior models of reliability and performance properties of software architecture, these properties are then evaluated with analysis and simulation techniques supported by CPN and its tools. In this paper we report our approach and experience on using CPN to model and evaluate the reliability and performance properties of different architecture designs of a critical software subsystem in a telephone switch system. The reliability and performance properties of two alternative solutions were modeled and compared through model analysis and extensive model simulation. The results helped us to find an ideal solution with high performance, low cost and acceptable reliability that met the industry standards
{"title":"Evaluating and Balancing Reliability and Performance Properties of Software Architecture Using Formal Modeling Techniques","authors":"Jianli Xu","doi":"10.1109/SEW.2006.16","DOIUrl":"https://doi.org/10.1109/SEW.2006.16","url":null,"abstract":"The run-time quality properties of software architecture, such as reliability and performance, are fundamental to telecom systems, but they are very hard to be precisely specified and evaluated with conventional methods. In our contribution we focus on modeling and analysis of architectural level run-time quality properties using formal methods. Colored Petri nets (CPN) is used to create specific system behavior models of reliability and performance properties of software architecture, these properties are then evaluated with analysis and simulation techniques supported by CPN and its tools. In this paper we report our approach and experience on using CPN to model and evaluate the reliability and performance properties of different architecture designs of a critical software subsystem in a telephone switch system. The reliability and performance properties of two alternative solutions were modeled and compared through model analysis and extensive model simulation. The results helped us to find an ideal solution with high performance, low cost and acceptable reliability that met the industry standards","PeriodicalId":127158,"journal":{"name":"2006 30th Annual IEEE/NASA Software Engineering Workshop","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2006-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128210735","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 selection of an appropriate software project management tool, as in the selection of many other tools, is often approached using an ad hoc process. Such non-rigorous approaches often based on personal preference, intuition, or marketing hype, can lead to an erroneous result. In this paper a rigorous model for selecting a software project management tool using the analytical hierarchy process (AHP) is presented. The AHP provides a flexible, systematic, and repeatable evaluation procedure that can easily be understood by the decision maker in selecting the appropriate software project management tool. Several relevant factors based on the most common features offered by commercial off-the-shelf solutions (COTS) are used as the selection criteria in ranking the software project management tools. The contribution of this work is to apply a well-known decision making procedure in a novel way to help decision makers better identify an appropriate software project management tool without having to go through a more extensive evaluation process. In addition, this work establishes a framework for comparing individual product decisions across projects, project managers, organizational groups, and organizations
{"title":"Software Project Management Tools: Making a Practical Decision Using AHP","authors":"Norita B. Ahmad, P. Laplante","doi":"10.1109/SEW.2006.30","DOIUrl":"https://doi.org/10.1109/SEW.2006.30","url":null,"abstract":"The selection of an appropriate software project management tool, as in the selection of many other tools, is often approached using an ad hoc process. Such non-rigorous approaches often based on personal preference, intuition, or marketing hype, can lead to an erroneous result. In this paper a rigorous model for selecting a software project management tool using the analytical hierarchy process (AHP) is presented. The AHP provides a flexible, systematic, and repeatable evaluation procedure that can easily be understood by the decision maker in selecting the appropriate software project management tool. Several relevant factors based on the most common features offered by commercial off-the-shelf solutions (COTS) are used as the selection criteria in ranking the software project management tools. The contribution of this work is to apply a well-known decision making procedure in a novel way to help decision makers better identify an appropriate software project management tool without having to go through a more extensive evaluation process. In addition, this work establishes a framework for comparing individual product decisions across projects, project managers, organizational groups, and organizations","PeriodicalId":127158,"journal":{"name":"2006 30th Annual IEEE/NASA Software Engineering Workshop","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2006-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131017567","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 reports on the latest developments in a deployed survivable secure system in relation to enabling the longer term aim of moving from a reactive to a predictive system. At this stage it has been decided to redevelop the event/rule processor into a distributed system to facilitate the future requirements of a predictive system
{"title":"Targeting Prediction: Engineering a Distributed Event Processor for an Autonomic Biometric System","authors":"Roy Sterritt, E. Hanna, P. O'Hagan, G. Garrity","doi":"10.1109/SEW.2006.32","DOIUrl":"https://doi.org/10.1109/SEW.2006.32","url":null,"abstract":"This paper reports on the latest developments in a deployed survivable secure system in relation to enabling the longer term aim of moving from a reactive to a predictive system. At this stage it has been decided to redevelop the event/rule processor into a distributed system to facilitate the future requirements of a predictive system","PeriodicalId":127158,"journal":{"name":"2006 30th Annual IEEE/NASA Software Engineering Workshop","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2006-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115892779","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 software products depends on the quality of the requirements used to create them. Expressiveness (i.e., the ability to convey the intended meaning by avoiding ambiguities and readability problems) is an important quality characteristic of natural language requirements. This paper describes an empirical study that used data from an industrial software project to identify possible relationships between expressiveness defects in natural language requirements and failures during testing. The study shows that test failures occur more frequently when there exist requirements cases with expressiveness defects
{"title":"An Empirical Study on the Relationship between Defective Requirements and Test Failures","authors":"R. Ferguson, G. Lami","doi":"10.1109/SEW.2006.9","DOIUrl":"https://doi.org/10.1109/SEW.2006.9","url":null,"abstract":"The quality of software products depends on the quality of the requirements used to create them. Expressiveness (i.e., the ability to convey the intended meaning by avoiding ambiguities and readability problems) is an important quality characteristic of natural language requirements. This paper describes an empirical study that used data from an industrial software project to identify possible relationships between expressiveness defects in natural language requirements and failures during testing. The study shows that test failures occur more frequently when there exist requirements cases with expressiveness defects","PeriodicalId":127158,"journal":{"name":"2006 30th Annual IEEE/NASA Software Engineering Workshop","volume":null,"pages":null},"PeriodicalIF":0.0,"publicationDate":"2006-04-24","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126044887","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
扫码关注我们
求助内容：
应助结果提醒方式：