{"title":"A survey on early separation of concerns","authors":"Safoora Shakil Khan, M. Rehman","doi":"10.1109/APSEC.2005.17","DOIUrl":"https://doi.org/10.1109/APSEC.2005.17","url":null,"abstract":"Aspect oriented software development (AOSD) focuses on the separation of crosscutting concerns. Crosscutting concerns are separable at the requirements phase, design phase, or implementation phase. In this survey, we have classified aspect oriented requirements engineering (AORE) approaches as traditional and non-traditional requirements engineering approaches. The traditional approaches are based on fundamental requirements engineering approaches such as viewpoint oriented, use case/scenario, and goal oriented approaches. Whereas the non-traditional approaches are based on component based engineering, feature driven developments, and domain analysis and engineering. The AORE models have been compared on the basis of systematic activities for separation of concerns: identify, separate, represent, and compose, conflict resolution techniques, and tool support. This survey deals with the open issues put forward by various authors and the observations made by analyses of the AORE models.","PeriodicalId":359862,"journal":{"name":"12th Asia-Pacific Software Engineering Conference (APSEC'05)","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-12-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121082882","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}
{"title":"Conformance testing of BDI properties in agent-based software","authors":"M. Zheng, V. Alagar","doi":"10.1109/APSEC.2005.54","DOIUrl":"https://doi.org/10.1109/APSEC.2005.54","url":null,"abstract":"Agent-based software engineering combines the strengths of agent theory with the practical software engineering methods for developing large intelligent systems. Designing and implementing agent-based systems are complicated tasks because the agent's BDI characteristics (beliefs, desires, intentions) when codified in the design/implementation as software characteristics may have acquired different connotations. Consequently testing the reliability of the implementation is equally hard. It is necessary to choose an agent's software abstraction that has a minimal deviation from the BDI agent concept, and use it as a formal basis to test an implementation. This paper proposes one such method for conformance testing of BDI properties in an agent-based system.","PeriodicalId":359862,"journal":{"name":"12th Asia-Pacific Software Engineering Conference (APSEC'05)","volume":"64 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-12-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124842162","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}
{"title":"A temporal logic for input output symbolic transition systems","authors":"M. Aiguier, P. L. Gall, D. Longuet, A. Touil","doi":"10.1109/APSEC.2005.19","DOIUrl":"https://doi.org/10.1109/APSEC.2005.19","url":null,"abstract":"In this paper, we present a temporal logic called /spl Fscr/ whose interpretation is over input output symbolic transition systems (IOSTS). IOSTS extend transition systems to communications and data in order to tackle communications with system environment. /spl Fscr/ is then defined as an extension of temporal logic CTL* (a temporal logic which mixes together the features of linear temporal logic (LTL) and computational temporal logic (CTL)). Three basic properties are established on /spl Fscr/: adequacy and preservation of properties along synchronized product and IOSTS refinement.","PeriodicalId":359862,"journal":{"name":"12th Asia-Pacific Software Engineering Conference (APSEC'05)","volume":"117 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-12-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128355835","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}
{"title":"Enhancement of a use cases based requirements engineering approach with scenarios","authors":"S. Somé","doi":"10.1109/APSEC.2005.64","DOIUrl":"https://doi.org/10.1109/APSEC.2005.64","url":null,"abstract":"Use cases and scenarios are sometimes considered as analogous. In this paper, we take the position that use cases and scenarios are different but play complementary roles in requirements engineering. A use case is a collection of scenarios. Use cases are appropriate as specification of a system required behavior in interaction with its actors. A scenario is an example of execution involving a system and its actors. A scenario may be defined with the intention that it should be supported or the intention that it should be avoided. Scenarios can thus be used to validate functional as well as non-functional requirements specification. We present an integration of scenarios to a use case based requirements engineering approach and discuss the merits of such integration.","PeriodicalId":359862,"journal":{"name":"12th Asia-Pacific Software Engineering Conference (APSEC'05)","volume":"23 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-12-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125200346","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}
{"title":"A tools environment for developing and reasoning about ontologies","authors":"J. Dong, Yuzhang Feng, Yuan-Fang Li, Jun Sun","doi":"10.1109/APSEC.2005.21","DOIUrl":"https://doi.org/10.1109/APSEC.2005.21","url":null,"abstract":"Started in the beginning of 2001, the semantic Web is regarded by many as the next generation of the Web. Ontology languages are the building blocks of semantic Web as they provide basic vocabularies for data markups: the ontologies. The correctness of shared ontologies is crucial to the proper functioning of agents. Hence ensuring the consistency of ontologies is a central issue in both the design and deployment phases of any semantic Web-aware application. Our experiences show that semantic Web is a novel and fruitful application domain for formal languages and their mature reasoning tool support. In order to ease the application of formal methods and tools to the semantic Web, we developed an integrated tools environment to support systematic development of OWL ontologies and then transformation, reasoning assistance and querying of them.","PeriodicalId":359862,"journal":{"name":"12th Asia-Pacific Software Engineering Conference (APSEC'05)","volume":"74 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-12-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127234785","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}
{"title":"Regression testing for component-based software systems by enhancing change information","authors":"Chengying Mao, Yansheng Lu","doi":"10.1109/APSEC.2005.95","DOIUrl":"https://doi.org/10.1109/APSEC.2005.95","url":null,"abstract":"In recent years, component-based software has been widely used in various application domains and becomes a fairly popular software form. However, due to the lack of information about the externally-developed components, system testers (i.e., component users) generally can't perform effective testing (especially regression testing) on their component-based systems. Component users don't know the details about change in component, so they aren't able to select the proper test cases to retest the modified system. In this paper, we present an improved regression testing method based on the enhanced change information of component version to test the software system containing some modified components. It is a collaborative testing method, needing the joint participations of component developer and user. Component developers calculate the change information from labeled method call graph and provide it to component users via XML files. Component users use this change information and their instrumentation records together to pick out test cases for next-round testing. In addition, we have employed preliminary experiments on some medium scale systems, the experiment results show that our regression testing method is fairly feasible and cost-effective in practice.","PeriodicalId":359862,"journal":{"name":"12th Asia-Pacific Software Engineering Conference (APSEC'05)","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-12-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116732508","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}
{"title":"A systematic method for scoping core assets in product line engineering","authors":"Shinyoung Park, Soo Dong Kim","doi":"10.1109/APSEC.2005.18","DOIUrl":"https://doi.org/10.1109/APSEC.2005.18","url":null,"abstract":"Product line engineering (PLE) is an effective reuse methodology where common features among members are captured into core assets and applications are produced by reusing the core assets, reducing development cost while increasing productivity. To maximize the reusability of core assets, optimal scoping of core assets is essential. If the scope is excessively broad, it results in high cost of asset development while lowering reusability. On the other hand, if the scope is too narrow, it results in a limited applicability, only supporting a small number of members in the domain. In this paper, we propose a process for domain analysis and economical analysis of core asset scope. Then, we define guidelines for each activity of the process. Since variability often occurs in PLE, we significantly treat the variability of features among members. By applying our scoping framework, one can develop core assets of which scope provide the most economical value.","PeriodicalId":359862,"journal":{"name":"12th Asia-Pacific Software Engineering Conference (APSEC'05)","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-12-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124069100","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}
Santokh Singh, Hsiao-Cheng Chen, Oliver Hunter, J. Grundy, J. Hosking
{"title":"Improving agile software development using extreme AOCE and aspect-oriented CVS","authors":"Santokh Singh, Hsiao-Cheng Chen, Oliver Hunter, J. Grundy, J. Hosking","doi":"10.1109/APSEC.2005.71","DOIUrl":"https://doi.org/10.1109/APSEC.2005.71","url":null,"abstract":"Currently there are no concurrent versioning systems (CVS) designed to properly support agile software development. The existing CVS lacks user friendliness and it requires users to be fully experienced with the system before they can adequately use it. Also its asynchronous style of merging often leads to code loss. In this paper, we describe a novel CVS system, called the aspect-oriented CVS (AOCVS) and our newly derived agile software development methodology, extreme aspect-oriented component engineering (extreme AOCE). Unlike the general CVS which is used for a vast variety of projects, AOCVS was designed and developed specifically for extreme AOCE. Our CVS tool merges the changes in a synchronous/real time fashion; this in turn removes the hassle for the developers on having to resolve merging conflicts. We also describe how our implemented AOCVS can be used to provide functionalities that can assist developers to produce and distribute reusable code and to communicate and manage aspect-oriented agile projects more efficiently and effectively. Our novel agile approach and tool allows software developers to use the rich cross-cutting systemic concerns, their behaviour and properties in aspect-oriented components to refactor, maintain, add functionalities and test complex software systems more easily, rapidly and accurately.","PeriodicalId":359862,"journal":{"name":"12th Asia-Pacific Software Engineering Conference (APSEC'05)","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-12-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127649917","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}
{"title":"Lightweight detection of program refactorings","authors":"Darren C. Atkinson, Todd King","doi":"10.1109/APSEC.2005.76","DOIUrl":"https://doi.org/10.1109/APSEC.2005.76","url":null,"abstract":"Poorly structured code is hard to maintain and read. Program refactoring can improve code structure and thus make it easier to preserve and to discern the underlying design. However, refactoring is a difficult and time-consuming process making it unattractive for many developers. An automated tool that could identify poorly structured code and make suggestions would make the refactoring process easier. Although in general refactorings may be quite difficult to locate automatically, we show that many can be detected using low-cost, syntactic techniques. We have built a tool to locate refactorings in C# programs. Our experiments indicate that the tool has an excellent success rate in identifying refactorings.","PeriodicalId":359862,"journal":{"name":"12th Asia-Pacific Software Engineering Conference (APSEC'05)","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-12-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128013643","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}
{"title":"A formal semantics of timed activity diagrams and its PROMELA translation","authors":"N. Guelfi, A. Mammar","doi":"10.1109/APSEC.2005.7","DOIUrl":"https://doi.org/10.1109/APSEC.2005.7","url":null,"abstract":"The lack of a precise semantics for UML activity diagrams makes the reasoning on models constructed using such diagrams infeasible. However, such diagrams are widely used in domains that require a certain degree of confidence. Due to economical interests, the business domain is one of these. To enhance confidence level of UML activity diagrams, this paper provides a formal definition of their syntax and semantics. The main interest of our approach is that we chose UML activity diagrams, which are recognized to be more tractable by engineers, and we extend them with timing constraints. We outline the translation of our semantics into the PROMELA input language of the SPIN model checker which can be used to check several properties.","PeriodicalId":359862,"journal":{"name":"12th Asia-Pacific Software Engineering Conference (APSEC'05)","volume":"119 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-12-15","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131025737","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}