Pub Date : 2009-05-16DOI: 10.1109/WOSQ.2009.5071553
Andrea Bei, M. Lancia, F. Lombardi, R. Puccinelli
The availability of open standards and tools have made often convenient for Public Administrations to internalize software development activities. In order to establish a software factory, it is critical to define processes. While many process standards have been devised over time, in our opinion there exist fewer effective guidelines on how to tailor them to an organization's actual needs. This paper describes the experience we acquired and the lessons we learned through the years on process definition by managing a number of software development projects within CNR1 Central Administration. In particular, a software development process is described that we consider adequate for small-to-medium-sized software factories (frequent case for non-ICT organizations). “Inclusion criteria” are also suggested for the artefacts of each phase, in order to allow further process tailoring. Our process is then discussed against a set of case studies which represent the empirical basis of our tailoring work. We believe our experience can be of use for other similar contexts, particularly within the Public Administration.
{"title":"Processes for software development within the Public Administration","authors":"Andrea Bei, M. Lancia, F. Lombardi, R. Puccinelli","doi":"10.1109/WOSQ.2009.5071553","DOIUrl":"https://doi.org/10.1109/WOSQ.2009.5071553","url":null,"abstract":"The availability of open standards and tools have made often convenient for Public Administrations to internalize software development activities. In order to establish a software factory, it is critical to define processes. While many process standards have been devised over time, in our opinion there exist fewer effective guidelines on how to tailor them to an organization's actual needs. This paper describes the experience we acquired and the lessons we learned through the years on process definition by managing a number of software development projects within CNR1 Central Administration. In particular, a software development process is described that we consider adequate for small-to-medium-sized software factories (frequent case for non-ICT organizations). “Inclusion criteria” are also suggested for the artefacts of each phase, in order to allow further process tailoring. Our process is then discussed against a set of case studies which represent the empirical basis of our tailoring work. We believe our experience can be of use for other similar contexts, particularly within the Public Administration.","PeriodicalId":158077,"journal":{"name":"2009 ICSE Workshop on Software Quality","volume":"32 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125588710","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}
Pub Date : 2009-05-16DOI: 10.1109/WOSQ.2009.5071556
Mikael Svahnberg, Kennet Henningsson
In recent years, quality attributes have received increased attention as being critical for a software system's success or failure. Different classifications of quality attributes frequently mention many relations both positive and negative between quality attributes. However, the classifications and the quality attribute relations are often presented in such a way that they are not easily compared with each other, which means that it is difficult to confirm the relations found in one source with the relations found in another. In this article we triangulate between different sources where quality attribute relations have been (or can be) expressed. The contribution is a consolidated view of which quality attributes that are considered (by several sources) to have positive or negative relations with each other.
{"title":"Consolidating different views of quality attribute relationships","authors":"Mikael Svahnberg, Kennet Henningsson","doi":"10.1109/WOSQ.2009.5071556","DOIUrl":"https://doi.org/10.1109/WOSQ.2009.5071556","url":null,"abstract":"In recent years, quality attributes have received increased attention as being critical for a software system's success or failure. Different classifications of quality attributes frequently mention many relations both positive and negative between quality attributes. However, the classifications and the quality attribute relations are often presented in such a way that they are not easily compared with each other, which means that it is difficult to confirm the relations found in one source with the relations found in another. In this article we triangulate between different sources where quality attribute relations have been (or can be) expressed. The contribution is a consolidated view of which quality attributes that are considered (by several sources) to have positive or negative relations with each other.","PeriodicalId":158077,"journal":{"name":"2009 ICSE Workshop on Software Quality","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131017790","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}
Pub Date : 2009-05-16DOI: 10.1109/WOSQ.2009.5071555
Parastoo Mohagheghi, Vegard Dehlen
This paper presents quality goals for models and provides a state-of-the-art analysis regarding model metrics. While model-based software development often requires assessing the quality of models at different abstraction and precision levels and developed for multiple purposes, existing work on model metrics do not reflect this need. Model size metrics are descriptive and may be used for comparing models but their relation to model quality is not well-defined. Code metrics are proposed to be applied on models for evaluating design quality while metrics related to other quality goals are few. Models often consist of a significant amount of elements, which allows a large amount of metrics to be defined on them. However, identifying useful model metrics, linking them to model quality goals, providing some baseline for interpretation of data, and combining metrics with other evaluation models such as inspections requires more theoretical and empirical work.
{"title":"Existing model metrics and relations to model quality","authors":"Parastoo Mohagheghi, Vegard Dehlen","doi":"10.1109/WOSQ.2009.5071555","DOIUrl":"https://doi.org/10.1109/WOSQ.2009.5071555","url":null,"abstract":"This paper presents quality goals for models and provides a state-of-the-art analysis regarding model metrics. While model-based software development often requires assessing the quality of models at different abstraction and precision levels and developed for multiple purposes, existing work on model metrics do not reflect this need. Model size metrics are descriptive and may be used for comparing models but their relation to model quality is not well-defined. Code metrics are proposed to be applied on models for evaluating design quality while metrics related to other quality goals are few. Models often consist of a significant amount of elements, which allows a large amount of metrics to be defined on them. However, identifying useful model metrics, linking them to model quality goals, providing some baseline for interpretation of data, and combining metrics with other evaluation models such as inspections requires more theoretical and empirical work.","PeriodicalId":158077,"journal":{"name":"2009 ICSE Workshop on Software Quality","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124431420","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}
Pub Date : 2009-05-16DOI: 10.1109/WOSQ.2009.5071559
Ana Sanz, Javier García, J. Saldaña, Antonio Amescua
Software Quality Assurance (SQA) is becoming a critical issue in software development and maintenance. Software development organizations are dedicating significant resources to testing as their contribution to SQA. This paper discusses the existing organizational approaches to implementing testing practices. Nowadays, software development organizations are beginning to outsource the testing-related activities to organizations (testing factories) in order to reduce the resources dedicated to testing and increasing the quality and reliability of the final software products and services. A software factory needs a specific organizational model for its management. The organizational model must be composed of a testing process model and an organizational structure establishing the required roles, responsibilities and competences. This paper focuses on describing a proposed process model to manage a software factory. Finally, this paper introduces the current experiences obtained from the proposed model.
{"title":"A proposal of a process model to create a test factory","authors":"Ana Sanz, Javier García, J. Saldaña, Antonio Amescua","doi":"10.1109/WOSQ.2009.5071559","DOIUrl":"https://doi.org/10.1109/WOSQ.2009.5071559","url":null,"abstract":"Software Quality Assurance (SQA) is becoming a critical issue in software development and maintenance. Software development organizations are dedicating significant resources to testing as their contribution to SQA. This paper discusses the existing organizational approaches to implementing testing practices. Nowadays, software development organizations are beginning to outsource the testing-related activities to organizations (testing factories) in order to reduce the resources dedicated to testing and increasing the quality and reliability of the final software products and services. A software factory needs a specific organizational model for its management. The organizational model must be composed of a testing process model and an organizational structure establishing the required roles, responsibilities and competences. This paper focuses on describing a proposed process model to manage a software factory. Finally, this paper introduces the current experiences obtained from the proposed model.","PeriodicalId":158077,"journal":{"name":"2009 ICSE Workshop on Software Quality","volume":"55 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124631916","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}
Pub Date : 2009-05-16DOI: 10.1109/WOSQ.2009.5071550
B. Wong, Mahwish Bhatti
Implementing software development successfully in an organization is possibly one of the most challenging issues that the industry faces today. Project failures and the lack of software quality have become a major concern for researchers and practitioners. For many software development projects as well as for many quality assurance departments, teamwork is extremely important. Therefore, nearly all organizations pay attention to teamwork which is essential for smooth operation of a project. It is believed that teamwork is crucial for the success or failure of a project. In addition to the importance of teamwork, team issues affecting its' performance also needs attention. Among these team issues, people issues are scarce in the literature. The research outlined in this paper investigated the factors which influence teamwork. It identified the importance of trust and how trust influences IT project teams and the role of project managers and team leaders in improving trust within teams. It also includes individual behaviors that affect trust within a team. A study of six project managers from two Australian organizations was conducted to investigate the factors which influence teamwork to result in project success and software quality. The results showed that trust is a central element of the many factors and that without trust in the team; teamwork will be negatively affected resulting in project failure and poor quality.
{"title":"The influence of team relationships on software quality","authors":"B. Wong, Mahwish Bhatti","doi":"10.1109/WOSQ.2009.5071550","DOIUrl":"https://doi.org/10.1109/WOSQ.2009.5071550","url":null,"abstract":"Implementing software development successfully in an organization is possibly one of the most challenging issues that the industry faces today. Project failures and the lack of software quality have become a major concern for researchers and practitioners. For many software development projects as well as for many quality assurance departments, teamwork is extremely important. Therefore, nearly all organizations pay attention to teamwork which is essential for smooth operation of a project. It is believed that teamwork is crucial for the success or failure of a project. In addition to the importance of teamwork, team issues affecting its' performance also needs attention. Among these team issues, people issues are scarce in the literature. The research outlined in this paper investigated the factors which influence teamwork. It identified the importance of trust and how trust influences IT project teams and the role of project managers and team leaders in improving trust within teams. It also includes individual behaviors that affect trust within a team. A study of six project managers from two Australian organizations was conducted to investigate the factors which influence teamwork to result in project success and software quality. The results showed that trust is a central element of the many factors and that without trust in the team; teamwork will be negatively affected resulting in project failure and poor quality.","PeriodicalId":158077,"journal":{"name":"2009 ICSE Workshop on Software Quality","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129670360","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}
Pub Date : 2009-05-16DOI: 10.1109/WOSQ.2009.5071552
Frank Salger, G. Engels, A. Hofmann
Early inspections of software requirements specifications (SRS) are known to be an effective and cost-efficient quality assurance technique. However, inspections are often applied with the underlying assumption that they work equally well to assess all kinds of quality attributes of SRS. Little work has yet been done to validate this assumption. At Capgemini sd&m, we set up an inspection technique to assess SRS, the so called “specification quality gate” (QG-Spec). The QG-Spec has been applied to a series of large scale commercial projects. In this paper we present our lessons learned and discuss, which quality attributes are effectively assessed by means of the QG-Spec - and which are not. We argue that our results can be generalized to other existing inspection techniques. We came to the conclusion that inspections have to be carefully balanced with techniques for constructive quality assurance in order to economically arrive at high quality SRS.
{"title":"Inspection effectiveness for different quality attributes of software requirement specifications: An industrial case study","authors":"Frank Salger, G. Engels, A. Hofmann","doi":"10.1109/WOSQ.2009.5071552","DOIUrl":"https://doi.org/10.1109/WOSQ.2009.5071552","url":null,"abstract":"Early inspections of software requirements specifications (SRS) are known to be an effective and cost-efficient quality assurance technique. However, inspections are often applied with the underlying assumption that they work equally well to assess all kinds of quality attributes of SRS. Little work has yet been done to validate this assumption. At Capgemini sd&m, we set up an inspection technique to assess SRS, the so called “specification quality gate” (QG-Spec). The QG-Spec has been applied to a series of large scale commercial projects. In this paper we present our lessons learned and discuss, which quality attributes are effectively assessed by means of the QG-Spec - and which are not. We argue that our results can be generalized to other existing inspection techniques. We came to the conclusion that inspections have to be carefully balanced with techniques for constructive quality assurance in order to economically arrive at high quality SRS.","PeriodicalId":158077,"journal":{"name":"2009 ICSE Workshop on Software Quality","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114493102","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}
Pub Date : 2009-05-16DOI: 10.1109/WOSQ.2009.5071558
M. T. Baldassarre, M. Piattini, F. Pino, G. Visaggio
Software process improvement is a planned, managed and controlled effort which aims to enhance the capability of the software development processes of an organization. In particular, SPI often involves process reference models, process assessment methods and models that guide process improvement though specific standards such as the ISO and CMMI families. Recently, growing interest has been shown towards the need for harmonization of different improvement technologies with the aim of presenting an integrated vision about the standards. In this sense this paper presents a comparison between the process areas of CMMI-DEV and the processes described in the latest version of ISO/IEC 12207:2008. Based on these results we investigate the relationship between the CMMI-DEV and ISO/IEC 15504-7 models with the aim of identifying the degree of coverage of CMMI-DEV maturity levels in relation to ISO/IEC 15504-7.
{"title":"Comparing ISO/IEC 12207 and CMMI-DEV: Towards a mapping of ISO/IEC 15504-7","authors":"M. T. Baldassarre, M. Piattini, F. Pino, G. Visaggio","doi":"10.1109/WOSQ.2009.5071558","DOIUrl":"https://doi.org/10.1109/WOSQ.2009.5071558","url":null,"abstract":"Software process improvement is a planned, managed and controlled effort which aims to enhance the capability of the software development processes of an organization. In particular, SPI often involves process reference models, process assessment methods and models that guide process improvement though specific standards such as the ISO and CMMI families. Recently, growing interest has been shown towards the need for harmonization of different improvement technologies with the aim of presenting an integrated vision about the standards. In this sense this paper presents a comparison between the process areas of CMMI-DEV and the processes described in the latest version of ISO/IEC 12207:2008. Based on these results we investigate the relationship between the CMMI-DEV and ISO/IEC 15504-7 models with the aim of identifying the degree of coverage of CMMI-DEV maturity levels in relation to ISO/IEC 15504-7.","PeriodicalId":158077,"journal":{"name":"2009 ICSE Workshop on Software Quality","volume":"83 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126281969","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}
Pub Date : 2009-05-16DOI: 10.1109/WOSQ.2009.5071554
Michele Bombardieri, F. Fontana
In the last years the software application portfolio has become a key asset for almost all companies. During their lives, applications undergo lots of changes to add new functionalities or to refactor older ones; these changes tend to reduce the quality of the applications themselves, causing the phenomenon known as software aging.
{"title":"Software aging assessment through a specialization of the SQuaRE quality model","authors":"Michele Bombardieri, F. Fontana","doi":"10.1109/WOSQ.2009.5071554","DOIUrl":"https://doi.org/10.1109/WOSQ.2009.5071554","url":null,"abstract":"In the last years the software application portfolio has become a key asset for almost all companies. During their lives, applications undergo lots of changes to add new functionalities or to refactor older ones; these changes tend to reduce the quality of the applications themselves, causing the phenomenon known as software aging.","PeriodicalId":158077,"journal":{"name":"2009 ICSE Workshop on Software Quality","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114252752","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}
Pub Date : 2009-05-16DOI: 10.1109/WOSQ.2009.5071557
Justin Wong, D. Ho, Luiz Fernando Capretz
Neuro-Fuzzy refers to a hybrid intelligent system using both neural network and fuzzy logic. In this study, neuro-fuzzy is applied to a backfiring and categorical data size estimation model. Evaluation was conducted to determine whether a neuro-fuzzy approach improves software size estimations. It was found that a neuro-fuzzy approach provides minimal improvement over the traditional backfiring sizing technique.
{"title":"An investigation of using Neuro-Fuzzy with software size estimation","authors":"Justin Wong, D. Ho, Luiz Fernando Capretz","doi":"10.1109/WOSQ.2009.5071557","DOIUrl":"https://doi.org/10.1109/WOSQ.2009.5071557","url":null,"abstract":"Neuro-Fuzzy refers to a hybrid intelligent system using both neural network and fuzzy logic. In this study, neuro-fuzzy is applied to a backfiring and categorical data size estimation model. Evaluation was conducted to determine whether a neuro-fuzzy approach improves software size estimations. It was found that a neuro-fuzzy approach provides minimal improvement over the traditional backfiring sizing technique.","PeriodicalId":158077,"journal":{"name":"2009 ICSE Workshop on Software Quality","volume":"73 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132616173","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}
Pub Date : 2009-05-16DOI: 10.1109/WOSQ.2009.5071551
F. Deißenböck, Elmar Jürgens, K. Lochmann, S. Wagner
Software quality models are a well-accepted means to support quality management of software systems. Over the last 30 years, a multitude of quality models have been proposed and applied with varying degrees of success. Despite successes and standardisation efforts, quality models are still being criticised, as their application in practice exhibits various problems. To some extent, this criticism is caused by an unclear definition of what quality models are and which purposes they serve. Beyond this, there is a lack of explicitly stated requirements for quality models with respect to their intended mode of application. To remedy this, this paper describes purposes and usage scenarios of quality models and, based on the literature and experiences from the authors, collects critique of existing models. From this, general requirements for quality models are derived. The requirements can be used to support the evaluation of existing quality models for a given context or to guide further quality model development.
{"title":"Software quality models: Purposes, usage scenarios and requirements","authors":"F. Deißenböck, Elmar Jürgens, K. Lochmann, S. Wagner","doi":"10.1109/WOSQ.2009.5071551","DOIUrl":"https://doi.org/10.1109/WOSQ.2009.5071551","url":null,"abstract":"Software quality models are a well-accepted means to support quality management of software systems. Over the last 30 years, a multitude of quality models have been proposed and applied with varying degrees of success. Despite successes and standardisation efforts, quality models are still being criticised, as their application in practice exhibits various problems. To some extent, this criticism is caused by an unclear definition of what quality models are and which purposes they serve. Beyond this, there is a lack of explicitly stated requirements for quality models with respect to their intended mode of application. To remedy this, this paper describes purposes and usage scenarios of quality models and, based on the literature and experiences from the authors, collects critique of existing models. From this, general requirements for quality models are derived. The requirements can be used to support the evaluation of existing quality models for a given context or to guide further quality model development.","PeriodicalId":158077,"journal":{"name":"2009 ICSE Workshop on Software Quality","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125200395","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
扫码关注我们
求助内容：
应助结果提醒方式：