Dissertations / Theses: 'Software development practice'

1

Kayongo, Patrick. "Why do software developers practice test-driven development?" Master's thesis, University of Cape Town, 2016. http://hdl.handle.net/11427/20417.

Full text

Abstract:

This dissertation describes research that has been undertaken to understand factors influencing software developers' intention to perform test driven development (TDD). Unit tests are a form of testing, where tests are written for small units of software being developed. TDD is a practice where these tests are written before the functionality is written, so as to guide the design of the code for the functionality, as well as to ensure test coverage for all functionality. There has been some research conducted to understand TDD by looking at its effects on both the outcomes and the practice of software development. It has been found to increase quality by decreasing defects, while also increasing the maintainability and the changeability of the code. On the other hand, some research has also found it to increase time spent on completing tasks. Despite this, to the best of the researcher's knowledge, there hasn't been research done to understand the behavioural components of TDD, and in particular, why developers choose to practice TDD. A conceptual model based on the Theory of Planned Behaviour (TPB) is described and used as a lens to understand intention. TPB proposes that intention to perform a behaviour (TDD in this case) is influenced by three factors: attitude towards the behaviour, subjective norm, and perceived behavioural control. This dissertation seeks to build onto this model for the purpose of understanding TDD, and proposes the following determinants of the influences of intention: attitude is influenced by attitude towards time taken, differences in quality, maintainability and developer efficiency; subjective norm is influenced by the perceived perception of the environment regarding changes in quality, time taken, and maintainability of the code. Lastly, perceived behavioural control is posited to be made up of perceived difficulty of TDD, and how much experience a developer has. This model is then tested based on data collected from a n online survey distributed around the world. 779 responses were collected from developers in various countries around the world. The majority of the respondents to practice TDD, allowing us to gain greater insight into why those that practice TDD actually do so. Because the study is a psychographic study, perceptions were understood from the developers using an ordinal Likert scale. To analyse this data in order to prove the hypotheses, Chi -¬‐ square tests with contingency tables, Kruskal -¬‐ Wallis tests and ordinal logistic regression were used as statistical methods. It is found the data collected does not conform to the model, and recommendations are made for a future study to form a more comprehensive model.

APA, Harvard, Vancouver, ISO, and other styles

2

Cater-Steel, Aileen Patricia, and n/a. "An Evaluation of Software Development Practice and Assessment-Based Process Improvement in Small Software Development Firms." Griffith University. School of Computing and Information Technology, 2005. http://www4.gu.edu.au:8080/adt-root/public/adt-QGU20060110.180345.

Full text

Abstract:

As software becomes increasingly important to all aspects of industry, there is a need to encourage practitioners to adopt best practice so as to improve the quality of the processes in use, and therefore achieve targets relating to time, budget and quality. The software development industry in Australia is dominated by a myriad of small firms. This presents a challenge in terms of determining the current practices of industry participants, and in devising improvement initiatives which are feasible for small organisations. Currently, the level of adoption of best practice among local software developers is unknown. To help improve the software industry, it is necessary to determine the current status of use of practices and techniques. Furthermore, the effectiveness of assessment-based software process improvement for small organisations needs to be evaluated. The objective of this research is to understand the extent of software development practices currently in use, and to evaluate the effectiveness of assessment-based software process improvement initiatives for small firms. To achieve this objective, an extensive mail survey of the Queensland software industry was conducted to identify and compare best practice in software development with current practice. The survey was based on the software best practice questionnaire used by the European Software Institute. Following on from this, a detailed evaluation of a process improvement program in 22 small firms was carried out. The program used the Rapid Assessments for Process Improvement for software Development (RAPID) model and method. RAPID is based on ISO/IEC 15504 (SPICE) and includes eight processes: requirements elicitation, software development, configuration management, quality assurance, project management, problem resolution, risk management, and process establishment. The evaluation analysed the process capability of the firms as reported from one-day software process assessments and also the extent of improvement as recorded at follow-up meetings held 7 to 16 months after the assessment. Both quantitative and qualitative techniques were used to analyse the assessment reports. The study confirmed that there is wide variation in the extent of adoption of software development best practice in terms of the individual practices, as well as the organisations. While project management planning and customer involvement practices are widely adopted, the use of metrics for estimating and testing are barely used by the organisations that responded to the survey. Overall, practices of a technical nature are more widely adopted compared to techniques related to support and management. Organisations involved in developing commercial off-the-shelf software have higher adoption than firms which do not develop such systems, and adoption of best practice is associated with the size of the development group. The leaders in adoption have significantly better practices when compared to the laggards for 40 of the 44 practices included in the survey. Furthermore, organisations from the finance, insurance and utilities sectors exhibited higher adoption of best practice compared to organisations from other sectors. The overall adoption of 48 percent implies that the organisations which responded have adopted, on average, almost half of the best practices in the questionnaire. While this overall adoption rate places the Queensland software industry in a competitive position compared to adoption of firms in European countries, there is scope for improvement. The process improvement assessments of 22 firms also confirmed that the capability of technical processes is higher than that of management processes; and suggested that higher capability is associated with the proportion of experienced staff and the proportion of staff with post graduate qualifications. Higher process capability is also associated with firms undertaking projects of lengthy durations. Most of the processes were rated at the lowest levels. Almost one third of all the processes were rated as incomplete (level 0) and 46 percent were rated as performed (level 1). The evaluation of the process improvement program was conducted by analysing the 22 assessment reports, and the 20 final reports from the follow-up meetings. The extent of improvement is associated with the proportion of technical staff and the proportion of formally qualified staff. The evaluation revealed that assessment-based process improvement programs are effective for small firms, regardless of the maturity of the processes at the time of the assessment. As well as detailing the process capability of 22 small software firms, this study provides an interesting insight into the actions, reasons for inaction, and reactions of the firms as far as implementing the recommendations from the assessments. Analysis of the reactions of the participants of this program suggests that for small firms, mentoring, training and organisation stability are important factors, while senior management support may not be an issue of concern. The study indicates that small firms can benefit from a low cost process improvement program with a restricted scope, a short time frame to evaluation, and mentoring from external assessors/consultants. It is also crucial that the firm is not disrupted by internal or external events during the course of the software process improvement program. Furthermore, this study provides a contribution to assessment methods by validating the RAPID model and method, and providing recommendations to improve the RAPID method. The outcomes from this research have the potential to better equip practitioners and consultants to undertake software process improvement, hence increasing the success of small software development firms in domestic and global markets.

APA, Harvard, Vancouver, ISO, and other styles

3

Cater-Steel, Aileen Patricia. "An Evaluation of Software Development Practice and Assessment-Based Process Improvement in Small Software Development Firms." Thesis, Griffith University, 2005. http://hdl.handle.net/10072/365666.

Full text

Abstract:

As software becomes increasingly important to all aspects of industry, there is a need to encourage practitioners to adopt best practice so as to improve the quality of the processes in use, and therefore achieve targets relating to time, budget and quality. The software development industry in Australia is dominated by a myriad of small firms. This presents a challenge in terms of determining the current practices of industry participants, and in devising improvement initiatives which are feasible for small organisations. Currently, the level of adoption of best practice among local software developers is unknown. To help improve the software industry, it is necessary to determine the current status of use of practices and techniques. Furthermore, the effectiveness of assessment-based software process improvement for small organisations needs to be evaluated. The objective of this research is to understand the extent of software development practices currently in use, and to evaluate the effectiveness of assessment-based software process improvement initiatives for small firms. To achieve this objective, an extensive mail survey of the Queensland software industry was conducted to identify and compare best practice in software development with current practice. The survey was based on the software best practice questionnaire used by the European Software Institute. Following on from this, a detailed evaluation of a process improvement program in 22 small firms was carried out. The program used the Rapid Assessments for Process Improvement for software Development (RAPID) model and method. RAPID is based on ISO/IEC 15504 (SPICE) and includes eight processes: requirements elicitation, software development, configuration management, quality assurance, project management, problem resolution, risk management, and process establishment. The evaluation analysed the process capability of the firms as reported from one-day software process assessments and also the extent of improvement as recorded at follow-up meetings held 7 to 16 months after the assessment. Both quantitative and qualitative techniques were used to analyse the assessment reports. The study confirmed that there is wide variation in the extent of adoption of software development best practice in terms of the individual practices, as well as the organisations. While project management planning and customer involvement practices are widely adopted, the use of metrics for estimating and testing are barely used by the organisations that responded to the survey. Overall, practices of a technical nature are more widely adopted compared to techniques related to support and management. Organisations involved in developing commercial off-the-shelf software have higher adoption than firms which do not develop such systems, and adoption of best practice is associated with the size of the development group. The leaders in adoption have significantly better practices when compared to the laggards for 40 of the 44 practices included in the survey. Furthermore, organisations from the finance, insurance and utilities sectors exhibited higher adoption of best practice compared to organisations from other sectors. The overall adoption of 48 percent implies that the organisations which responded have adopted, on average, almost half of the best practices in the questionnaire. While this overall adoption rate places the Queensland software industry in a competitive position compared to adoption of firms in European countries, there is scope for improvement. The process improvement assessments of 22 firms also confirmed that the capability of technical processes is higher than that of management processes; and suggested that higher capability is associated with the proportion of experienced staff and the proportion of staff with post graduate qualifications. Higher process capability is also associated with firms undertaking projects of lengthy durations. Most of the processes were rated at the lowest levels. Almost one third of all the processes were rated as incomplete (level 0) and 46 percent were rated as performed (level 1). The evaluation of the process improvement program was conducted by analysing the 22 assessment reports, and the 20 final reports from the follow-up meetings. The extent of improvement is associated with the proportion of technical staff and the proportion of formally qualified staff. The evaluation revealed that assessment-based process improvement programs are effective for small firms, regardless of the maturity of the processes at the time of the assessment. As well as detailing the process capability of 22 small software firms, this study provides an interesting insight into the actions, reasons for inaction, and reactions of the firms as far as implementing the recommendations from the assessments. Analysis of the reactions of the participants of this program suggests that for small firms, mentoring, training and organisation stability are important factors, while senior management support may not be an issue of concern. The study indicates that small firms can benefit from a low cost process improvement program with a restricted scope, a short time frame to evaluation, and mentoring from external assessors/consultants. It is also crucial that the firm is not disrupted by internal or external events during the course of the software process improvement program. Furthermore, this study provides a contribution to assessment methods by validating the RAPID model and method, and providing recommendations to improve the RAPID method. The outcomes from this research have the potential to better equip practitioners and consultants to undertake software process improvement, hence increasing the success of small software development firms in domestic and global markets.
Thesis (PhD Doctorate)
Doctor of Philosophy (PhD)
School of Computing and Information Technology
Full Text

APA, Harvard, Vancouver, ISO, and other styles

4

Hope, Stuart. "Parametric software project estimating: An analysis of current practice." Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 1998. https://ro.ecu.edu.au/theses/1430.

Full text

Abstract:

As society and the world economy moves into the second millennium. the service industries involving knowledge workers will continue to increase. Software is the enabling technology that is driving the knowledge industry. As the development of software is mostly a design process, where new artefacts are conceived and built, the prediction of outcomes in the process is fraught with difficulties. Software project estimating is one of the essential Software Engineering techniques that will enable the rationalisation of decision-making regarding software development. Estimates that are more accurate will increase the probability of success and lower the risk. This thesis analyses the current software project estimating techniques available to practitioners and examines current practice in the estimating of software projects within the Western Australian industry. The principal techniques examined are Function Point Analysis and COCOMO and these are shown to be flawed in their construction. The practices adopted by expert and experienced practitioners are analysed and it is shown that the formal algorithmic models are not widely used. It is also shown that estimates are required in a project's lifecycle before the full requirements are known. The Western Australian practices are also compared to similar analyses conducted in other countries.

APA, Harvard, Vancouver, ISO, and other styles

5

Rodríguez, P. (Pilar). "Combining lean thinking and agile software development:how do software-intensive companies use them in practice?" Doctoral thesis, Oulun yliopisto, 2013. http://urn.fi/urn:isbn:9789526203324.

Full text

Abstract:

