Trends, challenges and opportunities for performance engineering with modern business software

The author looks at trends in software and systems, and the current and likely implications of these trends on the discipline of performance engineering. In particular, he examines software complexity growth and its consequences for performance engineering for enhanced understanding, more efficient analysis and effective performance improvement. The pressures for adaptive and autonomous systems introduce further opportunities for performance innovation. The promise of aspect oriented software development technologies for assisting with some of these challenges is introduced.

F. + H. Engel AG: Erfolg mit releasefähiger Standard-Software

Die Firma F. + H. Engel AG ist ein Bieler Familienunternehmen, das an fünf Standorten tätig ist und die Geschäftsbereiche Stahl, Haustechnik und Eisenwaren abdeckt. Seit über 15 Jahren setzt ENGEL für die Unterstützung ihrer Handelsprozesse die Standardsoftware OpaccOne ein. Dabei orientiert sich das Unternehmen an den durch die Software gegebenen Möglichkeiten, um eine möglichst sichere, stabile und langfristig tragfähige Lösung sicher zu stellen. Dank der Releasefähigkeit der gewählten Standard-Business-Software profitierte Engel ohne grössere Umstellungen von deren laufend erweiterten Fähigkeiten in Bezug auf Funktionalität, Technologie, Anpassungs- und Erweiterungsmöglichkeiten. Dadurch konnte sich ENGEL über die Jahre mit dieser Software stetig weiterentwickeln und auch neue Anforderungen abdecken. Problematisch erwies sich die durch die Einführung eines Webshops deutlich höhere Anforderung an Umfang und Qualität der Produktstammdaten für das umfangreiche Sortiment. Der Aufwand für deren Pflege konnte von ENGEL auf die Dauer nicht geleistet werden. Deshalb entschied man sich für eine zweigleisige Strategie, indem für einen Teil des Sortiments auf die Dienstleistungen eines externen Inhaltsanbieters zurückgegriffen wird

Software directory : 1982.

Cover title.

Extracting Business Rules through Static Analysis of the Source Code

Красимир Манев, Нели Манева, Хараламби Хараламбиев - Подходът с използване на бизнес правила (БП) беше въведен в края на миналия век, за да се улесни специфицирането на фирмен софтуер и да може той да задоволи по-добре нуждите на съответния бизнес. Днес повечето от целите на подхода са постигнати. Но усилията, в научно-изследователски и практически аспект, за постигане на „’формална основа за обратно извличане на БП от съществуващи системи “продължават. В статията е представен подход за извличане на БП от програмен код, базиран на методи за статичен анализ на кода. Посочени са някои предимства и недостатъци на такъв подход.

IT-enabled sustainability transformation—the case of SAP

This teaching case describes how SAP, a leading global information technology (IT) solutions provider, embarked on a large-scale transformation program to implement a dual sustainability strategy of: (a) internally transforming the organization, and (b) addressing a business opportunity by developing IT solutions that enable their customers to become more sustainable. This case provides students with significant information about the development of SAP towards sustainability, including the company's underlying motivation, their approach to change and related challenges, and their use of IT to enable the transformation. The teaching case provides an opportunity to critically examine the benefits and risks of using IT in an effort to improve the sustainability of an organization, and to develop appropriate models for sustainable strategies and IT implementation efforts.

Effects of the Spudcan Penetration on the Adjacent Foundations

Abstract: To study the effects of spudcan penetration on the adjacent foundations of offshore platforms, experiments and numerical simulations (using business software ABAQUS) are carried out. It is shown that the penetration of spudcan can cause the soil layer affected in an annular zone. The affected zone has a maximum width of one times the diameter of the spudcan. The deflection of the platform’s foundation increases with the penetration of spudcan. The smaller the density of soil layer is, the bigger the displacement of the foundation is. However, the maximum displacement at the top of the foun- dation changes little once the penetration depth is over a critical value. The bigger the diameter and the penetration depth of the spudcan are, the bigger the displacements of the foundation are.

Офтуер за бизнеса или бизнес със софтуера

Avram Eskenazi - Being the majority of the globally used software, the dedicated study of the software products for business purposes would hardly lead to substantial results and conclusions. This is the reason the first part of the paper to only consider historical aspects (both at world and national level) of the subject. The second part attempts to systemize the unique characteristics of the software business, as well as some strategic lines of its development.

A methodology to select an enterprise resource planning system for a small or medium sized enterprise

Enterprise Resource Planning (ERP) systems are software programs designed to integrate the functional requirements, and operational information needs of a business. Pressures of competition and entry standards for participation in major manufacturing supply chains are creating greater demand for small business ERP systems. The proliferation of new offerings of ERP systems introduces complexity to the selection process to identify the right ERP business software for a small and medium-sized enterprise (SME). The selection of an ERP system is a process in which a faulty conclusion poses a significant risk of failure to SME’s. The literature reveals that there are still very high failure rates in ERP implementation, and that faulty selection processes contribute to this failure rate. However, the literature is devoid of a systematic methodology for the selection process for an ERP system by SME’s. This study provides a methodological approach to selecting the right ERP system for a small or medium-sized enterprise. The study employs Thomann’s meta-methodology for methodology development; a survey of SME’s is conducted to inform the development of the methodology, and a case study is employed to test, and revise the new methodology. The study shows that a rigorously developed, effective methodology that includes benchmarking experiences has been developed and successfully employed. It is verified that the methodology may be applied to the domain of users it was developed to serve, and that the test results are validated by expert users and stakeholders. Future research should investigate in greater detail the application of meta-methodologies to supplier selection and evaluation processes for services and software; additional research into the purchasing practices of small firms is clearly needed.^

