With advances in automatic position sensing and wireless connectivity, location-based services (LBS) are rapidly developing, particularly in fields of geographic, tourism and logistic information systems. Currently, Web service has been viewed as one of most significant innovations in business industry, and designed on demand to provide spatial related information for LBS consumption. However, the traditional Web Service Description Language (WSDL) cannot meet those requirements, as WSDL is not able to support semantic content and information. In recent years, Ontology came up with an effective approach to enhance service description, automated discovery, dynamic composition, enactment, and other tasks such as managing and using service-based systems. In this paper, we propose geographic ontology based on Geography Markup Language (GML) and extend OWL-S profile to form geographic profile. Web service, which is advertised on the basis of our GeoProfile, contains geographic information inherently.
{"title":"A Pragmatic GIS-Oriented Ontology for Location Based Services","authors":"Jun Shen, A. Krishna, Shuai Yuan, Ke Cai, Yu Qin","doi":"10.1109/ASWEC.2008.5","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.5","url":null,"abstract":"With advances in automatic position sensing and wireless connectivity, location-based services (LBS) are rapidly developing, particularly in fields of geographic, tourism and logistic information systems. Currently, Web service has been viewed as one of most significant innovations in business industry, and designed on demand to provide spatial related information for LBS consumption. However, the traditional Web Service Description Language (WSDL) cannot meet those requirements, as WSDL is not able to support semantic content and information. In recent years, Ontology came up with an effective approach to enhance service description, automated discovery, dynamic composition, enactment, and other tasks such as managing and using service-based systems. In this paper, we propose geographic ontology based on Geography Markup Language (GML) and extend OWL-S profile to form geographic profile. Web service, which is advertised on the basis of our GeoProfile, contains geographic information inherently.","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":"129687520","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}
Yoshiki Higo, Y. Matsumoto, S. Kusumoto, Katsuro Inoue
Refactoring is a set of operations to improve maintainability or understandability or other attributes of a software system without changing the external behavior of it, and it is getting much attention recently. However it is difficult to perform appropriate refactorings since the impact of refactoring should justify the cost. Therefore, before a refactoring is really performed, the effect and the cost of it should be estimated. The estimation makes it possible for us to adequately assess whether each refactoring should be performed or not. This paper shows that it is difficult for developers to perform appropriate refactorings, and proposes a method estimating refactoring effect. The method has been implemented as a software tool, and a case study was conducted with it. The result of the case study showed that the estimation of the tool helped a developer of the target software system to perform an appropriate refactoring.
{"title":"Refactoring Effect Estimation Based on Complexity Metrics","authors":"Yoshiki Higo, Y. Matsumoto, S. Kusumoto, Katsuro Inoue","doi":"10.1109/ASWEC.2008.23","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.23","url":null,"abstract":"Refactoring is a set of operations to improve maintainability or understandability or other attributes of a software system without changing the external behavior of it, and it is getting much attention recently. However it is difficult to perform appropriate refactorings since the impact of refactoring should justify the cost. Therefore, before a refactoring is really performed, the effect and the cost of it should be estimated. The estimation makes it possible for us to adequately assess whether each refactoring should be performed or not. This paper shows that it is difficult for developers to perform appropriate refactorings, and proposes a method estimating refactoring effect. The method has been implemented as a software tool, and a case study was conducted with it. The result of the case study showed that the estimation of the tool helped a developer of the target software system to perform an appropriate refactoring.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"4 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":"129821351","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}
Architecture description languages (ADLs) describe the abstracted structure of a system. In this paper we describe a new ADL based on extension of the existing CARE language used informally specifying and implementing reusable software components. The main elements of this ADL are components and connectors, with functional and nonfunctional behaviours and interfaces defined. The ADL includes a configuration part, describing the connection between components and connectors, defined using a CSP-like notation. The ADL is amenable to the use of theorem proving techniques for establishing correctness of the architecture. The recursive architecture is also specified as apart of the communication. The design for the CARE ADL is incorporated with the plan to leverage existing tools for matching and adapting CARE components, to develop support for the detection and correction of architecture mismatches (i.e. where components do not interoperate correctly).
{"title":"Specifying Software Architectures Using a Formal-Based Approach","authors":"D. Hemer, Yulin Ding","doi":"10.1109/ASWEC.2008.9","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.9","url":null,"abstract":"Architecture description languages (ADLs) describe the abstracted structure of a system. In this paper we describe a new ADL based on extension of the existing CARE language used informally specifying and implementing reusable software components. The main elements of this ADL are components and connectors, with functional and nonfunctional behaviours and interfaces defined. The ADL includes a configuration part, describing the connection between components and connectors, defined using a CSP-like notation. The ADL is amenable to the use of theorem proving techniques for establishing correctness of the architecture. The recursive architecture is also specified as apart of the communication. The design for the CARE ADL is incorporated with the plan to leverage existing tools for matching and adapting CARE components, to develop support for the detection and correction of architecture mismatches (i.e. where components do not interoperate correctly).","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"92 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":"129032715","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 basic idea behind software reuse is that software developers use reusable components found in software repositories to reduce the amount of code that has to be written and so increase productivity. A problem arises, however, if the repository is too big - it becomes difficult to find relevant components. What is needed is an effective means to query repositories. Most approaches to developing such means involves creating a good index to which the queries can be applied. Developing a good index requires identifying the relevant information on which to base the index. In this paper, we present the results of a project that used source code as the basis for the index.
{"title":"Indexing the Java API Using Source Code","authors":"Homan Ma, R. Amor, E. Tempero","doi":"10.1109/ASWEC.2008.33","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.33","url":null,"abstract":"The basic idea behind software reuse is that software developers use reusable components found in software repositories to reduce the amount of code that has to be written and so increase productivity. A problem arises, however, if the repository is too big - it becomes difficult to find relevant components. What is needed is an effective means to query repositories. Most approaches to developing such means involves creating a good index to which the queries can be applied. Developing a good index requires identifying the relevant information on which to base the index. In this paper, we present the results of a project that used source code as the basis for the index.","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":"114091018","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}
Nowadays there are systems to enact processes, but only technology is not enough to help software processes achieve their goals, specially those related to product quality, costs and schedule. Before process enactment, it is necessary to define and represent process models so that they reflect business aspects, are understood by all stakeholders, and are adjusted to software development processes and software factories characteristics. To correspond to these criteria, in this paper a method is proposed aiming to define an object oriented process architecture. This method helps to define process models that can be specialized to meet the needs of distinct organizations and software development processes. The result of this research is a method composed of a set of activities divided into phases to define process models at distinct abstraction levels.
{"title":"A Method to Define an Object Oriented Software Process Architecture","authors":"B. T. Borsoi, J. Becerra","doi":"10.1109/ASWEC.2008.20","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.20","url":null,"abstract":"Nowadays there are systems to enact processes, but only technology is not enough to help software processes achieve their goals, specially those related to product quality, costs and schedule. Before process enactment, it is necessary to define and represent process models so that they reflect business aspects, are understood by all stakeholders, and are adjusted to software development processes and software factories characteristics. To correspond to these criteria, in this paper a method is proposed aiming to define an object oriented process architecture. This method helps to define process models that can be specialized to meet the needs of distinct organizations and software development processes. The result of this research is a method composed of a set of activities divided into phases to define process models at distinct abstraction levels.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"18 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":"116751564","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}
Over the years many guidelines have been offered as to how to achieve good quality designs. We would like to be able to determine to what degree these guidelines actually help. To do that, we need to be able to determine when the guidelines have been followed. This is often difficult as the guidelines are often presented as heuristics or otherwise not completely specified. Nevertheless, we believe it is important to gather quantitative data on the effectiveness of design guidelines wherever possible. In this paper, we examine the use of "dependency injection", which is a design principle that is claimed to increase software design quality attributes such as extensibility, modifiability, testability, and reusability. We develop operational definitions for it and analysis techniques for detecting its use. We demonstrate these techniques by applying them to 34 open source Java applications.
{"title":"An Empirical Study into Use of Dependency Injection in Java","authors":"H. Y. Yang, E. Tempero, H. Melton","doi":"10.1109/ASWEC.2008.35","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.35","url":null,"abstract":"Over the years many guidelines have been offered as to how to achieve good quality designs. We would like to be able to determine to what degree these guidelines actually help. To do that, we need to be able to determine when the guidelines have been followed. This is often difficult as the guidelines are often presented as heuristics or otherwise not completely specified. Nevertheless, we believe it is important to gather quantitative data on the effectiveness of design guidelines wherever possible. In this paper, we examine the use of \"dependency injection\", which is a design principle that is claimed to increase software design quality attributes such as extensibility, modifiability, testability, and reusability. We develop operational definitions for it and analysis techniques for detecting its use. We demonstrate these techniques by applying them to 34 open source Java applications.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"41 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":"123174745","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}
S. Lee, Jing Sun, G. Dobbie, L. Groves, Yuan-Fang Li
The rapid increase in semistructured data usage has lead to the development of various database systems for semistructured data. Web services and applications that utilize large amounts of semistructured data require data to remain consistent and be stored efficient. Several normalization algorithms for semistructured database systems have been developed to satisfy these needs. However, these algorithms lack the verification that would ensure that data and constraints among the data are not lost or corrupted during normalization. In this paper, we propose a set of correctness criteria for normalization of semistructured data, which require that functional dependencies are preserved, data is not lost, and spurious data is not created during normalization. We use the Z specification language to provide a precise and declarative definition of our criteria.
{"title":"Correctness Criteria for Normalization of Semistructured Data","authors":"S. Lee, Jing Sun, G. Dobbie, L. Groves, Yuan-Fang Li","doi":"10.1109/ASWEC.2008.51","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.51","url":null,"abstract":"The rapid increase in semistructured data usage has lead to the development of various database systems for semistructured data. Web services and applications that utilize large amounts of semistructured data require data to remain consistent and be stored efficient. Several normalization algorithms for semistructured database systems have been developed to satisfy these needs. However, these algorithms lack the verification that would ensure that data and constraints among the data are not lost or corrupted during normalization. In this paper, we propose a set of correctness criteria for normalization of semistructured data, which require that functional dependencies are preserved, data is not lost, and spurious data is not created during normalization. We use the Z specification language to provide a precise and declarative definition of our criteria.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"3 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":"125768350","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}
Domain knowledge is crucial for the quality of requirements. The systems analysts, who have adequate knowledge of software often don't understand the organizational context well. The Tropos methodology proposes a set of concepts, which are effective in capturing the organizational context, the interactions between the software system and the human agents. Based on the Tropos methodology, Software System-Business Model (SS-BM), which integrates the Software System Actor (SSA) from early requirements organizational model has been proposed. In this paper, a methodological approach of applying the SS-BM to requirements list elicitation is presented. In the proposed method, requirements items were mapped to SS-BM elements based on their semantic meanings. The mapped requirements list and SS-BM were analyzed in a specific sequence according to multiple checking points. The problems of requirements list were identified in the analysis process. For each kind of problem identified a possible improvement is proposed. Quality indicators were used to summarize the quality of requirements at the end of the elicitation process.
{"title":"Requirements Elicitation Using Goal-Based Organizational Model","authors":"A. Krishna, He Lu","doi":"10.1109/ASWEC.2008.57","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.57","url":null,"abstract":"Domain knowledge is crucial for the quality of requirements. The systems analysts, who have adequate knowledge of software often don't understand the organizational context well. The Tropos methodology proposes a set of concepts, which are effective in capturing the organizational context, the interactions between the software system and the human agents. Based on the Tropos methodology, Software System-Business Model (SS-BM), which integrates the Software System Actor (SSA) from early requirements organizational model has been proposed. In this paper, a methodological approach of applying the SS-BM to requirements list elicitation is presented. In the proposed method, requirements items were mapped to SS-BM elements based on their semantic meanings. The mapped requirements list and SS-BM were analyzed in a specific sequence according to multiple checking points. The problems of requirements list were identified in the analysis process. For each kind of problem identified a possible improvement is proposed. Quality indicators were used to summarize the quality of requirements at the end of the elicitation process.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"24 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":"129789570","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. Pasala, Yannick L. H. Lew Yaw Fung, F. Akladios, G. AppalaRaju, R. Gorthi
In this paper, we propose a regression test suite selection strategy that recommends a smaller test suite to validate software applications upon deployment of upgrades to application components. The selection strategy is based on analyzing the dynamic behavior of the application and recommends a smaller test suite to validate software applications. Methods based on dynamic analysis of software applications are more efficient as they analyze the application by executing the application according to its intended use. Based on the proposed approach, we have developed a prototype tool called InARTS that determines the impact of upgrades on industrial applications and suggests a reduced set of regression tests. Results of two case studies performed on two practical applications using InARTS are included.
{"title":"Selection of Regression Test Suite to Validate Software Applications upon Deployment of Upgrades","authors":"A. Pasala, Yannick L. H. Lew Yaw Fung, F. Akladios, G. AppalaRaju, R. Gorthi","doi":"10.1109/ASWEC.2008.43","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.43","url":null,"abstract":"In this paper, we propose a regression test suite selection strategy that recommends a smaller test suite to validate software applications upon deployment of upgrades to application components. The selection strategy is based on analyzing the dynamic behavior of the application and recommends a smaller test suite to validate software applications. Methods based on dynamic analysis of software applications are more efficient as they analyze the application by executing the application according to its intended use. Based on the proposed approach, we have developed a prototype tool called InARTS that determines the impact of upgrades on industrial applications and suggests a reduced set of regression tests. Results of two case studies performed on two practical applications using InARTS are included.","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":"129667319","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Requirements elicitation and analysis is the most crucial process in requirements engineering since it moulds the shape of the desired end product. In dealing with a system's stakeholders in a process to elicit the requirements, conflicts are inevitable. In the initial state, usually, all the stakeholders have a common goal; to build a system. However as an individual, they do have their own perspectives and perceptions. In addition, the stakeholders, either as a representative of end users, a decision maker or a developer, have different concerns, priorities and responsibilities. This paper considers introducing negotiation spiral model with supporting elements in the requirements elicitation and analysis process. Many researches show that negotiation is necessary to handle conflicts in order to gain better requirements. It is believed that the quality of intermediate deliverables like the requirements document is correlated with the quality of the final product. The advantages of implementing negotiation process are well aligned requirements by all the stakeholders, improved system quality, a sound basis for resource estimation and less resource wastage.
{"title":"Negotiation in the Requirements Elicitation and Analysis Process","authors":"Sabrina Ahmad","doi":"10.1109/ASWEC.2008.66","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.66","url":null,"abstract":"Requirements elicitation and analysis is the most crucial process in requirements engineering since it moulds the shape of the desired end product. In dealing with a system's stakeholders in a process to elicit the requirements, conflicts are inevitable. In the initial state, usually, all the stakeholders have a common goal; to build a system. However as an individual, they do have their own perspectives and perceptions. In addition, the stakeholders, either as a representative of end users, a decision maker or a developer, have different concerns, priorities and responsibilities. This paper considers introducing negotiation spiral model with supporting elements in the requirements elicitation and analysis process. Many researches show that negotiation is necessary to handle conflicts in order to gain better requirements. It is believed that the quality of intermediate deliverables like the requirements document is correlated with the quality of the final product. The advantages of implementing negotiation process are well aligned requirements by all the stakeholders, improved system quality, a sound basis for resource estimation and less resource wastage.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"8 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":"130146604","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
扫码关注我们
求助内容：
应助结果提醒方式：