Abstract Software engineering is advancing according to market needs. Consequently, software development methods that initially caused controversies such as Agile, and more recently Lean, are increasingly being adopted by the software industry. Particularly, Lean Software Development, which was initially regarded as one of the Agile methods, is acquiring an identity of its own as a means to scale Agile. However, Lean thinking is still open to interpretation in the domain of software development, which differs fundamentally from the manufacturing domain where Lean originally emerged. Specific issues such as the essence of Lean Software Development, the compatibility of Lean and Agile and the best combination of them are not properly understood. This dissertation addresses Lean thinking and its combination with Agile in the field of software development, by providing empirical evidence on how software-intensive organisations use them in practice. The research was performed in four phases. First, the relevant literature was analysed to identify research opportunities. Second, a survey strategy was used to investigate status and trends in the adoption of Agile and Lean. The third phase explored in detail how Agile and Lean are combined in practice, by conducting case studies on two large-scale, industry-leading companies that were transforming their processes from Agile Software Development into Lean Software Development. Finally, in the fourth phase, the results of the previous research phases were synthetized to draw conclusions and outline implications. The results of the study confirmed the interest of practitioners in using a combination of Agile and Lean. Unlike in manufacturing, the borders of Agile and Lean are not clearly defined in the software domain. The results provided evidence of numerous compatibilities between Agile and Lean in software development. Generally, the use of Agile methods at a prescriptive level is guided by Lean principles. However, Lean thinking also brings new practical elements to software development processes, such as Kanban, work-in-progress limits, a ‘pull’ and ‘less waste’-oriented culture and an extended emphasis on transparency and collaborative development. The results showed the fundamental importance of practices that enable quick feedback, fast learning and adaptation
Tiivistelmä Ohjelmistotuotanto kehittyy markkinoiden tarpeiden mukaisesti. Aiemmin kiisteltyjä ketteriä menetelmiä, ja nykyään myös Lean-menetelmiä sovelletaan yhä useammin ohjelmistoteollisuudessa. Lean-menetelmiin perustuva Lean-ohjelmistokehitys erottuu selkeämmin välineenä laajentaa ketterien menetelmien käyttöä. Lean on yhä monitulkintainen ohjelmistotuotannossa, joka poikkeaa teollisuustuotannosta, josta Lean on peräisin. Lean-ohjelmistokehitystä, Lean- ja ketterien menetelmien yhteensopivuutta ja niiden parasta yhdistelmää ei vielä ymmärretä riittävän hyvin. Tämä väitöskirja käsittelee Lean-menetelmien yhdistämistä ketteriin menetelmiin ohjelmistotuotannossa. Tutkimus esittää kokemusperäistä tietoa, kuinka näitä menetelmiä käytetään ohjelmisto-alan organisaatioissa. Tutkimus oli nelivaiheinen. Aluksi tutkimusmahdollisuudet kartoitettiin tutkimalla aiheeseen liittyvää kirjallisuutta. Seuraavaksi tutkittiin kyselytutkimuksen avulla Lean- ja ketterien menetelmien käyttämisen nykytilaa ja kehitystä. Kolmannessa vaiheessa tapaustutkimuksilla selvitettiin Lean- ja ketterien menetelmien yhdistämistä käytännössä. Tapaustutkimuksia tehtiin kahdessa suuressa yrityksessä, jotka olivat muuttamassa prosessejaan ketteristä menetelmistä kohti Lean-ohjelmistokehitystä. Lopuksi aiemmat tutkimusvaiheet yhdistettiin johtopäätöksiä ja vaikutusten hahmottamista varten. Tutkimuksen tulokset vahvistavat Lean- ja ketterien menetelmien yhdistämisen kiinnostavan ohjelmistotuotannonharjoittajia. Lean- ja ketterien menetelmien rajat eivät ole selkeästi määriteltyjä ohjelmistotuotannossa. Tulokset tukevat käsitystä Lean- ja ketterien menetelmien yhteensopivuudesta. Lean ohjaa yleisellä tasolla ketterien menetelmien käyttöä. Lean tuo kuitenkin myös uusia elementtejä ohjelmistotuotantoon, kuten Kanban-menetelmän, keskeneräisen työn rajoittamisen, kysyntään perustuvan ’pull’-menetelmän ja turhan työn vähentämistä tavoittelevan ’less-waste’-työkulttuurin. Lean-ajattelu myös lisää painotusta läpinäkyvyyteen ja yhteistyöhön

APA, Harvard, Vancouver, ISO, and other styles

6

Heyer, Tim. "Semantic Inspection of Software Artifacts From Theory to Practice." Doctoral thesis, Linköping : Univ, 2001. http://www.ep.liu.se/diss/science_technology/07/25/index.html.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Nasir, Nayla. "Acceptance Testing in Agile Software Development - Perspectives from Research and Practice." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-21141.

Full text

Abstract:

Context: Acceptance testing is an important activity that verifies the conformance of a system to its acceptance criteria. It aims to provide a detailed communication of domain knowledge and is used to evaluate whether the customer requirements are met. Existing literature lacks empirical evidence for acceptance testing. Especially in the context of industry practice, it is not in the authors' consideration, except for a few studies, where the authors have investigated the state of practice in a specific domain. Objective: This study aims to recognize the state of research and practice of acceptance testing in Agile Software Development and investigate the similarities and differences in both perspectives. The study contributes to identify the industry-academia gap in the context of acceptance testing. Research Method: To identify the acceptance testing practices and challenges from research, I have conducted a literature review. For the industry perspective on acceptance testing practices and challenges, I have conducted an interview-based survey of the practitioners working in the Agile Software Development environment. I followed the snowball search strategy to search the primary studies, whereas to select the respondents, I used the convenience and snowball sampling method. For data analysis, I followed the approach of thematic synthesis. Results: The results of this thesis are the outcome of a literature review of 20 selected studies and an interview-based survey with 12 practitioners representing10 companies. I identified acceptance testing practices and challenges from research and industry. In the research, the most recommended form of acceptance testing is acceptance test-driven development (ATDD), and the majority of the studies are referring to the use of FIT for acceptance testing. Customer involvement in different phases of acceptance testing is recommended in research. From the interviews, I come across that acceptance testing is manual at large in the industry, and the most challenging aspect is the customer’s involvement. Conclusions: From the findings of this thesis, it is concluded that there is a gap between the research and industry perspective of acceptance testing practices. Currently, acceptance testing in the industry is mostly manual, the research is not focusing on this aspect of acceptance testing. Despite the differences, there are some commonalities as well. Especially, most challenges of acceptance testing are similar in both perspectives. Researchers have to consider the commonalities, and they have to look at how they can minimize the acceptance testing challenges from the perspective of the industry.

APA, Harvard, Vancouver, ISO, and other styles

8

Tanner, Maureen Cynthia. "Social conditions leading to Scrum process breakdowns during Global Agile Software Development: a theory of practice perspective." Doctoral thesis, University of Cape Town, 2013. http://hdl.handle.net/11427/17270.

Full text

Abstract:

