Artykuły w czasopismach: „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

Style APA, Harvard, Vancouver, ISO itp.

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ła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

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ła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

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ła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

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ła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

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

Style APA, Harvard, Vancouver, ISO itp.

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

Style APA, Harvard, Vancouver, ISO itp.

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

Style APA, Harvard, Vancouver, ISO itp.

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ła

Streszczenie:

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.

Style APA, Harvard, Vancouver, ISO itp.

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ła

Style APA, Harvard, Vancouver, ISO itp.

11

Cusumano, M., A. MacCormack, C. F. Kemerer i B. Crandall. "Software development worldwide: The state of the practice". IEEE Software 20, nr 6 (listopad 2003): 28–34. http://dx.doi.org/10.1109/ms.2003.1241363.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

12

Oyama, Leslie, Henri Shay Tannas i Steve Moulton. "Desktop and mobile software development for surgical practice". Journal of Pediatric Surgery 37, nr 3 (marzec 2002): 477–81. http://dx.doi.org/10.1053/jpsu.2002.30870.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

13

Maritz, Andries, i Fatima Hamdulay. "ACSESim: Agile and Lean software development in practice". Emerald Emerging Markets Case Studies 8, nr 1 (6.02.2018): 1–25. http://dx.doi.org/10.1108/eemcs-02-2017-0025.

Pełny tekst źródła

Streszczenie:

Subject area Agile software development, Knowledge workers and Lean thinking as a management system Study level/applicability The case lends itself to students of business management, or aspiring consultants, who have been exposed to operations management in general and Lean thinking specifically. It is an advanced case study, assuming prior knowledge in these subjects and approaches the subject matter from an organisational development point of view, rather than a pure operations point of view. It is thus well suited to an elective on operational excellence on an MBA or in executive education courses in Lean thinking Case overview The case starts with Mark, manager of a software development team, hearing that he will have budget for two new developers who will join his team in the coming year. While the extra help could be useful, he was considering what the impact of new people would be on the productivity of the team, which he felt was already stretched. Mark continues to consider the entire development chain and how code changes were implemented to ACSESim’s (the company’s primary product) graphical user interfaces. Having recently been acquired by an American company, he was also under pressure to start to adopt some of the parent company’s systems, which would constitute a fairly disruptive, but necessary, change, particularly for future collaborations with other developers in the parent company. With two new developers, experience taught Mark that development could slow down owing to training efforts. To minimise disruption, he was wondering about how to get the new developers up-to-speed quickly and streamline their operations within a changing corporate environment. The case highlights the different mechanisms that were in place at ACSESim, including the use of issue trackers; Kanban boards; version control software; automated systems; stand-up meetings, etc. Each of these mechanisms is discussed briefly and shows the value they added to the development practices that were in place. This also allows students to understand Agile practices and what Lean thinking might mean in a knowledge work environment and then to consider what the proposed changes might mean and how they could be deployed. Expected learning outcomes To gain an understanding of how Lean and Agile principles can be applied in a software development environment and Lean knowledge work in general To consider the best way to manage new hires so that they can become productive in a Lean or Agile software development environment, whilst dealing with pressures to migrate to new systems. Supplementary materials Teaching notes are available for educators only. Please contact your library to gain login details or email support@emeraldinsight.com to request teaching notes. Subject code CSS: 9: Operations and Logistics.

Style APA, Harvard, Vancouver, ISO itp.

14

de Cesare, Sergio, Mark Lycett, Robert D. Macredie, Chaitali Patel i Ray Paul. "Examining perceptions of agility in software development practice". Communications of the ACM 53, nr 6 (czerwiec 2010): 126–30. http://dx.doi.org/10.1145/1743546.1743580.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

15

HUHNS, MICHAEL N. "INTERACTION-ORIENTED SOFTWARE DEVELOPMENT". International Journal of Software Engineering and Knowledge Engineering 11, nr 03 (czerwiec 2001): 259–79. http://dx.doi.org/10.1142/s0218194001000530.

Pełny tekst źródła

Streszczenie:

This paper describes a new approach to the production of robust software. We first motivate the approach by explaining why the two major goals of software engineering — correct software and reusable software — are not being addressed by the current state of software practice. We then describe a methodology based on active, cooperative, and persistent software components, i.e., agents, and show how the methodology produces robust and reusable software. We derive requirements for the structure and behavior of the agents, and report on preliminary experiments on applications based on the methodology. We conclude with a roadmap for development of the methodology and ruminations about uses for the new computational paradigm.

Style APA, Harvard, Vancouver, ISO itp.

16

Kim, Kang-Tae. "Enabling reuse driven software development : lessons learned from embedded software industry practice". KIPS Transactions:PartD 13D, nr 2 (1.04.2006): 271–78. http://dx.doi.org/10.3745/kipstd.2006.13d.2.271.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

17