Identification and analysis of business and software services : A consolidated approach

Although the benefits of service orientation are prevalent in literature, a review, analysis, and evaluation of the 30 existing service analysis approaches presented in this paper have shown that a comprehensive approach to the identification and analysis of both business and supporting software services is missing. Based on this evaluation of existing approaches and additional sources, we close this gap by proposing an integrated, consolidated approach to business and software service analysis that combines and extends the strengths of the examined methodologies.

Business and software service lifecycle management

Although the service-oriented paradigm has been well established in the technical domain for quite some time now, service governance is still considered a research gap. To ensure adequate governance, there is a necessity to manage services as first-class assets throughout the lifecycle. Now that the concept of ser-vice-orientation is also increasingly applied on the business level to structure an organisation’s capabili-ties, the problem has become an even bigger chal-lenge. This paper presents a generic business and software service lifecycle and aligns it with the com-mon management layers in organisations. Using ser-vice analysis as an example, it moreover illustrates how activities in the service lifecycle may vary on lower levels of granularity depending on the focus on business or software services.

Value creation and value capture fro open source software publisher : a new business model based on mutualisation

Key topics: Since the birth of the Open Source movement in the mid-80's, open source software has become more and more widespread. Amongst others, the Linux operating system, the Apache web server and the Firefox internet explorer have taken substantial market shares to their proprietary competitors. Open source software is governed by particular types of licenses. As proprietary licenses only allow the software's use in exchange for a fee, open source licenses grant users more rights like the free use, free copy, free modification and free distribution of the software, as well as free access to the source code. This new phenomenon has raised many managerial questions: organizational issues related to the system of governance that underlie such open source communities (Raymond, 1999a; Lerner and Tirole, 2002; Lee and Cole 2003; Mockus et al. 2000; Tuomi, 2000; Demil and Lecocq, 2006; O'Mahony and Ferraro, 2007;Fleming and Waguespack, 2007), collaborative innovation issues (Von Hippel, 2003; Von Krogh et al., 2003; Von Hippel and Von Krogh, 2003; Dahlander, 2005; Osterloh, 2007; David, 2008), issues related to the nature as well as the motivations of developers (Lerner and Tirole, 2002; Hertel, 2003; Dahlander and McKelvey, 2005; Jeppesen and Frederiksen, 2006), public policy and innovation issues (Jullien and Zimmermann, 2005; Lee, 2006), technological competitions issues related to standard battles between proprietary and open source software (Bonaccorsi and Rossi, 2003; Bonaccorsi et al. 2004, Economides and Katsamakas, 2005; Chen, 2007), intellectual property rights and licensing issues (Laat 2005; Lerner and Tirole, 2005; Gambardella, 2006; Determann et al., 2007). A major unresolved issue concerns open source business models and revenue capture, given that open source licenses imply no fee for users. On this topic, articles show that a commercial activity based on open source software is possible, as they describe different possible ways of doing business around open source (Raymond, 1999; Dahlander, 2004; Daffara, 2007; Bonaccorsi and Merito, 2007). These studies usually look at open source-based companies. Open source-based companies encompass a wide range of firms with different categories of activities: providers of packaged open source solutions, IT Services&Software Engineering firms and open source software publishers. However, business models implications are different for each of these categories: providers of packaged solutions and IT Services&Software Engineering firms' activities are based on software developed outside their boundaries, whereas commercial software publishers sponsor the development of the open source software. This paper focuses on open source software publishers' business models as this issue is even more crucial for this category of firms which take the risk of investing in the development of the software. Literature at last identifies and depicts only two generic types of business models for open source software publishers: the business models of ''bundling'' (Pal and Madanmohan, 2002; Dahlander 2004) and the dual licensing business models (Välimäki, 2003; Comino and Manenti, 2007). Nevertheless, these business models are not applicable in all circumstances. Methodology: The objectives of this paper are: (1) to explore in which contexts the two generic business models described in literature can be implemented successfully and (2) to depict an additional business model for open source software publishers which can be used in a different context. To do so, this paper draws upon an explorative case study of IdealX, a French open source security software publisher. This case study consists in a series of 3 interviews conducted between February 2005 and April 2006 with the co-founder and the business manager. It aims at depicting the process of IdealX's search for the appropriate business model between its creation in 2000 and 2006. This software publisher has tried both generic types of open source software publishers' business models before designing its own. Consequently, through IdealX's trials and errors, I investigate the conditions under which such generic business models can be effective. Moreover, this study describes the business model finally designed and adopted by IdealX: an additional open source software publisher's business model based on the principle of ''mutualisation'', which is applicable in a different context. Results and implications: Finally, this article contributes to ongoing empirical work within entrepreneurship and strategic management on open source software publishers' business models: it provides the characteristics of three generic business models (the business model of bundling, the dual licensing business model and the business model of mutualisation) as well as conditions under which they can be successfully implemented (regarding the type of product developed and the competencies of the firm). This paper also goes further into the traditional concept of business model used by scholars in the open source related literature. In this article, a business model is not only considered as a way of generating incomes (''revenue model'' (Amit and Zott, 2001)), but rather as the necessary conjunction of value creation and value capture, according to the recent literature about business models (Amit and Zott, 2001; Chresbrough and Rosenblum, 2002; Teece, 2007). Consequently, this paper analyses the business models from these two components' point of view.