Global Software Development (GSD) and Agile are two popular software development trends that are gaining in popularity. In addition, more and more organisations are now seeking to engage in agile software development within the GSD context to reap the benefits of both ventures and achieve project success. Hence, agile methodologies adapted to fit the GSD context are commonly termed Global Agile Software Development (GASD) methodologies. However, because of geographical, temporal, and cultural challenges, collaboration is not easily realized in the GASD context. In addition, this work context is characterized by multiple overlapping fields of practice, which further hinder collaboration, and give rise to social challenges. Given the existence of these social challenges, there is a need to further investigate the human-centred aspect of collaboration during GASD. Following an extensive literature review on the application of Scrum and other agile methodologies in GASD between 2006 and 2011, it was noted that there is a lack of understanding of the social conditions giving rise to the social challenges experienced during GASD. It was noted that past studies have instead sought to describe these social challenges and to provide mitigating strategies in the form of best-practices, without detailing and theorising about the social conditions under which these social challenges emerge. One of the objective of the study was thus to investigate the use of Scrum during GASD. In particular, the Scrum process breakdowns experienced during and after Scrum's sprint planning and retrospective meetings were identified. The social conditions under which these breakdowns emerged were investigated in the light of Bourdieu's Theory of Practice. Scrum Process breakdowns were defined as any deviation from an ideal Scrum process (as per the Scrum methodology's guidelines) which yields to the emergence of social challenges, conflict or disagreements in the GASD team. The study was empirical and qualitative in nature and followed the positivist research paradigm. Two case studies, in line with Bonoma (1985)'s "drift" and "design" stages of case study design, were undertaken to investigate the phenomena of interest and answer the research questions. The first case focused on a distributed agile team executing a software project across South Africa (Cape Town) and Brazil (Sao Paulo) while the second case focused on a team executing an agile software project across India (Pune) and South Africa (Durban). The site selection was carefully thought out and the results from the first case informed the second case in order to add more richness in the data being gathered. In both case studies, data was collected through semi-structured interviews, documentation, field notes and direct observation. The underlying theoretical framework employed for the study was the Theory of Practice (Bourdieu, 1990). The study has identified various forms of Scrum process breakdowns occurring during and after sprint planning and retrospective meetings: » Different perceptions about task urgency at the software development sites » Disagreements on the suitability of software engineering practices » Low level of communication openness during meetings involving the whole GASD team compared to internal meetings at the sites » Impromptu changes to user stories' content and priorities » Product Owner's low level of authority » Disagreements on estimation mechanisms » Number of User Stories to be completed during the Sprint Is imposed on the team » Decisions on Scrum process updates not made by the development team » Selective invitation to retrospective meetings In addition, various social conditions were identified as possibly leading to the emergence of these Scrum process breakdowns in the GASD context: » GASD project stakeholders' low level of capital in the joint field » Different beliefs and values because of multiple fields Two theoretical propositions were derived to describe the social conditions and the corresponding Scrum process breakdowns which are likely to emerge under these conditions.

APA, Harvard, Vancouver, ISO, and other styles

9

Modi, Sunila. "Exploring the emergence of collaborative practices in globally distributed agile software development." Thesis, Brunel University, 2018. http://bura.brunel.ac.uk/handle/2438/16368.

Full text

Abstract:

Agile software development approaches have emerged as a response to perceived frustrations of more heavyweight plan-driven methods, and have now become well established within the information systems field. More recently, there has been a tremendous growth in applying agile methods in globally distributed settings. In light of this, there is a pressing need to understand how agile practices are adapted which were originally conceived for collocated settings, and now actually being used in globally distributed settings, taking into account the challenges posed by such contexts. The aim of this thesis is to contribute to this research gap, with a quest to better understand and unpack the "black-box" of how collaborative practices evolve within global agile settings. The value of this research lies in improving and advancing our understanding of the challenges the team members go through in adapting agile practices in global contexts. The research also explores how collaborative practices can support agility in globally distributed settings. In order to contribute to knowledge and increase conceptual clarity, there is a need to carry out in-depth and in-situ research within an organisational context. By taking a socio-technical perspective this study intends to extend our existing knowledge on how collaborative practices are evolving in real-time practice within globally distributed agile settings. The empirical evidence is drawn from a globally distributed team, operating in a global financial bank with offices based in London and Delhi. Interpretive research methods including semi-structured interviews and observations are used to understand team members' experiences of developing collaborative practices in a globally distributed context. Although existing literature on agile software development acknowledges the intrinsic significance of collaboration for effective functioning of agile methods, current studies fail to demonstrate a situated practice perspective on how collaborative practices are adapted in globally distributed settings. This study enlists the analytical concepts of boundary objects and Pickering's "mangle of practice" to better understand the process of how collaborative practices evolve in globally distributed agile teams. The resulting analysis provides us with a much more nuanced understanding of how interactions take place in developing collaborative practices in globally distributed contexts. The findings reveal that collaborative practices within such settings tend not to follow from pre-set expectations of how agile practices should work, but are temporally emergent. Team members have to revise collaborative practices through an ongoing process of mutual "tuning" within their situated contexts, in order to achieve a gradual state of interactive stability or a steadiness of practices. The results demonstrate how actors address the challenges in developing shared understandings to drive forward the joint software development process across global locations and move towards supporting agility within the projects. The thesis presents a pluralistic conceptual framework called the Collaborative Tuning Approach, which aids in gaining critical insights of issues related to adapting agile practices and also demonstrates how collaborative practices can act as enabler to achieving agility in such settings. The framework explains the challenges the team members face and how these are overcome when attempting to modify practices and indeed how these evolve through an ongoing state of flux and uncertainty leading to hybrid agile practices.

APA, Harvard, Vancouver, ISO, and other styles

10

Hansson, Kristina. "User-Centered Extreme Programming Development : a combination of two software development process in theory and practice." Thesis, University West, Department of Technology, Mathematics and Computer Science, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-549.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Ullah, Malik Imran, and Waqar Ali Zaidi. "Quality Assurance Activities in Agile : Philosophy to Practice." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2145.

Full text

Abstract:

Quality assurance activities, in software development, are the backbone of whole project. These activities are not only responsible of product quality, but also for process quality. In conventional software development QA is a separate group of QA experts. As the trends of software development moved towards agile development, QA activities also got changed. In agile development most of these activities are performed by developers. Close people collaboration, onsite customer and Test Driven Development are the approaches in agile development to achieve better product quality. In this thesis we have presented the philosophical as well as practical angle QA in agile development. Mindset of agile development revolves around product quality but there is much work to be done to impart quality of process in agile development to get it standardized and more organized. QA activities remain centric and focused to testing. Practices like SPI and following some standards are lacking in agile methodologies. In this thesis we have proposed to inject an extra layer of QA in agile projects. Purpose of injecting and extra layer, is to use the knowledge of QA experts to achieve quality in development process that will result in higher level of product quality.

APA, Harvard, Vancouver, ISO, and other styles

12

Lárusdóttir, Marta Kristín. "Listen to your users : The effect of usability evaluation on software development practice." Licentiate thesis, Uppsala universitet, Avdelningen för människa-datorinteraktion, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-227611.

Full text

Abstract:

A vast majority of the people in the western world use software systems on daily basis for achieving their goals. To be able to do that each person needs to communicate what he or she wants to do to the system and receive a response. This communication needs to be easy for the user, especially when the system is new to him or her. Otherwise, the user either quits using the system; it takes a very long time or gets very irritated. A software team that is making new software needs to evaluate the usability of the system and various methods have been introduced in the literature to do that. My research focus in this thesis is on usability evaluation. I study particularly, how usability evaluation methods can be compared, what data should be gathered in usability evaluation to gain knowledge on how the software affects users who are getting new software for their daily work and how useful this data is to the recipients. Two experiments are reported in this thesis where results from using three different usability evaluation methods are compared. The main result from these two studies is that the think-aloud evaluation method should be used, if the goal of the evaluation is to gather as realistic information as possible on usability problems that the users will have when using the system. Furthermore four case studies are described in the thesis, in which usability evaluation was done by using the think-aloud method in co-operation with real users in their real work situation. These studies give much richer information on the actual use of the systems involved. The findings from one of these case studies indicate that the results from user observation done on a system that users have not seen before or used only for few days are rather similar to the results from usability evaluation done when users have used the system for a longer period. So the common practice of doing user observation on a software system that the participants have not seen before and then interpreting that the results will be the same for actual usage of the system when users will use the system for their real tasks for shorter or longer period is adequate.

APA, Harvard, Vancouver, ISO, and other styles

13

Noruwana, Nimrod. "How do South African organisations adopt agile methodologies for software development in practice?" Master's thesis, University of Cape Town, 2010. http://hdl.handle.net/11427/11708.

Full text

Abstract:

Includes bibliographical references (leaves 81-90).
Before organisations adopt agile methods, they need to ensure that they are prepared for the change. They also need to understand the problems they are trying to address by adopting agile methods. Agile methods deviate substantially from traditional methods of systems development (Tolfo & Wazlawick, 2008). This, therefore, makes it difficult for organisations to adopt agile methods even though they might see them attractive, as the adoption of such methods has an effect on organisational culture. If the culture cannot accommodate an agile approach, then the organisation will not be able to adopt agile (Lindvall, Basisli, Boehm, Costa, Dangle, Shull, Teseriero, Williams & Zelkowitz, 2002). Having a culture that is conducive to the adoption of agile methods is almost unanimously perceived by agile experts to be a necessary factor for the introduction of agile methodologies (eWorkshop, 2002). It is also important to understand the phases organisations go through during the process of adopting agile methods.

APA, Harvard, Vancouver, ISO, and other styles

14

Hebig, Regina. "Evolution of model-driven engineering settings in practice." Phd thesis, Universität Potsdam, 2014. http://opus.kobv.de/ubp/volltexte/2014/7076/.

Full text

Abstract:

Nowadays, software systems are getting more and more complex. To tackle this challenge most diverse techniques, such as design patterns, service oriented architectures (SOA), software development processes, and model-driven engineering (MDE), are used to improve productivity, while time to market and quality of the products stay stable. Multiple of these techniques are used in parallel to profit from their benefits. While the use of sophisticated software development processes is standard, today, MDE is just adopted in practice. However, research has shown that the application of MDE is not always successful. It is not fully understood when advantages of MDE can be used and to what degree MDE can also be disadvantageous for productivity. Further, when combining different techniques that aim to affect the same factor (e.g. productivity) the question arises whether these techniques really complement each other or, in contrast, compensate their effects. Due to that, there is the concrete question how MDE and other techniques, such as software development process, are interrelated. Both aspects (advantages and disadvantages for productivity as well as the interrelation to other techniques) need to be understood to identify risks relating to the productivity impact of MDE. Before studying MDE's impact on productivity, it is necessary to investigate the range of validity that can be reached for the results. This includes two questions. First, there is the question whether MDE's impact on productivity is similar for all approaches of adopting MDE in practice. Second, there is the question whether MDE's impact on productivity for an approach of using MDE in practice remains stable over time. The answers for both questions are crucial for handling risks of MDE, but also for the design of future studies on MDE success. This thesis addresses these questions with the goal to support adoption of MDE in future. To enable a differentiated discussion about MDE, the term MDE setting'' is introduced. MDE setting refers to the applied technical setting, i.e. the employed manual and automated activities, artifacts, languages, and tools. An MDE setting's possible impact on productivity is studied with a focus on changeability and the interrelation to software development processes. This is done by introducing a taxonomy of changeability concerns that might be affected by an MDE setting. Further, three MDE traits are identified and it is studied for which manifestations of these MDE traits software development processes are impacted. To enable the assessment and evaluation of an MDE setting's impacts, the Software Manufacture Model language is introduced. This is a process modeling language that allows to reason about how relations between (modeling) artifacts (e.g. models or code files) change during application of manual or automated development activities. On that basis, risk analysis techniques are provided. These techniques allow identifying changeability risks and assessing the manifestations of the MDE traits (and with it an MDE setting's impact on software development processes). To address the range of validity, MDE settings from practice and their evolution histories were capture in context of this thesis. First, this data is used to show that MDE settings cover the whole spectrum concerning their impact on changeability or interrelation to software development processes. Neither it is seldom that MDE settings are neutral for processes nor is it seldom that MDE settings have impact on processes. Similarly, the impact on changeability differs relevantly. Second, a taxonomy of evolution of MDE settings is introduced. In that context it is discussed to what extent different types of changes on an MDE setting can influence this MDE setting's impact on changeability and the interrelation to processes. The category of structural evolution, which can change these characteristics of an MDE setting, is identified. The captured MDE settings from practice are used to show that structural evolution exists and is common. In addition, some examples of structural evolution steps are collected that actually led to a change in the characteristics of the respective MDE settings. Two implications are: First, the assessed diversity of MDE settings evaluates the need for the analysis techniques that shall be presented in this thesis. Second, evolution is one explanation for the diversity of MDE settings in practice. To summarize, this thesis studies the nature and evolution of MDE settings in practice. As a result support for the adoption of MDE settings is provided in form of techniques for the identification of risks relating to productivity impacts.
Um die steigende Komplexität von Softwaresystemen beherrschen zu können, werden heutzutage unterschiedlichste Techniken gemeinsam eingesetzt. Beispiele sind, Design Pattern, Serviceorientierte Architekturen, Softwareentwicklungsprozesse oder modellgetriebene Entwicklung (MDE). Ziel dabei ist die Erhöhung der Produktivität, so dass Entwicklungsdauer und Qualität stabil bleiben können. Während hoch entwickelte Softwareentwicklungsprozesse heute schon standardmäßig genutzt werden, fangen Firmen gerade erst an MDE einzusetzen. Jedoch zeigen Studien, dass der erhoffte Erfolg von MDE nicht jedes Mal eintritt. So scheint es, dass noch kein ausreichendes Verständnis dafür existiert, inwiefern MDE auch Nachteile für die Produktivität bergen kann. Zusätzlich ist bei der Kombination von unterschiedlichen Techniken damit zu rechnen, dass die erreichten Effekte sich gegenseitig negieren anstatt sich zu ergänzen. Hier entsteht die Frage wie MDE und andere Techniken, wie Softwareentwicklungsprozesse, zusammenwirken. Beide Aspekte, der direkte Einfluss auf Produktivität und die Wechselwirkung mit anderen Techniken, müssen aber verstanden werden um den Risiken für den Produktivitätseinfluss von MDE zu identifizieren. Außerdem, muss auch die Generalisierbarkeit dieser Aspekte untersucht werden. Das betrifft die Fragen, ob der Produktivitätseinfluss bei jedem Einsatz von MDE gleich ist und ob der Produktivitätseinfluss über die Zeit stabil bleibt. Beide Fragen sind entscheidend, will man geeignete Risikobehandlung ermöglichen oder künftige Studien zum Erfolg von MDE planen. Diese Dissertation widmet sich der genannten Fragen. Dafür wird zuerst der Begriff MDE Setting'' eingeführt um eine differenzierte Betrachtung von MDE-Verwendungen zu ermöglichen. Ein MDE Setting ist dabei der technische Aufbau, inklusive manueller und automatische Aktivitäten, Artefakten, Sprachen und Werkzeugen. Welche Produktivitätseinflüsse von MDE Settings möglich sind, wird in der Dissertation mit Fokus auf Änderbarkeit und die Wechselwirkung mit Softwareentwicklungsprozessen betrachtet. Dafür wird einerseits eine Taxonomie von Changeability Concerns'' (potentiell betroffene Aspekte von Änderbarkeit) vorgestellt. Zusätzlich, werden drei MDE Traits'' (Charakteristika von MDE Settings die unterschiedlich ausgeprägt sein können) identifiziert. Es wird untersucht welche Ausprägungen dieser MDE Traits Einfluss auf Softwareentwicklungsprozesse haben können. Um die Erfassung und Bewertung dieser Einflüsse zu ermöglichen wird die Software Manufaktur Modell Sprache eingeführt. Diese Prozessmodellierungssprache ermöglicht eine Beschreibung, der Veränderungen von Artefaktbeziehungen während der Anwendung von Aktivitäten (z.B. Codegenerierung). Weiter werden auf Basis dieser Modelle, Analysetechniken eingeführt. Diese Analysetechniken erlauben es Risiken für bestimmte Changeability Concerns aufzudecken sowie die Ausprägung von MDE Traits zu erfassen (und damit den Einfluss auf Softwareentwicklungsprozesse). Um die Generalisierbarkeit der Ergebnisse zu studieren, wurden im Rahmen der Arbeit mehrere MDE Settings aus der Praxis sowie teilweise deren Evolutionshistorien erhoben. Daran wird gezeigt, dass MDE Settings sich in einem breiten Spektrum von Einflüssen auf Änderbarkeit und Prozesse bewegen. So ist es weder selten, dass ein MDE Setting neutral für Prozesse ist, noch, dass ein MDE Setting Einschränkungen für einen Prozess impliziert. Ähnlich breit gestreut ist der Einfluss auf die Änderbarkeit.Zusätzlich, wird diskutiert, inwiefern unterschiedliche Evolutionstypen den Einfluss eines MDE Settings auf Änderbarkeit und Prozesse verändern können. Diese Diskussion führt zur Identifikation der strukturellen Evolution'', die sich stark auf die genannten Charakteristika eines MDE Settings auswirken kann. Mithilfe der erfassten MDE Settings, wird gezeigt, dass strukturelle Evolution in der Praxis üblich ist. Schließlich, werden Beispiele aufgedeckt bei denen strukturelle Evolutionsschritte tatsächlich zu einer Änderung der Charakteristika des betreffenden MDE Settings geführt haben. Einerseits bestärkt die ermittelte Vielfalt den Bedarf nach Analysetechniken, wie sie in dieser Dissertation eingeführt werden. Zum Anderen erscheint es nun, dass Evolution zumindest zum Teil die unterschiedlichen Ausprägungen von MDE Settings erklärt. Zusammenfassend wird studiert wie MDE Settings und deren Evolution in der Praxis ausgeprägt sind. Als Ergebnis, werden Techniken zur Identifikation von Risiken für Produktivitätseinflüsse bereitgestellt um den Einsatz von MDE Settings zu unterstützen.