Liebenberg, Janet, Magda Huisman i Elsa Mentz. "Software: University Courses versus Workplace Practice". Industry and Higher Education 29, nr 3 (czerwiec 2015): 221–35. http://dx.doi.org/10.5367/ihe.2015.0254a.

Pełny tekst źródła

Streszczenie:

There is a shortage of software developers with the right skills and knowledge, not only in South Africa but worldwide. Despite reports of a gap between industry needs and software education, the gap has mostly been explored in developed countries and in quantitative studies. This paper reports on a mixed methods study of the perceptions of professional software developers regarding what topics they learned from their formal education and the importance of these topics to their actual work. The analysis suggests that there is a gap between software development education and workplace practice and recommendations for software development education are made.

Style APA, Harvard, Vancouver, ISO itp.

18

Yiqin Bao, Yiqin Bao, Hao Zheng Yiqin Bao i Qiang Zhao Hao Zheng. "Development and Practice of Mobile Internet Experimental Platform System". 網際網路技術學刊 23, nr 2 (marzec 2022): 407–14. http://dx.doi.org/10.53106/160792642022032302019.

Pełny tekst źródła

Streszczenie:

As an emerging technology, mobile Internet technology involves almost all knowledge points in the application field of computer science and technology. The traditional Internet of things experiment box based on embedded technology has single equipment and limited functions, which can not meet the experimental requirements of mobile Internet from data perception, transmission to application. Aiming at the lack or incompleteness of the experimental platform in mobile internet teaching, a set of mobile Internet experimental platform system is designed. The platform is built according to the three levels of perception layer, transmission layer and application layer, using ZigBee, Modbus, MQTT and other protocols, which fully reflects the characteristics of the Internet of things (IoT) and mobile Internet, and meets the students’ mastery of mobile Internet knowledge. Through the design of 21 experimental projects, it meets the students’ mastery of mobile Internet knowledge, and can also meet the requirements of on-line teaching when COVID-19 is popular. The system practice shows that compared with before the platform is implemented, it improves the teaching level of students’ mastery of mobile Internet technology, and achieves a good purpose of experimental teaching.

Style APA, Harvard, Vancouver, ISO itp.

19

De Cesare, Sergio, Chaitali Patel, Nicola Iacovelli, Antonio Merico i Mark Lycett. "Tailoring Software Development Methodologies in Practice: A Case Study". Journal of Computing and Information Technology 16, nr 3 (2008): 157. http://dx.doi.org/10.2498/cit.1000898.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

20

Toth, Herbert. "On theory and practice of Assertion Based Software Development." Journal of Object Technology 4, nr 2 (2005): 109. http://dx.doi.org/10.5381/jot.2005.4.2.a2.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

21

Yong, Ding. "Design and Practice of Software Architecture in Agile Development". Journal of Physics: Conference Series 2074, nr 1 (1.11.2021): 012008. http://dx.doi.org/10.1088/1742-6596/2074/1/012008.

Pełny tekst źródła

Streszczenie:

Abstract Software architecture design is a very critical part of the software development process. In order to be able to respond to changes in user requirements in software development in a timely manner, a convenient and lightweight development model should be adopted. Agile development adopts a human-oriented, step-by-step development process that can quickly respond to changes in software requirements, adjust the design of software architecture in a timely manner and adapt to software development in a dynamic environment. Based on the analysis and comparison of traditional development process and agile development process, this paper analyzes the key technologies in agile architecture design and proposes a software architecture design method based on agile development mode.

Style APA, Harvard, Vancouver, ISO itp.

22

Kuhrmann, Marco, Philipp Diebold, Jurgen Munch, Paolo Tell, Kitija Trektere, Fergal McCaffery, Vahid Garousi i in. "Hybrid Software Development Approaches in Practice: A European Perspective". IEEE Software 36, nr 4 (lipiec 2019): 20–31. http://dx.doi.org/10.1109/ms.2018.110161245.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

23

Ståhl, Daniel, i Jan Bosch. "Modeling continuous integration practice differences in industry software development". Journal of Systems and Software 87 (styczeń 2014): 48–59. http://dx.doi.org/10.1016/j.jss.2013.08.032.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

24

Plant, Robert T., i Panagiotis Tsoumpas. "A survey of current practice in aerospace software development". Information and Software Technology 37, nr 11 (listopad 1995): 623–36. http://dx.doi.org/10.1016/0950-5849(95)98299-u.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

25

Heeager, Lise Tordrup. "Introducing Agile Practices in a Documentation-Driven Software Development Practice: A Case Study". Journal of Information Technology Case and Application Research 14, nr 1 (styczeń 2012): 3–24. http://dx.doi.org/10.1080/15228053.2012.10845693.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

26

Li, Xian Yu, Hua Wang, Jian Qun Zheng, Xiao Kun Li i Shan Wang. "The Research on the Software Requirement Development of Information System". Applied Mechanics and Materials 513-517 (luty 2014): 1854–57. http://dx.doi.org/10.4028/www.scientific.net/amm.513-517.1854.

