Innovation, competition and public procurement in the pre-commercial phase

Should the supply or the demand side bear the risk connected to innovation? The two polar cases identified in the literature are the supply push and the demand pull. The former is the typical one, with the supplier bearing the costs and obtaining the benefits from innovating. The latter is technology procurement, where the buyer takes the risk, by procuring the innovative good or service. With respect to this, pre-commercial procurement is a peculiar solution that can explain the debate found in the literature relative to its configuration either as a supply-side or a demand-side instrument. The separation from the commercial phase allows the procurer to take only (part of) the risks connected to R&D services. Also, competition among suppliers gives the opportunity of evaluating different solutions and to obtain, in the commercial phase, a lower price for the innovative good. The counterpart of all this is a large portion of risk being left to the supplier. As a consequence, suppliers need to obtain a larger share of the benefits of the innovation process. This economic reason, besides the legal restrictions on State aid, explains the need for a shared risks-shared benefits approach, centred on the agreements on the assignment of IPRs

An evaluation of the total quality management implementation strategy for the advanced solid rocket motor project at NASA's Marshall Space Flight Center

An evaluation of the NASA's Marshall Space Flight Center (MSFC) strategy to implement Total Quality Management (TQM) in the Advanced Solid Rocket Motor (ASRM) Project is presented. The evaluation of the implementation strategy reflected the Civil Service personnel perspective at the project level. The external and internal environments at MSFC were analyzed for their effects on the ASRM TQM strategy. Organizational forms, cultures, management systems, problem solving techniques, and training were assessed for their influence on the implementation strategy. The influence of ASRM's effort was assessed relative to its impact on mature projects as well as future projects at MSFC

Goal sketching: towards agile requirements engineering

This paper describes a technique that can be used as part of a simple and practical agile method for requirements engineering. The technique can be used together with Agile Programming to develop software in internet time. We illustrate the technique and introduce lazy refinement, responsibility composition and context sketching. Goal sketching has been used in a number of real-world development projects, one of which is described here

Testing in the incremental design and development of complex products

Testing is an important aspect of design and development which consumes significant time and resource in many companies. However, it has received less research attention than many other activities in product development, and especially, very few publications report empirical studies of engineering testing. Such studies are needed to establish the importance of testing and inform the development of pragmatic support methods. This paper combines insights from literature study with findings from three empirical studies of testing. The case studies concern incrementally developed complex products in the automotive domain. A description of testing practice as observed in these studies is provided, confirming that testing activities are used for multiple purposes depending on the context, and are intertwined with design from start to finish of the development process, not done after it as many models depict. Descriptive process models are developed to indicate some of the key insights, and opportunities for further research are suggested

Industry-driven innovative system development for the construction industry: The DIVERCITY project

Collaborative working has become possible using the innovative integrated systems in construction as many activities are performed globally with stakeholders situated in various locations. The Integrated VR based information systems can bind the fragmentation and provide communication and collaboration between the distributed stakeholders n various locations. The development of these technologies is vital for the uptake of these systems by the construction industry. This paper starts by emphasising the importance of construction IT research and reviews some future research directions in this area. In particular, the paper explores how virtual prototyping can improve the productivity and effectiveness of construction projects, and presents DIVERCITY, which is th as a case study of the research in virtual prototyping. Besides, the paper explores the requirements engineering of the DIVERCITY project. DIVERCITY has large and evolving requirements, which considered the perspectives of multiple stakeholders, such as clients, architects and contractors. However, practitioners are often unsure of the detail of how virtual environments would support the construction process, and how to overcome some barriers to the introduction of new technologies. This complicates the requirements engineering process

A model of electronic warfare systems acquisition and engineering for Saudi Arabia

