Reinhold Plösch, H. Gruber, A. Hentschel, Christian Körner, G. Pomberger, S. Schiffer, Matthias Saft, S. Storck
Internal software quality, e.g. the quality of code, has great impact on the overall quality of software. Besides well known manual inspection and review techniques more recent approaches utilize tool-based static code for the evaluation of internal software quality. Despite the high potential of static code analyzers the application of tools alone cannot replace well founded expert opinion. Knowledge, experience and fair judgement is indispensable for a valid, reliable quality assessment, which is accepted by software developers and managers. The EMISQ method (evaluation method for internal software quality), guides the assessment process for all stakeholders of an evaluation project. The method is supported by a tool that assists evaluators with their analysis and rating tasks and provides support for generating a code quality report. The application of the method in a pilot project has shown its applicability.
{"title":"The EMISQ Method - Expert Based Evaluation of Internal Software Quality","authors":"Reinhold Plösch, H. Gruber, A. Hentschel, Christian Körner, G. Pomberger, S. Schiffer, Matthias Saft, S. Storck","doi":"10.1109/SEW.2007.109","DOIUrl":"https://doi.org/10.1109/SEW.2007.109","url":null,"abstract":"Internal software quality, e.g. the quality of code, has great impact on the overall quality of software. Besides well known manual inspection and review techniques more recent approaches utilize tool-based static code for the evaluation of internal software quality. Despite the high potential of static code analyzers the application of tools alone cannot replace well founded expert opinion. Knowledge, experience and fair judgement is indispensable for a valid, reliable quality assessment, which is accepted by software developers and managers. The EMISQ method (evaluation method for internal software quality), guides the assessment process for all stakeholders of an evaluation project. The method is supported by a tool that assists evaluators with their analysis and rating tasks and provides support for generating a code quality report. The application of the method in a pilot project has shown its applicability.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"86 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123290241","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 Web Services Choreography Description Language (WS-CDL) is a newly developed specification for Web services composition to describe the observable behavior across multiple participants from a global perspective. However, this specification does not provide a formal semantics, whose informal description can lead to ambiguous understanding and different implementations. Hence, it causes difficulties for the engineering community to analyze the business behavior and ensure the correctness. In this paper, we present the semantics of WS-CDL in terms of process algebra CSP which has great advantages in designing and verifying concurrent processes. Therefore, all the properties we want to check within a WS-CDL document can be verified automatically in the CSP framework correspondingly. In addition, the exception and compensation handling mechanism, an important concept of long running transactions, is demonstrated clearly through our formalization work.
{"title":"Modeling and Verifying Web Services Choreography Using Process Algebra","authors":"Jing Li, Jifeng He, Huibiao Zhu, G. Pu","doi":"10.1109/SEW.2007.105","DOIUrl":"https://doi.org/10.1109/SEW.2007.105","url":null,"abstract":"The Web Services Choreography Description Language (WS-CDL) is a newly developed specification for Web services composition to describe the observable behavior across multiple participants from a global perspective. However, this specification does not provide a formal semantics, whose informal description can lead to ambiguous understanding and different implementations. Hence, it causes difficulties for the engineering community to analyze the business behavior and ensure the correctness. In this paper, we present the semantics of WS-CDL in terms of process algebra CSP which has great advantages in designing and verifying concurrent processes. Therefore, all the properties we want to check within a WS-CDL document can be verified automatically in the CSP framework correspondingly. In addition, the exception and compensation handling mechanism, an important concept of long running transactions, is demonstrated clearly through our formalization work.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"106 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122199336","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 JHU/APL Space Department develops Missions Operations Center (MOC) system software for all JHU/APL-supported NASA missions using a shared software architecture called Common Ground. The software architecture is 10 years old and difficult to maintain for current missions and to evolve for reuse in future missions. The Software Architecture Visualization and Evaluation (SAVE) tool and process developed by Fraunhofer Center - Maryland has been applied to the Common Ground software in order to avoid further maintenance and evolution problems. This report summarizes JHU/APL's experiences in using the SAVE tool and process to capture the originally planned architecture, to compare the actual Common Ground software to the planned architecture, to create a new target architecture, and to guide ongoing development to bring the planned and actual architectures into alignment.
{"title":"The SAVE Tool and Process Applied to Ground Software Development at JHU/APL: An Experience Report on Technology Infusion","authors":"W. Stratton, D. Sibol, M. Lindvall, P. Costa","doi":"10.1109/SEW.2007.110","DOIUrl":"https://doi.org/10.1109/SEW.2007.110","url":null,"abstract":"The JHU/APL Space Department develops Missions Operations Center (MOC) system software for all JHU/APL-supported NASA missions using a shared software architecture called Common Ground. The software architecture is 10 years old and difficult to maintain for current missions and to evolve for reuse in future missions. The Software Architecture Visualization and Evaluation (SAVE) tool and process developed by Fraunhofer Center - Maryland has been applied to the Common Ground software in order to avoid further maintenance and evolution problems. This report summarizes JHU/APL's experiences in using the SAVE tool and process to capture the originally planned architecture, to compare the actual Common Ground software to the planned architecture, to create a new target architecture, and to guide ongoing development to bring the planned and actual architectures into alignment.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"147 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128065284","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 reliability measurement and prediction are used to evaluate model parameters in advance of applying a model. Measurement involves collecting and analyzing data about the observed reliability of software, from which the parameters are estimated, for example, the occurrence of failures during test. Prediction is using a model to forecast future software reliability, for example, time to next failure during operation. In order to demonstrate the prediction methodology, we must use a software reliability model. Since the Schneidewind model has been used on the NASA Shuttle flight software for reliability predictions, and we have a considerable amount of Shuttle failure data, we use the model and data to demonstrate our methodology.
{"title":"A New Way to Predict Software Reliability with Parameter Evaluation: Shuttle Applications","authors":"N. Schneidewind","doi":"10.1109/SEW.2007.85","DOIUrl":"https://doi.org/10.1109/SEW.2007.85","url":null,"abstract":"Software reliability measurement and prediction are used to evaluate model parameters in advance of applying a model. Measurement involves collecting and analyzing data about the observed reliability of software, from which the parameters are estimated, for example, the occurrence of failures during test. Prediction is using a model to forecast future software reliability, for example, time to next failure during operation. In order to demonstrate the prediction methodology, we must use a software reliability model. Since the Schneidewind model has been used on the NASA Shuttle flight software for reliability predictions, and we have a considerable amount of Shuttle failure data, we use the model and data to demonstrate our methodology.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133151107","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 model driven architecture (MDA) has been widely used as a paradigm in software development. This paper presents an overview on the current research in the model driven architecture. We analyze the key concepts of the MDA by illustrative examples, explore the existing approaches and tools that support model transformation - the essential part of the MDA, and classify these methods based on a multidimensional scheme. Furthermore, this paper summarizes the current technical achievements of model transformation techniques in software development at different abstraction levels of a system.
{"title":"Transformational Approaches to Model Driven Architecture - A Review","authors":"Chunying Zhao, Kang Zhang","doi":"10.1109/SEW.2007.111","DOIUrl":"https://doi.org/10.1109/SEW.2007.111","url":null,"abstract":"The model driven architecture (MDA) has been widely used as a paradigm in software development. This paper presents an overview on the current research in the model driven architecture. We analyze the key concepts of the MDA by illustrative examples, explore the existing approaches and tools that support model transformation - the essential part of the MDA, and classify these methods based on a multidimensional scheme. Furthermore, this paper summarizes the current technical achievements of model transformation techniques in software development at different abstraction levels of a system.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129814066","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}
We revisit the automatic tool composition feature of the electronic tool integration platform under the perspective of planning. It turns out that in todays terminology, ETIs temporal logic-based synthesis of tool sequences is a form of planning-based automated orchestration. In contrast to Al-based planning approaches, our synthesis approach is not restricted to compute one solution, but it may compute all (shortest/minimal) solutions, with the intent to provide maximum insight into the potential design space.
{"title":"LTL Guided Planning: Revisiting Automatic Tool Composition in ETI","authors":"T. Margaria, B. Steffen","doi":"10.1109/SEW.2007.101","DOIUrl":"https://doi.org/10.1109/SEW.2007.101","url":null,"abstract":"We revisit the automatic tool composition feature of the electronic tool integration platform under the perspective of planning. It turns out that in todays terminology, ETIs temporal logic-based synthesis of tool sequences is a form of planning-based automated orchestration. In contrast to Al-based planning approaches, our synthesis approach is not restricted to compute one solution, but it may compute all (shortest/minimal) solutions, with the intent to provide maximum insight into the potential design space.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"66 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122259091","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}
A. Marcal, Felipe Santana Furtado Soares, A. D. Belchior
Over the past years, the capability maturity model (CMM) and capability maturity model integration (CMMI) have been broadly used for assessing organizational maturity and process capability throughout the world. However, the rapid pace of change in information technology has caused increasing frustration to the heavyweight plans, specifications, and other documentation imposed by contractual inertia and maturity model compliance criteria. In light of that, agile methodologies have been adopted to tackle this challenge. The aim of our paper is to present mapping between CMMI and one of these methodologies, Scrum. It shows how Scrum addresses the Project Management Process Areas of CMMI. This is useful for organizations that have their plan-driven process based on the CMMI model and are planning to improve its processes toward agility or to help organizations to define a new project management framework based on both CMMI and Scrum practices.
{"title":"Mapping CMMI Project Management Process Areas to SCRUM Practices","authors":"A. Marcal, Felipe Santana Furtado Soares, A. D. Belchior","doi":"10.1109/SEW.2007.102","DOIUrl":"https://doi.org/10.1109/SEW.2007.102","url":null,"abstract":"Over the past years, the capability maturity model (CMM) and capability maturity model integration (CMMI) have been broadly used for assessing organizational maturity and process capability throughout the world. However, the rapid pace of change in information technology has caused increasing frustration to the heavyweight plans, specifications, and other documentation imposed by contractual inertia and maturity model compliance criteria. In light of that, agile methodologies have been adopted to tackle this challenge. The aim of our paper is to present mapping between CMMI and one of these methodologies, Scrum. It shows how Scrum addresses the Project Management Process Areas of CMMI. This is useful for organizations that have their plan-driven process based on the CMMI model and are planning to improve its processes toward agility or to help organizations to define a new project management framework based on both CMMI and Scrum practices.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"90 2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128834961","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}
Business grids are envisioned to become the adaptive service-oriented utility infrastructure for arbitrary business applications and related transactions. Consolidation, virtualization and automation enables this service architecture while satisfying the needs for agility and cost efficiency in today's and tomorrow's ever changing business environment. It also allows for the non disruptive infusion of new technology components. This brief industrial report focuses on a main cornerstone to achieve this vision, virtualization technologies and examines the current practice and required research directions.
{"title":"Virtualization the Enabler for the Autonomic Business Grid","authors":"S. Wakid, Roy Sterritt","doi":"10.1109/SEW.2007.114","DOIUrl":"https://doi.org/10.1109/SEW.2007.114","url":null,"abstract":"Business grids are envisioned to become the adaptive service-oriented utility infrastructure for arbitrary business applications and related transactions. Consolidation, virtualization and automation enables this service architecture while satisfying the needs for agility and cost efficiency in today's and tomorrow's ever changing business environment. It also allows for the non disruptive infusion of new technology components. This brief industrial report focuses on a main cornerstone to achieve this vision, virtualization technologies and examines the current practice and required research directions.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123928497","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 "Requirements to Design to Code" (R2D2C) project of NASA's Software Engineering Laboratory is based on inferring a formal specification, currently using Communicating Sequential Processes (CSP), from system requirements supplied in the form of scenarios, a user-friendly medium often used to describe the behavior of computer systems under development. The scenarios are first converted into an intermediate form, CSP traces, from which are derived CSP specifications. This work, called Mise en Scene, defines a new scenario medium (Scenario Notation Language, SNL) suitable for control-dominated systems, coupled with a two-stage process for automatic translation of scenarios to a new trace medium (Trace Notation Language, TNL) which encompasses CSP traces. A survey of the "scenario" concept and a small case study are also presented.
NASA软件工程实验室的“从设计到编码的需求”(R2D2C)项目基于从以场景形式提供的系统需求推断出正式规范，目前使用通信顺序过程(CSP)，这是一种用户友好的媒介，通常用于描述正在开发的计算机系统的行为。场景首先被转换成中间形式CSP轨迹，CSP轨迹是CSP规范的派生形式。这项名为Mise en Scene的工作定义了一种适用于控制主导系统的新场景媒介(场景符号语言，SNL)，并结合了将场景自动转换为包含CSP轨迹的新跟踪媒介(跟踪符号语言，TNL)的两阶段过程。对“场景”概念的调查和一个小的案例研究也被提出。
{"title":"Mise en Scene: Converting Scenarios to CSP Traces in Support of Requirements-Based Programming","authors":"J. Carter, W. B. Gardner","doi":"10.1109/SEW.2007.104","DOIUrl":"https://doi.org/10.1109/SEW.2007.104","url":null,"abstract":"The \"Requirements to Design to Code\" (R2D2C) project of NASA's Software Engineering Laboratory is based on inferring a formal specification, currently using Communicating Sequential Processes (CSP), from system requirements supplied in the form of scenarios, a user-friendly medium often used to describe the behavior of computer systems under development. The scenarios are first converted into an intermediate form, CSP traces, from which are derived CSP specifications. This work, called Mise en Scene, defines a new scenario medium (Scenario Notation Language, SNL) suitable for control-dominated systems, coupled with a two-stage process for automatic translation of scenarios to a new trace medium (Trace Notation Language, TNL) which encompasses CSP traces. A survey of the \"scenario\" concept and a small case study are also presented.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116066268","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 developing a new domain-specific architectural style, there can be uncertainty about the feasibility of using that style. In particular, the HADES architectural style contains refactoring patterns intended to remove undesirable scheduling features such as deadlock and livelock, but these patterns have not yet been fully validated. We report on the translation between the HADES structure and the input languages for two popular model checkers (SPIN and NuSMV) to help validate these patterns. We found model checking to be a valuable asset in confirming the presence of undesirable features.
{"title":"Using Model Checking to Validate Style-Specific Architectural Refactoring Patterns","authors":"Z. Stephenson, J. Mcdermid","doi":"10.1109/SEW.2007.112","DOIUrl":"https://doi.org/10.1109/SEW.2007.112","url":null,"abstract":"When developing a new domain-specific architectural style, there can be uncertainty about the feasibility of using that style. In particular, the HADES architectural style contains refactoring patterns intended to remove undesirable scheduling features such as deadlock and livelock, but these patterns have not yet been fully validated. We report on the translation between the HADES structure and the input languages for two popular model checkers (SPIN and NuSMV) to help validate these patterns. We found model checking to be a valuable asset in confirming the presence of undesirable features.","PeriodicalId":277367,"journal":{"name":"31st IEEE Software Engineering Workshop (SEW 2007)","volume":"52 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2007-03-06","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134049357","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
扫码关注我们
求助内容：
应助结果提醒方式：