Fabian Fagerholm, Arto Hellas, Matti Luukkainen, K. Kyllonen, S. Yaman, Hanna Mäenpää
Today's students are prospective entrepreneurs and employees in modern, start-up like environments within established companies. In these settings, software development projects face extreme requirements in terms of innovation and attractiveness of the end-product. They also suffer severe consequences of failure such as termination of the development effort and bankruptcy. As the abilities needed in start-ups are not among those traditionally taught in universities, new knowledge and skills are required to prepare students for the volatile environment that new market entrants face. This paper reports experiences gained during seven years of teaching start-up knowledge and skills in a higher-education institution. We offer a collection of patterns that help educational institutions to design, implement and operate physical environments, curricula and teaching materials, and to plan interventions that may be required for project-based start-up education.
{"title":"Patterns for Designing and Implementing an Environment for Software Start-Up Education","authors":"Fabian Fagerholm, Arto Hellas, Matti Luukkainen, K. Kyllonen, S. Yaman, Hanna Mäenpää","doi":"10.1109/SEAA.2017.67","DOIUrl":"https://doi.org/10.1109/SEAA.2017.67","url":null,"abstract":"Today's students are prospective entrepreneurs and employees in modern, start-up like environments within established companies. In these settings, software development projects face extreme requirements in terms of innovation and attractiveness of the end-product. They also suffer severe consequences of failure such as termination of the development effort and bankruptcy. As the abilities needed in start-ups are not among those traditionally taught in universities, new knowledge and skills are required to prepare students for the volatile environment that new market entrants face. This paper reports experiences gained during seven years of teaching start-up knowledge and skills in a higher-education institution. We offer a collection of patterns that help educational institutions to design, implement and operate physical environments, curricula and teaching materials, and to plan interventions that may be required for project-based start-up education.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-09-28","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129909051","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}
Agile software development approaches have emerged to overcome the inherent challenges of the traditional software development methodologies. With that in mind, they offer a set of simple yet effective practices based on the values and supporting principles of the Agile Manifesto. Today, more and more organizations are practicing Agile but transitioning to Agile is not as straightforward as it might seem. The benefits afforded by the agile values, principles and practices are not fully obtained and adapters struggle to become more mature; i.e. increase their Agility. For, adapters to address this problem, agility assessments have been designed to be aware of the situation of their transition and make sure that they are heading in the right direction. However, these assessments still require significant amount of time and effort to apply. To overcome this problem, we have developed a web-based agility assessment tool which is a part of an integrated agility assessment approach. The approach consists of a structured and comprehensive agility assessment model (AgilityMod), an exemplar agility assessment process and a web based agility assessment tool (AssessAgility). This research focuses on the final component of the approach: AssessAgility tool and presents a multiple case study that was conducted to evaluate tool's capabilities in terms of providing guidance, automation and reducing the effort spent on the assessments.
{"title":"Assessment of Agility in Software Organizations with a Web-Based Agility Assessment Tool","authors":"O. E. Adali, Özden Özcan Top, Onur Demirörs","doi":"10.1109/SEAA.2017.61","DOIUrl":"https://doi.org/10.1109/SEAA.2017.61","url":null,"abstract":"Agile software development approaches have emerged to overcome the inherent challenges of the traditional software development methodologies. With that in mind, they offer a set of simple yet effective practices based on the values and supporting principles of the Agile Manifesto. Today, more and more organizations are practicing Agile but transitioning to Agile is not as straightforward as it might seem. The benefits afforded by the agile values, principles and practices are not fully obtained and adapters struggle to become more mature; i.e. increase their Agility. For, adapters to address this problem, agility assessments have been designed to be aware of the situation of their transition and make sure that they are heading in the right direction. However, these assessments still require significant amount of time and effort to apply. To overcome this problem, we have developed a web-based agility assessment tool which is a part of an integrated agility assessment approach. The approach consists of a structured and comprehensive agility assessment model (AgilityMod), an exemplar agility assessment process and a web based agility assessment tool (AssessAgility). This research focuses on the final component of the approach: AssessAgility tool and presents a multiple case study that was conducted to evaluate tool's capabilities in terms of providing guidance, automation and reducing the effort spent on the assessments.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"57 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-09-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125758011","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 : 2017-09-01DOI: 10.1109/SEAA.2017.8114695
Daniel Ståhl, Torvald Mårtensson, J. Bosch
DevOps and continuous practices are attracting steadily growing attention by both practitioners and researchers in the software engineering community. The terms are often used inconsistently, interchangeably and with unclear meaning, however. Taking the position that this ambiguity and miscommunication renders the community great harm, in that it impedes our ability to critically appraise these practices, their effects and interplay between them, we analyze how published literature on both continuous practices and DevOps treat the terms. Based on this analysis, along with statements by often cited sources in the community as well as personal experience from researching and practicing these concepts, we propose guidelines to help authors reduce ambiguity in their publications. Additionally, definitions designed to reflect mainstream interpretation while disentangling the terms from one another are presented.
{"title":"Continuous practices and devops: beyond the buzz, what does it all mean?","authors":"Daniel Ståhl, Torvald Mårtensson, J. Bosch","doi":"10.1109/SEAA.2017.8114695","DOIUrl":"https://doi.org/10.1109/SEAA.2017.8114695","url":null,"abstract":"DevOps and continuous practices are attracting steadily growing attention by both practitioners and researchers in the software engineering community. The terms are often used inconsistently, interchangeably and with unclear meaning, however. Taking the position that this ambiguity and miscommunication renders the community great harm, in that it impedes our ability to critically appraise these practices, their effects and interplay between them, we analyze how published literature on both continuous practices and DevOps treat the terms. Based on this analysis, along with statements by often cited sources in the community as well as personal experience from researching and practicing these concepts, we propose guidelines to help authors reduce ambiguity in their publications. Additionally, definitions designed to reflect mainstream interpretation while disentangling the terms from one another are presented.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"50 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124464457","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
the increasing desire by many for a better world and easier living conditions have contributed to various efforts to the frontiers of innovation in information technology (IT). The ensuing phenomena is the launch of many software startups to give meaning to such innovations in IT. Interestingly, the rate at which many of such startups fail is usually higher than expected. A collaborative effort by actors in IT innovation ecosystem has been posited to lead to a successful startup. However, there is the need for a trust model to ensure that the collaborative effort become meaningful. Through the lens of Morgan and Hunt's commitment trust theory, this study examines the antecedents of trust among actors in successful software startup. The paper proposes "Startup Trust Model" and contributes to understanding of formation and maintenance of trust in software startups and makes a case for the study of trust in software startup
{"title":"Startup Trust Model: The Role of Trust in Successful Software Startup","authors":"Nana Assyne, J. Adjei","doi":"10.1109/SEAA.2017.46","DOIUrl":"https://doi.org/10.1109/SEAA.2017.46","url":null,"abstract":"the increasing desire by many for a better world and easier living conditions have contributed to various efforts to the frontiers of innovation in information technology (IT). The ensuing phenomena is the launch of many software startups to give meaning to such innovations in IT. Interestingly, the rate at which many of such startups fail is usually higher than expected. A collaborative effort by actors in IT innovation ecosystem has been posited to lead to a successful startup. However, there is the need for a trust model to ensure that the collaborative effort become meaningful. Through the lens of Morgan and Hunt's commitment trust theory, this study examines the antecedents of trust among actors in successful software startup. The paper proposes \"Startup Trust Model\" and contributes to understanding of formation and maintenance of trust in software startups and makes a case for the study of trust in software startup","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"114 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117212168","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 refactoring aims at optimizing software modularization by improving internal software structure without altering its external behavior. There exists various approaches for suggesting refactoring opportunities, based on different sources of information, e.g., structural, semantic, and historical. In this paper, we propose a data fusion model to combine different sources of information in order to identify refactoring opportunities and we instantiate it to support Move Class refactoring. We report the results of our validation conducted on four software systems and we show that our proposal improves the modularization quality by 29% and that our tool is able to provide meaningful recommendations for move class refactoring. Specifically, more than 70% of the recommendations were considered meaningful from the developers' point of view.
{"title":"Data Fusion for Software Remodularization","authors":"Rim Mahouachi, K. Ghédira","doi":"10.1109/SEAA.2017.18","DOIUrl":"https://doi.org/10.1109/SEAA.2017.18","url":null,"abstract":"Software refactoring aims at optimizing software modularization by improving internal software structure without altering its external behavior. There exists various approaches for suggesting refactoring opportunities, based on different sources of information, e.g., structural, semantic, and historical. In this paper, we propose a data fusion model to combine different sources of information in order to identify refactoring opportunities and we instantiate it to support Move Class refactoring. We report the results of our validation conducted on four software systems and we show that our proposal improves the modularization quality by 29% and that our tool is able to provide meaningful recommendations for move class refactoring. Specifically, more than 70% of the recommendations were considered meaningful from the developers' point of view.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"198 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127316209","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 paper we analyze at the class level the quality of the software portions including classes participating in design patterns instances (DP classes) with respect to the remaining software portions (NoDP classes). The performed study is based on 10 software systems from which information about design pattern instances and CK (Chidamber and Kemerer) metrics were obtained by exploiting repositories of pattern instances and the tool Understand, respectively. The analysis revealed that the use of design patterns impacts on the quality of the software.
{"title":"How the Use of Design Patterns Affects the Quality of Software Systems: A Preliminary Investigation","authors":"C. Gravino, M. Risi","doi":"10.1109/SEAA.2017.32","DOIUrl":"https://doi.org/10.1109/SEAA.2017.32","url":null,"abstract":"In this paper we analyze at the class level the quality of the software portions including classes participating in design patterns instances (DP classes) with respect to the remaining software portions (NoDP classes). The performed study is based on 10 software systems from which information about design pattern instances and CK (Chidamber and Kemerer) metrics were obtained by exploiting repositories of pattern instances and the tool Understand, respectively. The analysis revealed that the use of design patterns impacts on the quality of the software.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122512410","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
A key challenge in cyber-physical systems is their highly dynamic nature including changing system goals. Therefore, these systems have to autonomously manage their system goals and continuously evaluate their achievement at run-time. However, with the increasing complexity of system goals including, e.g., priorities, dependencies, and conflicts among goals, abinary or qualitative judgement of achievement of goals is not sufficient any more. Instead, it is necessary to quantify the degree to which the goals are fulfilled in order to balance the cost-benefit ratio at run-time. In this paper, we present a hierarchical and modular goal model that allows for capturing complex relations between subgoals, e.g., dependencies and conflicts. We provide an algorithm that efficiently evaluates gradual achievement of goalsat run-time. Due to the modular structure of our model and our evaluation, goals can easily be added, removed, and changed at run-time. With our approach, we a) ease the design of goal-aware autonomous systems by providing an explicit structure that emphasises relations between subgoals, b) provide an automatic quantification of the satisfaction of complex system goals that can be used to, e.g., evaluate autonomous decisions at runtime, andc) enable runtime management of changing system goals.
{"title":"Runtime Management and Quantitative Evaluation of Changing System Goals","authors":"V. Klös, Thomas Göthel, Adrian Lohr, S. Glesner","doi":"10.1109/SEAA.2017.66","DOIUrl":"https://doi.org/10.1109/SEAA.2017.66","url":null,"abstract":"A key challenge in cyber-physical systems is their highly dynamic nature including changing system goals. Therefore, these systems have to autonomously manage their system goals and continuously evaluate their achievement at run-time. However, with the increasing complexity of system goals including, e.g., priorities, dependencies, and conflicts among goals, abinary or qualitative judgement of achievement of goals is not sufficient any more. Instead, it is necessary to quantify the degree to which the goals are fulfilled in order to balance the cost-benefit ratio at run-time. In this paper, we present a hierarchical and modular goal model that allows for capturing complex relations between subgoals, e.g., dependencies and conflicts. We provide an algorithm that efficiently evaluates gradual achievement of goalsat run-time. Due to the modular structure of our model and our evaluation, goals can easily be added, removed, and changed at run-time. With our approach, we a) ease the design of goal-aware autonomous systems by providing an explicit structure that emphasises relations between subgoals, b) provide an automatic quantification of the satisfaction of complex system goals that can be used to, e.g., evaluate autonomous decisions at runtime, andc) enable runtime management of changing system goals.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"77 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"122906397","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}
Usman Rafiq, Sohaib Shahid Bajwa, Xiaofeng Wang, M. I. Lunesu
Requirements elicitation is the first crucial stage of a requirements engineering process, which intends to uncover, acquire and elaborate requirements for software systems. When software startups are concerned, requirements elicitation is particularly challenging due to the high uncertainty that a startup is confronted with. Few studies have investigated how software startups conduct requirements elicitation and what techniques are used in such a context. This study intends to address this knowledge gap. Three software startups from different part of the globe were studied. The findings reveal that the requirements elicitation process in startups is primordial and mainly informal, and it is an ongoing process alongside with product evolution. Software startups do employ established requirements elicitation techniques including interviews, prototyping and brainstorming. They also utilize other less common ones such as competitor analysis, collaborative team discussion and use of model users. This study highlights the market-driven nature of requirements that software startups have to deal with, and offers the first insights on the requirements elicitation techniques that could be relevant and applicable in the context of software startups.
{"title":"Requirements Elicitation Techniques Applied in Software Startups","authors":"Usman Rafiq, Sohaib Shahid Bajwa, Xiaofeng Wang, M. I. Lunesu","doi":"10.1109/SEAA.2017.73","DOIUrl":"https://doi.org/10.1109/SEAA.2017.73","url":null,"abstract":"Requirements elicitation is the first crucial stage of a requirements engineering process, which intends to uncover, acquire and elaborate requirements for software systems. When software startups are concerned, requirements elicitation is particularly challenging due to the high uncertainty that a startup is confronted with. Few studies have investigated how software startups conduct requirements elicitation and what techniques are used in such a context. This study intends to address this knowledge gap. Three software startups from different part of the globe were studied. The findings reveal that the requirements elicitation process in startups is primordial and mainly informal, and it is an ongoing process alongside with product evolution. Software startups do employ established requirements elicitation techniques including interviews, prototyping and brainstorming. They also utilize other less common ones such as competitor analysis, collaborative team discussion and use of model users. This study highlights the market-driven nature of requirements that software startups have to deal with, and offers the first insights on the requirements elicitation techniques that could be relevant and applicable in the context of software startups.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"44 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127869095","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}
Agile software development and formal methods are seemingly on the opposite ends of the rigorousness scale. If carefully used, the can efficiently function in synergy to provide an evolutionary, iterative and tailorable process for a correct-by-construction system. In this work, we present the use of agile and formal methods in the academic context at the project course. We describe the development of the meeting scheduler – a web application, which utilised the Event-B formal method and the Vaadin framework within the Scrum development process. Our contribution includes remarks and advice for student projects regarding (i) the use of Scrum and (ii) the application of formal methods in "traditional" software development. We believe that results can be to some extent transferred to an industrial setting, where learning new technologies is involved within agile development processes.
{"title":"To Agile or not to Agile Students (With a Twist): Experience Report from a Student Project Course","authors":"Marta Olszewska, S. Ostroumov, M. Olszewski","doi":"10.1109/SEAA.2017.54","DOIUrl":"https://doi.org/10.1109/SEAA.2017.54","url":null,"abstract":"Agile software development and formal methods are seemingly on the opposite ends of the rigorousness scale. If carefully used, the can efficiently function in synergy to provide an evolutionary, iterative and tailorable process for a correct-by-construction system. In this work, we present the use of agile and formal methods in the academic context at the project course. We describe the development of the meeting scheduler – a web application, which utilised the Event-B formal method and the Vaadin framework within the Scrum development process. Our contribution includes remarks and advice for student projects regarding (i) the use of Scrum and (ii) the application of formal methods in \"traditional\" software development. We believe that results can be to some extent transferred to an industrial setting, where learning new technologies is involved within agile development processes.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"19 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124364323","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Nowadays, there are many embedded systems with different architectures that have incorporated GPUs. However, it is difficult to develop CPU-GPU embedded systems using component-based development (CBD), since existing CBD approaches have no support for GPU development. In this context, when targeting a particular CPU-GPU platform, the component developer is forced to construct hardware-specific components, which are problematic to (re-)use in different contexts. Moreover, hard-coding specific GPU-usage characteristics (e.g., the number of utilized GPU threads) inside the component is not possible without making detailed assumptions about the system in which the component is used, which conflicts with separation-of-concerns CBD principle.The paper presents a solution to allow component-based development of platform-agnostic CPU-GPU embedded systems through: i) high-level API, ii) adapters, and iii) code template. The API abstracts the specifics of the different platforms, while the adapters externalize hardware-specific activities outside components. We also raise the decision regarding the GPU-usage specifications, from the component to the system level. Furthermore, to minimize the development effort, we provide a code template that contains ready-made code fragments required for GPU development. As a case study, we examine the feasibility of our solution applied on a component-based vision system of an underwater robot.
{"title":"Developing CPU-GPU Embedded Systems Using Platform-Agnostic Components","authors":"G. Campeanu, Jan Carlson, Séverine Sentilles","doi":"10.1109/SEAA.2017.20","DOIUrl":"https://doi.org/10.1109/SEAA.2017.20","url":null,"abstract":"Nowadays, there are many embedded systems with different architectures that have incorporated GPUs. However, it is difficult to develop CPU-GPU embedded systems using component-based development (CBD), since existing CBD approaches have no support for GPU development. In this context, when targeting a particular CPU-GPU platform, the component developer is forced to construct hardware-specific components, which are problematic to (re-)use in different contexts. Moreover, hard-coding specific GPU-usage characteristics (e.g., the number of utilized GPU threads) inside the component is not possible without making detailed assumptions about the system in which the component is used, which conflicts with separation-of-concerns CBD principle.The paper presents a solution to allow component-based development of platform-agnostic CPU-GPU embedded systems through: i) high-level API, ii) adapters, and iii) code template. The API abstracts the specifics of the different platforms, while the adapters externalize hardware-specific activities outside components. We also raise the decision regarding the GPU-usage specifications, from the component to the system level. Furthermore, to minimize the development effort, we provide a code template that contains ready-made code fragments required for GPU development. As a case study, we examine the feasibility of our solution applied on a component-based vision system of an underwater robot.","PeriodicalId":151513,"journal":{"name":"2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA)","volume":"107 3 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2017-08-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130478751","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
扫码关注我们
求助内容：
应助结果提醒方式：