APA, Harvard, Vancouver, ISO, and other styles

15

Anderfelt, Victor. "From Mob Programming to Mob Development : User-Centred Design in Collaborative Software Development." Thesis, Uppsala universitet, Institutionen för informatik och media, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-414221.

Full text

Abstract:

Mob programming is a collaborative software development method that has gained increasing attention in both industry and research. While the focus of mob programming is on the benefits of teams programming together, there are also potential benefits for other aspects of the software development process. However, there is a lack of research on the use of the method outside the domain of programming. This study explores user-centred design (UCD) in mob programming through a case study of three software development teams at Sveriges Television, a Swedish public broadcasting company. Results show that the teams use the method for a variety of tasks in their daily work, calling for a rebranding of the method to mob development to encompass the broader scope. The integration of UCD is analysed through the principles of user-centred agile software development. The results indicate that a revision of these principles is needed to include the cross-functional and social factors that mob development adds to the software development process.

APA, Harvard, Vancouver, ISO, and other styles

16

de, Klerk Anneke. "The impact of event management software on the standards of practice within the event management sector in Cape Town." Thesis, Cape Peninsula University of Technology, 2013. http://hdl.handle.net/20.500.11838/1770.

Full text

Abstract:

Dissertation submitted in partial fulfilment of the requirements for the degree Master of Technology: Business Information Systems in the Faculty of Business at the Cape Peninsula University of Technology 2013
Event management is a very competitive field; therefore, event managers must work hard to distinguish themselves from other event management companies. One way of doing this is by using event management software to provide a holistic service which allows for better efficiency in the workplace. Technology is constantly changing; therefore it is imperative to keep abreast of trends in technology in order to improve one’s business and services. As an event manager, one should also consider what it takes in order to organise a successful event. The internationally accredited Event Management Body of Knowledge (EMBOK) has identified several areas that are crucial for an event manager to constantly control and manage in order to create an exceptional event, and these domain areas encompass a set of guidelines to ensure successful event projects. However, one should determine if the software is able to assist event managers with all the necessary features and functions required to organise a successful event as per the outline from EMBOK. The research aimed to analyse the software in terms of its capabilities and compare it to the EMBOK guidelines. The aim of the study was to further identify whether the software is able to complete all the tasks outlined by EMBOK and if not, what else would be needed to fill the gaps. The research also reviewed what impact the software has on events, that is, how it assists or improves tasks conducted or how it does not assist or becomes problematic in accomplishing the various phases and tasks. Qualitative research was selected as the appropriate method in order to gain an understanding of the events managers’ point of view with regards to the software. The research required detailed descriptions and narratives of the software as well as the experiences and opinions of the user. For this reason it was determined that qualitative research would best suit the needs of the research. In order to get detailed answers a semi-structured in-depth interview guide was used and the answers transcribed in order to analyse and get results. The software was selected based on its international usability and because of its use by South African government departments such as the Department of International Relations and Cooperation (DIRC) and the Department of Trade and Industry (DTI). The Cape Town-based individuals from the software’s client list were contacted and selected to participate in the study. The research was conducted with five representatives with previous experience of the software in the events industry in Cape Town. The interview guides were compiled with Likert-scale questions and open-ended questions. The questions were carefully compiled to link the functionality of the software and the criteria as identified by EMBOK. The answers were recorded and transcribed to analyse and determine the opinions of the representatives on the functionality and comprehensiveness of the software to be used for event management. The interviews established that the move towards technology is preferable as it creates efficiency in the workplace. The software assists in alleviating the workload of event managers; however, the interviews also indicated that the software does not always fulfil the requirements for all the tasks. Several tasks required the use of combinations of software; in some instances, the manager preferred to do the task manually. It was concluded that the software does not provide the level of flexibility required in event management, which is a vital criterion, owing to the field’s changing nature.

APA, Harvard, Vancouver, ISO, and other styles

17

Penmetsa, Sneha, and Navya Lingampalli. "An Empirical Analysis of the Usageand Impact of RequirementsAttributes on RequirementsEngineering Research and Practice : A mixed method approach." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13352.

Full text

Abstract:

Context: Requirement Engineering (RE) is one of the important phases inthe development of any software. Hence, there is a need to take much careon the elicitation and management of these requirements. Attributes playan important role in order to store and manage the important informationabout the requirements. There has been a lot of research performed inthe literature regarding the attributes of requirements engineering, but stillthere is a gap in the research that is concerned to requirement attributesin particular. Hence we focused more on identification and management ofthese requirement attributes. Objectives: In the current thesis, we focused mainly on the requirementattributes used in the companies and how they are managed. The majorobjectives we have framed in order to achieve our aim are: 1. To identify the publication trends in the literature of requirementsengineering that mainly focus on requirement attributes. 2. To identify the requirement attributes that are used by the softwarecompanies which includes both global attributes and project specificattributes. 3. To investigate how the requirement engineering models impact theselection of requirement attributes in companies. 4. To identify the phase and sequence of the requirement attributesbased on the four phases (elicitation, analysis, documentation and validation)of requirements engineering. 5. To investigate how the requirement attributes help in documentingand managing the continuous changes to requirements. Methods: In this thesis, we have performed Systematic Mapping Study(SMS),Systematic Literature Review (SLR) and Survey methods in order to achieveour aim and objectives. SLR is performed through the snowballing procedurebased on the guidelines of Wohlin[1].SMS is performed based on theguidelines of petersen et al.[2]. The main aim of the SMS is to identifythe publication trends in the literature on requirements engineering. Themain aim of SLR is to extract important information about the RE modelsand changes in requirements engineering. The main aim of the Survey is tovalidate the information retrieved from the SLR. Results: 83 requirement attributes were identified through the SLR outof which 15 attributes are in common. These 15 attributes are includedin the survey questionnaire. From these attributes, ID and description areidentified as most commonly used attributes from the survey. Publication trends related to requirement attributes are observed from the past 25 yearsrequirement attributes. From the survey, it is observed that there is a highimpact of RE models on requirement attributes. It is also observed thatmaximum number of attributes is stored in the form of documents and indatabases by the companies and the attributes are generally documented inanalysis phase and in specification phase. Results from the survey indicatedthat there is no particular sequence to document the attributes and theyare identified and documented based on the needs. Conclusions: This thesis lists different attributes that are used by thecompanies and also gives important information about the requirement attributesin detail that is close to the practical scenarios. It also gives scopefor further researches related to requirement attributes. This thesis helpthe practitioners to know the importance of consideration of requirementattributes in developing a project and its advantages. This work can beextended further by considering large number of attributes and retrievingresponses and opinions by large population.

APA, Harvard, Vancouver, ISO, and other styles

18

Ressin, Malte. "An empirical examination of interdisciplinary collaboration within the practice of localisation and development of international software." Thesis, University of West London, 2015. https://repository.uwl.ac.uk/id/eprint/2858/.

Full text

Abstract:

Acceptance on international markets is an important selling proposition for software products and a key to new markets. The adaptation of software products for specific markets is called software localisation. Practitioner reports and research suggests that activities of developers and translators do not mesh seamlessly, leading to problems such as disproportionate cost, lack of quality, and delayed product release. Yet, there is little research on localisation as a comprehensive activity and its human factors. This thesis examines how software localisation is handled in practice, how the localisation process is integrated into development, and how software developers and localisers work individually and collaboratively on international software. The research aims to understand how localisation issues around the above-mentioned classifications of cost, quality and time issues are caused. Qualitative and quantitative data is gathered through semi-structured interviews and an online survey. The interviews focused on the individual experiences of localisation and development professionals in a range of relevant roles. The online survey measured cultural competence, attitude towards and self-efficacy in localisation, and properties of localisation projects. Interviews were conducted and analysed following Straussian Grounded Theory. The survey was statistically analysed to test a number of hypotheses regarding differences between localisers and developers, as well as relationships between project properties and software quality. Results suggest gaps in knowledge, procedure and motivation between developers and translators, as well as a lack of cross-disciplinary knowledge and coordination. Further, a grounded theory of interdisciplinary collaboration in software localisation explains how collaboration strategies and conflicts reciprocally affect each other and are affected by external influences. A number of statistically significant differences between developers and localisers and the relevance of certain project properties to localisation were confirmed. The findings give new insights into interdisciplinary issues in the development of international software and suggest new ways to handle interdisciplinary collaboration in general.

APA, Harvard, Vancouver, ISO, and other styles

19

Frössler, Frank. "A practice theoretical analysis of real time collaboration technology: skype and sametime in software development projects." Göttingen Cuvillier, 2008. http://d-nb.info/990403025/04.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

DANTULURI, PAVAN KUMAR VARMA, and RAMAKRISHNA NETHI. "Investigating the Application of TDD Practice in Large-Scale Industries." Thesis, Blekinge Tekniska Högskola, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16805.

Full text

Abstract:

Context: Developer’s within software companies work chosen choice of software development process. Choice of a particular Software Development Process impacts the work environment, end-product and might also have financial risks due to delay in delivering in the final software product. Objectives: we are investigating if the TDD could impact/applicable in large-scale industries. To achieve that we first identify the strengths and challenges while using TDD in large-scale industries. Identify what modifications can enhance the impact of TDD in large-Scale industries. Methods: Systematic Literature Review (SLR) has been used to investigate the application of TDD in large-scale industries. Using the info from SLR we conducted an online survey for validating the results obtained from SLR. As a last step we have conducted semi structured interviews to gather information from developers across industries practicing and practiced TDD. The data from the qualitative and quantitative methods is triangulated by identifying the strengths, challenges and modifications in applying TDD to large-scale industries. Results: The findings from our SLR, results validated from Survey and responses from interview participants show that TDD have both strengths, Challenges and modifications. Conclusions: Some challenges encountered when using TDD in large-scale industries are Negative test cases, linking test case modules of several developers, Communication, Overall idea about project, lack of TDD knowledge for developers practicing TDD, also lack of automation tools supporting the development of unit test-cases.

APA, Harvard, Vancouver, ISO, and other styles

21

Ávila, Vinicius Porto de. "Noção de Knowing-in-practice : um estudo etnográfico em um ambiente de desenvolvimento de software." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2013. http://hdl.handle.net/10183/77756.

Full text

Abstract:

Ao longo das últimas décadas, um crescente número de autores tem enfatizado a centralidade e a importância estratégica do conhecimento dentro das organizações. Apesar dos esforços significativos de pesquisadores de vários domínios, a tarefa de compreender o conhecimento organizacional permanece controversa. Duas escolas de pensamento contrastantes desempenham funções importantes na formação do discurso dominante, tanto na esfera acadêmica quanto no mundo gerencial: a visão tecno-racional da gestão do conhecimento (knowledge management) e a perspectiva social construtivista do conhecimento na prática (knowing-in-practice). O conceito de knowing-in-practice está situado dentro de dois grandes eixos teóricos: aprendizagem organizacional e teorias baseadas em prática. Meu objetivo nesse estudo foi identificar e compreender o knowing-in-practice dos indivíduos organizacionais pesquisados a partir das práticas de trabalho. Para isso, além de identificar e descrever as práticas de trabalho do grupo, também foi preciso descrever e analisar as relações estabelecidas entre os integrantes da equipe. Para viabilizar a pesquisa, desenvolvi um estudo etnográfico, realizado entre os meses de setembro de 2011 e dezembro de 2012, em uma equipe de desenvolvedores de software, situada em Porto Alegre (RS). De modo complementar, esclareço algumas noções importantes da área de desenvolvimento de software, principalmente em relação às metodologias ágeis. Após descrever o espaço físico e o cotidiano dos profissionais, o movimento de entrada e saída de integrantes da equipe, a comunicação e as práticas dos desenvolvedores, identifico e analiso o knowing-in-practice da equipe, esse situado nos artefatos, na dinâmica das interações, na linguagem e no contexto físico. O knowing-in-practice está diretamente relacionado ao ato de fazer uma ação ou atividade, ele é produzido localmente de forma emergente, situada e ativa. O knowing se caracteriza como um fluxo constante de saberes e fazeres, por isso seu caráter dinâmico, temporário e presente através das práticas.
Over the past decades, a growing number of authors have emphasized the centrality and strategic importance of knowledge within organizations. Despite the significant efforts of researchers from various fields, the task of understanding organizational knowledge remains controversial. Two contrasting schools of thought play important roles in the formation of the dominant discourse, both in the academic and in the managerial world: the techno-rational view of knowledge management and the social constructivist perspective of knowledge in practice (knowing-in-practice.) The concept of knowing-in-practice is located within two major theoretical axes: organizational learning and practice-based theories. My goal in this study was to identify and understand the knowing-in-practice of the organizational individuals surveyed from their working practices. For this, besides to identify and describe the working practices of the group, was also necessary to describe and analyze the relationships established between team members. In order to enable the research, I conducted an ethnographic study, between the months of September 2011 and December 2012, in a team of software developers located in Porto Alegre (RS). In a complementary way, I clarify some important notions in the area of software development, particularly in relation to the agile methodologies. After describing the physical space and the everyday work of the professionals, the movement of incoming and outgoing team members, the communication and the working practices of the developers, I identify and analyze the knowing-in-practice of the team, located in the artifacts, in the dynamics of interactions, in the language and in the physical context. The knowing-in-practice is directly related to the act of making an action or activity; it is locally produced in an emergent, situated and active form. The knowing is characterized as a steady flow of know-hows, so its dynamic, temporary and through the practices nature.

APA, Harvard, Vancouver, ISO, and other styles

22

Moe, Nils Brede. "From Improving Processes To Improving Practice : Software Process Improvement in Transition from Plan-driven to Change-driven Development." Doctoral thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-13365.

Full text

Abstract:

As information technology’s role in the modern economy grows in importance, society makes exponentially greater demands on the diversity and quality of the software being produced. To develop high quality software, a good software development process is important. Software process improvement is about improving software quality and reliability, employee and client satisfaction, and return on investment. From the mid 1990s onwards, agile software development has been challenging the traditional (plandriven) view of software development. Agile software development accords primacy to uniqueness, ambiguity, complexity, and change, as opposed to prediction, verifiability, and control. The fundamental differences between traditional and agile software process improvement and the lack of research on these differences, gave rise to the overall problem addressed by this thesis: “How does Software Process Improvement work change with the introduction of agile software development in plan-driven companies?” This thesis focus on answering the following research questions: What characterizes SPI in plan-driven companies?, What characterizes SPI in change-driven companies?, and What are the key SPI challenges when implementing change-driven development? This thesis summarizes six years of studies in three small and medium-sized companies in Norway. The overall research method has been the same: case study and action research. Qualitative data in the form of interviews and participant observations constitute the most important source of evidence. Through a synthesis of contributions from twelve papers, ten key findings connected to the three research questions has been identified. To summarize, software process improvement in plan-driven companies is characterized by a participative bottom-up approach when creating company best practice, focus on project management support, high individual autonomy, and long cycles of single-loop learning; the goal of reflection on projects is to improve future projects. Software process improvement in changedriven companies is characterized by supporting the whole team and not only project management, practice is improved by short cycles of single-loop learning, and the goal of reflection in projects is to improve the current project. Finally, software process improvement challenges while implementing change-driven development are to increase redundancy to create conditions for the team to self-manage, to learn how to learn, and to perceive the adoption of change-driven development as a large, long-term organizational change project. The overall contribution of this thesis is that it shows empirically that the goal of software process improvement changes from improving processes to improving practice. However, achieving this goal is challenging when only part of the organization is involved in the change. Also contributions are deep knowledge about software process improvement in plan- and change-driven small- and medium-sized companies, knowledge about software process improvement challenges when implementing change-driven development, and increase the body of literature on longitudinal action research

APA, Harvard, Vancouver, ISO, and other styles

23

Silva, Ricardo Diniz Souza e. "The pedagogical use of Modellus software in collaborative practice of students to facilitate the development of meaningful learning kinematics." Universidade Federal do CearÃ, 2014. http://www.teses.ufc.br/tde_busca/arquivo.php?codArquivo=12473.

Full text

Abstract:

In recent decades the teaching and learning of physics in secondary schools have been widely discussed. In academia many proposed changes are described by experts. The use of computers as a teaching tool in education, favors the construction of physical knowledge, breaking stigmas where the teacher moves the position of the owner and developer of knowledge to mediator of learning. Observing the growing interest of young people by computers and the introduction of educational computing in schools, developed the thesis within the research line Digital Technologies in the Teaching of Science and Mathematics, in order to encourage educators and learners regarding the use of educational technologies Kinematics and learning. This research investigates facilitating the development of the learning process Cinematic using an educational approach that values learning articulating the operational and pedagogical use of the Software Modellus. So, we left for a pedagogical action, which was conceived and developed with the students of the 3rd year of high school, a state school in the city of Cascavel - Ce. To effect it was designed an educational approach , basing himself on some theoretical assumptions : David Ausubel (Theory of Meaningful Learning), Joseph Novak (Concept Maps), Armando Valente (The pedagogical use of computers, according to the constructivist approach) and Almeida (model learning development , constructed by the learner and aided by the interactive use of the computer ) . To proceed with the development of research, this researcher - educator adopted a qualitative research approach and characteristics of action research. To realize the pedagogical practice, we conducted 16 classes divided into two phases, totaling 32 class hours, the first being to diagnose prior knowledge using a traditional methodology with lectures, questionnaires, pre -and post - tests. The second phase aimed to develop a methodology for collaborative learning applied to the use of software to work Modellus the construction of charts, tables, and animations with students in the computer lab. We conclude that such a strategy favored constructivist learning and education process.
Nas Ãltimas dÃcadas o ensino e aprendizagem de FÃsica nas escolas secundÃrias tÃm sido amplamente discutidos. Nos meios acadÃmicos muitas propostas de mudanÃas sÃo apontadas por especialistas. A utilizaÃÃo do computador como ferramenta pedagÃgica na educaÃÃo, favorece a construÃÃo dos conhecimentos fÃsicos, quebrando estigmas onde o professor passa da posiÃÃo de dono do conhecimento para colaborador e mediador da aprendizagem. Ao observar o crescente interesse dos jovens por computadores e a introduÃÃo da informÃtica educativa nas escolas, desenvolvemos a dissertaÃÃo dentro da linha de pesquisa Tecnologias Digitais no Ensino de CiÃncias e MatemÃtica, com a finalidade de fomentar educadores e educandos, quanto ao uso das tecnologias de ensino e aprendizagem de CinemÃtica. A presente pesquisa investiga a facilitaÃÃo do desenvolvimento do processo de aprendizagem de CinemÃtica utilizando uma metodologia educacional que valoriza a aprendizagem articulando-se o uso operacional e pedagÃgico do Software Modellus. Assim, partimos para uma aÃÃo pedagÃgica, que foi concebida e desenvolvida junto aos alunos do 3Â ano do Ensino MÃdio, numa escola estadual da cidade de Cascavel-Ce. Para efetivÃ-la, foi concebida uma proposta educativa, fundamentando-se em alguns pressupostos teÃricos: David Ausubel (Teoria da Aprendizagem Significativa), Joseph Novak (Mapas Conceituais), Armando Valente (O uso pedagÃgico do computador, segundo a proposta construtivista) e Almeida (Modelo de desenvolvimento da aprendizagem, construÃdo pelo aluno e auxiliado pelo uso interativo do computador). Para proceder ao desenvolvimento da pesquisa, o presente pesquisador-educador adotou uma abordagem de pesquisa qualitativa e com caracterÃsticas de pesquisa-aÃÃo. Para efetivar a prÃtica pedagÃgica, realizamos 16 aulas, subdivididas em duas fases, totalizando 32 horas aulas, sendo a primeira para diagnosticar os conhecimentos prÃvios utilizando uma metodologia tradicional com aulas expositivas, aplicaÃÃo de questionÃrios, prÃ-teste e pÃs-testes. A segunda fase visava desenvolver uma metodologia de aprendizagem colaborativa aplicada ao uso do software Modellus para trabalhar a construÃÃo de grÃficos, tabelas e animaÃÃes junto aos alunos no laboratÃrio de informÃtica. ConcluÃmos que tal estratÃgia favoreceu a aprendizagem e o processo de educaÃÃo construtivista.

APA, Harvard, Vancouver, ISO, and other styles

24

Jiarou, Huang, and Ye Sigewei. "The management differences between self-organizing team and traditional team: Focus on communication and coordination." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-18867.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Vrazalic, Lejla. "Towards holistic human-computer interaction evaluation research and practice development and validation of the distributed usability evaluation method /." Access electronically, 2004. http://www.library.uow.edu.au/adt-NWU/public/adt-NWU20050106.151954/index.html.

Full text

Abstract:

Thesis (Ph.D.)--University of Wollongong, 2004.
Typescript. This thesis is subject to a 2 year embargo (16/09/2004 to 16/09/2006) and may only be viewed and copied with the permission of the author. For further information please Contact the Archivist. Includes bibliographical references: p. 360-374.

APA, Harvard, Vancouver, ISO, and other styles

26

Zhang, Guangyu. "Product Manager view on Practical Assumption Management Lifecycle about System Use." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-15406.

Full text

Abstract:

Context. In practice, software projects frequently fail in many fields, which causes the huge loss for the human being. Assumption faults are recognized as a main reason for the software project failures. As the world is changing fast, environment assumptions of software can be easily wrong. The daily assumption-related activities show not enough effectiveness and efficiency to deal with assumption faults. For example, no documenting of key assumptions, inappropriate assumption validation, lack of knowledge. In research, there is no empirical research about assumption management practice. Two assumption management frameworks were outlined. They both support the assumption formulation and assumption management. The formal assumption management framework provides an assumption-component mapping function to analyze assumption failures. Objectives. Our goal is figuring out how development team members handle environment assumptions today in practice and how they might handle them better tomorrow. To be specific, I test the applicability of the so far theoretical assumption management frameworks and investigate the assumption type, assumption formulation and assumption management in practical software development Methods. An interview-based survey was implemented with 6 product managers from Chinese software companies. They have rich experiences on assumption management and software development. I used directed content analysis to analyze the qualitative data. The result of the research is intended to be a static validation of the assumption management frameworks. Results. Interviewees consider that the assumption-component mapping function of the formal assumption management framework is useful in making decisions and analyzing the problems. However, using these frameworks takes too much effort. The functions of frameworks are covered by the development team members and the existing tools. Assumptions tend to be discovered when they frequently change and are important to the requirements. The main assumption types are user habit assumptions and quality attribute assumptions, which are both requirement assumptions. The user habit assumptions consist of name, description and value, while the quality attribute assumption formulation is name and value. The major assumption treatment activities are figuring out the value of assumptions, assumption monitoring, assumption validation and handling assumption failures. Assumption failures result in the loss of users and benefits. Assumption failures are always caused by the poor ability and experience of development team members. Conclusion. I create an assumption management model based on my result, and find out the advantages and disadvantages of the formal assumption management framework and semi-formal assumption management framework. The research could help improve the efficiency and effectiveness of assumption management practice. Also. The research can be treated as the starting point to study assumption management practice deeper.

APA, Harvard, Vancouver, ISO, and other styles

27

Ahlström, Catharina, and Kristina Fridensköld. "How to support and enhance communication : in a student software development project." Thesis, Blekinge Tekniska Högskola, Institutionen för arbetsvetenskap och medieteknik, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1624.

Full text

Abstract:

