Gotowa bibliografia na temat „Software development practice”
Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych
Spis treści
Zobacz listy aktualnych artykułów, książek, rozpraw, streszczeń i innych źródeł naukowych na temat „Software development practice”.
Przycisk „Dodaj do bibliografii” jest dostępny obok każdej pracy w bibliografii. Użyj go – a my automatycznie utworzymy odniesienie bibliograficzne do wybranej pracy w stylu cytowania, którego potrzebujesz: APA, MLA, Harvard, Chicago, Vancouver itp.
Możesz również pobrać pełny tekst publikacji naukowej w formacie „.pdf” i przeczytać adnotację do pracy online, jeśli odpowiednie parametry są dostępne w metadanych.
Artykuły w czasopismach na temat "Software development practice"
1
Khan, AK. "Amalgamation of Personal Software Process in Software Development Practice". Science, Technology and Arts Research Journal 1, nr 2 (16.12.2013): 59. http://dx.doi.org/10.4314/star.v1i2.98784.
Pełny tekst źródła
2
Linkevics, Gusts. "Adopting to Agile Software Development". Applied Computer Systems 16, nr 1 (1.12.2014): 64–70. http://dx.doi.org/10.1515/acss-2014-0014.
Pełny tekst źródłaStreszczenie:
Abstract Agile software development can be made successful, but there is no well-defined way how to achieve this. The problem is that the successful adoption of agile methods and practices is a complex process and this process should be customizable for a particular organization or a team. This research focuses on identification of agile methods and practices. Result of the research is the ranking of agile methods, practices and their usage trends. As some terms of agile software development are interpreted differently in different organizations and teams, terminology used is analyzed. Results of the research can be used as a reference material for those who are planning to adopt agile methods or are looking for the next agile practice to implement. Results will be used for the development of an expert system to support agile adoption.
3
Humayun, Mamoona, Mahmood Niazi, Mohammed Assiri i Mariem Haoues. "Secure Global Software Development: A Practitioners’ Perspective". Applied Sciences 13, nr 4 (14.02.2023): 2465. http://dx.doi.org/10.3390/app13042465.
Pełny tekst źródłaStreszczenie:
Global software development (GSD) is rapidly becoming standard practice in the software industry due to its many potential benefits. However, one of the biggest challenges in GSD projects is to explicitly include security in the different phases of the global software development life cycle (GSDLC). To make GSD projects secure and successful, it is necessary to identify secure software development (SSD) practices vital to GSD project success. This article aims to identify SSD practices critical for GSD projects. To do this, we selected 36 security practices vital to the security of non-GSD projects from existing scientific and grey literature on software security. From the identified security practices, we shortlisted the security practices which are critical for GSD projects based on practitioners’ opinions using an online survey. Fifty-four GSD practitioners participated in this survey. Participants who evaluated these practices were asked to score each SSD practice on a four-point scale to indicate its relevance to GSD projects. The results obtained from the survey uncovered critical SSD practices that are primarily applicable to GSD projects. Our findings reveal variations of opinion among GSD practitioners with varying experience and company size regarding the importance of selected security practices for GSD. According to study findings, 16/36 practices are critical for GSD projects. These identified security practices belong to various phases of GSDLC.
4
Conger, Sue. "Software Development Life Cycles and Methodologies". International Journal of Information Technologies and Systems Approach 4, nr 1 (styczeń 2011): 1–22. http://dx.doi.org/10.4018/jitsa.2011010101.
Pełny tekst źródłaStreszczenie:
Information Systems as a discipline has generated thousands of research papers, yet the practice still suffers from poor-quality applications. This paper evaluates the current state of application development, finding practice wanting in a number of areas. Changes recommended to fix historical shortcomings include improved management attention to risk management, testing, and detailed work practices. In addition, for industry’s move to services orientation, recommended changes include development of usable interfaces and a view of applications as embedded in the larger business services in which they function. These business services relate to both services provided to parent-organization customers as well as services provided by the information technology organization to its constituents. Because of this shift toward service orientation, more emphasis on usability, applications, testing, and improvement of underlying process quality are needed. The shift to services can be facilitated by adopting tenets of IT service management and user-centered design and by attending to service delivery during application development.
5
Henry, O. Nwaete. "Secure software development: industrial practice - a review". i-manager’s Journal on Software Engineering 16, nr 3 (2022): 60. http://dx.doi.org/10.26634/jse.16.3.18674.
Pełny tekst źródłaStreszczenie:
The current state of application assets with respect to their development, functionality, scalability, user friendliness, and compatibility with legacy systems has witnessed an unprecedented degree of positive improvements. This induced increase in productivity and value has been a product of the technological innovations within and around the software development landscape. Owing to specific software development practices including software reusability, Object Oriented Programming (OOP), encapsulation, and portability, all sectors of the economy have come to embrace software products that have helped to drive business transactions. Nonetheless, the proliferation of software which has driven up the velocity, veracity and volume of data associated with transactions has become a goldmine for grabs. Hackers and adversaries alike have thus capitalized on this development to exploit the potential threats and vulnerabilities associated with software products. Insecure software is global issue, and one that impacts individuals, organizations and governments. Data loss is both a security and privacy issue, with compliance, regulatory and legal concerns, and bad actors are relentless in their efforts to steal, deface, alter/manipulate, destroy, and compromise software systems. Organizations should therefore embrace secure code principles, threat modeling, and institute a Secure Software Development Lifecycle (SSDLC) practice that will aid the embedment of security into the development phase, to contain the risks, threats, and vulnerabilities that are inherent in software development. This paper demonstrates an effort to provide and arm organizations with the necessary tools, processes, and mechanisms that can be leveraged to combat cyber-threats and enforce Information Assurance (IA) within and around enterprise application assets. Beginning with an overview of the contemporary software development practices witnessed in diverse organizations, including financial, energy, aviation, commerce, nuclear, defense, and several other Critical Infrastructure (CI) organizations, the tenets of a composite, structured and robust. SSDLC has been presented to promote a defense-in-depth security for enterprise organizations.
6
Bencina, Ross. "Creative software development: reflections on AudioMulch practice". Digital Creativity 17, nr 1 (styczeń 2006): 11–24. http://dx.doi.org/10.1080/14626260600665660.
Pełny tekst źródła
7
Knop, Sven Erik. "Transparent software development between theory and practice". ATZelektronik worldwide 13, nr 2 (kwiecień 2018): 56–59. http://dx.doi.org/10.1007/s38314-018-0013-1.
Pełny tekst źródła
8
Prikladnicki, Rafael, Jorge Luis Nicolas Audy i Roberto Evaristo. "Global software development in practice lessons learned". Software Process: Improvement and Practice 8, nr 4 (październik 2003): 267–81. http://dx.doi.org/10.1002/spip.188.
Pełny tekst źródła
9
Jankovic, Marko, Slavko Zitnik i Marko Bajec. "Reconstructing de facto software development methods". Computer Science and Information Systems 16, nr 1 (2019): 75–104. http://dx.doi.org/10.2298/csis180226038j.
Pełny tekst źródłaStreszczenie:
Software development is a complex process that requires disciplined engineering approaches. Empirical studies show that companies still don?t document their development practice, or if they do, these are not up-to-date and do not reflect how they really develop software. The main objective of this paper is to propose an approach that can help companies in documenting their real development practice. Comparing to existing approaches that require substantial effort on the side of project members, our approach extracts information on development practice directly from software repositories. Five companies have been studied to identify information that can be retrieved from software repositories. Based on this, an approach to reconstruct development practice has been developed. The approach has been evaluated on a real software repository shared by an additional company. The results confirm that software repository information suffice for the reconstruction of various aspects of development process, i.e. disciplines, activities, roles, and artifacts.
10
ADLER, PAUL S. "PRACTICE AND PROCESS: THE SOCIALIZATION OF SOFTWARE DEVELOPMENT." Academy of Management Proceedings 2003, nr 1 (sierpień 2003): C1—C6. http://dx.doi.org/10.5465/ambpp.2003.13793117.
Pełny tekst źródłaRozprawy doktorskie na temat "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.
Pełny tekst źródłaStreszczenie:
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.
2
Cater-Steel, Aileen Patricia, i 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.
Pełny tekst źródłaStreszczenie:
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.
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.
Pełny tekst źródłaStreszczenie:
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
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.
Pełny tekst źródłaStreszczenie:
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.
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.
Pełny tekst źródłaStreszczenie:
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 adaptationTiivistelmä 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
6
Heyer, Tim. "Semantic Inspection of Software Artifacts From Theory to Practice". Doctoral thesis, Linköping : Univ, 2001. http://www.ep.liu.se/diss/science_technology/07/25/index.html.
Pełny tekst źródła
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.
Pełny tekst źródłaStreszczenie:
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.
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.
Pełny tekst źródłaStreszczenie:
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.
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.
Pełny tekst źródłaStreszczenie:
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.
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.
Pełny tekst źródłaKsiążki na temat "Software development practice"
1
Software development and professional practice. [New York, N.Y.]: Apress, 2011.
Znajdź pełny tekst źródła
2
Dooley, John. Software Development and Professional Practice. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-3802-7.
Pełny tekst źródła
3
Vliet, J. C. van. Software engineering: Principles and practice. Chichester: Wiley, 1993.
Znajdź pełny tekst źródła
4
1951-, Haug Michael, red. Software best practice. Berlin: Springer, 2001.
Znajdź pełny tekst źródła
5
1961-, Müller Wolfgang, red. Hardware-dependent software: Principles and practice. Dordrecht: Springer, 2009.
Znajdź pełny tekst źródła
6
Software engineering: Principles and practice. Wyd. 2. Chichester [England]: John Wiley, 2000.
Znajdź pełny tekst źródła
7
Software engineering: Principles and practice. Wyd. 3. Hoboken, NJ: John Wiley & Sons, 2008.
Znajdź pełny tekst źródła
8
Software prototyping: Adoption, practice, and management. London: McGraw-Hill, 1991.
Znajdź pełny tekst źródła
9
H, Madhavji Nazim, Fernandez Ramil Juan Carlos i Perry Dewayne E, red. Software evolution and feedback: Theory and practice. Chichester, England: John Wiley & Sons, 2006.
Znajdź pełny tekst źródła
10
Oetinger, Ralf. Benutzergerechte Software-Entwicklung. Berlin: Springer, 1988.
Znajdź pełny tekst źródłaCzęści książek na temat "Software development practice"
1
Calefato, Fabio, i Filippo Lanubile. "Practice: Collaborative Development Environments". W Global Software and IT, 109–23. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2011. http://dx.doi.org/10.1002/9781118135105.ch15.
Pełny tekst źródła
2
Duchowski, Andrew T. "System Software Development". W Eye Tracking Methodology: Theory and Practice, 77–95. London: Springer London, 2003. http://dx.doi.org/10.1007/978-1-4471-3750-4_7.
Pełny tekst źródła
3
Dooley, John. "Software Architecture". W Software Development and Professional Practice, 47–58. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-3802-7_5.
Pełny tekst źródła
4
Rodden, Tom, Val King, John Hughes i Ian Sommerville. "Process modelling and development practice". W Software Process Technology, 59–64. Berlin, Heidelberg: Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/3-540-57739-4_8.
Pełny tekst źródła
5
Dooley, John. "Introduction to Software Development". W Software Development and Professional Practice, 1–5. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-3802-7_1.
Pełny tekst źródła
6
Paulish, Daniel J. "Practice: Global Software Architecture Development". W Global Software and IT, 59–67. Hoboken, NJ, USA: John Wiley & Sons, Inc., 2011. http://dx.doi.org/10.1002/9781118135105.ch9.
Pełny tekst źródła
7
Doyle, Maureen, Laurie Williams, Mike Cohn i Kenneth S. Rubin. "Agile Software Development in Practice". W Lecture Notes in Business Information Processing, 32–45. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-06862-6_3.
Pełny tekst źródła
8
Sharp, Helen, i Hugh Robinson. "Three ‘C’s of Agile Practice: Collaboration, Co-ordination and Communication". W Agile Software Development, 61–85. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12575-1_4.
Pełny tekst źródła
9
Schatten, Alexander, Markus Demolsky, Dietmar Winkler, Stefan Biffl, Erik Gostischa-Franta i Thomas Östreicher. "Qualitätssicherung und Test-Driven Development". W Best Practice Software-Engineering, 113–62. Heidelberg: Spektrum Akademischer Verlag, 2010. http://dx.doi.org/10.1007/978-3-8274-2487-7_5.
Pełny tekst źródła
10
Dooley, John F. "Ethics and Professional Practice". W Software Development, Design and Coding, 283–304. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3153-1_18.
Pełny tekst źródłaStreszczenia konferencji na temat "Software development practice"
1
Morrison, Patrick, Benjamin H. Smith i Laurie Williams. "Surveying Security Practice Adherence in Software Development". W the Hot Topics in Science of Security: Symposium and Bootcamp. New York, New York, USA: ACM Press, 2017. http://dx.doi.org/10.1145/3055305.3055312.
Pełny tekst źródła
2
Wang, Yi, i Min Zhang. "Penalty policies in professional software development practice". W the 32nd ACM/IEEE International Conference. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1810295.1810302.
Pełny tekst źródła
3
Brink, Christopher, Martin Peters i Sabine Sachweh. "Improved software project management through the use of product lines". W Project Management Development – Practice and Perspectives. Latvijas Universitāte, 2012. http://dx.doi.org/10.22364/pmdpp.2012.01.
Pełny tekst źródła
4
Díaz, Jessica, Rubén Almaraz, Jennifer Pérez i Juan Garbajosa. "DevOps in practice". W XP '18 Companion: 19th International Conference on Agile Software Development. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3234152.3234199.
Pełny tekst źródła
5
Lin, Weiguo, i Xiaomin Fan. "Software Development Practice for FDA-Compliant Medical Devices". W 2009 International Joint Conference on Computational Sciences and Optimization, CSO. IEEE, 2009. http://dx.doi.org/10.1109/cso.2009.191.
Pełny tekst źródła
6
Kassab, Mohamad, Joanna DeFranco i Phillip A. Laplante. "Software development for medical devices: State of practice". W 2017 IEEE 28th Annual Software Technology Conference (STC). IEEE, 2017. http://dx.doi.org/10.1109/stc.2017.8234459.
Pełny tekst źródła
7
Kayongo, Patrick, Wallace Chigona i Zwelithini Mabhena. "Why do software developers practice test-driven development?" W 2016 International Conference on Advances in Computing and Communication Engineering (ICACCE). IEEE, 2016. http://dx.doi.org/10.1109/icacce.2016.8073775.
Pełny tekst źródła
8
Heitmeyer, Constance, Ralph Jeffords, Ramesh Bharadwaj i Myla Archer. "RE Theory Meets Software Practice: Lessons from the Software Development Trenches". W 15th IEEE International Requirements Engineering Conference (RE 2007). IEEE, 2007. http://dx.doi.org/10.1109/re.2007.20.
Pełny tekst źródła
9
"Continuous Test-Driven Development - A Novel Agile Software Development Practice and Supporting Tool". W 8th International Conference on Evaluation of Novel Software Approaches to Software Engineering. SciTePress - Science and and Technology Publications, 2013. http://dx.doi.org/10.5220/0004587202600267.
Pełny tekst źródła
10
Crick, Tom, Tom Prickett, Jill Bradnum i Alan Godfrey. "Gender parity in peer assessment of team software development projects". W CEP 2022: Computing Education Practice 2022. New York, NY, USA: ACM, 2022. http://dx.doi.org/10.1145/3498343.3498346.
Pełny tekst źródłaRaporty organizacyjne na temat "Software development practice"
1
Striuk, Andrii M., i Serhiy O. Semerikov. The Dawn of Software Engineering Education. [б. в.], luty 2020. http://dx.doi.org/10.31812/123456789/3671.
Pełny tekst źródłaStreszczenie:
Designing a mobile-oriented environment for professional and practical training requires determining the stable (fundamental) and mobile (technological) components of its content and determining the appropriate model for specialist training. In order to determine the ratio of fundamental and technological in the content of software engineers’ training, a retrospective analysis of the first model of training software engineers developed in the early 1970s was carried out and its compliance with the current state of software engineering development as a field of knowledge and a new the standard of higher education in Ukraine, specialty 121 “Software Engineering”. It is determined that the consistency and scalability inherent in the historically first training program are largely consistent with the ideas of evolutionary software design. An analysis of its content also provided an opportunity to identify the links between the training for software engineers and training for computer science, computer engineering, cybersecurity, information systems and technologies. It has been established that the fundamental core of software engineers’ training should ensure that students achieve such leading learning outcomes: to know and put into practice the fundamental concepts, paradigms and basic principles of the functioning of language, instrumental and computational tools for software engineering; know and apply the appropriate mathematical concepts, domain methods, system and object-oriented analysis and mathematical modeling for software development; put into practice the software tools for domain analysis, design, testing, visualization, measurement and documentation of software. It is shown that the formation of the relevant competencies of future software engineers must be carried out in the training of all disciplines of professional and practical training.
2
Vakaliuk, Tetiana A., Valerii V. Kontsedailo, Dmytro S. Antoniuk, Olha V. Korotun, Iryna S. Mintii i Andrey V. Pikilnyak. Using game simulator Software Inc in the Software Engineering education. [б. в.], luty 2020. http://dx.doi.org/10.31812/123456789/3762.
Pełny tekst źródłaStreszczenie:
The article presents the possibilities of using game simulator Sotware Inc in the training of future software engineer in higher education. Attention is drawn to some specific settings that need to be taken into account when training in the course of training future software engineers. More and more educational institutions are introducing new teaching methods, which result in the use of engineering students, in particular, future software engineers, to deal with real professional situations in the learning process. The use of modern ICT, including game simulators, in the educational process, allows to improve the quality of educational material and to enhance the educational effects from the use of innovative pedagogical programs and methods, as it gives teachers additional opportunities for constructing individual educational trajectories of students. The use of ICT allows for a differentiated approach to students with different levels of readiness to study. A feature of any software engineer is the need to understand the related subject area for which the software is being developed. An important condition for the preparation of a highly qualified specialist is the independent fulfillment by the student of scientific research, the generation, and implementation of his idea into a finished commercial product. In the process of research, students gain knowledge, skills of the future IT specialist and competences of the legal protection of the results of intellectual activity, technological audit, marketing, product realization in the market of innovations. Note that when the real-world practice is impossible for students, game simulators that simulate real software development processes are an alternative.
3
Kiv, Arnold E., Olexandr V. Merzlykin, Yevhenii O. Modlo, Pavlo P. Nechypurenko i Iryna Yu Topolova. The overview of software for computer simulations in profile physics learning. [б. в.], wrzesień 2019. http://dx.doi.org/10.31812/123456789/3260.
Pełny tekst źródłaStreszczenie:
The paper deals with the possibilities of using specialized (virtual labs and simulators, software for natural process simulation) and general (programming languages and libraries, spreadsheets, CAS) software in school researches. Such software as virtual labs, software for natural process simulation, programming languages and libraries in school researches can be used to simulate phenomena that cannot be learned in a school lab (for example, for modeling a radioactive decay or for demonstrating the states of relativistic mechanics). Also, virtual labs in school practice are usually used in those cases where students cannot perform an experiment in real labs. For example, it is convenient for distance learning. The using of programming languages and libraries in physics learning research requires both students’ physics research competencies and programming competencies. That is why using this software in physics classes can hardly be recommended. However, programming languages and libraries can become a powerful tool for the formation and development of research competencies of physics students in extracurricular learning activities. The implementation of the spreadheets and the CAS in school physics researches is the easiest and has its benefits.
4
Arhin, Stephen, Babin Manandhar, Kevin Obike i Melissa Anderson. Impact of Dedicated Bus Lanes on Intersection Operations and Travel Time Model Development. Mineta Transportation Institute, czerwiec 2022. http://dx.doi.org/10.31979/mti.2022.2040.
Pełny tekst źródłaStreszczenie:
Over the years, public transit agencies have been trying to improve their operations by continuously evaluating best practices to better serve patrons. Washington Metropolitan Area Transit Authority (WMATA) oversees the transit bus operations in the Washington Metropolitan Area (District of Columbia, some parts of Maryland and Virginia). One practice attempted by WMATA to improve bus travel time and transit reliability has been the implementation of designated bus lanes (DBLs). The District Department of Transportation (DDOT) implemented a bus priority program on selected corridors in the District of Columbia leading to the installation of red-painted DBLs on corridors of H Street, NW, and I Street, NW. This study evaluates the impacts on the performance of transit buses along with the general traffic performance at intersections on corridors with DBLs installed in Washington, DC by using a “before” and “after” approach. The team utilized non-intrusive video data to perform vehicular turning movement counts to assess the traffic flow and delays (measures of effectiveness) with a traffic simulation software. Furthermore, the team analyzed the Automatic Vehicle Locator (AVL) data provided by WMATA for buses operating on the study segments to evaluate bus travel time. The statistical analysis showed that the vehicles traveling on H Street and I Street (NW) experienced significantly lower delays during both AM (7:00–9:30 AM) and PM (4:00–6:30 PM) peak hours after the installation of bus lanes. The approximation error metrics (normalized squared errors) for the testing dataset was 0.97, indicating that the model was predicting bus travel times based on unknown data with great accuracy. WMATA can apply this research to other segments with busy bus schedules and multiple routes to evaluate the need for DBLs. Neural network models can also be used to approximate bus travel times on segments by simulating scenarios with DBLs to obtain accurate bus travel times. Such implementation could not only improve WMATA’s bus service and reliability but also alleviate general traffic delays.
5
Luqi. Increasing the Practical Impact of Formal Methods for Computer-Aided Software Development,. Fort Belvoir, VA: Defense Technical Information Center, wrzesień 1995. http://dx.doi.org/10.21236/ada310438.
Pełny tekst źródła
6
Whitener, Dustin, i John Fulton. The ERSDT Software Quality Assurance Plan Practices and Development Environment Setup for RASCAL 5. Office of Scientific and Technical Information (OSTI), marzec 2021. http://dx.doi.org/10.2172/1773271.
Pełny tekst źródła
7
Colston, Sharon N. Implementation of Successful Practices Using an Iterative Development Methodology for an AEGIS Configuration Management Software Application. Fort Belvoir, VA: Defense Technical Information Center, wrzesień 1998. http://dx.doi.org/10.21236/ada363072.
Pełny tekst źródła
8
Gurieiev, Viktor, Yulii Kutsan, Anna Iatsyshyn, Andrii Iatsyshyn, Valeriia Kovach, Evgen Lysenko, Volodymyr Artemchuk i Oleksandr Popov. Simulating Systems for Advanced Training and Professional Development of Energy Specialists in Power Sector. [б. в.], listopad 2020. http://dx.doi.org/10.31812/123456789/4456.
Pełny tekst źródłaStreszczenie:
The crisis of the system of professional development and personnel training in the energy sector exists not only in Ukraine but also all over the world. The article describes the concept of development and functioning of the industry system of personnel training in the energy sector of Ukraine. The importance of using modern web-oriented technologies to improve the skills of operational and dispatching personnel in the energy sector of Ukraine is substantiated. The meth- ods of distributed power system operating modes modelling are presented. De- velopment and software tools for the construction of distributed simulating sys- tems and particular features of cloud technologies application for the creation of a virtual training centers network in the energy sector, as well as the ways to automate the process of simulating scenarios development are described. The ex- perience of introducing remote training courses for energy specialists and remote web-based training simulators based on a comprehensive model of the energy system of Ukraine is presented. An important practical aspect of the research is the application of software and data support for the development of personnel key competencies in the energy sector for rapid recognition of accidents and, if necessary, accident management. This will allow them to acquire knowledge and practical skills to solve the problems of analysis, modelling, forecasting, and monitoring data visualization of large power systems operating modes.
9
Coulson, Saskia, Melanie Woods, Drew Hemment i Michelle Scott. Report and Assessment of Impact and Policy Outcomes Using Community Level Indicators: H2020 Making Sense Report. University of Dundee, 2017. http://dx.doi.org/10.20933/100001192.
Pełny tekst źródłaStreszczenie:
Making Sense is a European Commission H2020 funded project which aims at supporting participatory sensing initiatives that address environmental challenges in areas such as noise and air pollution. The development of Making Sense was informed by previous research on a crowdfunded open source platform for environmental sensing, SmartCitizen.me, developed at the Fab Lab Barcelona. Insights from this research identified several deterrents for a wider uptake of participatory sensing initiatives due to social and technical matters. For example, the participants struggled with the lack of social interactions, a lack of consensus and shared purpose amongst the group, and a limited understanding of the relevance the data had in their daily lives (Balestrini et al., 2014; Balestrini et al., 2015). As such, Making Sense seeks to explore if open source hardware, open source software and and open design can be used to enhance data literacy and maker practices in participatory sensing. Further to this, Making Sense tests methodologies aimed at empowering individuals and communities through developing a greater understanding of their environments and by supporting a culture of grassroot initiatives for action and change. To do this, Making Sense identified a need to underpin sensing with community building activities and develop strategies to inform and enable those participating in data collection with appropriate tools and skills. As Fetterman, Kaftarian and Wanderman (1996) state, citizens are empowered when they understand evaluation and connect it in a way that it has relevance to their lives. Therefore, this report examines the role that these activities have in participatory sensing. Specifically, we discuss the opportunities and challenges in using the concept of Community Level Indicators (CLIs), which are measurable and objective sources of information gathered to complement sensor data. We describe how CLIs are used to develop a more indepth understanding of the environmental problem at hand, and to record, monitor and evaluate the progress of change during initiatives. We propose that CLIs provide one way to move participatory sensing beyond a primarily technological practice and towards a social and environmental practice. This is achieved through an increased focus in the participants’ interests and concerns, and with an emphasis on collective problem solving and action. We position our claims against the following four challenge areas in participatory sensing: 1) generating and communicating information and understanding (c.f. Loreto, 2017), 2) analysing and finding relevance in data (c.f. Becker et al., 2013), 3) building community around participatory sensing (c.f. Fraser et al., 2005), and 4) achieving or monitoring change and impact (c.f. Cheadle et al., 2000). We discuss how the use of CLIs can tend to these challenges. Furthermore, we report and assess six ways in which CLIs can address these challenges and thereby support participatory sensing initiatives: i. Accountability ii. Community assessment iii. Short-term evaluation iv. Long-term evaluation v. Policy change vi. Capability The report then returns to the challenge areas and reflects on the learnings and recommendations that are gleaned from three Making Sense case studies. Afterwhich, there is an exposition of approaches and tools developed by Making Sense for the purposes of advancing participatory sensing in this way. Lastly, the authors speak to some of the policy outcomes that have been realised as a result of this research.
10
Semerikov, Serhiy O., Mykhailo M. Mintii i Iryna S. Mintii. Review of the course "Development of Virtual and Augmented Reality Software" for STEM teachers: implementation results and improvement potentials. [б. в.], 2021. http://dx.doi.org/10.31812/123456789/4591.
Pełny tekst źródłaStreszczenie:
The research provides a review of applying the virtual reality (VR) and augmented reality (AR) technology to education. There are analysed VR and AR tools applied to the course “Development of VR and AR software” for STEM teachers and specified efficiency of mutual application of the environment Unity to visual design, the programming environment (e.g. Visual Studio) and the VR and AR platforms (e.g. Vuforia). JavaScript language and the A-Frame, AR.js, Three.js, ARToolKit and 8th Wall libraries are selected as programming tools. The designed course includes the following modules: development of VR tools (VR and Game Engines; physical interactions and camera; 3D interface and positioning; 3D user interaction; VR navigation and introduction) and development of AR tools (set up AR tools in Unity 3D; development of a project for a photograph; development of training materials with Vuforia; development for promising devices). The course lasts 16 weeks and contains the task content and patterns of performance. It is ascertained that the course enhances development of competences of designing and using innovative learning tools. There are provided the survey of the course participants concerning their expectations and the course results. Reduced amounts of independent work, increased classroom hours, detailed methodological recommendations and increased number of practical problems associated with STEM subjects are mentioned as the course potentials to be implemented.