Pełny tekst źródła

Streszczenie:

Based upon the synopsis of software requirement development, this paper describes the practices of user requirements exploitation, product requirements exploitation, requirements analysis and validation, and then puts forward engineering process relation and requirement development practice. Meanwhile, further works are brought forward. This will benefit the software requirement development of information system.

Style APA, Harvard, Vancouver, ISO itp.

27

Arcos-Medina, Gloria, i David Mauricio. "Identifying Factors Influencing on Agile Practices for Software Development". Journal of information and organizational sciences 44, nr 1 (25.06.2020): 1–31. http://dx.doi.org/10.31341/jios.44.1.1.

Pełny tekst źródła

Streszczenie:

Agile practices are activities or actions that are utilized during software development to improve the quality and productivity of the resulting software. Those practices are influenced by a set of factors that affect the realization of their objectives. The purpose of this study is to determine the influence of organizational factors and the personnel working on the software development project to the agile practices. To this end, a model has been proposed that is composed of six critical success factors derived from the theories of administrative and human behavior and four groups of agile practices, and resulted in identifying 13 factor-practice relationships. The results from 146 questionnaires addressed to individuals involved in the software development process show that the factors of Confidence, Perception of Self-efficacy, Integrity and Availability of the Information and Experiences Learned, and Media Used all have a noteworthy positive influence on teamwork agile practices.

Style APA, Harvard, Vancouver, ISO itp.

28

Cordoba-Pachon, Jose Rodrigo, i Cecilia Loureiro-Koechlin. "Online ethnography: a study of software developers and software development". Baltic Journal of Management 10, nr 2 (7.04.2015): 188–202. http://dx.doi.org/10.1108/bjm-01-2014-0016.

Pełny tekst źródła

Streszczenie:

Purpose – Qualitative research has made important contributions to social science by enabling researchers to engage with people and get an in-depth understanding of their views, beliefs and perceptions about social phenomena. With new and electronically mediated forms of human interaction (e.g. the online world), there are new opportunities for researchers to gather data and participate with or observe people in online groups. The purpose of this paper is to present features, challenges and possibilities for online ethnography as an innovative form of qualitative research. Design/methodology/approach – Ethnography is about telling a story about what happens in a particular setting or settings. In order to do this online, it is important to revisit, adopt and adapt some ideas about traditional (offline) ethnography. The paper distinguishes online ethnography from other types of research. It draws some generic features of online ethnography and identifies challenges for it. With these ideas in mind the paper presents and provides a reflection of an online ethnography of software developers. Findings – Online ethnography can provide valuable insights about social phenomena. The paper identifies generic features of this approach and a number of challenges related to its practice. These challenges have to do with to the choice of settings, use of online data for research, representation of people and generation of valuable and useful knowledge. The paper also highlights issues for future consideration in research and practice. Practical implications – The ethnography helped the researcher to identify and address a number of methodological challenges in practice and position herself in relation to relevant audiences she wanted to speak to. The paper also suggests different orientations to online ethnography. Lessons learned highlight potential contributions as well as further possibilities for qualitative research in the online world. Originality/value – Online ethnography offers possibilities to engage with a global audience of research subjects. For academics and practitioners the paper opens up possibilities to use online tools for research and it shows that the use of these tools can help overcome difficulties in access and interaction with people and to study a diversity of research topics, not only those that exist online. The paper offers guidance for researchers about where to start and how to proceed if they want to conduct online ethnography and generate useful and valuable knowledge in their area of interest.

Style APA, Harvard, Vancouver, ISO itp.

29

Amritesh i Subhas C. Misra. "Conceptual modeling for knowledge management to support agile software development". Knowledge Engineering Review 29, nr 4 (wrzesień 2014): 496–511. http://dx.doi.org/10.1017/s0269888914000198.

Pełny tekst źródła

Streszczenie:

AbstractAgile software development (ASD) has emerged as a result of consolidated values proposed under the lightweight methods of software engineering. Despite bearing some criticisms, the initial deployment and results observed in the practice environment represents its increasing domination over the traditional software development practices. Any ASD method, in particular, requires knowledge-intensive practices and typically employs multi-disciplinary expert team working extended periods of time for weeks on a nearly continuous basis. A huge amount of tacit knowledge creation and exchange happens in the entire process over the project lifecycle, which attracts the attention of research in the domain of knowledge management (KM). In this paper, first, we have mapped the agile values and agile principles, and in its support, we have argued upon and the need for integrated KM infrastructure and proposed a KM model that can be employed within the organization. We have also developed a conceptual framework for knowledge sharing and learning for the individual practitioners for the sustainability of agile team. We attempt to create an organizational learning framework for knowledge creation and exchange among the involved entities in a collaborative practice environment.

Style APA, Harvard, Vancouver, ISO itp.

30

