Thiago Gottardi, R. Durelli, O. P. López, V. V. D. Camargo
Over the last years a number of Crosscutting Frameworks (CFs) have been developed employing white-box strategies. This strategy requires significant technical knowledge to reuse these frameworks, such as, knowledge in specific programming languages, architectural details and also about the framework nomenclature. Besides, the reuse process can only be initiated when the development reaches the implementation phase, avoiding starting the reuse process in early development phases. In this paper we present a model-based approach for reusing CFs that improves the productivity by allowing the application engineer to concentrate on what is really important during the reuse process. We present the foundations of our approach and also the result of two experiments that uses two versions of a Persistence CF, the original and the model-based. The results were promising regarding the effort employed to conduct the reuse process, but almost no difference was noticed concerning the effort in conducting maintenance activities.
{"title":"Model-Based Reuse for Crosscutting Frameworks: Assessing Reuse and Maintainability Effort","authors":"Thiago Gottardi, R. Durelli, O. P. López, V. V. D. Camargo","doi":"10.1109/SBES.2012.27","DOIUrl":"https://doi.org/10.1109/SBES.2012.27","url":null,"abstract":"Over the last years a number of Crosscutting Frameworks (CFs) have been developed employing white-box strategies. This strategy requires significant technical knowledge to reuse these frameworks, such as, knowledge in specific programming languages, architectural details and also about the framework nomenclature. Besides, the reuse process can only be initiated when the development reaches the implementation phase, avoiding starting the reuse process in early development phases. In this paper we present a model-based approach for reusing CFs that improves the productivity by allowing the application engineer to concentrate on what is really important during the reuse process. We present the foundations of our approach and also the result of two experiments that uses two versions of a Persistence CF, the original and the model-based. The results were promising regarding the effort employed to conduct the reuse process, but almost no difference was noticed concerning the effort in conducting maintenance activities.","PeriodicalId":286943,"journal":{"name":"2012 26th Brazilian Symposium on Software Engineering","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126708293","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}
Karolyne Oliveira, J. Castro, E. Santos, R. Fidalgo, Sergio España, Ó. Pastor
As a result of new business demands and technological advances processes are becoming increasingly complex and heterogeneous. This calls for business processes that must be managed in an autonomic manner in response to changes in its environmental context. However, a key challenge is to provide variability, understandability and scalability in modeling increasingly complex business processes. In our work we rely on explicit representation of environment variability through context-awareness and quality attributes in order to properly represent autonomic features in Business Process Models. We outline a process that helps to define the modularity of the Business Process Models, indicating where the system needs to be instrumented. A meta-model with the concepts used is presented. This novel approach provides four well-defined levels of abstraction: Communicational Level, Technological Level, Operational Level and Service Level. A real example is used to illustrate our proposal.
{"title":"A Multi Level Approach to Autonomic Business Process","authors":"Karolyne Oliveira, J. Castro, E. Santos, R. Fidalgo, Sergio España, Ó. Pastor","doi":"10.1109/SBES.2012.20","DOIUrl":"https://doi.org/10.1109/SBES.2012.20","url":null,"abstract":"As a result of new business demands and technological advances processes are becoming increasingly complex and heterogeneous. This calls for business processes that must be managed in an autonomic manner in response to changes in its environmental context. However, a key challenge is to provide variability, understandability and scalability in modeling increasingly complex business processes. In our work we rely on explicit representation of environment variability through context-awareness and quality attributes in order to properly represent autonomic features in Business Process Models. We outline a process that helps to define the modularity of the Business Process Models, indicating where the system needs to be instrumented. A meta-model with the concepts used is presented. This novel approach provides four well-defined levels of abstraction: Communicational Level, Technological Level, Operational Level and Service Level. A real example is used to illustrate our proposal.","PeriodicalId":286943,"journal":{"name":"2012 26th Brazilian Symposium on Software Engineering","volume":"72 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125759006","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}
Thiago Pinheiro de Araújo, Carla Wanderley, Arndt von Staa
Distributed systems are hard to debug due to the difficulty to collect, organize and relate information about their behavior. When a failure is detected the task to infer the system's state and the operations that have some connection with the problem is often quite difficult and usual debugging techniques often do not apply and, when they do, they are not very effective. This work presents a mechanism based on event logs annotated with contextual information, allowing visualization tools to organize events according to the context of interest for the system operator. We applied this mechanism to a real system and its the effort and cost to detect and diagnose the cause of problems was dramatically reduced.
{"title":"An Introspection Mechanism to Debug Distributed Systems","authors":"Thiago Pinheiro de Araújo, Carla Wanderley, Arndt von Staa","doi":"10.1109/SBES.2012.13","DOIUrl":"https://doi.org/10.1109/SBES.2012.13","url":null,"abstract":"Distributed systems are hard to debug due to the difficulty to collect, organize and relate information about their behavior. When a failure is detected the task to infer the system's state and the operations that have some connection with the problem is often quite difficult and usual debugging techniques often do not apply and, when they do, they are not very effective. This work presents a mechanism based on event logs annotated with contextual information, allowing visualization tools to organize events according to the context of interest for the system operator. We applied this mechanism to a real system and its the effort and cost to detect and diagnose the cause of problems was dramatically reduced.","PeriodicalId":286943,"journal":{"name":"2012 26th Brazilian Symposium on Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130843799","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}
Iuri Santos Souza, R. Oliveira, G. Gomes, E. Almeida
Manage the evolution in Software Product Lines (SPL) can bring some benefits such as keep the trace ability between assets in core assets and products, avoid some irregular growth or decrease before it becomes a threat to the system, and also use the products feedback to improve the core asset quality. In order to understand the evolution in SPL, this paper presents an empirical study to investigate evidence between information from features non-conformities and data from corrective maintenance, based on an SPL industrial project in the medical domain. The investigation aims at tracking the features non-conformities and their likely root causes using results from two preliminary studies. The first one captured and classified the features non-conformities from features specification of nine sub-domains and the second one investigated the evolution of SPL assets along the sub-domains development. The study sample was analyzed using statistical techniques, such as Spearman correlation rank and Poisson regression models. The findings indicated that there is significant positive correlation between feature non-conformities and corrective maintenance. Sub-domains with a high number of feature non-conformities had a higher number of corrective maintenance. Moreover, sub-domains qualified as high risk have also positive correlation with corrective maintenance. This correlation allows the building of predictive models to estimate corrective maintenance based on the risk sub-domain attribute values.
{"title":"On the Relationship between Inspection and Evolution in Software Product Lines: An Exploratory Study","authors":"Iuri Santos Souza, R. Oliveira, G. Gomes, E. Almeida","doi":"10.1109/SBES.2012.18","DOIUrl":"https://doi.org/10.1109/SBES.2012.18","url":null,"abstract":"Manage the evolution in Software Product Lines (SPL) can bring some benefits such as keep the trace ability between assets in core assets and products, avoid some irregular growth or decrease before it becomes a threat to the system, and also use the products feedback to improve the core asset quality. In order to understand the evolution in SPL, this paper presents an empirical study to investigate evidence between information from features non-conformities and data from corrective maintenance, based on an SPL industrial project in the medical domain. The investigation aims at tracking the features non-conformities and their likely root causes using results from two preliminary studies. The first one captured and classified the features non-conformities from features specification of nine sub-domains and the second one investigated the evolution of SPL assets along the sub-domains development. The study sample was analyzed using statistical techniques, such as Spearman correlation rank and Poisson regression models. The findings indicated that there is significant positive correlation between feature non-conformities and corrective maintenance. Sub-domains with a high number of feature non-conformities had a higher number of corrective maintenance. Moreover, sub-domains qualified as high risk have also positive correlation with corrective maintenance. This correlation allows the building of predictive models to estimate corrective maintenance based on the risk sub-domain attribute values.","PeriodicalId":286943,"journal":{"name":"2012 26th Brazilian Symposium on Software Engineering","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125036521","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}
André Di Thommazo, Gabriel Malimpensa, T. R. Oliveira, Guilherme Olivatto, S. Fabbri
Background: Requirements management is considered one of the activities responsible for system failures. The difficulty regarding to requirements trace ability makes the system changes hard to be managed. Objective: This paper presents two approaches that allow the automated generation of the Requirements Trace ability Matrix (RTM): the RTM-E approach, which is based on the requirement input data, and the RTM-NLP approach, which is based on Natural Language Processing-NLP. Method: The RTM-E comprises the requirements dependency related to the data manipulated by them, while the RTM-NLP comprises the requirements dependency related to the similarities of their functionality descriptions. The results are shown through visualization of information in order to facilitate the understanding of such dependencies. Results: We conducted an experimental study in which both approaches were applied to 18 requirements documents. The RTMs created automatically were compared with the reference RTM created manually based on the stakeholders knowledge. Comparing the generated matrices, it was seen that the RTM-E on average matches 82% to the reference RTM, while the RTM-NLP approach on average matches 53%. Conclusions: The results show that generating the RTM based on these approaches, the effectiveness on determining the requirements dependences is satisfactory and motivates to keep studying in order to make improvements for both approaches.
{"title":"Requirements Traceability Matrix: Automatic Generation and Visualization","authors":"André Di Thommazo, Gabriel Malimpensa, T. R. Oliveira, Guilherme Olivatto, S. Fabbri","doi":"10.1109/SBES.2012.29","DOIUrl":"https://doi.org/10.1109/SBES.2012.29","url":null,"abstract":"Background: Requirements management is considered one of the activities responsible for system failures. The difficulty regarding to requirements trace ability makes the system changes hard to be managed. Objective: This paper presents two approaches that allow the automated generation of the Requirements Trace ability Matrix (RTM): the RTM-E approach, which is based on the requirement input data, and the RTM-NLP approach, which is based on Natural Language Processing-NLP. Method: The RTM-E comprises the requirements dependency related to the data manipulated by them, while the RTM-NLP comprises the requirements dependency related to the similarities of their functionality descriptions. The results are shown through visualization of information in order to facilitate the understanding of such dependencies. Results: We conducted an experimental study in which both approaches were applied to 18 requirements documents. The RTMs created automatically were compared with the reference RTM created manually based on the stakeholders knowledge. Comparing the generated matrices, it was seen that the RTM-E on average matches 82% to the reference RTM, while the RTM-NLP approach on average matches 53%. Conclusions: The results show that generating the RTM based on these approaches, the effectiveness on determining the requirements dependences is satisfactory and motivates to keep studying in order to make improvements for both approaches.","PeriodicalId":286943,"journal":{"name":"2012 26th Brazilian Symposium on Software Engineering","volume":"37 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116960013","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Software developers have difficulties in implementing exception handling code in their systems. In particular, they fail in implementing appropriate handling actions. Not surprisingly, recurring failures and performance issues are often related to the poor exception handling actions implemented in real software systems. In this paper we propose, implement and evaluate a set of three heuristic strategies used to recommend exception handling code in programming tasks. Given a method in which the developer wants to handle an exception, the heuristics recommend a list of code fragments implementing exception handling. The heuristics' goal is to accurately find code fragments implementing exception handling and recommend these fragments according to the context of developers' implementation task. Hence, the proposed heuristics may assist developers in the process of discovering exception handling actions relevant to their context by providing concrete examples. We believe that a recommender system based on the proposed heuristics may be used in the future as a tool for aiding exception handling implementation.
{"title":"Heuristic Strategies for Recommendation of Exception Handling Code","authors":"E. Barbosa, Alessandro F. Garcia, M. Mezini","doi":"10.1109/SBES.2012.22","DOIUrl":"https://doi.org/10.1109/SBES.2012.22","url":null,"abstract":"Software developers have difficulties in implementing exception handling code in their systems. In particular, they fail in implementing appropriate handling actions. Not surprisingly, recurring failures and performance issues are often related to the poor exception handling actions implemented in real software systems. In this paper we propose, implement and evaluate a set of three heuristic strategies used to recommend exception handling code in programming tasks. Given a method in which the developer wants to handle an exception, the heuristics recommend a list of code fragments implementing exception handling. The heuristics' goal is to accurately find code fragments implementing exception handling and recommend these fragments according to the context of developers' implementation task. Hence, the proposed heuristics may assist developers in the process of discovering exception handling actions relevant to their context by providing concrete examples. We believe that a recommender system based on the proposed heuristics may be used in the future as a tool for aiding exception handling implementation.","PeriodicalId":286943,"journal":{"name":"2012 26th Brazilian Symposium on Software Engineering","volume":"51 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124427073","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}
Fellipe Araújo Aleixo, M. Freire, D. A. D. Costa, Edmilson Campos Neto, U. Kulesza
This paper presents a comparative study of compositional and annotative modeling approaches for software process lines. In our comparative study, Open UP and Scrum based software process lines extracted from existing projects are modeled and implemented using an existing compositional approach -- EPF Composer, and an annotative approach -- GenArch-P, with the main aim to address a systematic variability management and automatic process derivation. In order to promote the analysis of the approaches were adapted some comparison criteria previously adopted in other studies. Our study results show that the annotative approach can bring many advantages to the modeling of software process lines considering our comparison criteria. On the other hand, our study also concludes that many existing compositional mechanisms should also be integrated with annotative approaches in order to improve the modularity of process elements associated to specific kinds of process variabilities.
{"title":"A Comparative Study of Compositional and Annotative Modelling Approaches for Software Process Lines","authors":"Fellipe Araújo Aleixo, M. Freire, D. A. D. Costa, Edmilson Campos Neto, U. Kulesza","doi":"10.1109/SBES.2012.11","DOIUrl":"https://doi.org/10.1109/SBES.2012.11","url":null,"abstract":"This paper presents a comparative study of compositional and annotative modeling approaches for software process lines. In our comparative study, Open UP and Scrum based software process lines extracted from existing projects are modeled and implemented using an existing compositional approach -- EPF Composer, and an annotative approach -- GenArch-P, with the main aim to address a systematic variability management and automatic process derivation. In order to promote the analysis of the approaches were adapted some comparison criteria previously adopted in other studies. Our study results show that the annotative approach can bring many advantages to the modeling of software process lines considering our comparison criteria. On the other hand, our study also concludes that many existing compositional mechanisms should also be integrated with annotative approaches in order to improve the modularity of process elements associated to specific kinds of process variabilities.","PeriodicalId":286943,"journal":{"name":"2012 26th Brazilian Symposium on Software Engineering","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124230422","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}
K. Ferreira, Roberta Coeli Neves Moreira, Mariza Bigonha, R. Bigonha
The dependence among modules in a software system usually is represented as a network, in which the nodes are the modules, and the edges are the connections between the modules. The relationships among modules in software systems are hard to assess, especially in large programs. Knowing the nature of the software system structures is very important to improve maintenance tasks and other challenging tasks in software development. A previous work of the authors of this paper has defined a model to the topology of software networks, named Little House. This model is a generic macroscopic view of software systems, and it is an adaptation of the well-known Bow-tie model. According to Little House, a software network can be partitioned into six components, in such a way there is a special pattern of connections among them. This paper describes the results of a quantitative evaluation of Little House. The aim of this work is to investigate whether the components of Little House can be described by any pattern of software metric values. The results of this evaluation indicate that in the software systems developed currently there are two main components of Little House that have critical values of metrics. This finding suggests that classes from those components should be carefully considered when maintenance tasks are performed in the program.
{"title":"A Generic Macroscopic Topology of Software Networks - A Quantitative Evaluation","authors":"K. Ferreira, Roberta Coeli Neves Moreira, Mariza Bigonha, R. Bigonha","doi":"10.1109/SBES.2012.26","DOIUrl":"https://doi.org/10.1109/SBES.2012.26","url":null,"abstract":"The dependence among modules in a software system usually is represented as a network, in which the nodes are the modules, and the edges are the connections between the modules. The relationships among modules in software systems are hard to assess, especially in large programs. Knowing the nature of the software system structures is very important to improve maintenance tasks and other challenging tasks in software development. A previous work of the authors of this paper has defined a model to the topology of software networks, named Little House. This model is a generic macroscopic view of software systems, and it is an adaptation of the well-known Bow-tie model. According to Little House, a software network can be partitioned into six components, in such a way there is a special pattern of connections among them. This paper describes the results of a quantitative evaluation of Little House. The aim of this work is to investigate whether the components of Little House can be described by any pattern of software metric values. The results of this evaluation indicate that in the software systems developed currently there are two main components of Little House that have critical values of metrics. This finding suggests that classes from those components should be carefully considered when maintenance tasks are performed in the program.","PeriodicalId":286943,"journal":{"name":"2012 26th Brazilian Symposium on Software Engineering","volume":"120 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134523137","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}
J. E. T. Herrera, Isela Macia Bertran, P. Salas, R. Pinho, Ronald Vargas, Alessandro F. Garcia, J. Araújo, K. Breitman
It is well-known that effective requirements analysis plays a crucial role in the quality of software systems. However, the scattered and tangled nature of certain system's concerns can hinder the proper understanding and treatment of import requirements. A key goal of prominent Aspect-Oriented Requirement Engineering (AORE) techniques, such as EA-Miner and Theme/Doc, is to support the automatic identification of crosscutting concerns at textual requirements documents. However, it is still unknown whether and which of these approaches produce accurate results in large text documents and according to the software engineers' expectations. In this context, this paper presents an analysis regarding the accuracy of the aforementioned AORE approaches when processing requirements of two industry software systems. Around 300 pages of requirements descriptions in these systems were the target of our investigation. In general, EA-Miner suffered more than Theme/Doc from the incompleteness and inconsistencies of requirements documents. In addition, other factors can differently influence each approach's accuracy, such as: the participation of requirements engineers, and the level of details provided in the requirements document.
{"title":"Revealing Crosscutting Concerns in Textual Requirements Documents: An Exploratory Study with Industry Systems","authors":"J. E. T. Herrera, Isela Macia Bertran, P. Salas, R. Pinho, Ronald Vargas, Alessandro F. Garcia, J. Araújo, K. Breitman","doi":"10.1109/SBES.2012.10","DOIUrl":"https://doi.org/10.1109/SBES.2012.10","url":null,"abstract":"It is well-known that effective requirements analysis plays a crucial role in the quality of software systems. However, the scattered and tangled nature of certain system's concerns can hinder the proper understanding and treatment of import requirements. A key goal of prominent Aspect-Oriented Requirement Engineering (AORE) techniques, such as EA-Miner and Theme/Doc, is to support the automatic identification of crosscutting concerns at textual requirements documents. However, it is still unknown whether and which of these approaches produce accurate results in large text documents and according to the software engineers' expectations. In this context, this paper presents an analysis regarding the accuracy of the aforementioned AORE approaches when processing requirements of two industry software systems. Around 300 pages of requirements descriptions in these systems were the target of our investigation. In general, EA-Miner suffered more than Theme/Doc from the incompleteness and inconsistencies of requirements documents. In addition, other factors can differently influence each approach's accuracy, such as: the participation of requirements engineers, and the level of details provided in the requirements document.","PeriodicalId":286943,"journal":{"name":"2012 26th Brazilian Symposium on Software Engineering","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134639672","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}
Research on motivation has made important contributions for the software engineering practice, but it has mostly adopted quantitative approaches, towards generalizable statements. However, given the complexity of the human behavior, motivation seems to be affected by diverse environmental conditions, and to be moderated by individual and organizational characteristics. Therefore, contextualized and explanatory theories are needed to account for this diversity. This research presents a grounded theory aimed at describing and explaining the motivation of software engineers in the context of a small private software company, in Recife, Brazil. Semi structured interviews were carried out over four months, and data were analyzed using grounded theory procedures. As a result, we present statements that connect, relate, and make sense of contextual factors, describing the central story of motivation in the company. In this case study, learning and growth needs emerged as the strongest drivers of motivation, which in turn increase the goal commitment of engineers and create the conditions for better job performance.
{"title":"Towards an Explanatory Theory of Motivation in Software Engineering: A Qualitative Case Study of a Small Software Company","authors":"A. C. A. França, David E. S. Carneiro, F. Silva","doi":"10.1109/SBES.2012.28","DOIUrl":"https://doi.org/10.1109/SBES.2012.28","url":null,"abstract":"Research on motivation has made important contributions for the software engineering practice, but it has mostly adopted quantitative approaches, towards generalizable statements. However, given the complexity of the human behavior, motivation seems to be affected by diverse environmental conditions, and to be moderated by individual and organizational characteristics. Therefore, contextualized and explanatory theories are needed to account for this diversity. This research presents a grounded theory aimed at describing and explaining the motivation of software engineers in the context of a small private software company, in Recife, Brazil. Semi structured interviews were carried out over four months, and data were analyzed using grounded theory procedures. As a result, we present statements that connect, relate, and make sense of contextual factors, describing the central story of motivation in the company. In this case study, learning and growth needs emerged as the strongest drivers of motivation, which in turn increase the goal commitment of engineers and create the conditions for better job performance.","PeriodicalId":286943,"journal":{"name":"2012 26th Brazilian Symposium on Software Engineering","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2012-09-23","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132137837","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
扫码关注我们
求助内容：
应助结果提醒方式：