Speech control is an attractive user interface paradigm for many applications. However, there is little support for the systematic construction of the speech interface part of an application. In this paper we introduce a model-based technique for producing a speech interface facility for interactive applications. The technique assumes a conceptual model of the application that is used for inferring the application-specific part of the speech grammar and for the run-time control of the speech interface. The approach has been evaluated by generating an experimental speech interface for Rational Software Modeler and Microsoft Office PowerPoint. The main benefits of the approach are rapid development of speech interfaces, support for customizing applications beyond existing GUI, and support for context- based speech commands.
{"title":"Automated Derivation of Speech Interfaces: A Model-Based Approach","authors":"Samuel Lahtinen, H. Suontausta, K. Koskimies","doi":"10.1109/ASWEC.2008.34","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.34","url":null,"abstract":"Speech control is an attractive user interface paradigm for many applications. However, there is little support for the systematic construction of the speech interface part of an application. In this paper we introduce a model-based technique for producing a speech interface facility for interactive applications. The technique assumes a conceptual model of the application that is used for inferring the application-specific part of the speech grammar and for the run-time control of the speech interface. The approach has been evaluated by generating an experimental speech interface for Rational Software Modeler and Microsoft Office PowerPoint. The main benefits of the approach are rapid development of speech interfaces, support for customizing applications beyond existing GUI, and support for context- based speech commands.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"8 3","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114026862","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 article presents a novel control-flow based test sequence generation technique using UML 2.0 activity diagram, which is a behavioral type of UML diagram. Like other model-based techniques, this technique can be used in the earlier phases of the development process owing to the availability of the design models of the system. The activity diagram model is seamlessly converted into a colored Petri net. We proposed a technique that enables the automatic generation of test sequences according to a given coverage criteria from the execution of the colored Petri nets model. Two types of structural coverage criteria for AD based models, namely sequential and concurrent coverage are described. The proposed technique was applied to an example to demonstrate its feasibility and the generated test sequences were evaluated against selected coverage criteria. This technique can potentially be adapted to service oriented applications, workflows, and concurrent applications.
{"title":"Towards Automated Test Sequence Generation","authors":"U. Farooq, C. Lam, Huaizhong Li","doi":"10.1109/ASWEC.2008.64","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.64","url":null,"abstract":"The article presents a novel control-flow based test sequence generation technique using UML 2.0 activity diagram, which is a behavioral type of UML diagram. Like other model-based techniques, this technique can be used in the earlier phases of the development process owing to the availability of the design models of the system. The activity diagram model is seamlessly converted into a colored Petri net. We proposed a technique that enables the automatic generation of test sequences according to a given coverage criteria from the execution of the colored Petri nets model. Two types of structural coverage criteria for AD based models, namely sequential and concurrent coverage are described. The proposed technique was applied to an example to demonstrate its feasibility and the generated test sequences were evaluated against selected coverage criteria. This technique can potentially be adapted to service oriented applications, workflows, and concurrent applications.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"14 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121489240","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}
Mehdi Mirakhorli, Abdorrahman Khanipour Rad, F. S. Aliee, Abbas Mirakhorli, M. Pazoki
Although software projects can benefit from XP practices, all projects can't directly adopt it. Characteristics of some projects make it difficult to use XP directly, therefore, we need to tailor XP to the local conditions, contexts and the size of these projects. In this article we will describe why defining XP by its practices has problems and with the belief that XP's values make it agile, XP's practices do not define XP and XP is defined by its rules, we introduce a practical technique for tailoring XP. Proposed technique benefits from RDP (rule-description-practice) cards for identifying a set of suitable practices for a specific project: organizing "YourXP" software development process.
{"title":"RDP Technique: Take a Different Look at XP for Adoption","authors":"Mehdi Mirakhorli, Abdorrahman Khanipour Rad, F. S. Aliee, Abbas Mirakhorli, M. Pazoki","doi":"10.1109/ASWEC.2008.62","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.62","url":null,"abstract":"Although software projects can benefit from XP practices, all projects can't directly adopt it. Characteristics of some projects make it difficult to use XP directly, therefore, we need to tailor XP to the local conditions, contexts and the size of these projects. In this article we will describe why defining XP by its practices has problems and with the belief that XP's values make it agile, XP's practices do not define XP and XP is defined by its rules, we introduce a practical technique for tailoring XP. Proposed technique benefits from RDP (rule-description-practice) cards for identifying a set of suitable practices for a specific project: organizing \"YourXP\" software development process.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129847603","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}
Tan Phan, Jun Han, Jean-Guy Schneider, T. Ebringer, T. Rogers
Policy based management in service oriented architecture (SOA) allows organizations to apply rules and regulations on their business processes. Policy has long been employed in the management of traditional distributed systems and many policy frameworks have been proposed. However, SOA differs in several aspects to traditional systems thus there is a unique set of requirements for an effective SOA policy system. In this paper, we evaluate five popular policy frameworks which are IETF, Ponder, KAoS, Rei and WS-policy against a number of general and SOA-specific criteria to identify what features of these existing systems can be adopted for SOA and what are not. We then, based on their feature sets, discuss the applicability of the frameworks for SOA management.
{"title":"A Survey of Policy-Based Management Approaches for Service Oriented Systems","authors":"Tan Phan, Jun Han, Jean-Guy Schneider, T. Ebringer, T. Rogers","doi":"10.1109/ASWEC.2008.56","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.56","url":null,"abstract":"Policy based management in service oriented architecture (SOA) allows organizations to apply rules and regulations on their business processes. Policy has long been employed in the management of traditional distributed systems and many policy frameworks have been proposed. However, SOA differs in several aspects to traditional systems thus there is a unique set of requirements for an effective SOA policy system. In this paper, we evaluate five popular policy frameworks which are IETF, Ponder, KAoS, Rei and WS-policy against a number of general and SOA-specific criteria to identify what features of these existing systems can be adopted for SOA and what are not. We then, based on their feature sets, discuss the applicability of the frameworks for SOA management.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"103 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116297376","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}
Automatic identification of software faults has enormous practical significance. This requires characterizing program execution behavior. Equally important is the aspect of diagnosing (finding root-cause of) faults encountered. In this article, we address the problem of identifying the root cause of failure from the test sequences that caused failure. Taking analogies from biological sequence alignment and information retrieval domains we propose two approaches for finding the root cause of failure. The first approach is to align all the test sequences pertaining to a fault and identifying the common pattern among these sequences. The other approach is based on an information retrieval technique viz., the latent semantic indexing (LSI). Our experiments and analysis showed that the sequence alignment based approach has the potential to aid significantly in identifying the root cause of failure. The LSI based approach automatically clusters the test sequences based on their functionality, which assists in determining the different manifestations of a fault.
{"title":"Root Cause Analysis Using Sequence Alignment and Latent Semantic Indexing","authors":"R. Bose, U. Suresh","doi":"10.1109/ASWEC.2008.39","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.39","url":null,"abstract":"Automatic identification of software faults has enormous practical significance. This requires characterizing program execution behavior. Equally important is the aspect of diagnosing (finding root-cause of) faults encountered. In this article, we address the problem of identifying the root cause of failure from the test sequences that caused failure. Taking analogies from biological sequence alignment and information retrieval domains we propose two approaches for finding the root cause of failure. The first approach is to align all the test sequences pertaining to a fault and identifying the common pattern among these sequences. The other approach is based on an information retrieval technique viz., the latent semantic indexing (LSI). Our experiments and analysis showed that the sequence alignment based approach has the potential to aid significantly in identifying the root cause of failure. The LSI based approach automatically clusters the test sequences based on their functionality, which assists in determining the different manifestations of a fault.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121931968","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}
G. Concas, Manuela Lisci, S. Pinna, Guido Porruvecchio, Selene Uras
In this research, we focus the attention on some of the most successful open source (OS) projects. We are interested in studying the characteristics of the social networks comprising these popular and mature OS developer communities. By examining developers mailing lists (MLs), we adopt some social network analysis (SNA) measures to evaluate interactions among community members. A knowledge of these relationships is useful for a better understanding of communication flows among team members and whether there is someone coordinating, controlling and facilitating the information process.
{"title":"Open Source Communities as Social Networks: An Analysis of Some Peculiar Characteristics","authors":"G. Concas, Manuela Lisci, S. Pinna, Guido Porruvecchio, Selene Uras","doi":"10.1109/ASWEC.2008.10","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.10","url":null,"abstract":"In this research, we focus the attention on some of the most successful open source (OS) projects. We are interested in studying the characteristics of the social networks comprising these popular and mature OS developer communities. By examining developers mailing lists (MLs), we adopt some social network analysis (SNA) measures to evaluate interactions among community members. A knowledge of these relationships is useful for a better understanding of communication flows among team members and whether there is someone coordinating, controlling and facilitating the information process.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126492620","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 tutorial gives an introduction to wireless sensor networks (WSNs) and how they can be utilised and integrated in an industrial setting. The basic principles presented will be supplemented with results from extensive laboratory tests and studies of such networks. The authors have for several years been working on evaluating wireless sensor systems, examining specifications and testing WSN technologies in laboratories. Experiences from this work will be presented, in addition to a real-world example from an offshore oil production plant in the North Sea. This includes software interfacing towards the existing monitoring system and network infrastructure.
{"title":"Wireless Sensor Networks: Introduction to Installation and Integration on an Offshore Oil & Gas Platform","authors":"Stig Petersen, Simon Carlsen","doi":"10.1109/ASWEC.2008.86","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.86","url":null,"abstract":"This tutorial gives an introduction to wireless sensor networks (WSNs) and how they can be utilised and integrated in an industrial setting. The basic principles presented will be supplemented with results from extensive laboratory tests and studies of such networks. The authors have for several years been working on evaluating wireless sensor systems, examining specifications and testing WSN technologies in laboratories. Experiences from this work will be presented, in addition to a real-world example from an offshore oil production plant in the North Sea. This includes software interfacing towards the existing monitoring system and network infrastructure.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122291558","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 developing software using model-driven approach, the key technique used is model transformation. Model transformation is part of a new approach in developing software called Model-Driven Architecture (MDA). Model transformation requires the development of transformation rules. Design of the transformation rules will allow the rules to be understood by people without the need to know the language to write the rules. This paper proposes a notation for designing the transformation rules. The abstract syntax, concrete syntax, semantics and well-formedness of the proposed notation are explained here. Examples and experience in using the notation are also given.
{"title":"Proposed Design Notation for Model Transformation","authors":"L. Rahim, Sharifah Bahiyah Rahayu Syed Mansoor","doi":"10.1109/ASWEC.2008.41","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.41","url":null,"abstract":"In developing software using model-driven approach, the key technique used is model transformation. Model transformation is part of a new approach in developing software called Model-Driven Architecture (MDA). Model transformation requires the development of transformation rules. Design of the transformation rules will allow the rules to be understood by people without the need to know the language to write the rules. This paper proposes a notation for designing the transformation rules. The abstract syntax, concrete syntax, semantics and well-formedness of the proposed notation are explained here. Examples and experience in using the notation are also given.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"5 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116116906","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 the process of deciding what to include in future release(s) of a product. Basically the problem can be seen as a company-wide optimization problem involving many stakeholders where the goal is to maximize utilization of the often limited resources of a company and turn them into business benefit. Saliu and Ruhe have proposed a set of key aspects for release planning methods, of which only a subset have been validated in industry. In this paper we use the Saliu and Ruhe key aspects as a starting point for identifying key aspects of release planning. To do this we have performed a multiple case study involving 7 international industrial companies, all producers of software intensive products. Our contribution is (1) a more strict meaning of a release planning key aspect, (2) validation of some of the aspects proposed by Saliu and Ruhe, and (3) an extension of the key aspects. We also capture state-of-the-practice for release planning in industry.
{"title":"Key Aspects of Software Release Planning in Industry","authors":"M. Lindgren, R. Land, C. Norström, Anders Wall","doi":"10.1109/ASWEC.2008.32","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.32","url":null,"abstract":"Software release planning is the process of deciding what to include in future release(s) of a product. Basically the problem can be seen as a company-wide optimization problem involving many stakeholders where the goal is to maximize utilization of the often limited resources of a company and turn them into business benefit. Saliu and Ruhe have proposed a set of key aspects for release planning methods, of which only a subset have been validated in industry. In this paper we use the Saliu and Ruhe key aspects as a starting point for identifying key aspects of release planning. To do this we have performed a multiple case study involving 7 international industrial companies, all producers of software intensive products. Our contribution is (1) a more strict meaning of a release planning key aspect, (2) validation of some of the aspects proposed by Saliu and Ruhe, and (3) an extension of the key aspects. We also capture state-of-the-practice for release planning in industry.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128134969","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 investigate the status of the agile implementation phase within two Canadian organizations. We do this by comparing current agile process models to the industrial practice. Our results show that the organizations studied have adopted most of the activities as suggested in the agile models. However, they had to make some revisions, due to the fact that some of the guidelines as provided by the agile models were unclear, conflicting, ambiguous or they were simply missing.
{"title":"Agile Implementation Phase in Two Canadian Organizations","authors":"Jaana Nyfjord, M. Kajko-Mattsson","doi":"10.1109/ASWEC.2008.29","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.29","url":null,"abstract":"In this paper, we investigate the status of the agile implementation phase within two Canadian organizations. We do this by comparing current agile process models to the industrial practice. Our results show that the organizations studied have adopted most of the activities as suggested in the agile models. However, they had to make some revisions, due to the fact that some of the guidelines as provided by the agile models were unclear, conflicting, ambiguous or they were simply missing.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"68 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2008-03-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133992037","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
扫码关注我们
求助内容：
应助结果提醒方式：