• Title/Summary/Keyword: Developers

Search Result 1,739, Processing Time 0.02 seconds

A study on Factors Affecting the Relational Commitment of Application Developers to the Market (스마트폰 애플리케이션 개발자의 마켓결속 요인에 관한 연구)

  • Park, Su-Yong;Lee, Jung-Hoon;Park, Jae-Bum
    • Journal of Information Technology Applications and Management
    • /
    • v.18 no.4
    • /
    • pp.183-202
    • /
    • 2011
  • Since smart phones are changing the media for communication and its related mobile market, it is imperative to attract more application developers for success in application store business in order to attract more app users. By using aspects of the commitment marketing theory and the relationship marketing theory, this research study identified factors that influence on the relational commitment of application developers to the market. Survey of application developers from Korean mobile application developers' community was conducted to test the hypothesized model. The empirical results showed from an economic behavioral perspective market demand for applications and perceived usefulness of development tool led to relational commitment of developers mediated by perceived satisfaction while attractiveness of alternatives had no significant effect. In addition, fairness of review process and interactivity, based on the relationship marketing theory perspective, showed significant effect on the relational commitment of developers mediated by trust for application market.

The Impact on Structures of Knowledge Creation and Sharing on Performance of Open Collaboration: Focus on Open Source Software Development Communities (개방형협업 참여자의 지식창출·지식공유 구조와 혁신 성과: 오픈소스 소프트웨어 개발 커뮤니티를 중심으로)

  • Koo, Kyungmo;Baek, Hyunmi;Lee, Saerom
    • Knowledge Management Research
    • /
    • v.18 no.4
    • /
    • pp.287-306
    • /
    • 2017
  • This research focus on the effect of developers' participation structure in knowledge creation and knowledge sharing activities in open source software development projects. Based on preferential selection theory, hypotheses of relationship between a developers' concentration of knowledge creation/sharing activities and collaboration performance was derived. To verify the hypotheses, we use the Gini coefficient in the commit contribution of the developers (knowledge creation) and the centralization index in the repository issue network (knowledge sharing network). Using social network analysis, this paper calculates centralization index from developers in the issue boards in each repository based on data from 837 repositories in GitHub, a leading open source software development platform. As a result, instead of all developers creating and sharing knowledge equally, only a few of developers creating and sharing knowledge intensively further improve the performance of the open collaboration. In other words, a few developers predominantly providing commit and actively responding to issues raised from other developers enhance the project performance. The results of this study are expected to be used by developers who manage open source software project as a governance strategy, which could improve the performance of open collaboration.

Resolution Methods for Developer's Difficulties in the Serious Game Developing Process for Science Learning (과학 학습 기능성 게임 개발 과정에서 개발자가 겪는 어려움과 대처 방법)

  • Hwang, Hyunjung;Lee, Changhoon;Jhun, Youngseok
    • Journal of The Korean Association of Information Education
    • /
    • v.18 no.1
    • /
    • pp.121-132
    • /
    • 2014
  • The main goal of this research is to invest the difficulties in the process of developing serious game for science learning to acquire the suggestion. We analysed the journals written by developers of game scenario on the procedure of the development and on the review of the accomplished game. Then we also interviewed the scenario developers as well as game developers. When interviewing the game developers, we passed them the thoughts and questions of scenario developers. The possible difficulties in developing serious game are form the difference of cognitions on the skills which can be embodied in the development process and interaction and communication problem between scenario developers and game developers. As a consequence of the research, we acquired some suggestions for developing serious game as follows; 1) Scenario developers and game developers must understand the concepts of serious game as well as learning theory; 2) Both scenario developers and game developers should be aware of secured technological capacity and allowed time period. 3) Scenario developer should take a part of game developer' role as using a learning contents authoring tool; 4) Scenario developers have to consistently interact with game developers in developing the games; 5) Scenario should be concretely described in detail; and 6) A Supervisor is essential to control both scenario developers and game developers.

Analysis of how Development Methodologies Influence the Potential Motivation of Software Developers (개발방법론이 개발직무의 동기유발성에 미치는 영향에 대한 분석)

  • Hwang, Soon-Sam;Kim, Sung-Kun
    • Journal of Information Technology Applications and Management
    • /
    • v.17 no.2
    • /
    • pp.1-18
    • /
    • 2010
  • The Agile methodology is a new trend in software development. Nowadays enterprises have been adopting the agile methodology in an effort to deal effectively with rapidly changing user requirements. In most cases, much improvement was accomplished in the software development. Some studies have mentioned that the motivation of software developers is a contributing factor on the improvement. However, it is not known yet what aspects of the agile methodology get them to be motivated. The aims of this study are the comparison between the traditional methodologies and agile methodology and look into potential motivation of software developer and their jobcharacteristics. For the empirical analyzing, research data were collected by 77 developers of 4 domestic IT companies. The analysis shows that there is significant differences on developer's potential motivation according to what kind of methodology is used. Agile developers to be more motivated than others methodologies developers. It also shows in detail that what kinds of job characteristics of developer are different among them depending on methodologies.

  • PDF

An Outcome-Based Approach in Medical Curriculum Development (성과중심교육과정 개발절차에 대한 고찰)

  • Ahn, Jae Hee;Yang, Eunbae B.
    • Korean Medical Education Review
    • /
    • v.15 no.1
    • /
    • pp.9-18
    • /
    • 2013
  • An outcome-based curriculum is perceived to be one alternative educational approach in medical education. Nonetheless, it is difficult for curriculum developers to convert from traditional curriculum to an outcome-based curriculum because research documenting its development process is rare. Therefore, this study aims to introduce the development process and method of outcome-based curriculum. For the purpose of this study, we used diverse data analyses, such as an existing literature search, development model analysis, and case analysis. We identified five phases from the analysis. First, the curriculum developers analyze the physician's job or a high performer in a medical situation. Second, curriculum developers extract outcomes and competencies through developing a curriculum, affinity diagraming, and critical incident interviews. Third, curriculum developers determine the proficiency levels of each outcome and competency evaluation methods. Fourth, curriculum developers conduct curriculum mapping with outcomes and competencies. Fifth, curriculum developers develop an educational system. Also, it is important to develop an assessment system for the curriculum implementation in the process of developing the outcome-based curriculum. An outcome-based curriculum influences all the people concerned with education in a medical school including the professors, students, and administrative staff members. Therefore, curriculum developers should consider not only performance assessment tools for the students but also assessment indicators for checking curriculum implementation and managing curriculum quality.

Effort Analysis of Unit Testing Conducted by Non-Developer of Source Code (원개발자 부재에 따른 원시코드 기반의 단위테스트 노력 분석)

  • Yoon, Hoijin
    • Journal of Information Technology Services
    • /
    • v.11 no.4
    • /
    • pp.251-262
    • /
    • 2012
  • Unit testing is one of the test levels, which tests an individual unit or a group of related units. Recently, in Agile Development or Safety-critical System Development, the unit testing plays an important role for the qualities. According to the definition of unit testing, it is supposed to be done by the developers of units. That is because test models for the unit testing refers to the structure of units, and others but its original developers hardly can understand the structures. However, in practice, unit testing is often asked to be done without the original developers. For example, it is when faults are revealed in customer sites and the development team does not exit any more. In this case, instead of original developers, other developers or test engineers take a product and test it. The unit testing done by a non-developer, who is not the original developer, would cause some difficulties or cause more cost. In this paper, we tests an open source, JTopas, as a non-developer, with building test models, implementing test codes, and executing test cases. To fit this experiment to practical testing situations, we designed it based on the practices of unit testing, which were surveyed through SPIN(Software Process Improvement Network). This paper analyzes which part of unit testing done by non-developers needs more effort compared to the unit testing done by original developers. And it concludes that Agile Development contributes on reducing the extra effort caused by non-developers, since it implements test codes first before developing source code. That means all the units have already included their own tests code when they are released.

Recommendation for Development of Clinical Skill Contents in the Competency-Based Sasang Constitutional Medicine Education (사상체질의학 역량중심의 임상실기 내용 개발을 위한 제언)

  • Yu, Jun-Sang
    • Journal of Sasang Constitutional Medicine
    • /
    • v.31 no.4
    • /
    • pp.1-8
    • /
    • 2019
  • An outcome-based curriculum or competency-based curriculum is regarded to be one of the mainstream curricula to make students centered. It is believed to be able to support a flexible, time-independent curriculum. However, it is not easy for the curriculum developers to convert from the traditional curriculum to an competency-based curriculum. Traditional medicines including Sasang constitutional medicine(SCM) have been on the verge of transforming their curricula. Considering the contents of the clinical skills in terms of an outcome-based curriculum in SCM, at least five categories needs to be covered. First, curriculum developers need to consider the understanding of relevant diseases concerning SCM although SCM could be used as the method to treat all kinds of diseases. Second, curriculum developers facilitate the students to diagnose patients' SCM types. Third, curriculum developers conduct the establishment of competencies to understand the patterns of SCM symptomology. Fourth, curriculum developers develop the diverse treatment methods and procedures to make students participate. Fifth, curriculum developers make students teach and consult their patients in terms of SCM regimen. Development of the clinical skill contents in detail depends on the situation of each colleges. Competency-based medical curriculum in SCM could influence on the management of the curriculum quality.

Differences across countries in the impact of developers' collaboration characteristics on performance : Focused on weak tie theory (국가별 오픈소스 소프트웨어 개발자의 네트워크 특성이 개방형 협업 성과에 미치는 영향 : 약한 연결 이론을 중심으로)

  • Lee, Saerom;Baek, Hyunmi;Lee, Uijun
    • The Journal of Information Systems
    • /
    • v.29 no.2
    • /
    • pp.149-171
    • /
    • 2020
  • Purpose With the advent of the 4th Industrial Revolution, related technologies such as IoT, big data, and artificial intelligence technologies are developing through not only specific companies but also a number of unspecified developers called open collaboration. For this reason, it is important to understand the nature of the collaboration that leads to successful open collaboration. Design/methodology/approach We focused the relationship between the collaboration characteristics and collaboration performance of developers who participating in open source software development, which is a representative open collaboration. Specifically, we create the country-specific network and draw the individual developers characteristics from the network such as collaboration scope and collaboration intensity. We compare and analyze the characteristics of developers across countries and explore whether there are differences between indicators. We develop a Web crawler for GitHub, a representative OSSD development site, and collected data of developers who located at China, Japan, Korea, the United States, and Canada. Findings China showed the characteristics of cooperation suitable for the form of weak tie theory, and consistent results were not drawn from other countries. This study confirmed the necessity of exploratory research on collaboration characteristics by country considering that there are differences in open collaboration characteristics or software development environments by country.

A Study on Perceptions of Developers on Information Systems Success (정보시스템 성공에 대한 개발자 가치구조에 관한 연구)

  • Kim, Joong Han
    • Journal of Korea Society of Industrial Information Systems
    • /
    • v.27 no.3
    • /
    • pp.47-58
    • /
    • 2022
  • As firms increase their operations in the international arena, there is a growing need for managers to understand cross-cultural issues in adopting information systems(IS). The present study surveyed IS developers with respect to their perceptions on the importance of various criteria for successful development of information systems. The results indicated that developers perceive criteria related to the organizational and systems level to be more important than criteria on the strategic and user level. In addition, the developers perceive immediate/direct criteria as more important that indirect/long term criteria. The current study found little differences between developers working for innovative versus those working for non-innovative companies with respect to their views on the importance of various success criteria. There were also very little differences in the perceptions of IS developers at different hierarchical ranks.

A Study of Factors Associated with Software Developers Job Turnover (데이터마이닝을 활용한 소프트웨어 개발인력의 업무 지속수행의도 결정요인 분석)

  • Jeon, In-Ho;Park, Sun W.;Park, Yoon-Joo
    • Journal of Intelligence and Information Systems
    • /
    • v.21 no.2
    • /
    • pp.191-204
    • /
    • 2015
  • According to the '2013 Performance Assessment Report on the Financial Program' from the National Assembly Budget Office, the unfilled recruitment ratio of Software(SW) Developers in South Korea was 25% in the 2012 fiscal year. Moreover, the unfilled recruitment ratio of highly-qualified SW developers reaches almost 80%. This phenomenon is intensified in small and medium enterprises consisting of less than 300 employees. Young job-seekers in South Korea are increasingly avoiding becoming a SW developer and even the current SW developers want to change careers, which hinders the national development of IT industries. The Korean government has recently realized the problem and implemented policies to foster young SW developers. Due to this effort, it has become easier to find young SW developers at the beginning-level. However, it is still hard to recruit highly-qualified SW developers for many IT companies. This is because in order to become a SW developing expert, having a long term experiences are important. Thus, improving job continuity intentions of current SW developers is more important than fostering new SW developers. Therefore, this study surveyed the job continuity intentions of SW developers and analyzed the factors associated with them. As a method, we carried out a survey from September 2014 to October 2014, which was targeted on 130 SW developers who were working in IT industries in South Korea. We gathered the demographic information and characteristics of the respondents, work environments of a SW industry, and social positions for SW developers. Afterward, a regression analysis and a decision tree method were performed to analyze the data. These two methods are widely used data mining techniques, which have explanation ability and are mutually complementary. We first performed a linear regression method to find the important factors assaociated with a job continuity intension of SW developers. The result showed that an 'expected age' to work as a SW developer were the most significant factor associated with the job continuity intention. We supposed that the major cause of this phenomenon is the structural problem of IT industries in South Korea, which requires SW developers to change the work field from developing area to management as they are promoted. Also, a 'motivation' to become a SW developer and a 'personality (introverted tendency)' of a SW developer are highly importantly factors associated with the job continuity intention. Next, the decision tree method was performed to extract the characteristics of highly motivated developers and the low motivated ones. We used well-known C4.5 algorithm for decision tree analysis. The results showed that 'motivation', 'personality', and 'expected age' were also important factors influencing the job continuity intentions, which was similar to the results of the regression analysis. In addition to that, the 'ability to learn' new technology was a crucial factor for the decision rules of job continuity. In other words, a person with high ability to learn new technology tends to work as a SW developer for a longer period of time. The decision rule also showed that a 'social position' of SW developers and a 'prospect' of SW industry were minor factors influencing job continuity intensions. On the other hand, 'type of an employment (regular position/ non-regular position)' and 'type of company (ordering company/ service providing company)' did not affect the job continuity intension in both methods. In this research, we demonstrated the job continuity intentions of SW developers, who were actually working at IT companies in South Korea, and we analyzed the factors associated with them. These results can be used for human resource management in many IT companies when recruiting or fostering highly-qualified SW experts. It can also help to build SW developer fostering policy and to solve the problem of unfilled recruitment of SW Developers in South Korea.