A major activity within the systems engineering process is the requirements definition and analysis phase. In technical systems, planning this phase looks too technical for top management and too broad for the engineers specialized in narrow technical fields. This categorization (too technical/too broad) represents a gap between top management and specialized engineering. In Saudi Arabia, such a gap is believed to be very wide. The main objective of this research is to find a way to narrow this gap between management and engineering when planning government systems, especially in electronic warfare (EW) systems. A solution in this effort is to streamline the process of systems acquisition, with more focus on the requirements definition phase before signing the contract. An acquisition procedural model has been developed. This model is structured in five sequenced phases linked through decision points. The first phase focuses on a method to develop threat analysis reports and why such a deterrent capability is needed. Requirements engineering is the main activity within the second phase. In this phase, the concept of structuring systems and subsystems into objects is explored by applying object-oriented expert systems to probe requirements completeness, correctness, consistency, traceability, timeliness, and documentation. Skeletons of three object-oriented knowledge bases for a Planning Support for Communication System (PSCS) were developed using EW sub-fields as the domain objects. The other three model phases are invitation for presentation, request-for-proposal (RFP) package development, and source selection. Government and corporate engineers in Saudi Arabia have reviewed the model, and it has a strong potential of becoming a Saudi national standard. Data analysis attributes the model\u27s strength to its applicability in 1) structuring the task of systems acquisition and keeping a documentation profile; 2) increasing government agencies\u27 self-reliance when planning systems; and 3) facilitating the generation of sound requirements --Abstract, page iii

Requirements engineering: a review and research agenda

This paper reviews the area of requirements engineering. It outlines the key concerns to which attention should be devoted by both practitioners, who wish to "reengineer" their development processes, and academics, seeking intellectual challenges. It presents an assessment of the state-of-the-art and draws conclusions in the form of a research agenda

Challenges of adopting agile methods in a public organization

Agile development methods are widely used among business enterprises. Since the introduction of the Agile Manifesto in 2001, several agile methods have been implemented, first in single-team set-ups and later in larger multi-team set-ups for complex Information Technology (IT) system development. However, the adoption of agile methods has been slow in the public sector. This is also reflected in the academic literature, as there are only a few studies discussing agile adoption in public organizations. This paper contributes to research on the use of agile practices specifically in the context of public organizations, and sheds light on the challenges a public organization may face while adopting these practices. The aim of this paper is to identify and categorize the challenges that may hinder efficient adoption and use of agile methods in public IT projects that include private software vendors. This research is based on a case study of a large governmental office. As a result, this paper presents several categories of identified challenges, the root causes of these challenges, and a discussion of the characteristics of these challenges for the public sector

Case study : an evaluation of the implementation of an Enterprise Resource Planning System (ERP) at a South African municipal entity.

Master of Commerce in Information Systems and Technology. University of KwaZulu-Natal, Pietermaritzburg, 2018.Enterprise resource planning (ERP) is a computer based software application that is widely implemented in many business organisations. These systems have evolved over the years into component based modules with the ability to easily integrate with other systems, provide real time information and improve information sharing and collaboration. Choosing an ERP system is a complex process and the literature clearly illustrates the failure of organisations to effectively specify, select and implement ERP systems resulting in the inability to effectively harness the associated benefits. This study focuses on a South African water utility and the processes followed in procuring and implementing an ERP system. It is interesting to note, that in this study, despite the utility having experienced a failed ERP implementation decided to replace the same? ERP system. A rigorous process was followed to find a replacement ERP system only to set aside all alternate commercial of-the-shelf systems and re-implement the original failed ERP system. To gain insight of the processes followed, the COTS theoretical framework is presented to bring the reader’s attention to associated theoretical studies. In this study, we will conduct a systematic literature review on ERP systems, its background, implementation processes and associated implementation outcomes. This research, presents a case study that will describe and explore the process of ERP implementation at the water utility. We will document the process the utility followed in acquiring and setting up functional and non-functional evaluation criteria for the ERP system. Further, we have considered the processes of preparation, evaluation, selection and implementation. The analysis of the implementation process has brought to light the importance of defining ERP scopes based on business requirements, specifications based on the business scopes and evaluation criterion. The findings and results from this case study will contribute to the conceptual and contextual understanding of the specification, selection and implementation of ERP systems