Annarelli, Alessandro, Cinzia Battistella i Fabio Nonino. "Web-application development projects by online communities". Industrial Management & Data Systems 117, nr 1 (6.02.2017): 166–97. http://dx.doi.org/10.1108/imds-10-2015-0440.

Pełny tekst źródła

Streszczenie:

Purpose The purpose of this paper is to propose an in-depth analysis of online communities of practice that support the innovative development of web applications. The analysis is aimed at understanding the preeminent characteristics of communities of practice that can favour the process of innovation (conceptualisation and realization of a web application) and if these characteristics differ in the diverse phases of a software development project (requirement specification, design, implementation and verification). Design/methodology/approach The authors adopted a multiple case study research design, selected 29 communities of practice related to the development of web applications and classified them recognizing the different practices that refer to the different phases of the innovation process of web-applications software development. Finally, the authors focussed on seven communities comparing five important dimensions for each one. Findings The results of the empirical analysis show that the best practices are different, considering the different phases of the project, and that these practices can be strategies directed at members to attract them and also, strategies directed at the community to permit collaboration. Originality/value The paper proposes an important and new insight into the management of virtual communities of practice (VCoP). The authors supposed that the ways to manage a VCoP could depend on project phases. In particular, the management practices of community should differ according to the different project phases, i.e. requirements specification, design, implementation and verification of the software. Literature in this sense presented only research focussed on the different effects of virtualness on teams depending on the length of team duration and on communication efforts.

Style APA, Harvard, Vancouver, ISO itp.

31

Misra, Subhas C., i Virender Singh. "Conceptualizing open agile software development life cycle (OASDLC) model". International Journal of Quality & Reliability Management 32, nr 3 (2.03.2015): 214–35. http://dx.doi.org/10.1108/ijqrm-08-2013-0127.

Pełny tekst źródła

Streszczenie:

Purpose – Software development life cycle (SDLC) has always been the core methodology for any software engineer that depicts the entire development process which an organization is bound to utilize to achieve successful software. The purpose of this paper is to bring forth a conceptual model after analysing the best practices in SDLC, and extracting the best out of agile methodologies and the open source software, thereby bringing forward an optimised structure. Design/methodology/approach – The OASDLC is hypothesized specifically for “Brihaspati” project and is formulated keeping in mind the gaps and limitations posed by existing SDLC models. OASDLC is further put to test for achieving lower costs and efforts involved. The tests are further substantiated by means of hypothesis validation through execution of a survey based research. Findings – It has been observed that the present conceptual model further optimizes the efforts involved while adopting such a practice. Originality/value – This paper proposes a novel SDLC model so as to achieve a best practice for a software project. On analysing the issues involved such as tight budget and timelines, it led the authors to formulate a newer concept “Open Agile Software Development Life Cycle model” (OASDLC).

Style APA, Harvard, Vancouver, ISO itp.

32

Huang, Tao, i Chih-Chiang Fang. "Optimization of Software Test Scheduling under Development of Modular Software Systems". Symmetry 15, nr 1 (9.01.2023): 195. http://dx.doi.org/10.3390/sym15010195.

Pełny tekst źródła

Streszczenie:

Software testing and debugging is a crucial part of the software development process since defective software not only incurs customer dissatisfaction but also might incur legal issues. However, the managers of a software development company cannot arbitrarily prolong their software debugging period due to their software testing budget and opportunity in the market. Accordingly, in order to propose an advantageous testing project, the managers should be aware of the influence of the testing project on cost, quality, and time to make the best decision. In this study, a new software reliability growth model (SRGM) with consideration of the testing staff’s learning effect is proposed to achieve better prediction. The methods of estimating the model’s parameters and the symmetric confidence intervals are also proposed in the study. Moreover, in the past, most of the SRGMs focused on a single software system. However, in practice, some software systems were developed using modular-based system engineering approaches. Therefore, traditional software testing work can be changed to multiple modular testing work in this scenario. Therefore, the manager can use this to dispatch multiple staff groups to perform the individual testing work simultaneously. The study proposes two mathematical programming models to handle the scheduling of modular testing work. Additionally, the design of a computerized decision support system is also proposed in the study for the application in practice.

Style APA, Harvard, Vancouver, ISO itp.

33

Fannoun, Sufian, i John Kerins. "Towards organisational learning enhancement: assessing software engineering practice". Learning Organization 26, nr 1 (14.01.2019): 44–59. http://dx.doi.org/10.1108/tlo-09-2018-0149.

Pełny tekst źródła

Streszczenie:

Purpose Issues surrounding knowledge management, knowledge transfer and learning within organisations challenge continuity and resilience in the face of changing environments. While initiatives are principally applied within large organisations, there is scope to assess how the processes are handled within small and medium enterprises and consider how they might be enhanced. This paper aims to present an evaluation of practice within an evolving software development unit to determine what has been learned and how the knowledge acquired has been used to further organisational development. These results provide the basis for the design and implementation of a proposed support tool to enhance professional practice. Design/methodology/approach A small software development unit which has successfully delivered bespoke systems since its establishment a number of years ago was selected for analysis. In-depth interviews were carried out with each member of the unit to elicit an understanding of individual and collective development. Interview data were recorded and transcribed and subjected to qualitative analysis to identify key themes underpinning knowledge acquisition and utilisation. Samples of project documentation were scrutinised to corroborate interview data. After analysing the data, a focus-group meeting was held to validate the results and to generate further insights into learning within the unit. Findings Qualitative analysis of the data revealed key changes in thinking and practice within the unit, as well as insight into the development of individual and collective contextual knowledge, tacit understanding and learning. This analysis informed the proposal of a bespoke, lightweight, Web-based system to support knowledge capture and organisational learning. This approach has the potential to promote resilience and enhance practice in similar small or start-up enterprises. Research limitations/implications Purposeful sampling was used in selecting a small software development unit. This enabled in-depth interviewing of all six members of the organisation. This offered a rich environment from which to derive awareness and understanding of individual and collective knowledge acquisition and learning. Focussing on a single small enterprise limits the extent to which the findings can be generalised. However, the research provides evidence of effective practice and learning and has identified themes for the development of a support tool. This approach can be extended to similar domains to advance research into their learning and development. Practical implications Results of the work undertaken so far have generated promising foundations for the proposed support tool. This offers software developers a potentially useful system within which they can reflect upon, and record, key learning events affecting technical, managerial and professional practice. Originality/value Small enterprises have limited resources to support organisational learning. The qualitative research undertaken so far has yielded valuable insight into the successful development of a single software development unit. The construction of a support tool to enhance knowledge acquisition and learning has the capacity to consolidate valuable, and potentially scarce, expertise. It also has the potential to facilitate further research to determine how the prototype might be extended or revised to improve its contribution to the unit’s development.

Style APA, Harvard, Vancouver, ISO itp.

34

Vasquez, Kriss Melody Calla, Julia Lizet Torres Rivera, Elizabeth Mayuri-Ramos, Ruth Huamani-Torres i July Rivera-Zamudio. "Research Hotbeds: A Practice for Scientific Development in Universities". NeuroQuantology 20, nr 5 (18.05.2022): 568–74. http://dx.doi.org/10.14704/nq.2022.20.5.nq22210.

Pełny tekst źródła

Streszczenie:

The study carried out seeks to explain how the seedbeds; they are part of the formative research program of the universities to fine-tune research methods, strengthen critical thinking; problem solving and promoting innovation. In this sense, the study was developed under the quantitative approach of cross-sectional scope; descriptive-correlational level; with the non-probabilistic-intentional sampling type. With the participation of 1116 university students of the formative research program. Obtaining as a result that the relevant point that the training sessions in the framework of the formative research showed to the research hotbeds is that they were related to the particular interest of the participants for an effective management of the bibliographic reference managers. There is an interest in accessing scientific databases; and optimally handle software such as Zotero, EndNote and Mendeley; in order to manage scientific information through storage, organization, managing citations and bibliographic references. Coming to the conclusion that the seedbeds represent in the formative research of the universities; a program to stimulate the development of research skills in students of various cycles through the development of courses related to research methodology, scientific writing, use of computer tools for managing references.

Style APA, Harvard, Vancouver, ISO itp.

35

Gorschek, Tony, Ewan Tempero i Lefteris Angelis. "On the use of software design models in software development practice: An empirical investigation". Journal of Systems and Software 95 (wrzesień 2014): 176–93. http://dx.doi.org/10.1016/j.jss.2014.03.082.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

36

Rashid, Awais, Thomas Cottenier, Phil Greenwood, Ruzanna Chitchyan, Regine Meunier, Roberta Coelho, Mario Südholt i Wouter Joosen. "Aspect-Oriented Software Development in Practice: Tales from AOSD-Europe". Computer 43, nr 2 (luty 2010): 19–26. http://dx.doi.org/10.1109/mc.2010.30.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

37

Bajec, Marko, Damjan Vavpotič i Marjan Krisper. "Practice-driven approach for creating project-specific software development methods". Information and Software Technology 49, nr 4 (kwiecień 2007): 345–65. http://dx.doi.org/10.1016/j.infsof.2006.05.007.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

38

Ghimire, Dipendra, i Stuart Charters. "The Impact of Agile Development Practices on Project Outcomes". Software 1, nr 3 (5.08.2022): 265–75. http://dx.doi.org/10.3390/software1030012.

Pełny tekst źródła

Streszczenie:

Agile software development methods were introduced to minimize problems faced using traditional software development approaches. There are several Agile approaches used in developing software projects, these include Scrum, Extreme programming and Kanban. An Agile approach focuses on collaboration between customers and developers and encourages development teams to be self-organizing. To achieve this there are different Agile practices teams choose to use in their projects. Some teams only use one practice whilst others use a combination of practices. The most common practices used are stand-ups, user stories, Burndown chart/Burnup chart, pair programming, Epic and User stories. This paper reports on the analysis of the data collected from people involved in Agile software development teams and identifies that the combination of practices in Agile software development have an impact on the communication in the team, project requirements and project priorities, with more practices being adopted correlating with better project outcomes.