This report, in which we have put an emphasis on the word communication, is based on a student software development project conducted during spring 2002. We describe how the use of design tools plays a key role in supporting communication in group activities and to what extent communication can be supported and enhanced by tools such as mock-ups and metaphors in a group project. We also describe a design progress from initial sketches to a final mock-up of a GUI for a postcard demo application.
I denna rapport, som baserar sig på ett studentprojekt utfört under våren 2002, har vi fokuserat på ordet kommunikation. Vi beskriver hur användande av designverktyg kan spela en nyckelroll när det gäller att stöda kommunikation i gruppaktiviteter och i vilken utsträckning kommunikation kan stödas och förstärkas av verktyg som mockuper och metaforer. Vi beskriver också en designprogress från initiala skisser till färdig mockup av ett grafiskt användargränssnitt för en demoapplikation av en vykortstjänst.

APA, Harvard, Vancouver, ISO, and other styles

28

Ramraj, Varun. "Computational analysis of clinical practice guidelines : development of a software suite and document standard for storage and analysis of care maps." Thesis, University of British Columbia, 2010. http://hdl.handle.net/2429/28760.

Full text

Abstract:

Clinical Practice Guidelines (CPGs) guide optimal utilization of clinical delivery of health care through evidence-based medicine, where care procedures are rigorously evaluated and improved through the examination of evidence. Care mapping is the technique of using flowcharts to graphically capture CPGs as discrete, actionable steps. Health professionals can create and use care maps to expedite and ensure excellence in optimal process workflow in patient care. Analysis of care maps would provide insight into similarities and differences in care procedures. However, quantitative analysis of care maps is difficult to perform manually, and becomes impossible as the set of care maps for comparison increases. Computational methods could be employed to obtain the required quantitative data, but current document standards for developing, sharing and visualizing care maps are not rigorous enough for computational analysis to take place. By using Bioinformatics approaches, we can solve these problems. Firstly, we can develop a standard care map file format for electronic storage. Systems Biology Markup Language (SBML), a document format used to describe biological pathways, can be used to develop the required file format. This method works because care maps are notionally very similar to biological pathways. It allows use of multiple alignment algorithms (traditionally used to align and cluster biological pathways) with these transformed care maps in order to derive quantitative data. This project involved the development of a software suite that is able to generate care maps in the SBML format and align them using an existing global multiple pathway alignment algorithm. It is part of a larger project that examines efficacy of CPGs. This would allow for two important studies to be conducted: a breadth study across multiple EDs and a longitudinal study over time within a single ED to see how it has been able to implement and adapt to the CPGs. By utilizing Bioinformatics approaches in care mapping, two important objectives were realized: the creation of a document standard for care maps, and computational comparison and contrast of CPGs. This opens up the exciting new field of Translational Informatics, which applies existing Bioinformatics concepts to e-Health, e-Medicine and Health Informatics.

APA, Harvard, Vancouver, ISO, and other styles

29

Korraprolu, Srinivasa Abhilash. "Evaluation of the Relevance of Agile Maturity Models in the Industry : A Case Study." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16788.

Full text

Abstract:

Background. Over the years, agile software development has become increasingly popular in the software industry. One of the reasons is that agile development addressed the needs of the organisations better than the traditional models, such as the waterfall model. However, the textbook version of agile development still leaves something to be desired. This could be learnt by observing the implementation of agile methods/frameworks in the industry. The teams often customize agile methods to suit their context-specific needs. When teams in the industry decide to adopt the agile way of working, they are confronted by a choice¾either they have to implement all the agile practices at a time or adopt them over the time. The former choice has shown to come with risks and, therefore, was found that practitioners generally preferred the latter. However, agile practices are not independent, they have dependencies amongst them. A new approach to agile development emerged in the recent years known as Agile Maturity Models (AMMs). AMMs claim to offer a better path to agile adoption. In AMMs, the practices are typically introduced gradually in a particular order. However, these AMMs are multifarious and haven’t been sufficiently evaluated¾especially in the industry practice. Thus, they need to be evaluated in order to understand their relevance in the industry. Objectives. The goal is to evaluate the relevance of AMMs in the industry. By finding relevant AMMs, they could be used to alleviate the formation of agile teams and contribute toward their smoother functioning. By finding those that aren’t, this research could act as a cautionary to those practitioners who could potentially implement these AMMs and risk failure. The objectives are: identifying the agile practice dependencies in the AMMs; finding the agile practice dependencies in an agile team by conducting a case study in the industry; comparing the dependencies from the case study with those in the AMMs.  Methods. The agile maturity models were identified and analysed. A case study was conducted on an agile team to identify the dependencies between the agile practices in the industry practice. Semi-structured interviews were conducted with members of the agile team. Qualitative coding was used to analyse the collected data. The dependencies from the case study were compared with the AMMs to achieve the aim of this research. Results. It was found that dependencies between individual agile practices in the AMMs were almost never possible to be found. However, practices suggested in each maturity levels were derived. Hence, the dependencies were found in the maturity-level level. From the case study, 20 agile practice dependencies were found. 7/8 AMMs were found to be not relevant. 1 AMM couldn’t be evaluated as it heavily relied on the practitioner’s choices. Conclusions. The researchers could use the evaluation method presented in this thesis to conduct more such evaluations. By doing so, the dynamics present in the industry teams could be better understood. On their basis, relevant AMMs could be developed in the future. Such AMMs could help practitioners leverage agile development.

APA, Harvard, Vancouver, ISO, and other styles

30

Babb, Jeffry. "TOWARDS A REFLECTIVE-AGILE LEARNING MODEL AND METHOD IN THE CASE OF SMALL-SHOP SOFTWARE DEVELOPMENT: EVIDENCE FROM AN ACTION RESEARCH STUDY." VCU Scholars Compass, 2009. http://scholarscompass.vcu.edu/etd/1763.

Full text

Abstract:

The ascension and use of agile and lightweight software development methods have challenged extant software design and development paradigms; this is especially notable in the case of small-team and small-shop software development. In this dissertation, a Reflective-Agile Learning Method and Methodology (RALMM) for small-shop software development, is proposed to enhance communication and learning in the use of agile methods. The purpose of the inquiry in this dissertation pertains to: the nature of the professional practice of small team software development; the implications of the epistemology of Reflective Practice has for the professional practice of small-team software development; and whether the introduction of Reflective Practice to an extant agile methodology improves process, productivity and professional confidence for a small development team. This dissertation uses Dialogical Action Research (Mårtensson and Lee 2004), or Dialogical AR, a qualitative and interpretive research approach, to iteratively develop and refine the Reflective-Agile Learning Model and Method (RALMM). The proposed model and method also considers Hazzan and Tomayko’s (2002, 2004, and 2005) synthesis of Schön’s (1983, 1987) Reflective Practice and Extreme Programming (XP). RALMM is shaped by Argyris and Schön’s theories of practice (1974) and Organizational Learning (1978, 1996) and Schön’s ancillary work on generative metaphor (1979) and frames (Schön et al. 1994). The RALMM artifact was developed in a Dialogical AR Partnership using Lee’s (2007) framework for synthesizing design science and action research. The development and use of RALMM facilitated theorizing on the role of Reflective Practice in the successful use of agile methods. To assist in interpretation and analysis, the data collected during Dialogical AR cycles are analyzed using Strauss and Corbin’s (1998) Grounded Theory as a mode of analysis to guide in the coding and analysis of qualitative evidence from the research. As a result of this research, RALMM improved the practitioners’ processes and productivity. Furthermore, RALMM helped to establish, formalize and reinforce a team learning system for the continued development of the practitioners’ professional repertoire. Additionally, the iterative development of RALMM provides a basis for theorizing on Reflective Practice as an epistemology, paradigm, metaphor and frame of reference for the professional practice of small-shop software development.

APA, Harvard, Vancouver, ISO, and other styles

31

Sidenvall, Adrian. "Knowledge sharing in and between agile software development teams using knowledge practices : An interpretive case study at a medium-sized medical IT company." Thesis, Linköpings universitet, Industriell ekonomi, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-138950.

Full text

Abstract:

Agile methods for software development have become popular, especially since the agile manifesto was written in 2001. Many positive effects have been found in organizations using agile methods, but also several dangers. Communication and collaboration in teams is often mentioned as something that works well with the methods, but interactions between teams are often lacking. Since agile teams are cross-functional and focused on products rather than specializations, knowledge becomes spread out in the organization. Within teams, different members often have different deep knowledge, but instead have a lot of knowledge about their products in common. This allows them to discuss knowledge related to the product well, but limits their possibility to discuss advanced topics and experiences regarding their deep knowledge or specialization within their team. These issues are important to consider when applying agile methods in organizations, and the research about the issues is quite thin. In this research, I have taken an interpretive approach and carried out a case study at the development department of a medium-sized IT company providing large software systems for the healthcare industry, for which I have used the pseudonym MedTech. Three different teams have been studied through interviews with all members as well as observations of agile practices like daily meetings. Further, I have studied three different knowledge practices that MedTech uses to complement the creation and sharing of knowledge that happens in teams. These three complementary knowledge practices had different forms and handled knowledge in different ways. One was closely related to what literature often calls communities of practice, which are groups where members share an interest and interact to deepen their knowledge. In this practice at MedTech, meetings were used to discuss experiences and knowledge about topics within specific areas. Another was more focused on one-way communication through presentations and reading tips, spreading more basic knowledge to a wider audience. The third complementary knowledge practice let employees use 12 work hours every sixth week to do whatever they wanted that related to their knowledge, allowing them to e.g. explore new technologies and be creative or simply read up on some interesting topic. My results show that agile teams support some sharing and creation of knowledge, especially through having members work closely to each other and share experiences, and through practising their skills in daily work, with help from each other when necessary. Like other research has shown, there was however a lack of practices for interactions between teams in the agile methods. Such interactions were crucial since I found teams to be comparable to theories about communities of knowing, where teams create strong perspectives, the sharing of which is important for utilization and creation of knowledge. The complementary knowledge practice that related to communities of practice was shown to be good for connecting employees with similar specializations, who would normally be separated in different teams. This allowed for creation and sharing of knowledge as individuals needed to explain their experiences and could combine knowledge from different members of the community. The other two complementary knowledge practices were shown to be good for increasing motivation to create and share knowledge, and showing that the organization valued the knowledge of individuals.

APA, Harvard, Vancouver, ISO, and other styles

32

Redfearn, Brady Edwin. "User Experience Engineering Adoption and Practice: A Longitudinal Case Study." BYU ScholarsArchive, 2013. https://scholarsarchive.byu.edu/etd/3762.

Full text

Abstract:

User Experience Engineering (UxE) incorporates subject areas like usability, HCI, interaction experience, interaction design, "human factors", ergonomics", cognitive psychology", behavioral psychology and psychometrics", systems engineering", [and] "computer science," (Hartson, 1998). It has been suggested that UxE will be the main success factor in organizations as we enter the "loyalty decade" of software development, where the repeat usage of a product by a single customer will be the metric of product success (Alghamdi, 2010; Law & van Schaik, 2010, p. 313; Nielsen, 2008; Van Schaik & Ling, 2011). What is relatively unknown in the current academic literature is whether existing UxE methodologies are effective or not when placed in a longitudinal research context (Law & van Schaik, 2010). There is room for the exploration of the effects of long-term UxE practices in a real-world case study scenario. The problem, addressed in this study, is that a lack of the application of UxE-related processes and practices with an industrial partner had resulted in customer dissatisfaction and a loss of market share. A three-year case study was performed during which 10 UxE-related metrics were gathered and analyzed to measure the improvements in the design of the customer's experience that long-term UxE practices could bring to a small corporate enterprise. The changes that occurred from the corporate and customer's point of view were analyzed as the customer's experience evolved throughout this long-term UxE study. Finally, an analysis of the problems and issues that arose in the implementation of UxE principles during the application of long-term UxE processes was performed. First-hand training between the research team and company employees proved essential to the success of this project. Although a long-term UxE process was difficult to implement within the existing development practices of the industrial partner, a dramatic increase in customer satisfaction and customer engagement with the company system was found. UxE processes led to increased sales rates and decreased development costs in the long-term. All 10 metrics gathered throughout this study showed measurable improvements after long-term UxE processes and practices were adopted by the industrial partner.

APA, Harvard, Vancouver, ISO, and other styles

33

