Factors Influencing the Adoption of ISO/IEC 29110 in Thai Government Projects

Author(s):  
Veeraporn Siddoo ◽  
Noppachai Wongsai

This paper presents the views of four Thai government organizations who had been awarded ISO/IEC 29110 Basic Profile Certification. Team ideas as to the success factors and barriers involved in implementations are explored. In-depth interviews with closed- and open-ended questions were conducted. The data collected was analyzed using qualitative content analysis. The results show two reasons for choosing standard, first, to enhance software development process, and second, because the financial support from the SIPA. The success factors were supportive organizational policy, staff participation, availability of time and resources for the improvement of the software process, consultations with the SIPA and team commitment and recognition. The barrier factors were time constraints, lack of experience, documentation load, unsynchronized means of communication and improper project selection. The findings were based on four diverse organizations. Other countries may take into account the variations e.g. working culture or organizational structure when seeking to apply these results.

Author(s):  
Veeraporn Siddoo ◽  
Noppachai Wongsai

This paper presents the views of four Thai government organizations who had been awarded ISO/IEC 29110 Basic Profile Certification. Team ideas as to the success factors and barriers involved in implementations are explored. In-depth interviews with closed- and open-ended questions were conducted. The data collected was analyzed using qualitative content analysis. The results show two reasons for choosing standard, first, to enhance software development process, and second, because the financial support from the SIPA. The success factors were supportive organizational policy, staff participation, availability of time and resources for the improvement of the software process, consultations with the SIPA and team commitment and recognition. The barrier factors were time constraints, lack of experience, documentation load, unsynchronized means of communication and improper project selection. The findings were based on four diverse organizations. Other countries may take into account the variations e.g. working culture or organizational structure when seeking to apply these results.


2014 ◽  
pp. 1363-1384
Author(s):  
Mohammad Zarour ◽  
Alain Abran ◽  
Jean-Marc Desharnais

Software organizations have been struggling for decades to improve the quality of their products by improving their software development processes. Designing an improvement program for a software development process is a demanding and complex task. This task consists of two main processes: the assessment process and the improvement process. A successful improvement process requires first a successful assessment; failing to assess the organization’s software development process could create unsatisfactory results. Although very small enterprises (VSEs) have several interesting characteristics such as flexibility and ease of communications, initiating an assessment and improvement process based on well-known Software Process Improvement (SPI) models such as Capability Maturity Model Integration (CMMI) and ISO 15504 is more challenging in such VSEs. Accordingly, researchers and practitioners have designed a few assessment methods to meet the needs of VSEs organizations to initiate an SPI process. This chapter discusses the assessment and improvement process in VSEs; we first examine VSEs characteristics and problems. Next, we discuss the different assessment methods and standards designed to fit the needs of such organizations and how to compare them. Finally, we present future research work perceived in this context.


Author(s):  
Sarwosri Sarwosri ◽  
Umi Laili Yuhana ◽  
Siti Rochimah ◽  
Rizky Januar Akbar ◽  
Maidina Choirun Nisa

In a software development project, aspects of software quality are very important. All stakeholders expect high quality of software. To ensure the quality of software products, it is also necessary to ensure that the process that is carried out have a quality. Research that is mostly done is in terms of assessing the quality of software products. But the software process is also very important to be assessed from their quality too. In every software development process, the developer needs guidance in carrying out every aspect of it. In each of these aspects, it must be determined what goals are to be achieved and how to measure whether those goals have been achieved or not. One method that can be used for this is the Extended Goal Question Metric method. In this method, for each development process in software, will be determined what aspects must be achieved, from each aspect there are defined a number of goals to measure these aspects. For each goal, one or more goal will be determined one or more questions that are relevant to that. For each Question an appropriate metric will be determined. The next step is mapping between G to Q and Q to M. The measurement is done by calculating the goal value obtained from the metric calculation. From this metric, the value of each Goal will be obtained, whether it was achieved or not. Tests were carried out on the software process for the development of academic system features at DPTSI ITS. The value of each goal has exceeded 0.51 (for a scale of 0-1) so that it achieved the quality of the Software development process. The total average score was 0.889. 