Style APA, Harvard, Vancouver, ISO itp.

39

Almeida, Fernando. "Using Agile Practice for Student Software Projects". Journal of Education and Vocational Research 3, nr 9 (15.09.2012): 280–90. http://dx.doi.org/10.22610/jevr.v3i9.79.

Pełny tekst źródła

Streszczenie:

Agile methodology as a relatively new approach to software engineering is becoming more popular in both industry and academia. Learning agile software development methodologies will unquestionably increase the capabilities and competences of our students as entry-level software engineers. However, how agile methods and techniques should be taught at the undergraduate level in additional to traditional approaches is still being debated. This study was conducted on a studentprogramming project, with sample size of 23 students from the Informatics Engineering course. The Scrum methodology was adopted and 28 user stories and 4 sprints were created. The results indicate a significant impact on studentsâ€™ skill improvement and let them to have the first contact with real projects and clients. Besides that, the students agree that the adoption of the Scrum methodology helped them to improve the participation and collaboration. However, some issues were also detected in terms of communication and tasks planning. Therefore, we proposed some polities that could help and boost the software development process inside a classroom.

Style APA, Harvard, Vancouver, ISO itp.

40

Song, Xi Jun, i Zhi Lian Zeng. "Research on Application of Software Engineering Theory in Software Development". Applied Mechanics and Materials 687-691 (listopad 2014): 1921–24. http://dx.doi.org/10.4028/www.scientific.net/amm.687-691.1921.

Pełny tekst źródła

Streszczenie:

With the development of information society, the size and number of computer software increases sharply. This demands the quality of software higher and higher. Thus does software engineering management come into being, and is enriched, developed and perfected in engineering practice continually. In this paper, the author analyses the new theory's research background, meaning, and the applicant region. This paper sums up the experience of software engineering implementation in project developing, and points out the problems of software in software explore. From the character and existing problem in software, the author compares the usability of a lot of soft engineer process models in developing organization, points out the importance of the implantation in these organizations. In the end, this paper also gives its suggestions on implant principle, organization development, system building, staff training, and environment construction.

Style APA, Harvard, Vancouver, ISO itp.

41

Murphy, Thomas, i Kathryn Cormican. "Towards holistic goal centered performance management in software development: lessons from a best practice analysis". International Journal of Information Systems and Project Management 3, nr 4 (8.02.2022): 23–36. http://dx.doi.org/10.12821/ijispm030402.

Pełny tekst źródła

Streszczenie:

There are strong motivating factors for more effective performance measurement practices in software development. Astute practices in this domain are lauded to improve efficiency and effectiveness. However previous studies have shown that measurement in software is intricate, complex and fraught with challenges. Consequently it is poorly managed in practice. Our research seeks to better understand performance management in a real world software development setting in order to identify the challenges and generate a roadmap for improvement. This paper presents findings from an inductive analysis of a radical measurement program in a global software organization. Our study investigates the level at which non-compliance with best practice can explain the company’s disappointing results. We found that a narrow focus on projects, rather than on organizational goals, has seriously hindered its success. We also found that the rate of change in the organization as a whole was impinging on the effective implementation of its measurement program. An analysis of the results demonstrates just how challenging software measurement is. The findings provide an evaluation of best practice relative to the literature that is informed by real industry experience.

Style APA, Harvard, Vancouver, ISO itp.

42

Yang, Fan, i Xiao Dong Cheng. "Software Development in Mining Subsedence Prediction". Advanced Materials Research 760-762 (wrzesień 2013): 1967–71. http://dx.doi.org/10.4028/www.scientific.net/amr.760-762.1967.

Pełny tekst źródła

Streszczenie:

Long-term scientific research and production practice show that there are rules to follow in mining influence, but the amount of measurement data collation and analysis not only cost of manpower, material resources, and calculation is very prone to error. Computer to replace manual calculation, not only convenient, quick, efficient, and adopts automatic generation technology by drawing graphs, is unattainable by manual technology. Mine land reclamation in mining subsidence is expected to software research for mining design, mining area coal mine district design, land compensation, land reclamation and comprehensive utilization technology work provides a scientific basis, promote the process of security coal pillar mining, ensures the mine in each work smoothly, improve the economic benefit of mine, to the national economy and the sustainable development of coal industry itself has important significance.

Style APA, Harvard, Vancouver, ISO itp.

43

Taylor, Katie Jane. "Adopting Agile software development: the project manager experience". Information Technology & People 29, nr 4 (7.11.2016): 670–87. http://dx.doi.org/10.1108/itp-02-2014-0031.

Pełny tekst źródła

Streszczenie:

Purpose Early research into Agile approaches explored particular practices or quantified improvements in code production. Less well researched is how Agile teams are managed. The project manager (PM) role is traditionally one of “command and control” but Agile methods require a more facilitative approach. How this changing role plays out in practice is not yet clearly understood. The purpose of this paper is to provide insight into how adopting Agile techniques shape the working practices of PMs and critically reflect on some of the tensions that arise. Design/methodology/approach An ethnographic approach was used to surface a richer understanding of the issues and tensions faced by PMs as Agile methods are introduced. Ethnographic fiction conveys the story to a wider audience. Findings Agile approaches shift responsibility and spread expert knowledge seeming to undermine the traditional PM function. However, the findings here show various scenarios that allow PMs to wrest control and become more of a “gate-keeper”. Ethnographic fiction communicates a sense of the PMs frustration with the conflict between the need to control and the desire for teams to take more responsibility. Originality/value Stories provide insight and communicate the experiential feel behind issues faced by PMs adopting Agile to surface useful knowledge. The objective is not how to measure knowledge, but how to recognize it. These reflections are valuable to fellow researchers as well as practitioners and contribute to the growing literature on Agile project management.

Style APA, Harvard, Vancouver, ISO itp.

44

Zmeev, D. O., O. A. Zmeev i L. S. Ivanova. "Antipattern Practice for Essence Practice Library". Programmnaya Ingeneria 13, nr 7 (22.08.2022): 311–21. http://dx.doi.org/10.17587/prin.13.311-321.

Pełny tekst źródła

Streszczenie:

The Essence graphical representation language allows to describe various project management practices in software development. At the moment, the Practice Library describes the most popular development methodologies, but work with various risks, such as code smells or antipatterns, which may be cause of future problems, is not represented. This article presents an extension for the Practice Library of the Essence language in the form of a practice for working with antipatterns. To represent antipatterns in the system, the Antipattern subalpha, its states and checkpoints are proposed. Antipatterns states and checkpoints: 1. Detected: Рѕ Signs of poor-quality design or implementation of the Software System have been found. Рѕ The boundaries of the low-quality area in the Software System have been defined. Рѕ Work Products associated with the inferior part of the Software System have been defined. 2. Identified: Рѕ The Software System Elements included in the Antipattern have been determined. Рѕ The type of antipattern has been determined. Рѕ Dependencies of the Software System on the antipattern elements have been determined. Рѕ The impact of the antipattern on the Software System has been estimated. 3. Refactoring Method Defined: Рѕ Possible options for refactoring have been identified. Рѕ The cost of the refactoring options has been assessed. Рѕ The most suitable refactoring method has been selected. 4. Fixed: Рѕ The Software System elements included in the antipattern are completely covered by tests. Рѕ The antipattern has been refactored. Рѕ Tests confirm that the Software System remains operational. Рѕ The Work Products related to the changed part of the Software System have been updated. 5. Closed: Рѕ Tests, reviews or other appropriate activities have been undertaken to ensure that the antipattern has been corrected or shown not to actually be a fault or flaw. Рѕ The antipattern management has been finalized. Рѕ Technical debt has decreased. To record data about an antipattern, the work product Antipattern Report and its levels of details with checkpoints are proposed. Levels of details and checkpoints are: 1. Antipattern detected: Рѕ The components of the Software System included in the antipattern are defined. 2. Antipatterns properties are determined: Рѕ An antipattern type has been defined. 3. Antipattern influence determined: Рѕ The cost of antipattern fixing was estimated. Рѕ An assessment of possible losses associated with the presence of an antipattern was carried out. Рѕ The antipattern is recognized as mandatory for elimination. 4. Antipattern eliminated вЂ” optional: Рѕ Refactoring completed. Рѕ Testing showed the correct work of the components included in the antipattern. Рѕ Antipattern elimination activity completed. To analyze the architecture of the system, the Inspect Architecture activity is proposed. The Fix Architecture activity represents actions to fix architecture flaws. Code analysis is presented as a Review the Code activity, and correction of deficiencies found during the analysis is presented as a Refactor the Code activity. The influence of subalpha on the state of the Software System alpha is analyzed. Recommendations were given on the proposed activities. Information about activities is presented in the form of diagrams in the Essence language. The proposed practice allows to record information about the found flaws in the code, process them correctly and avoid problems with the project in the future. It is an example of working with entities that negatively affect the progress of the project.

Style APA, Harvard, Vancouver, ISO itp.

45

Avison, D. E., H. U. Shah i D. N. Wilson. "Software quality standards in practice: the limitations of using ISO-9001 to support software development". Software Quality Journal 3, nr 2 (czerwiec 1994): 105–11. http://dx.doi.org/10.1007/bf00213633.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

46