Weed, Amanda J. "Bridging Advertising and Public Relations Pedagogy and Practice: A Mixed-Methods Analysis of Education Objectives and Industry Needs." Ohio University / OhioLINK, 2018. http://rave.ohiolink.edu/etdc/view?acc_num=ohiou1529687320594136.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Bronson, Darren (Darren Frazier) 1970. "Best practices for evolutionary software development." Thesis, Massachusetts Institute of Technology, 1999. http://hdl.handle.net/1721.1/80490.

Full text

Abstract:

Thesis (M.B.A.)--Massachusetts Institute of Technology, Sloan School of Management; and, (S.M.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 1999.
Includes bibliographical references (p. 41-42).
by Darren Bronson.
S.M.
M.B.A.

APA, Harvard, Vancouver, ISO, and other styles

35

Fassler, Andreas. "Merging Task-Centered Social Work and Motivational Interviewing in Outpatient Medication Assisted Substance Abuse Treatment: Model Development for Social Work Practice." VCU Scholars Compass, 2007. http://hdl.handle.net/10156/1977.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Rae, Janet Lillian. "Conceptualising effective educational software development working practices." Thesis, Open University, 2007. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.446111.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

patney, vikas. "Software Engineering Best Practices for Parallel Computing Development." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsmiljö Informationsteknik, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-23803.

Full text

Abstract:

In today’s computer age, the numerical simulations are replacing the traditional laboratory experiments. Researchers around the world are using advanced computer software and multiprocessor computer technology to perform experiments, and analyse these simulation results to advance in their respective endeavours. With a wide variety of tools and technologies available, it could be a tedious and time taking task for a non-computer science researcher to choose appropriate methodologies for developing simulation software The research of this thesis addresses the use of Message Passing Interface (MPI) using object-oriented programming techniques and discusses the methodologies suitable to scientific computing, also, propose a customized software engineering development model.

APA, Harvard, Vancouver, ISO, and other styles

38

Abheeshta, Putta. "Comparative Analysis of Software Development Practices across Software Organisations : India and Sweden." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13355.

Full text

Abstract:

Context. System Development Methodologies (SDM’s) have been an area of intensive research in the field of software engineering. Different software organisations adopt different development methodologies and use different development practices. The frequency of usage of development practices and acceptance factors for adoption of development methodology are crucial for software organisations. The factors of acceptance and development practices differ across geographical locations. Many challenges have been presented in the literature with respect to the mismatch of the development practices across organisations while collaborating across organisations in distributed development. There is no considerable amount of research done in context of differences across development practices and acceptance factors for adoption of a particular development methodology. Objectives. The primary objectives of the research are to find out a) differences in (i) practice usage (ii) acceptance factors such as organisational, social and cultural b) explore the reasons for the differences and also investigate consequences of such differences while collaborating, across organisations located in India and Sweden. Methods. A literature review was conducted by searching in scientific databases for identifying common agile and plan-driven development practices and acceptance theories for development methodologies. Survey was conducted across organisations located in India and Sweden to find out the usage frequency of development practices and acceptance factors. Ten interviews were conducted to investigate, reasons for differences and consequences of differences from the software practitioners from organisations located in India and Sweden. Literature evidences were used to support the results collected from interviews. Results. From the survey, organisations in India have adopted a higher frequency of plan driven practices when compared to Sweden and agile practices were adopted at higher frequency in Sweden when compared to India. The number of organisations adopting "pure agile" methodologies have been significantly higher in Sweden. There was significant differences were found across the acceptance factors such as cultural, organisational, image and career factors between India and Sweden. The factors such as cultural, social, human, business and organisational factors are responsible for such differences across development practices and acceptance factors. Challenges related to communication, coordination and control were found due to the differences, while collaborating between Indian and Sweden sites. Conclusions. The study signifies the importance of identifying the frequency of development practices and also the acceptance factors responsible for adoption of development methodologies in the software organisations. The mismatch between these practices will led to various challenges. The study draws insights into various non-technical factors such as cultural, human, organisational, business and social while collaborating between organisations. Variations across these factors will lead to many coordination, communication and control issues. Keywords: Development Practices, Agile Development, Plan Driven Development, Acceptance Factors, Global Software Development.
-

APA, Harvard, Vancouver, ISO, and other styles

39

Iqbal, Ajmal, and Syed Shahid Abbas. "Communication Risks and Best practices in Global Software Development." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5090.

Full text

Abstract:

Context. Global Software Development (GSD) or Global Software Engineering (GSE) is defined as the plan of action in which the software development is performed under various boundaries, such as temporal, political, organizational and cultural [1,2] . The projects developed in globally distributed environment are containing more risks than projects developed in collocated environment because of different challenges such as temporal, geographical and socio-cultural distances [67]. In this thesis communication risks have been discussed along with their causes and effects that hinder the effectiveness of GSD projects. Moreover mitigation practices to resolve communication risks and their negative impacts are also discussed. Objectives. The study describes the identification of communication risks, their causes, effects and the practices to mitigate the risks from both literature and industrial perspectives. Some recommendations has also been discussed on the basis of these resulted communication risks and their mitigation practices. Methods. Detailed systematic literature review in order to collect the data from relevant empirical studies with respect to our scope has been conducted in the first phase. Studies were selected from various Electronic Data Sources (EDS) such as IEEE Xplore (IEEE), ACM Digital Library (ACM), Inspec (IS), Compendex (CD), ISI Web of Science (WoS), Cite Seer (CS), Google Scholar (GS), Science Direct (SD), Springer Link (SL), Wiley Inter Science (WIS), and Business Source Premier (BSP). In second phase 22 industrial interviews were conducted from 13 different multinational organizations. In third phase data analysis has been made based on the analysis of ground theory. On the basis of the codes of grounded theory, comparative analysis has been performed between literature and industrial settings. At the end of the thesis some recommendations has been provided in order to resolve communication risks in GSD. Results. As a result of systematic literature review 44 risks, 44 causes, 38 effects and 63 practices have been identified in GSD with respect to communication. 27 risks, 22 causes, 19 effects and 39 mitigation practices were identified from the industrial interviews. These risks, causes, effects and practices are not only described in this thesis but also mapped in relation to each other. At the end in comparative analysis the combined risks, causes, effects and practices were identified in tabular form. In total 47 risks, 45 causes, 39 effects and 65 mitigation practices were identified through this work. Conclusions. Communication plays a fundamental role in achieving the best practices in Global Software Engineering. This study points out the salient risks and limitations that hamper the process of smooth communication in geographically dispersed teams. The causes and effects of the mentioned risks are discussed in detail and a set of recommendations is provided to cope with those risks and to minimize their effect. The resultant set of recommendations is based on the best suitable practices which shall be followed by globally distributed organizations to achieve a fully communicated environment just like an in-house development setting.
0046760622684

APA, Harvard, Vancouver, ISO, and other styles

40

Tegegne, E. (Esubalew). "Software development methodologies and practices in startups:systematic literature review." Master's thesis, University of Oulu, 2018. http://urn.fi/URN:NBN:fi:oulu-201804041421.

Full text

Abstract:

Startups are newly created companies with little or no operating history and with limited resources and markets. Software startup are aiming to develop cutting edge software products under highly uncertain conditions, overcoming fast-growing markets under multiple influences. The significance of startups for economic development is growing in software business due to their ability to quickly create innovative technologies and their potential to scale to a wide market. The objective of this thesis is to identify and analyze existing scientific literature regarding software development methodologies and practices used in startup companies published between Jan 2006 and Dec 2016. A systematic literature review was conducted to explore the previous research on software development methods and practices in startups. A review protocol was developed and used as a procedure to conduct the review. The data was collected from three databases i.e. IEEE Xplore, Scopus, ISI Web of Science. This research identified 30 relevant primary studies out of a total 1249 papers to answer defined research questions. The result show that agile and Lean Startup methodologies are the most used methodologies across startup companies. Due to the flexible nature of startups, tailoring specific methodology is a common practice among startup companies. Additionally, a total of 95 software development work practices are extracted from primary studies. This thesis concludes that software development methodologies in startups are informal, customized, and highly dependent on the experience of project managers. It is also noted that principles related to these development methodologies are not strictly followed due to limited resources and uncertainty in the market. Furthermore, the results shows that software startups choose development methodologies and practices which are flexible, light-weight and allow rapid changes.

APA, Harvard, Vancouver, ISO, and other styles

41

Knaggs, Peter J. "Practical and theoretical aspects of FORTH software development." Thesis, Teesside University, 1993. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.386116.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Shahrezaei, Khashayar, and Pontus Holmström. "Software development from theory to practical machining techniques." Thesis, Luleå tekniska universitet, Institutionen för teknikvetenskap och matematik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:ltu:diva-79289.

Full text

Abstract:

In already optimized processes it may be challenging to find room for further improvement. The solution can be found in the advanced software and tools that support the digital manufacturing, all the way from planning and design to in-machining and machining analysis. This project the- sis focuses on developing a process methodology to transcribe Sandvik Coromant’s theories and knowledge about machining operation grooving into machine-readable formats. Various software development models have been analysed and a particular model inspired by the incremental and iterative process model was developed to match the context of this project. This project thesis describes the working methodology for gathering theories and translating them into machine-interpretable format. A working methodology developed in this project thesis succeeded in transcribing different human- readable theories such as people’s minds (experts within the field) and handbooks into a machine- interpretable format. The proposed algorithms for tool path generation was developed and imple- mented successfully through the integration of mathematical modelling. MATLAB and Siemens NX has been used to build a proof of concept environment.

APA, Harvard, Vancouver, ISO, and other styles

43

Acharya, Mod Nath, and Nazam Aslam. "Coordination in Global Software Development : Challenges, associated threats, and mitigating practices." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-6054.

Full text

Abstract:

Global Software Development (GSD) is an emerging trend in today's software world in which teams are geographically dispersed, either in close proximity or globally. GSD provides certain advantages to development companies like low development cost, access to cheap and skilled labour etc. This type of development is noted as a more risky and challenging as compared to projects developed with teams under same roof. Inherently the nature of GSD projects are cooperative in which many software developers work on a common project, share information and coordinate activities. Coordination is a fundamental part of software development. GSD comprises different types of development systems i.e. insourcing, outsourcing, nearshoring, or farshoring, whatever the types of development systems selected by a company there exist the challenges to coordination. Therefore the knowledge of potential challenges, associated threats to coordination and practices to mitigate them plays a vital role for running a successful global project.

APA, Harvard, Vancouver, ISO, and other styles

44

Servadei, Giacomo. "The Scrum approach to software development." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2015. http://amslaurea.unibo.it/8255/.

Full text

Abstract:

Agile methodologies have become the standard approach to software development. The most popular and used one is Scrum. Scrum is a very simple and flexible framework that respond to unpredictability in a really effective way. However, his implementation must be correct, and since Scrum tells you what to do but not how to do it, this is not trivial. In this thesis I will describe the Scrum Framework, how to implement it and a tool that can help to do this. The thesis is divided into three parts. The first part is called Scrum. Here I will introduce the framework itself, its key concepts and its components. In Scrum there are three components: roles, meetings and artifacts. Each of these is meant to accomplish a series of specific tasks. After describing the “what to do”, in the second part, Best Practices, I will focus on the “how to do it”. For example, how to decide which items should be included in the next sprint, how to estimate tasks, and how should the team workspace be. Finally, in the third part called Tools, I will introduce Visual Studio Online, a cloud service from Microsoft that offers Git and TFVC repositories and the opportunity to manage projects with Scrum. == Versione italiana: I metodi Agile sono diventati l’approccio standard per lo sviluppo di software. Il più famoso ed utilizzato è Scrum. Scrum è un framework molto semplice e flessibile che risponde ai cambiamenti in una maniera molto efficace. La sua implementazione deve però essere corretta, e visto che Scrum ci dice cosa fare ma non come farlo, questo non risulta essere immediato. In questa tesi descriverò Scrum, come implementarlo ed uno strumento che ci può aiutare a farlo. La tesi è divisa in tre parti. La prima parte è chiamata Scrum. Qui introdurrò il framework, i suoi concetti base e le sue componenti. In Scrum ci sono tre componenti: i ruoli, i meeting e gli artifact. Ognuno di questi è studiato per svolgere una serie di compiti specifici. Dopo aver descritto il “cosa fare”, nella seconda parte, Best Practices, mi concentrerò sul “come farlo”. Ad esempio, come decidere quali oggetti includere nella prossima sprint, come stimare ogni task e come dovrebbe essere il luogo di lavoro del team. Infine, nella terza parte chiamata Tools, introdurrò Visual Studio Online, un servizio cloud della Microsoft che offre repository Git e TFVC e l’opportunità di gestire un progetto con Scrum.

APA, Harvard, Vancouver, ISO, and other styles

45

Mullins, Thomas E. "Impact of adopting commercial practices in software development and maintenance." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1995. http://handle.dtic.mil/100.2/ADA294481.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Suomela, R. (Riku). "Using lean principles to improve software development practices in a large-scale software intensive company." Master's thesis, University of Oulu, 2015. http://urn.fi/URN:NBN:fi:oulu-201511212155.

Full text

Abstract:

Lean software development is the result of adapting lean principles from the manufacturing context to the software development domain. Recently, the various applications of lean software development have been studied but more empirical evidence is needed, especially from the practitioners’ point of view. Firstly, this thesis provides answers for the understanding of lean software development from the practitioners’ point of view. Secondly, this thesis provides answers on the opportunities and barriers in applying the lean software development. In order to study this, a case study was conducted in a large-scale software intensive company. Focus groups were conducted to collect qualitative data. Studying the understanding of lean software development showed that four of the seven lean software development principles were identifiable from the discussion in the focus group sessions. The difference between agile and lean was recognized. The opportunities in achieving a culture of continuous improvement and involving people in the transformation were found and can be also identified from the existing research. Some new opportunities were also identified, such as using informal code-reviews as a practice in development and focusing improvements on the activities that consume the most time in the day-to-day work. The barriers that were found, such as avoiding sub-optimization, facilitation of improvement and having time to experiment, can also be identified from the existing research. Some of the barriers not identifiable from the existing research were the lack of quality thinking and varying standards in gate keeping. The findings of this study were presented in the case company with positive feedback and were discussed to be included into future improvement initiatives. This study also identified the power of the focus group method as a tool that could be used to drive improvement work. Suggested directions for future research include studying lean software development in a similar case study and taking a look at the possibilities of using focus group method as a tool for driving improvement initiatives in software development companies.

APA, Harvard, Vancouver, ISO, and other styles

47

Shahriyari, Salman. "Distributed Agile Development; Suitability, Challenges and Practices." Thesis, Högskolan i Borås, Institutionen Handels- och IT-högskolan, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-17340.

Full text

Abstract:

Uncertainty in software development and business environment and the need to increase thespeed of development have driven organizations to search for methods that are responsive toboth change and speed. Providing iterative development, agile development involvescustomers and users through different phases of development, and delivers frequent releasesof software to customer while receives the corresponding feedback. Using this approach, agiledevelopment thus aims at addressing mentioned issues of speed and uncertainty whiledeveloping only what customer needs from the beginning of the project. On the other hand,distributed software development is used in many organizations to reach global talent andglobal market. The problems associated with distributed software development such as lack ofenough communication and team coherency, have forced project managers to combine it withagile to mitigate these social problems. This study focuses on distributed agile development,its suitability for a typical project and its challenges and deficiencies. Text analysis andinterviews using qualitative methods are used in this scientific research work. From thetheoretical view point, different text covering agile methodology, distributed development andcombination of them were considered. This study covered two parts: first, an evaluation ofagile and distributed development opportunities and problems to help determine whether ornot distributed development is suitable for a project and second, considering the challengesonce starting to use this method and practices required to regard them. For the empirical part,the focus was put on Volvo IT employees by having seven interviews with members who arecurrently active in distributed agile development. These interviews were used to compare andverify the finding of the theoretical part. The results of the study were categorized into twosections. In the first part, important elements required to verify the suitability of using thismethod are provided. The recommended factors for this evaluation are cost, productivity,customer, team structure, etc. In the second part, the challenges of using distributed agiledevelopment were categorized into four parts: (a) challenges of selected agile method, whichthe focus in this study is Scrum, (b) challenges with time-zone differences, (c) communicationchallenges and (d) finally team building challenges. The required practices to address thesechallenges were also provided.
Program: Masterutbildning i Informatik

APA, Harvard, Vancouver, ISO, and other styles

48

Garrigós, Janina, and Pau Minoves. "Adopting Free/Libre/Open Source Software Practices, Techniques and Methods for Industrial Use." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4184.

Full text

Abstract:

Today’s software companies face the challenges of highly distributed development projects and constant changing requirements. To be competitive, the software time to market has to be reduced as much as possible while keeping the expected quality. Development methodologies try to address this challenges by introducing new practices, techniques and methods for communication, requirements management, quality assurance, etc. This thesis proposes the adoption of relevant Free/Libre/Open Source Software practices to improve industrial developments. Many FLOSS projects have proven very successful, producing high quality products with steady frequent releases. The selection of the FLOSS best practices that would benefit industrial developments, and its adaptation for a corporate environment is the aim of this study. To achieve this goal, a framework to compare FLOSS and industrial development methodologies has been created and executed. Three successful FLOSS projects where selected as study targets, as well as two Ericsson’s projects. The framework served to identify FLOSS methodology strengths and compare them with the Ericsson projects. Analysing the significant differences resulting from this comparison, FLOSS best practices were tailored to fit industrial development environments. The final results of the thesis are six adoption opportunities that aim to improve software quality and overall development productivity while increasing practitioners’ motivation and commitment.

APA, Harvard, Vancouver, ISO, and other styles

49

Shoshah, Mohammad. "Third-Party Development Practices for Mobile Platforms." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsmiljö Informationsteknik, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-19789.

Full text

Abstract:

Information Technology (IT) evolution in the recent decades has been able to grow the mobility of the end-user. A contributing factor has impacted and improved the smartphone area. This, in turn, has changed end-users’ expectations and experiences in the recent years in terms of available services, which have made mobile applications (apps) to find their place in daily life. In line with the significant growth of smartphones, as the iPhone and Android phones, is also the development of mobile applications exploded. Mobile use has - with this - fundamentally changed and much of what customers used to do on the computer, they do now on their mobile. It makes of course requires that third-parties have a mobile presence and correct utilization, this new arena enormous business opportunities. Hence, as mobile devices become a more visible business tool, it becomes important for organizations to develop applications to meet customer needs and stay competitive. Third-party development is relevantly in the core of software development nowadays. The introduction of smartphones and tablet devices, the associated products, and services in the form of apps has significantly changed software developments practices for developers. The aim of this research formulated to study the development process and practices associated with third-parties and their effects on dealing with various mobile platforms and boundary resources (SKDs and APIs). Qualitative study and exploratory design are extensively conducted for data collection and analysis. Primary data is gathered based on experiences, opinions, and insights from the experts in the subject, and secondary data is gathered from literature, which constantly supports the primary data and ensures the research credibility. The main contribution and results of this study are the factors and development process that third-party developers take into consideration when developing apps for iOS and Android such as ecosystem, programing language, platform, programing model, tools, development process model, supply chain, and submission apps. The success of the digital ecosystems and platform knowledge adopted by Apple and Google has gained a lot of attention from developers in the last years concerning mobile application development. This, in turn, was the key factor of their success at the smartphones market and the portal for developers from all the world.

APA, Harvard, Vancouver, ISO, and other styles

50

Lwakatare, L. E. (Lucy Ellen). "DevOps adoption and implementation in software development practice:concept, practices, benefits and challenges." Doctoral thesis, Oulun yliopisto, 2017. http://urn.fi/urn:isbn:9789526217116.

Full text

Abstract:

Abstract In the last decade, the software industry has been marked by a growing trend of software companies’ ability to deploy new software features fast and frequently in short release cycle times. The companies’ software release cycles have been shortened to hours and minutes rather than months. To enable the transformation towards short release cycle times, companies have adopted several different strategies, including the DevOps approach. DevOps in the software industry emerged to represent a professional movement emphasising the collaboration between software development and operations. In practice, DevOps affects the company culture, processes, products, associated technologies and organisational structures used in software development and operations processes. The multifaceted nature of DevOps makes the concept ambiguous and difficult for software companies to adopt as there are many different paths to its adoption. The purpose of the thesis is to provide detailed description of the adoption and implementation of DevOps in software development comprehending the DevOps concept definition, and its practices, benefits and challenges. The research was performed by systematically reviewing the literature, multi-vocal documents and making qualitative inquiries among software practitioners; and based on that the consolidated body of knowledge of DevOps was constructed. The key finding of the research is that the DevOps approach includes an automated software deployment mechanism focusing on the rapid and repeatable release of software changes and automated management of operational infrastructure. The adoption and implementation of DevOps practices are prominent in software companies that use cloud computing technology, while its adoption is challenging in the embedded system domain. DevOps is not a silver bullet; challenges pertaining to the management of infrastructures due to legacy technologies still persist. The key lesson learned in the adoption and implementation of DevOps is that the software operational infrastructure is no longer considered separate from the development of software features; and this is achieved by having software development and operations teams jointly working together
Tiivistelmä Viimeisen vuosikymmenen aikana ohjelmistoteollisuudessa on ollut kasvavana trendinä ohjelmistotalojen lisääntyvä kyky toimittaa ohjelmistomuutoksia nopeasti ja usein toistuvina päivityksinä. Yritysten ohjelmistotoimitus- ja päivitysjaksot ovat lyhentyneet kuukausista tunneiksi ja jopa minuuteiksi. Yritykset ovat ottaneet käyttöön useita erilaisia toimintatapoja kyetäkseen muuttamaan toimintaansa lyhyen aikavälin ohjelmistopäivityksiin kykeneväksi, joista yksi viimeisimmistä on DevOps (saumaton ohjelmiston kehittäminen ja käyttö). Ohjelmistotuotannossa DevOps syntyi ohjelmistoteollisuudessa ammattilaisten alkaessa painottaa ohjelmistojen kehittämisen ja käytön yhteistyön tärkeyttä. Käytännössä DevOpsilla on vaikutusta ohjelmisto-organisaation toimintakulttuuriin, prosesseihin, tuotteisiin, sekä teknologioihin ja organisaatiorakenteisiin, joita käytetään ohjelmistokehityksessä ja käyttöönottoprosessissa. DevOpsin käsitteen moniulotteisuudesta johtuen käsitteen sisältö jää usein epäselväksi ja samalla sen mukainen toiminta vaikeasti käyttöön otettavaksi ohjelmistoyrityksissä, koska toteutus on mahdollista tehdä monella eri tavalla. Tämän väitöksen tarkoituksena on antaa selkeä kuvaus DevOpsista ja sen toteutuksesta ohjelmistokehityksessä niin, että sen käsite, ja käytännöt, sekä sen tarjoamat edut ja haasteet tulevat ymmärretyiksi. Tutkimuksessa suoritettiin systemaattinen kirjallisuuskatsaus tieteellisiin julkaisuihin ja muihin lähinnä käytännön kokemuksiin pohjautuviin lähteisiin, suoritettiin kvalitatiiviset kyselytutkimukset, joiden kohteena olivat ohjelmistoammattilaiset, sekä muodostettiin näiden pohjalta saumattoman ohjelmistokehityksen ja käytön yhtenäinen tietämyskanta. Tutkimuksen keskeinen tulos on, että DevOps-lähestymistapa sisältää automaattisen ohjelmiston käyttöönottomekanismin, joka keskittyy nopeiden ja toistettavien ohjelmistomuutosten käyttöönottoon ja sitä tukevan operatiivisen infrastruktuurin hallintaan. DevOpsin omaksuminen ja käyttöönotto ovat näkyvästi esillä pilvipalvelinteknologiaa käyttävissä ohjelmistoyrityksissä, kun taas sen käyttöönotto on haastavaa sulautettujen järjestelmien alueella. DevOps ei ole mikään ’hopealuoti’, vaan sisältää erityisesti infrastruktuurien hallintaan liittyviä haasteita, jotka johtuvat edelleen käytössä olevista vanhoista tekniikoista. Keskeisin oppima DevOpsin omaksumisesta ja soveltamisesta käytäntöön on, että ohjelmistojen käyttöinfrastruktuuria ei enää tarkastella erillään ohjelmistojen kehittämisestä, vaan ne toimivat saumattomassa yhteistyössä keskenään

APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic 'Software development practice'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles