Participatory Sensing is a new paradigm that empowers non-professional citizens to collect and share sensory data from their surrounding environments using their mobile phones. The emergence of the participatory sensing has resulted in a broad range of novel participatory sensing applications (PSA). PSA are more suitable to be developed by the people who want to launch the campaign, rather than the professional software developer. However, the development of PSA requires complex programming skill, and thus only professionals can build them. Inspired by the concept of end-user programming, this paper develops a tool, named PSAFactory, for non-professional people who do not understand the programming techniques to develop their own PSA in a quick and simple way. With this tool, non-professionals can build PSA by just doing some simple settings, while the tool will run automatically to tackle common issues in a completely transparent manner. Besides, two prototype applications are developed with the tool.
{"title":"PSAFactory: An End-User Programming Tool for Building Participatory Sensing Applications","authors":"Jiangtao Wang, Yasha Wang, Hao Wang","doi":"10.1109/ICGSEW.2014.8","DOIUrl":"https://doi.org/10.1109/ICGSEW.2014.8","url":null,"abstract":"Participatory Sensing is a new paradigm that empowers non-professional citizens to collect and share sensory data from their surrounding environments using their mobile phones. The emergence of the participatory sensing has resulted in a broad range of novel participatory sensing applications (PSA). PSA are more suitable to be developed by the people who want to launch the campaign, rather than the professional software developer. However, the development of PSA requires complex programming skill, and thus only professionals can build them. Inspired by the concept of end-user programming, this paper develops a tool, named PSAFactory, for non-professional people who do not understand the programming techniques to develop their own PSA in a quick and simple way. With this tool, non-professionals can build PSA by just doing some simple settings, while the tool will run automatically to tackle common issues in a completely transparent manner. Besides, two prototype applications are developed with the tool.","PeriodicalId":396979,"journal":{"name":"2014 IEEE International Conference on Global Software Engineeering Workshops","volume":"PP 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2014-08-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126428800","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. Noll, A. Butterfield, Kevin Farrell, Tom Mason, Miles McGuire, Ross McKinley
Context: Software development is often characterised as a "wicked problem" due to changing requirements and the realization that the problem to be solved is not really understood until a solution is created. global software development (GSD) introduces a host of additional complexities to software development as a result of global distance (geographic separation, timezone differences, and language and cultural gaps). Problem: A common approach to teaching software engineering concepts is to have students form teams to create a software product, this allow them to experience the problems first hand. However, this approach is much more difficult for GSD, due to the need to have distributed project teams. Approach: We developed a serious game, called "GSD Sim", that allows players to manage a globally distributed software project. Players allocate teams of programmers to different locations around the world, and assign these teams to develop modules that comprise the software product. A simulator generates events, such as integration failures or requirements misunderstandings that cause project delays, players can make tactical and strategic interventions to address and prevent adverse events. Result: GSD Sim allows students to experience the difficulties involved in GSD from a project manager's point of view, in a much shorter time and at lower cost than a real global software development project. The game is also entertaining in its own right. Conclusion: GSD Sim has the potential to reinforce conceptual instruction with hands-on learning at a fraction of the time and cost that would be required to run a true distributed software project.
{"title":"GSD Sim: A Global Software Development Game","authors":"J. Noll, A. Butterfield, Kevin Farrell, Tom Mason, Miles McGuire, Ross McKinley","doi":"10.1109/ICGSEW.2014.12","DOIUrl":"https://doi.org/10.1109/ICGSEW.2014.12","url":null,"abstract":"Context: Software development is often characterised as a \"wicked problem\" due to changing requirements and the realization that the problem to be solved is not really understood until a solution is created. global software development (GSD) introduces a host of additional complexities to software development as a result of global distance (geographic separation, timezone differences, and language and cultural gaps). Problem: A common approach to teaching software engineering concepts is to have students form teams to create a software product, this allow them to experience the problems first hand. However, this approach is much more difficult for GSD, due to the need to have distributed project teams. Approach: We developed a serious game, called \"GSD Sim\", that allows players to manage a globally distributed software project. Players allocate teams of programmers to different locations around the world, and assign these teams to develop modules that comprise the software product. A simulator generates events, such as integration failures or requirements misunderstandings that cause project delays, players can make tactical and strategic interventions to address and prevent adverse events. Result: GSD Sim allows students to experience the difficulties involved in GSD from a project manager's point of view, in a much shorter time and at lower cost than a real global software development project. The game is also entertaining in its own right. Conclusion: GSD Sim has the potential to reinforce conceptual instruction with hands-on learning at a fraction of the time and cost that would be required to run a true distributed software project.","PeriodicalId":396979,"journal":{"name":"2014 IEEE International Conference on Global Software Engineeering Workshops","volume":"26 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2014-08-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115758705","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}
Global in-house software development centers of multinational companies in India need to grow to continue attracting talent. For mature centers, to grow sustainably is a challenge, because it involves these centers steadily taking on global roles for product lifecycle activities. A precondition for this is creating within team members a global mindset coupled with awareness of quality of the entire product, extending beyond the quality of a product's components. Therefore, it's necessary for the center to establish a culture for increased quality awareness so as to demonstrate quality orientation for global products. We outline how our 4 C approach, which balances culture, content, career, and compensation -- the 4 Cs, effectively enabled this cultural transformation at an in-house software development center of Siemens, a German multinational company. As part of the 4 C approach we rolled out initiatives to create quality awareness, and intensified training on software engineering, technical expertise, domain knowhow, and behavioral skills to ensure teams possess required competences and the required mindset. We also defined tool-assisted processes and workflows aimed at making code quality a habit.
{"title":"Establishing a Culture for Increased Quality Awareness Using the 4 C Approach","authors":"V. S. Mani, G. Höfner","doi":"10.1109/ICGSEW.2014.10","DOIUrl":"https://doi.org/10.1109/ICGSEW.2014.10","url":null,"abstract":"Global in-house software development centers of multinational companies in India need to grow to continue attracting talent. For mature centers, to grow sustainably is a challenge, because it involves these centers steadily taking on global roles for product lifecycle activities. A precondition for this is creating within team members a global mindset coupled with awareness of quality of the entire product, extending beyond the quality of a product's components. Therefore, it's necessary for the center to establish a culture for increased quality awareness so as to demonstrate quality orientation for global products. We outline how our 4 C approach, which balances culture, content, career, and compensation -- the 4 Cs, effectively enabled this cultural transformation at an in-house software development center of Siemens, a German multinational company. As part of the 4 C approach we rolled out initiatives to create quality awareness, and intensified training on software engineering, technical expertise, domain knowhow, and behavioral skills to ensure teams possess required competences and the required mindset. We also defined tool-assisted processes and workflows aimed at making code quality a habit.","PeriodicalId":396979,"journal":{"name":"2014 IEEE International Conference on Global Software Engineeering Workshops","volume":"48 2","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2014-08-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"120839952","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}
Previous work reports that some software companies have tried to implement FTS, but have failed to realize the anticipated outcomes. In our research, we propose a software process model to support FTS implementation, named FTS-SPM (Follow the Sun Software Process Model). The proposed FTS-SPM comprises six sub-processes and twenty-five best practices. In this paper, we present the preliminary results from an expert panel conducted with 20 participants to validate the FTS-SPM software process model. Specific questions were asked to a group of GSD (Global Software Development) experts to uncover the usefulness and relevance of each best practice mentioned in FTS-SPM. The initial findings from interviews show that not all twenty-five best practices are perceived as high value practices for FTS projects.
{"title":"FTS-SPM: A Software Process Model for Follow the Sun Development: Preliminary Results","authors":"Josiane Kroll, Ita Richardson, J. Audy","doi":"10.1109/ICGSEW.2014.14","DOIUrl":"https://doi.org/10.1109/ICGSEW.2014.14","url":null,"abstract":"Previous work reports that some software companies have tried to implement FTS, but have failed to realize the anticipated outcomes. In our research, we propose a software process model to support FTS implementation, named FTS-SPM (Follow the Sun Software Process Model). The proposed FTS-SPM comprises six sub-processes and twenty-five best practices. In this paper, we present the preliminary results from an expert panel conducted with 20 participants to validate the FTS-SPM software process model. Specific questions were asked to a group of GSD (Global Software Development) experts to uncover the usefulness and relevance of each best practice mentioned in FTS-SPM. The initial findings from interviews show that not all twenty-five best practices are perceived as high value practices for FTS projects.","PeriodicalId":396979,"journal":{"name":"2014 IEEE International Conference on Global Software Engineeering Workshops","volume":"28 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2014-08-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125854111","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 paper presents three large projects that were developed using OPEN Global Research and Development Process over a 5 year span. The three projects are significantly different in the domain of applicability and scope but were all developed using the same process for OPEN Global collaboration. The OPEN Global Collaboration process is based on the identification of global competence centers staffed with domain experts that are managed by a central team responsible for high-level requirements, overall architecture and quality assurance. The key enabler for OPEN Global Collaboration process is the selection of the domain experts of the global competence centers. These domain experts are internationally recognized experts and they are responsible for the complete specification and development of the components under their responsibility. This is a key insight as it signficantly reduces the required communication between the central and remote teams. As a consequence, the communication is centered on the interface between components and not on the detailed component specifications.
{"title":"Tutorial 1: Multi-year Results of Using an OPEN Global Research and Development Process on Three Different Application Domains","authors":"Alberto Avritzer","doi":"10.1109/ICGSEW.2014.20","DOIUrl":"https://doi.org/10.1109/ICGSEW.2014.20","url":null,"abstract":"The paper presents three large projects that were developed using OPEN Global Research and Development Process over a 5 year span. The three projects are significantly different in the domain of applicability and scope but were all developed using the same process for OPEN Global collaboration. The OPEN Global Collaboration process is based on the identification of global competence centers staffed with domain experts that are managed by a central team responsible for high-level requirements, overall architecture and quality assurance. The key enabler for OPEN Global Collaboration process is the selection of the domain experts of the global competence centers. These domain experts are internationally recognized experts and they are responsible for the complete specification and development of the components under their responsibility. This is a key insight as it signficantly reduces the required communication between the central and remote teams. As a consequence, the communication is centered on the interface between components and not on the detailed component specifications.","PeriodicalId":396979,"journal":{"name":"2014 IEEE International Conference on Global Software Engineeering Workshops","volume":"34 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2014-08-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130709141","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}
Qin Ma, Sam Schmit, Christian Glodt, Pierre Kelsen
In the pure model-driven view of software engineering, models are the sole artifacts to be created and maintained and executable source code is entirely generated from the models. However, due to the variety of modern platforms and the complexity of capturing them correctly in models, this vision has not yet been fully realized. In this paper, we propose an approach that allows combining high-level models with low-level code into an executable system. The approach is based on two modeling languages, one presenting a common abstraction of modeling and programming languages, and the other allowing to express the bridge between the model and code. We illustrate our approach using a running example of an invoicing system for which the business logic requirements are captured by an executable model and the requirements on the graphical user interface are directly mocked up using a GUI designer tool that generates Java code.
{"title":"Combining Models with Code: A Tale of Two Languages","authors":"Qin Ma, Sam Schmit, Christian Glodt, Pierre Kelsen","doi":"10.1109/ICGSEW.2014.9","DOIUrl":"https://doi.org/10.1109/ICGSEW.2014.9","url":null,"abstract":"In the pure model-driven view of software engineering, models are the sole artifacts to be created and maintained and executable source code is entirely generated from the models. However, due to the variety of modern platforms and the complexity of capturing them correctly in models, this vision has not yet been fully realized. In this paper, we propose an approach that allows combining high-level models with low-level code into an executable system. The approach is based on two modeling languages, one presenting a common abstraction of modeling and programming languages, and the other allowing to express the bridge between the model and code. We illustrate our approach using a running example of an invoicing system for which the business logic requirements are captured by an executable model and the requirements on the graphical user interface are directly mocked up using a GUI designer tool that generates Java code.","PeriodicalId":396979,"journal":{"name":"2014 IEEE International Conference on Global Software Engineeering Workshops","volume":"40 7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2014-08-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130589610","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}
Successfully managing distributed projects on an industry scale has rapidly become a key competence for any engineering manager. Challenges vary, be it distributed teams and collaboration technologies, handling cultural diversity and multisite projects, optimizing outsourcing and offshoring capacities, or managing suppliers. The vast majority of global activities do not deliver to targets and half of them fail. The diversity of cultures, suppliers and products require dedicated techniques, tools, and practices to overcome challenges. This tutorial summarizes experiences and guidance from industry in a way to help knowledge and technology transfer. It looks to processes and approaches for successfully handling global software development and outsourcing and offers many practical hints and concrete explanations to make distributed teams and projects a success. Session attendees can raise specific questions from industry practice or academic research to get firsthand insight into GSE state of practice as well as new thoughts and trends that will shape the future.
{"title":"Tutorial 2: Distributed Engineering Teams - Lessons from Industry","authors":"C. Ebert","doi":"10.1109/ICGSEW.2014.21","DOIUrl":"https://doi.org/10.1109/ICGSEW.2014.21","url":null,"abstract":"Successfully managing distributed projects on an industry scale has rapidly become a key competence for any engineering manager. Challenges vary, be it distributed teams and collaboration technologies, handling cultural diversity and multisite projects, optimizing outsourcing and offshoring capacities, or managing suppliers. The vast majority of global activities do not deliver to targets and half of them fail. The diversity of cultures, suppliers and products require dedicated techniques, tools, and practices to overcome challenges. This tutorial summarizes experiences and guidance from industry in a way to help knowledge and technology transfer. It looks to processes and approaches for successfully handling global software development and outsourcing and offers many practical hints and concrete explanations to make distributed teams and projects a success. Session attendees can raise specific questions from industry practice or academic research to get firsthand insight into GSE state of practice as well as new thoughts and trends that will shape the future.","PeriodicalId":396979,"journal":{"name":"2014 IEEE International Conference on Global Software Engineeering Workshops","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2014-08-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121812933","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}
Although challenges in Global Software Development (GSD) are now well known, companies are still looking for workable solutions to issues relating to poor communication, lack of control, low staff morale, and ambiguous requirements, all of which are prevalent in distributed development settings. Solutions offered are often difficult to implement, are disparate, and can be theoretical rather than practical. We conducted a case study with a GSD company, currently using a plan driven approach to development, and uncovered many GSD problems. We mapped each problem to solutions known to work in Agile development settings. Although work has been undertaken in Agile for GSD, we look to the literature to identify practices that specifically address challenges for organisations already engaged in GSD, who are open to moving from a plan-driven/waterfall development process to a more agile approach. Many challenges are addressed by Agile practices, for example requirements ambiguity, need for autonomy, or unpredictable customer expectations. We hypothesise that many GSD problems can be solved by organisations taking an agile approach to their development.
{"title":"Using Agile Practices to Solve Global Software Development Problems -- A Case Study","authors":"Sarah Beecham, J. Noll, Ita Richardson","doi":"10.1109/ICGSEW.2014.7","DOIUrl":"https://doi.org/10.1109/ICGSEW.2014.7","url":null,"abstract":"Although challenges in Global Software Development (GSD) are now well known, companies are still looking for workable solutions to issues relating to poor communication, lack of control, low staff morale, and ambiguous requirements, all of which are prevalent in distributed development settings. Solutions offered are often difficult to implement, are disparate, and can be theoretical rather than practical. We conducted a case study with a GSD company, currently using a plan driven approach to development, and uncovered many GSD problems. We mapped each problem to solutions known to work in Agile development settings. Although work has been undertaken in Agile for GSD, we look to the literature to identify practices that specifically address challenges for organisations already engaged in GSD, who are open to moving from a plan-driven/waterfall development process to a more agile approach. Many challenges are addressed by Agile practices, for example requirements ambiguity, need for autonomy, or unpredictable customer expectations. We hypothesise that many GSD problems can be solved by organisations taking an agile approach to their development.","PeriodicalId":396979,"journal":{"name":"2014 IEEE International Conference on Global Software Engineeering Workshops","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2014-08-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130354189","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}
With the acceleration of urbanization, the demand of high quality public services has been increasing. In the past fifteen years, each department of Chinese government has established its own information service system to provide public services to people. However, these systems are isolated from each other and the services they have provided are not well organized. To tackle this problem, this paper proposes a novel platform for the service management and application development in smart cities. Based on this platform, different people can collaborate and make their contributions, such as requirement acquisition and service development. First, we gather all information and services from existing system to the platform. Second, the platform can publish application or service development requirements based on the crowdsourcing paradigm. Third, small-to-medium service vendors and developers could undertake these development tasks and make use of services provided by our open platform to develop innovative applications. Finally, it provides human-centered services to citizens in appropriate channels when necessary. In this paper, we present the architecture design of the platform and key technologies to implement it. Besides, two practice cases in smart cities of China are given to demonstrate the effectiveness of the platform.
{"title":"Citizen Fusion Service Platform for Smart Cities: Architecture, Technologies and Practice","authors":"Fangping Li, Jiangtao Wang","doi":"10.1109/ICGSEW.2014.15","DOIUrl":"https://doi.org/10.1109/ICGSEW.2014.15","url":null,"abstract":"With the acceleration of urbanization, the demand of high quality public services has been increasing. In the past fifteen years, each department of Chinese government has established its own information service system to provide public services to people. However, these systems are isolated from each other and the services they have provided are not well organized. To tackle this problem, this paper proposes a novel platform for the service management and application development in smart cities. Based on this platform, different people can collaborate and make their contributions, such as requirement acquisition and service development. First, we gather all information and services from existing system to the platform. Second, the platform can publish application or service development requirements based on the crowdsourcing paradigm. Third, small-to-medium service vendors and developers could undertake these development tasks and make use of services provided by our open platform to develop innovative applications. Finally, it provides human-centered services to citizens in appropriate channels when necessary. In this paper, we present the architecture design of the platform and key technologies to implement it. Besides, two practice cases in smart cities of China are given to demonstrate the effectiveness of the platform.","PeriodicalId":396979,"journal":{"name":"2014 IEEE International Conference on Global Software Engineeering Workshops","volume":"75 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2014-08-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123279183","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 software engineering, the conceptual model captures key concepts and relationships between concepts in a problem domain. In general, a conceptual model is usually constructed by one or several modelers, and the quality of the constructed model has a tight relation with the modelers' personal experience and capability. In this paper, we propose a stigmergy-based collaborative conceptual modeling approach to weakening the correlation between the quality of a conceptual model and the modelers' personal experience and capability. The main characteristic of this approach is twofold. First, this approach provides an indirect interaction method to solve the communication problem among the temporal and topographical distributed modelers in a global context. Second, this approach alleviates the impact of low-quality elements in the model constructed by individual modelers and helps to elicit the conceptual model effectively and efficiently. We have developed a web-based tool to support this approach, and conducted a case study to evaluate the feasibility of this approach.
{"title":"Stigmergy-Based Collaborative Conceptual Modeling","authors":"Yi Jiang, Wei Zhang, Haiyan Zhao","doi":"10.1109/ICGSEW.2014.11","DOIUrl":"https://doi.org/10.1109/ICGSEW.2014.11","url":null,"abstract":"In software engineering, the conceptual model captures key concepts and relationships between concepts in a problem domain. In general, a conceptual model is usually constructed by one or several modelers, and the quality of the constructed model has a tight relation with the modelers' personal experience and capability. In this paper, we propose a stigmergy-based collaborative conceptual modeling approach to weakening the correlation between the quality of a conceptual model and the modelers' personal experience and capability. The main characteristic of this approach is twofold. First, this approach provides an indirect interaction method to solve the communication problem among the temporal and topographical distributed modelers in a global context. Second, this approach alleviates the impact of low-quality elements in the model constructed by individual modelers and helps to elicit the conceptual model effectively and efficiently. We have developed a web-based tool to support this approach, and conducted a case study to evaluate the feasibility of this approach.","PeriodicalId":396979,"journal":{"name":"2014 IEEE International Conference on Global Software Engineeering Workshops","volume":"67 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2014-08-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114825907","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}