Yahya, Norzariyah, i Siti Sarah Maidin. "Hybrid agile development phases: the practice in software projects as performed by software engineering team". Indonesian Journal of Electrical Engineering and Computer Science 29, nr 3 (1.03.2023): 1738. http://dx.doi.org/10.11591/ijeecs.v29.i3.pp1738-1749.

Pełny tekst źródła

Streszczenie:

The combination of scrum and waterfall is one of the software engineering teams that preferred hybrid agile models. The purpose of combining the two models is to leverage the advantages of each also to tailor the hybrid agile model to the needs of the project. However, to what extent are the phases, stages, and features of scrum and waterfall implemented in a software project remains unclear. Additionally, which phase will employ scrum, and when will waterfall be deemed optimal is also the arising question. This research adopted a qualitative study, and interviews are used as a data collection instrument. The interview is conducted based on an interview protocol, and thematic analysis is utilized to extract the themes from the interviews. This study investigates how the scrum and waterfall models are utilized in a software project, and three themes were identified in answering the research question. The findings indicate five development phases in a hybrid agile project and that waterfall is the preferable model in planning, while development is on scrum, and project testing and deployment could be either waterfall or scrum.

Style APA, Harvard, Vancouver, ISO itp.

47

Cusumano, M. A., W. Crandall, A. MacCormack i C. F. Kemerer. "Critical Decisions in Software Development: Updating the State of the Practice". IEEE Software 26, nr 5 (wrzesień 2009): 84–87. http://dx.doi.org/10.1109/ms.2009.124.

Pełny tekst źródła

Style APA, Harvard, Vancouver, ISO itp.

48

Mileff, Péter, i Judit Dudra. "Effective Pixel Rendering in Practice". Production Systems and Information Engineering 10, nr 1 (2022): 1–15. http://dx.doi.org/10.32968/psaie.2022.1.1.

Pełny tekst źródła

Streszczenie:

The graphics processing unit (GPU) has now become an integral part of our lives through both desktop and portable devices. Thanks to dedicated hardware, visualization has been significantly accelerated, softwares today only use the GPU for rasterization. As a result of this development, now we use only triangle-based rendering, and pixel-based image manipulations can only be performed using shaders. It can be stated that today’s GPU pipeline cannot provide the same flexibility as the previous software implementation. This paper discusses an efficient software implementation of pixel-based rasterization. After reviewing the current GPU-based drawing process, we will show how to access pixel level drawing in this environment. Finally, a more efficient storage and display format than the classic solution is presented, which performance far exceeds the previous solution.

Style APA, Harvard, Vancouver, ISO itp.

49

Muchlas, Muchlas, i Pramudita Budiastuti. "Development of Learning Devices of Basic Electronic Virtual Laboratory Based on PSPICE Software". Journal of Vocational Education Studies 3, nr 1 (29.04.2020): 1. http://dx.doi.org/10.12928/joves.v3i1.2085.

Pełny tekst źródła

Streszczenie:

The availability of modules to support basic electronic practices based on virtual laboratories has not yet met the needs. The purpose of this development research is to produce basic electronic practice learning devices based on the PSPICE application program. The development procedure uses ADDIE (analysis, design, development, implementation, evaluation). ADDIE is used to direct the design process as specified. Product performance was tested using ongoing formative evaluation. The product feasibility test uses a comparative analysis of the results of the PSPICE experiment against the theory. The results show that all modules developed can display the same characteristics as their theoretical character. The results show that the modules have very good performance. Modules are suitable for use as a medium for basic electronic practice using PSPICE-based virtual laboratories. The products are in the form of electronic circuits with 31 schematic PSPICE formats. Product results to support basic electronic practices covering topics: capacitor filling and discharging, RC circuits, diode characteristics, wave forming circuits, rectifier circuits, voltage clamp, voltage circuits, transistor characteristics, and amplifier transistor.

Style APA, Harvard, Vancouver, ISO itp.

50

Siau, Keng, i Yuhong Tian. "Open Source Software Development Process Model". Journal of Global Information Management 21, nr 4 (październik 2013): 103–20. http://dx.doi.org/10.4018/jgim.2013100106.

Pełny tekst źródła

Streszczenie:

The global open source movement has provided software users with more choices, lower software acquisition cost, more flexible software customization, and possibly higher quality software product. Although the development of open source software is dynamic and it encourages innovations, the process can be chaotic and involve members around the globe. An Open Source Software Development (OSSD) process model to enhance the survivability of OSSD projects is needed. This research uses the grounded theory approach to derive a Phase-Role-Skill-Responsibility (PRSR) OSSD process model. The three OSSD process phases -- Launch Stage, Before the First Release, and Between Releases -- address the characteristics of the OSSD process as well as factors that influence the OSSD process. In the PRSR model, different roles/actors are required to have different skills and responsibilities corresponding to each of the three OSSD process phases. This qualitative research contributes to the software development literature as well as open source practice.

Style APA, Harvard, Vancouver, ISO itp.

Artykuły w czasopismach na temat „Software development practice”

Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych