Search results

Top management support is considered to be an area that has high impact on project success. However, previous studies have also stated that effective top management support practices may vary across industries. This paper focuses on top management support for projects executed in the software sector. The objective of this study is to identify those top management support processes that have the greatest impact on software development project success and to compare these critical processes with the actual type of support provided by organisations.

About 17 top management support processes have been identified from the literature. Their effectiveness has been calculated according to their relative impact on project success. Data has been collected from 213 software development project managers and their supervisors in Japan, Israel and New Zealand. For each country, the impact of top management support processes on project success has been analysed to identify critical processes. Then, the actual level of use of both critical and non critical top management support processes by senior managers has been compared.

Different critical top management support processes have been identified in each country. However, six processes have been found to have higher contribution to project success than others. These processes are described and discussed in the paper. It has also been found that in all three countries top managers do not invest more effort in critical processes, than in non critical ones. Instead, in all countries, executives choose to perform easy‐to‐do processes. Critical top management support processes, which have higher impact on project success, often do not receive an appropriate level of attention from senior managers in the software industry.

Senior managers in the software industry may focus on critical processes, rather than paying lip service to less important ones. Specific practices designed to support these critical processes are also presented in the paper.

The paper suggests a detailed list of critical top management support processes, which significantly improve project success in different cultures. The paper also discusses this list in comparison with what is currently done by executives in the software industry and concludes with specific recommendations to managers in the software industry.

This paper aims to describe an effort to provide for a robust and secure software development paradigm intended to support DevSecOps in a naval aviation enterprise (NAE) software support activity (SSA), with said paradigm supporting strong traceability and provability concerning the SSA’s output product, known as an operational flight program (OFP). Through a secure development environment (SDE), each critical software development function performed on said OFP during its development has a corresponding record represented on a blockchain.

An SDE is implemented as a virtual machine or container incorporating software development tools that are modified to support blockchain transactions. Each critical software development function, e.g. editing, compiling, linking, generates a blockchain transaction message with associated information embedded in the output of a said function that, together, can be used to prove integrity and support traceability. An attestation process is used to provide proof that the toolchain containing SDE is not subject to unauthorized modification at the time said critical function is performed.

Blockchain methods are shown to be a viable approach for supporting exhaustive traceability and strong provability of development system integrity for mission-critical software produced by an NAE SSA for NAE embedded systems software.

A blockchain-based authentication approach that could be implemented at the OFP point-of-load would provide for fine-grain authentication of all OFP software components, with each component or module having its own proof-of-integrity (including the integrity of the used development tools) over its entire development history.

Many SSAs have established control procedures for development such as check-out/check-in. This does not prove the SSA output software is secure. For one thing, a build system does not necessarily enforce procedures in a way that is determinable from the output. Furthermore, the SSA toolchain itself could be attacked. The approach described in this paper enforces security policy and embeds information into the output of every development function that can be cross-referenced to blockchain transaction records for provability and traceability that only trusted tools, free from unauthorized modifications, are used in software development. A key original concept of this approach is that it treats assigned developer time as a transferable digital currency.

Many national and regional governments and various trade associations have created and are currently developing services that aim to provide support for firms that have just begun to or which plan to operate in international markets. Consequently, the purpose of this chapter is to illustrate the role of various support services especially in the case of software small and medium-sized enterprises (SMEs) aiming to expand internationally and accelerate their international growth. In the empirical part of the chapter, the authors review the key support organisations Finland has for its software industry. Through a descriptive empirical survey (n = 25) of the industry, we illustrate the role of various support services that are especially targeted at firms aiming to accelerate their international growth, irrespective of the phase of internationalisation. Furthermore, the authors study the use, quality and effectiveness of the internationalisation of support services from the viewpoint of managers of Finnish software SMEs. Based on our results, it is easy and logical to argue that better targeted programmes should be developed for rapidly internationalising firms in the turbulent software market. However, there are already a few innovative and better targeted programmes being offered to Finnish software firms. According to our study, in the later phases of internationalisation, the key to success is more closely linked to the availability of external funding as well as knowledge and contacts provided by international consultants.

With precursor software dating to 1972, multi‐LIS became the first commercially available, fully integrated library system in North America to run on the Unix operating system. In 1988, multiLIS developers, Sobeco Ernst & Young Inc. (SEY), ported multiLIS software to the MIPS Reduced Instruction Set Computer (RISC) processor, making it the First fully integrated software program to be available on a RISC platform. multiLIS fully supports both CAN/MARC and USMARC as well as the monographs specifications of UNIMARC. As the multiLIS software was developed in a resource‐sharing environment, consortiums are a natural market for the multiLIS product.

