Agile software development methods are nowadays wide spread and accepted. From the software measurement point-of-view not all metrics and methods from conventional lifecycle models can be used without adaptation. Distinct techniques in agile software development like refactoring needs new approaches and quality models in the area of software measurement. Therefore this paper describes a quality model, distinct metrics and their implementation into a measurement tool for quality management in agile software development.
{"title":"Software Metrics for Agile Software Development","authors":"M. Kunz, R. Dumke, N. Zenker","doi":"10.1109/ASWEC.2008.61","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.61","url":null,"abstract":"Agile software development methods are nowadays wide spread and accepted. From the software measurement point-of-view not all metrics and methods from conventional lifecycle models can be used without adaptation. Distinct techniques in agile software development like refactoring needs new approaches and quality models in the area of software measurement. Therefore this paper describes a quality model, distinct metrics and their implementation into a measurement tool for quality management in agile software development.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"69 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":"132735770","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}
Performance testing is one of the vital activities spanning the whole life cycle of software engineering. While there are a considerable number of performance testing products and open source tools available, they are either too expensive and complicated for small projects, or too specific and simple for diverse performance tests. This paper presents a general-purpose testing framework for both simple and small, and complicated and large-scale performance testing. Our framework proposes an abstraction to facilitate performance testing by separating the application logic from the common performance testing functionalities. This leads to a set of general-purpose data models and components, which form the core of the framework. The framework has been prototyped on both .NET and Java platforms and was used for a number of performance-related projects.
{"title":"Yet Another Performance Testing Framework","authors":"Shiping Chen, D. Moreland, S. Nepal, J. Zic","doi":"10.1109/ASWEC.2008.53","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.53","url":null,"abstract":"Performance testing is one of the vital activities spanning the whole life cycle of software engineering. While there are a considerable number of performance testing products and open source tools available, they are either too expensive and complicated for small projects, or too specific and simple for diverse performance tests. This paper presents a general-purpose testing framework for both simple and small, and complicated and large-scale performance testing. Our framework proposes an abstraction to facilitate performance testing by separating the application logic from the common performance testing functionalities. This leads to a set of general-purpose data models and components, which form the core of the framework. The framework has been prototyped on both .NET and Java platforms and was used for a number of performance-related projects.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"140 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":"129393597","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}
Traditional software teams consist of independently focused self-managing professionals with high individual but low team autonomy. A challenge with introducing agile software development is that it requires a high level of both individual and team autonomy. This paper studies the barriers with introducing self-organizing teams in agile software development and presents data from a seven month ethnographic study of professional developers in a Scrum team. We found the most important barrier to be the highly specialized skills of the developers and the corresponding division of work. In addition we found a lack of system for team support, and reduced external autonomy to be important barriers for introducing self- organizing teams. These findings have implications for software development managers and practitioners.
{"title":"Understanding Self-Organizing Teams in Agile Software Development","authors":"N. B. Moe, Torgeir Dingsøyr, T. Dybå","doi":"10.1109/ASWEC.2008.28","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.28","url":null,"abstract":"Traditional software teams consist of independently focused self-managing professionals with high individual but low team autonomy. A challenge with introducing agile software development is that it requires a high level of both individual and team autonomy. This paper studies the barriers with introducing self-organizing teams in agile software development and presents data from a seven month ethnographic study of professional developers in a Scrum team. We found the most important barrier to be the highly specialized skills of the developers and the corresponding division of work. In addition we found a lack of system for team support, and reduced external autonomy to be important barriers for introducing self- organizing teams. These findings have implications for software development managers and practitioners.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"159 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":"132365214","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}
Today, agile methods become a popular approach to develop software systems. They try to satisfy customer, respond to changes, release in less time and achieve suitable profits for developers. XP is one of the most popular agile methods which is currently being used and different kinds of research have been accomplished about its various aspects such as pair programming. In spite of all benefits known of XP, it does not involve architectural techniques yet. As it is mentioned in many technical reports, the way to achieve high quality of system is to consider its architecture as an important matter in the development process. This paper introduces two practices in order to empower XP's development process toward improving system's architecture. The main characteristic of proposed solution is that it is derived from values and practices of XP in order to be compatible with XP process model and to keep its agility intact.
{"title":"Embedding Architectural Practices into Extreme Programming","authors":"A. A. Sharifloo, A. Saffarian, F. S. Aliee","doi":"10.1109/ASWEC.2008.65","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.65","url":null,"abstract":"Today, agile methods become a popular approach to develop software systems. They try to satisfy customer, respond to changes, release in less time and achieve suitable profits for developers. XP is one of the most popular agile methods which is currently being used and different kinds of research have been accomplished about its various aspects such as pair programming. In spite of all benefits known of XP, it does not involve architectural techniques yet. As it is mentioned in many technical reports, the way to achieve high quality of system is to consider its architecture as an important matter in the development process. This paper introduces two practices in order to empower XP's development process toward improving system's architecture. The main characteristic of proposed solution is that it is derived from values and practices of XP in order to be compatible with XP process model and to keep its agility intact.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"7 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":"114980166","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 tutorial, we will review contemporary research that aims to 'align' the Web services with the modern Web in two significant aspects - Web services architectural styles and Web services discovery mechanism. Based on a comprehensive survey, we will identify several critical open issues that need to be addressed when incorporating Web (2.0) techniques and philosophies into the Web services practice. These key issues and their associated solutions give rise to our proposed research framework - an alternative Web services paradigms. This tutorial also introduces our recent work in this direction: (1) An evolution trend driven by engineering principles for Internet-scaled Web services architectural design. (2) A Web services discovery platform built on top of Web 2.0 techniques and attitude. In summary, this tutorial demonstrates how to move towards creating an alternative Web services paradigm that aligns itself with the modern Web.
{"title":"Alternative Web Service Paradigms","authors":"T. Dillon, Chen Wu","doi":"10.1109/ASWEC.2008.85","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.85","url":null,"abstract":"In this tutorial, we will review contemporary research that aims to 'align' the Web services with the modern Web in two significant aspects - Web services architectural styles and Web services discovery mechanism. Based on a comprehensive survey, we will identify several critical open issues that need to be addressed when incorporating Web (2.0) techniques and philosophies into the Web services practice. These key issues and their associated solutions give rise to our proposed research framework - an alternative Web services paradigms. This tutorial also introduces our recent work in this direction: (1) An evolution trend driven by engineering principles for Internet-scaled Web services architectural design. (2) A Web services discovery platform built on top of Web 2.0 techniques and attitude. In summary, this tutorial demonstrates how to move towards creating an alternative Web services paradigm that aligns itself with the modern Web.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"111 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":"124130793","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 order to describe how a structure -system evolution directory (SED), can be used to facilitate the evolution of multi-agent systems, we first introduce a case study on citation finding. We use this case study to explain the components within a SED and the process to build a SED. A unified and simple model directory is used to describe the life cycle of a system and a goal model to describe the meaning among system artefacts. Developers can not only get all necessary information ranging from high level system requirements to low level source code from the model, but also can understand semantic connections between system artefacts. Different versions of a system can be recorded easily in the structure. We believe the structure has potential for further speeding up and automating the process of system evolution. All in all, the structure complements current agent-oriented methodologies.
{"title":"Supporting Evolving Multi-agent Systems with a System Evolution Directory","authors":"Bin Lu, L. Sterling, K. Taveter","doi":"10.1109/ASWEC.2008.54","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.54","url":null,"abstract":"In order to describe how a structure -system evolution directory (SED), can be used to facilitate the evolution of multi-agent systems, we first introduce a case study on citation finding. We use this case study to explain the components within a SED and the process to build a SED. A unified and simple model directory is used to describe the life cycle of a system and a goal model to describe the meaning among system artefacts. Developers can not only get all necessary information ranging from high level system requirements to low level source code from the model, but also can understand semantic connections between system artefacts. Different versions of a system can be recorded easily in the structure. We believe the structure has potential for further speeding up and automating the process of system evolution. All in all, the structure complements current agent-oriented methodologies.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"26 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":"116148814","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}
F. Gonçalves, C. Bezerra, A. D. Belchior, Ciro Carneiro Coelho, Carlo Giovano S. Pires
To achieve the highest CMMI maturity level, an organization needs to identify problems, improvement opportunities and innovation and to perform actions to solve the problems and implement the innovations and improvements. Six sigma is a methodology that supports CMMI through a systematic method for problem analysis and process improvement. In this context, this work presents a strategy for identifying, prioritizing and classifying improvement and innovation actions using six sigma in compliance with CMMI level 5. It also presents a practical example of the proposed approach.
{"title":"A Strategy for Identifying, Classifying and Prioritizing Improvement and Innovation Actions: A CMMI Level 5 and Six Sigma Approach","authors":"F. Gonçalves, C. Bezerra, A. D. Belchior, Ciro Carneiro Coelho, Carlo Giovano S. Pires","doi":"10.1109/ASWEC.2008.46","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.46","url":null,"abstract":"To achieve the highest CMMI maturity level, an organization needs to identify problems, improvement opportunities and innovation and to perform actions to solve the problems and implement the innovations and improvements. Six sigma is a methodology that supports CMMI through a systematic method for problem analysis and process improvement. In this context, this work presents a strategy for identifying, prioritizing and classifying improvement and innovation actions using six sigma in compliance with CMMI level 5. It also presents a practical example of the proposed approach.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"155 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":"116227414","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 session at the Australian Software Engineering Conference is concerned with ICT education from the holistic perspective of preparation in high schools, the university experience, transition to the workforce, and the contribution by industry, government, and professional bodies. The project to ascertain the issues and challenges facing the national ICT education sector is supported by the Carrick institute as a discipline-based initiative. Consultations to date with various stakeholders have revealed numerous concerns that include: the dispersed nature of the ICT sector; erroneous perceptions of ICT disciplines; decline in enrolments; gender imbalance; lack of industry involvement; and balancing knowledge with generic skills acquisition. This forum will involve the project team and invited participants to report on findings from consultations and research. Attendees will be invited to respond and to contribute their issues and challenges that are of particular concern to the software engineering community. The seven disciplines that comprise ICT are electrical engineering, computer engineering, telecommunications engineering, software engineering, computer science, information technology, and information systems.
{"title":"Issues in Australian ICT Education","authors":"T. Koppi, F. Naghdy, J. Chicharo","doi":"10.1109/ASWEC.2008.83","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.83","url":null,"abstract":"This session at the Australian Software Engineering Conference is concerned with ICT education from the holistic perspective of preparation in high schools, the university experience, transition to the workforce, and the contribution by industry, government, and professional bodies. The project to ascertain the issues and challenges facing the national ICT education sector is supported by the Carrick institute as a discipline-based initiative. Consultations to date with various stakeholders have revealed numerous concerns that include: the dispersed nature of the ICT sector; erroneous perceptions of ICT disciplines; decline in enrolments; gender imbalance; lack of industry involvement; and balancing knowledge with generic skills acquisition. This forum will involve the project team and invited participants to report on findings from consultations and research. Attendees will be invited to respond and to contribute their issues and challenges that are of particular concern to the software engineering community. The seven disciplines that comprise ICT are electrical engineering, computer engineering, telecommunications engineering, software engineering, computer science, information technology, and information systems.","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":"121096695","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}
Viewpoint-based conceptual modeling is concerned with the identification of a complete and coherent set of software models that have been developed with the involvement of various analysts. The contribution of multiple analysts in this process will provide a rich and comprehensive final product. One of the major concerns in any process requiring the direct involvement of human analysts is the introduction of uncertainty and inconsistency. In this paper, we employ a formal model based on belief theory that attempts to capture the degree of analysts' uncertainty towards their specifications and builds on these information to create a unique integrated model. The model is employed in the process of developing a conceptual model for the Pet Store application. The results show that the formal framework provides suitable tools for formal negotiation, belief revision, consensus building, belief recommendation and expert reliability evaluation.
{"title":"Experiences on the Belief-Theoretic Integration of Para-consistent Conceptual Models","authors":"E. Bagheri, A. Ghorbani","doi":"10.1109/ASWEC.2008.44","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.44","url":null,"abstract":"Viewpoint-based conceptual modeling is concerned with the identification of a complete and coherent set of software models that have been developed with the involvement of various analysts. The contribution of multiple analysts in this process will provide a rich and comprehensive final product. One of the major concerns in any process requiring the direct involvement of human analysts is the introduction of uncertainty and inconsistency. In this paper, we employ a formal model based on belief theory that attempts to capture the degree of analysts' uncertainty towards their specifications and builds on these information to create a unique integrated model. The model is employed in the process of developing a conceptual model for the Pet Store application. The results show that the formal framework provides suitable tools for formal negotiation, belief revision, consensus building, belief recommendation and expert reliability evaluation.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"23 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":"125233311","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}
B. Henderson-Sellers, Cesar Gonzalez-Perez, J. Ralyté
Two main candidates for the atomic element to be used in situational method engineering (SME) have been proposed: the "method fragment" and the "method chunk". These are examined here in terms of their conceptual integrity and in terms of how they may be used in method construction. Also, parallels are drawn between the two approaches. Secondly, the idea of differentiating an interface from a body has been proposed for method chunks (but not for method fragments). This idea is examined and mappings are constructed between the interface and body concepts of method chunks and the concepts used to describe method fragments. The new ISO/IEC 24744 standard metamodel is used as a conceptual framework to perform these mappings.
{"title":"Comparison of Method Chunks and Method Fragments for Situational Method Engineering","authors":"B. Henderson-Sellers, Cesar Gonzalez-Perez, J. Ralyté","doi":"10.1109/ASWEC.2008.67","DOIUrl":"https://doi.org/10.1109/ASWEC.2008.67","url":null,"abstract":"Two main candidates for the atomic element to be used in situational method engineering (SME) have been proposed: the \"method fragment\" and the \"method chunk\". These are examined here in terms of their conceptual integrity and in terms of how they may be used in method construction. Also, parallels are drawn between the two approaches. Secondly, the idea of differentiating an interface from a body has been proposed for method chunks (but not for method fragments). This idea is examined and mappings are constructed between the interface and body concepts of method chunks and the concepts used to describe method fragments. The new ISO/IEC 24744 standard metamodel is used as a conceptual framework to perform these mappings.","PeriodicalId":231903,"journal":{"name":"19th Australian Conference on Software Engineering (aswec 2008)","volume":"59 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":"125245642","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
扫码关注我们
求助内容：
应助结果提醒方式：