Home About us Contact | |||
Software Development Process (software + development_process)
Selected AbstractsA temporal perspective of the computer game development processINFORMATION SYSTEMS JOURNAL, Issue 5 2009Patrick Stacey Abstract., This paper offers an insight into the games software development process from a time perspective by drawing on an in-depth study in a games development organization. The wider market for computer games now exceeds the annual global revenues of cinema. We have, however, only a limited scholarly understanding of how games studios produce games. Games projects require particular attention because their context is unique. Drawing on a case study, the paper offers a theoretical conceptualization of the development process of creative software, such as games software. We found that the process, as constituted by the interactions of developers, oscillates between two modes of practice: routinized and improvised, which sediment and flux the working rhythms in the context. This paper argues that while we may predeterminately lay down the broad stages of creative software development, the activities that constitute each stage, and the transition criteria from one to the next, may be left to the actors in the moment, to the temporality of the situation as it emerges. If all development activities are predefined, as advocated in various process models, this may leave little room for opportunity and the creative fruits that flow from opportunity, such as enhanced features, aesthetics and learning. [source] BBN based approach for improving the software development process of an SME,a case studyJOURNAL OF SOFTWARE MAINTENANCE AND EVOLUTION: RESEARCH AND PRACTICE, Issue 2 2010S. Bibi Abstract This article proposes an approach for improving the software process of a small/medium company. The methodology is presented through a case study during which estimation models have been applied, evaluated and introduced in a telecommunication software development process. The proposed methodology uses Bayesian Belief Networks to represent the relationships among implementation, product and process metrics and their impact on the development effort. The estimation models that were derived were applied and evaluated on the on-going projects of the company. Finally, by performing the same analysis on data from the International Software Benchmarking Standards Group (ISBSG) repository, it is demonstrated how one company can utilize data from other companies when it lacks sufficient data of its own. Copyright © 2009 John Wiley & Sons, Ltd. [source] Assessing maintainability change over multiple software releasesJOURNAL OF SOFTWARE MAINTENANCE AND EVOLUTION: RESEARCH AND PRACTICE, Issue 1 2008Denis Kozlov Abstract The focus of the paper is to reveal the relationships between software maintainability and other internal software quality attributes. The source code characteristics of five Java-based open-source software products are analyzed using the software measurement tool SoftCalc. The relationships between maintainability and internal quality attributes are identified based on the Pearson product moment correlation analysis. Our results show negative correlations between maintainability and some well-known internal software quality attributes, as well as the ones between maintainability and complexity metrics. Particularly, according to our results, the Number of Data Variables Declared and the Decisional Complexity McClure Metric have the strongest correlations with maintainability. The results of our study, that is to say, knowledge about the relationships between internal software quality attributes and maintainability, can be used as a basis for improvement of software maintainability at earlier stages of the software development process. Copyright © 2007 John Wiley & Sons, Ltd. [source] Lessons learned by participants of distributed software developmentKNOWLEDGE AND PROCESS MANAGEMENT: THE JOURNAL OF CORPORATE TRANSFORMATION, Issue 2 2005Seija Komi-Sirviö The maturation of the technical infrastructure has enabled the emergence and growth of distributed software development. This has created tempting opportunities for companies to distribute their software development, for example, to economically favourable countries so as to gain needed expertise or to get closer to customers. Nonetheless, such distribution potentially creates problems that need to be understood and addressed in order to make possible the gains offered. To clarify and understand the most difficult problems and their nature, a survey of individuals engaged in distributed software development was conducted. The purpose of this survey was to gather and share lessons learned in order to better understand the nature of the software development process when operating in a distributed software development environment and the problems that may be associated with such distributed processes. Through a clear appreciation of the risks associated with distributed development it becomes possible to develop approaches for the mitigation of these risks. This paper presents the results of the survey, focusing on the most serious problems raised by the respondents. Some practical guidelines that have been developed by industry to overcome these problems are also briefly summarized. Copyright © 2005 John Wiley & Sons, Ltd. [source] University timetabling through conceptual modelingINTERNATIONAL JOURNAL OF INTELLIGENT SYSTEMS, Issue 11 2005Jonathan Lee A number of approaches have been proposed in tackling the timetabling problem, such as operational research, human-machine interaction, constraint programming, expert systems, and neural networks. However, there are still several key challenges to be addressed: easily reformulated to support changes, a generalized framework to handle various timetabling problems, and ability to incorporate knowledge in the timetabling system. In this article, we propose an automatic software engineering approach, called task-based conceptual graphs, to addressing the challenges in the timetabling problem. Task-based conceptual graphs provide the automation of software development processes including specification, verification, and automatic programming. Maintenance can be directly performed on the specifications rather than on the source code; moreover, hard and soft constraints can be easily inserted or removed. A university timetabling system in the Department of Computer Science and Information Engineering at National Central University is used as an illustrative example for the proposed approach. © 2005 Wiley Periodicals, Inc. Int J Int Syst 20: 1137,1160, 2005. [source] |