This article aims to outline steps for the inexperienced, including both internal and external considerations, to ensure informed choices when selecting digital library software.

The paper takes a step‐by‐step approach in how to choose the correct software for a specific library application; and then how to test it and cost out the project.

The choice of delivery software for digital libraries impacts usability, interoperability, support costs, and the ability to migrate materials over time. Intelligent selection requires careful assessment of internal needs and resources, as well as careful assessment of the options. Other considerations may be preferences related to the goals of your library, such as support of metadata standards, interoperability with other systems, and additional functionality.

If user and client needs are not weighed, the outcome will be a tremendous disappointment. In addition, failure to consider the hardware and personnel support necessary can spell disaster.

A clear and concise step‐by‐step approach to project management from assessment of requirements to purchase decision.

A common user interface replaces the multiple interfaces found among individual electronic library resources, reducing the time and effort spent by the user in both searching and learning to use a range of databases. Although the primary function of a common user interface is to simplify the search process, such products can be holistic solutions designed to address requirements other than searching, such as user authentication and site branding. This review provides a detailed summary of software currently on the market. The products reviewed were EnCompass, MetaLib, Find‐It‐All OneSearch, ZPORTAL, CPORTAL, InfoTrac Total Access, MetaFind, MuseSearch, SiteSearch, Single Search, Chameleon Gateway, and WebFeat.

The purpose of this paper is to evaluate open source software (OSS) for digital libraries and collection management and to propose different utilization scenarios based on the characteristics of the tools.

The tools are assessed on the basis of their technical features and options, the type of the content they manage, the support for common library operations such as cataloging and circulation, the searching support and the interoperability options. Then they are evaluated by users and finally a number of usage scenarios are analyzed based on the results of the evaluation.

The basic findings of the study is that open source digital library and collection management tools offer advanced operations and support various metadata and interoperability protocols with easy and user-friendly interfaces. Most of the tools are extensively used under various settings and establishments already. Language support for the interfaces should be extended with more languages and some tools with limited operations should be improved to be of practical use.

The findings of the paper could be used support the selection of specific open source tools for various types of establishments.

The study reviews the characteristics of a few OSS for digital libraries and collection management and reveals their specific strengths and weaknesses. It also presents a number of realistic scenarios and proposes the usage of specific tools based on time, technology and staff constraints.

This is a case study on the opportunities provided by Open Source library systems and the experience of delivering these systems through a shared service.

This chapter derives from desk research, interviews, and direct involvement in the project. The format is a case study, setting out a detailed timeline of events with information that can be applied in other settings.

This chapter presents reflections on the value and limitations of collaboration amongst libraries and librarians on an innovative approach to library systems and technologies. It also presents reflections on lessons learned from the processes and detailed discussion of the success factors for shared services and the reasons why such initiatives may not result in the outcomes predicted at the start.

Libraries and IT services considering Open Source and shared service approaches to provision will find material in this study useful when planning their projects.

The nature of collaboration and collaborative working is studied and observations made about the way that outcomes cannot always be predicted or controlled. In a genuine collaboration, the outcome is determined by the interactions between the partners and is unique to the specifics of that collaboration.

The case study derives from interviews, written material and direct observation not generally in the public domain, providing a strong insider’s view of the activity.

One key to improving team‐based software development is to support the developers’ ability to work together. Sets out one site’s response to this challenge. Developers at this site have a facility, which we will call the “team room”, allowing team members to work together. This is a computer‐supported meeting room that arose from the voluntary, and reflective, efforts of software developers to make it easier for them to work together. The team room’s popularity shows up in its extensive use for meetings and its acceptance as an integral part of software development at this site. When people use the team room, they work on a shared screen, making it easier to work together. Because they can work together, meetings become a time of work, not a pause between work sessions. Explains how these positive work outcomes have had some unexpected effects. For example, developers at this site now rely on room use to help deal with intra‐group conflict, so that the team room has become a buffer to social interaction, serving as a conduit for action.

The Bradley Library Information Support System (BLISS) is a comprehensive local area network designed to provide library users with an array of electronic information access and management services to support Bradley University's curriculum, research, and scholarly activities. The LAN is designed in a client/server architecture, with function‐specific Unix servers operating over an Ethernet network, to support a range of services both within the library and campuswide. BLISS workstations are available to both patrons and staff and located throughout the library; some BLISS resources are network‐accessible to the general campus community. A menu interface lists the resources available and establishes a transparent connection between the user and the selected resource. BLISS is a joint project of the library and computing services, providing a platform for the development of cohesive electronic information services and for the training, documentation, and mediation serices necessary to effectively use them.