Search results for "Software development"
showing 10 items of 278 documents
Analysing software integration scenarios: the case of telecommunications operations software
2008
Telecom operators deploy a vast number of software systems to support their operations. Vendors of this software often integrate in their products several software systems, in order to enable innovations, minimize customer's integration efforts, etc. Different integration scenarios can be envisioned, and the issue of identifying more beneficial scenarios is of a great importance to the vendors. This paper aims at analyzing different software integration scenarios from the viewpoint of their support for innovations, and focuses on the context of telecommunications operations software. For each scenario, the overall modularity of the set of software systems is evaluated, and the expected bene…
Apathy Towards the Integration of Usability Work: A Case of System Justification
2016
In this article we report from a case study of a software development organization and we study in particular the developers’ and product managers’ attitudes towards integrating usability work into software development. We offer explanations based on system justification theory illuminating what would-be integrators might be up against. The analysis shows how the developers only pay lip service to usability work and how they treat users superficially. It further shows how that leads to stereotyping of usability designers and users in order to preserve status quo, and how internalization of inequality between the developers and usability designers rationalizes the preservation of status quo.…
Explaining Change Paths of Systems and Software Development Practices
2010
This chapter discusses how systems development practices are shaped. Based on interviews conducted in ten development organizations and previous literature, we identify eight types of change paths in systems development practices: emergence, adoption, idealization, formalization, abandonment, informalization, entropy, and disobedience. We argue that the eight change path types provide an integrated theoretical framework on the study of how systems development practices change in organizations, projects, and among individual developers in a given context. We discuss how this framework complements existing theories and concepts of the contemporary literature on systems development.
MetaEdit+ A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment
1996
Computer Aided Software Engineering (CASE) environments have spread at a lower pace than expected. One reason for this is the immaturity of existing environments in supporting development in-the-large and by-many and their inability to address the varying needs of the software developers. In this paper we report on the development of a next generation CASE environment called MetaEdit+. The environment seeks to overcome all the above deficiencies, but in particular pays attention to catering for the varying needs of the software developers. MetaEdit+ is a multi-method, multi-tool platform for both CASE and Computer Aided Method Engineering (CAME). As a CASE tool it establishes a versatile an…
Development Platforms as a Niche for Software Companies in Open Source Software
2006
As long as information systems do not become overly large and while they address a well-known domain, they can be controlled by engineering staff. Nevertheless, when dealing with large-scale, complex, or innovative information systems, it can be difficult to separate design issues and to formulate a meaningful information system proposal. In such a context, platforms for software engineering appear to be a promising approach. In this paper, we propose to view development platforms as a major opportunity for Open Source Software and Open Formats.
Editorial: Software language engineering
2008
Software languages play an important role in software development. Software languages are the artificial languages that are used to describe software systems at various abstraction levels. They are applied to describe requirements and designs for software, definitions of software architectures, and implementations of software systems. A huge variety of different technological spaces exist to describe languages: programming languages, software modeling languages, data modeling languages, domain-specific languages, ontology language, and others.
The Place and Role of Security Patterns in Software Development Process
2006
Security is one of the key quality attributes for many contemporary software products. Designing, developing, and maintaining such software necessitates the use of a secure-software development process which specifies how achieving this quality goal can be supported throughout the development life-cycle. In addition to satisfying the explicitly-stated functional security requirements, such process is aimed at minimising the number of vulnerabilities in the design and the implementation of the software. The secure software development is a challenging task spanning various stages of the development process. This inherent difficulty may be to some extent alleviated by the use of the so-called…
A modest but practical software process modeling technique for software process improvement
2002
One of the main problems with software engineering is due to the difficulties in evaluating and improving our software processes, especially in the light of the fact that reuse depends on a process which supports it. Generally used approaches to the evaluation and improvement of software processes are based on the CMM, for example. In this paper we present a technique to improve software processes through modeling and evaluation. The presented technique is fairly easy to use, provides reasonably good results and requires only a fraction of resources required by CMM appraisals. Copyright © 2002 John Wiley & Sons, Ltd.
Defining the Process for Making Software System Modernization Decisions
2006
This paper outlines a process for software system modernization decisions. The rationale of the process is explained and the process is defined in a way that allows its adaptation for other organizations and situations. The process is a light-weight one and is based on the use of objective data. The procedures for collecting the data are explained. The process has been used to solve a real industrial decision making situation in which the process was successful.
Software Business Education for Software Engineers: Towards an Integrated Curriculum
2006
All software is developed to create value to its stakeholders. Software engineering decisions and business value are closely linked with each other: technical decisions may have a profound impact on the business potential of software. Yet, software engineering education usually does not provide students with sufficient knowledge on business-related issues. We believe that the general business education is too abstract and unfocused to address the specific characteristics of software business. This paper suggests specific areas of business competencies that should be integrated into the software engineering curriculum. In addition, we compare these topics with software business curricula in …