Behavior Driven Development (BDD) is a software development process that combines the general techniques and principles of Test Driven Development (TDD) with ideas from Domain Driven Design (DDD) and Object Oriented (OO) analysis. It describes a cycle of interactions with well-defined outputs, resulting in the deliverable, tested working software. Today, BDD has evolved into an established agile practice. However, compared to other agile methodology frameworks, such as Scrum and Kanban, BDD is a relatively new. Thus, available resources explaining BDD is still limited and the BDD approach is still under development. Based on this observation, this literature review aims to provide the key of success as well as the challenge that lies on the implementation process of BDD in IT Project. We identified 3 success factors and 5 challenges. The success factors are focusing in product value, having a thorough system behavior definition, and using the right BDD supporting tools. Meanwhile, the most challenging part are the difficulties in writing BDD scenario and automating the test case to maintain the system quality.


Author(s):  
Rory O’Connor ◽  
Shuib Basri

This article identifies the effect of team dynamics in the context of software development teams and its impact on software process improvement (SPI) activities in very small companies, in order to understand the relationship between these two variables. Most software development work is done by teams of software engineers working together in a collaborative manner to execute a software development process. Although there is much literature examining software process and how to improve it, less attention has been paid to the issues of team-working and specifically the impact of team dynamics on the software development process. Team dynamics is the term used to define how people work and interact together in teams. Teamwork is more effective with the existence of positive team dynamic, as it encourages a better working environment with satisfied, fulfilled employees who will in turn be more productive. This paper presents the results of a research study of team dynamics in very small software development companies and its impact on the software development process and software process improvement activities.


2018 ◽  
Vol 7 (2.29) ◽  
pp. 325
Author(s):  
Ramzi A. Haraty ◽  
Gongzhu Hu

Modeling of software process has been a very challenging problem and constantly debated in the software development community in the past 30+ years, largely due to the complex nature of the software development process that involves not only the technical knowledge and skills but also many other factors, such as human, management, quality assessment, and cost. Although the situations of creating software differ greatly from one case to another, there are some common themes shared by many of the situations, and hence various software process models have been emerged to address these common themes. In this paper, we present a review of the software process models commonly used in practice, from traditional to agile, and assessment of these models with metrics and case studies.


Author(s):  
L C Manikandan ◽  
R K Selvakumar

Software engineering is an engineering division connected with development of software product using well-defined scientific principles, techniques and actions. Two different types of activities like software framework activities and umbrella activities are included in standard software process model. Testing acts important job in software development process, i.e. the specified functionality and requirements are tested. The objective of this paper is to provide the software process framework and testing techniques for young researchers.


2021 ◽  
pp. 4089-4098
Author(s):  
Irfan Ahmad Khan, Dr. Dipti Kumari

Software development is a complex process which is divided into many phases. According to the software type and industries the development process is restructured. During the entire development what are the main factors which is influencing the process and affecting the quality. The main objective of this study is to focus on factors influencing the development process and how it affects the small scale industries after coming in to the real practice. Entire Software development is a layered process in which different factors are responsible to get the best products. This paper is focused on different technical and non-technical influencing factors which give major impact on the software quality. With influencing factors, their applicability in small scale industries also studied. Three important technical factors i.e. SDLC model and its principles, Cost estimation and Risk parameter whereas two important influencing factors in non-technical.i.e. success factors and environmental factors. Non-technical factors more influencing than technical factors.  All technical and non-technical factors have their own role but to apply all these quality parameters in small scale industries we need to make them more easy for their applicability. If quality development process and its parameters are tuned to easy and affordable level more businessmen will shift from manual working environment to the digital working environment.


2020 ◽  
Vol 23 (2) ◽  
pp. 140-158 ◽  
Author(s):  
Tanja Lindacher

Co-teaching is fundamental to inclusive education. However, the way co-teaching is implemented, varies considerably, and establishing and allocating instructional responsibilities does not follow a standardized pattern. This study is based on four cases – two located at traditional secondary schools and two at newly created community schools – and includes semi-structured in-depth interviews with four regular teachers and four special education teachers. It aims at providing insight into how co-teaching partners in Germany perceive their own and their partner’s instructional responsibilities. Data are analyzed with a structuring technique of qualitative content analysis. It becomes evident that the partners in each case do not always follow identical instructional intents. Nonetheless, different types of teacher knowledge seem to complement each other effectively in co-teaching relationships. Although, of course provided primarily for pupils with special needs, special education expertise also seems to support pupils without such needs. The results indicate a need to secure and integrate co-teaching relationships structurally into a school’s development process. The article concludes with some options for development in practice.


Sign in / Sign up

Export Citation Format

Share Document