A Survey of Applications and Research in Integrated Design Systems Technology

The initial part of the study was begun with a combination of literature searches, World Wide Web searches, and contacts with individuals and companies who were known to members of our team to have an interest in topics that seemed to be related to our study. There is a long list of such topics, such as concurrent engineering, design for manufacture, life-cycle engineering, systems engineering, systems integration, systems design, design systems, integrated product and process approaches, enterprise integration, integrated product realization, and similar terms. These all capture, at least in part, the flavor of what we describe here as integrated design systems. An inhibiting factor in this inquiry was the absence of agreed terminology for the study of integrated design systems. It is common for the term to be applied to what are essentially augmented Computer-Aided Design (CAD) systems, which are integrated only to the extent that agreements have been reached to attach proprietary extensions to proprietary CAD programs. It is also common for some to use the term integrated design systems to mean a system that applies only, or mainly, to the design phase of a product life cycle. It is likewise common for many of the terms listed earlier to be used as synonyms for integrated design systems. We tried to avoid this ambiguity by adopting the definition of integrated design systems that is implied in the introductory notes that we provided to our contacts, cited earlier. We thus arrived at this definition: Integrated Design Systems refers to the integration of the different tools and processes that comprise the engineering, of complex systems. It takes a broad view of the engineering of systems, to include consideration of the entire product realization process and the product life cycle. An important aspect of integrated design systems is the extent to which they integrate existing, "islands of automation" into a comprehensive design and product realization environment. As the study progressed, we relied increasingly upon a networking approach to lead us to new information. The departure point for such searches often was a government-sponsored project or a company initiative. The advantage of this approach was that short conversations with knowledgeable persons would usually cut through confusion over differences of terminology, thereby somewhat reducing the search space of the study. Even so, it was not until late in our eight-month inquiry that we began to see signs of convergence of the search, in the sense that a number of the latest inquiries began to turn up references to earlier contacts. As suggested above, this convergence often occurred with respect to particular government or company projects

Benefits realization management in the context of a national digital transformation initiative in English provider organizations

BACKGROUND: The Global Digital Exemplar (GDE) Programme is a national initiative to promote digitally enabled transformation in English provider organizations. The Programme applied benefits realization management techniques to promote and demonstrate transformative outcomes. This work was part of an independent national evaluation of the GDE Programme. AIMS: We explored how benefits realization management was approached and conceptualized in the GDE Programme. METHODS: We conducted a series of 36 longitudinal case studies of provider organizations participating in the GDE Programme, 12 of which were in depth. Data collection included a combination of 628 interviews (with implementation staff in provider organizations, national programme management staff, and suppliers), 499 documents (of national and local implementation plans and lessons learned), and 190 nonparticipant observations (of national and local programme management meetings to develop insights into the broader context of benefits realization activities, tensions arising, and how these were negotiated). Data were coded drawing on a sociotechnical framework developed in related work and thematically analyzed, initially within and then across cases, with the help of NVivo 11 software. RESULTS: Most stakeholders broadly agreed with the rationale of benefits realization in the GDE Programme to show due diligence that public money was appropriately spent, and to develop an evidence base supporting the value of digitally enabled transformation. Differing national and local reporting purposes, however, created tensions. Central requirements, for progress reporting and tracking high-level benefits, had limited perceived local value and were seen to impose an unnecessary burden on provider organizations. This was accentuated by the lack of harmonization of reporting requirements to different stakeholders (which differed in content and timing). There were tensions between the desire for early evidence of outcomes and the slow processes of infrastructural change (which created problems of attribution of benefits to causes as benefits emerged gradually and over long timeframes), and also between reporting immediately visible local changes and showing how these flowed through to high level organization wide benefits (eg, in terms of health outcomes or cost savings/return on investment). The attempt to fulfill these diverging agendas and informational needs within a single reporting tool had limited success. These difficulties were mitigated by efforts to simplify reporting requirements and to support targeted collection of key national outcome measures. Although progress was hampered by an initial lack of benefits realization expertise in provider organizations, some providers subsequently retained these skills for their own change management purposes. CONCLUSIONS: There is a need to recognize the limitations and cost of benefits realization management practices in the context of healthcare digitalization where benefits may materialize over long timeframes and in unanticipated ways. Although diverse stakeholder information needs may create tensions, prior agreement about rationales for collecting information and a targeted approach to tracking local and high-level benefits may enhance local relevance, reduce perceived reporting burdens, and improve acceptance/effectiveness. A single integrated reporting mechanism is unlikely to fulfill both national and local requirements

Towards implementing integrated building product libraries

Electronic product catalogues and brochures are gaining popularity but there is little agreement on content, format and searching methods. This limits their usability and integration with existing construction software tools. This paper examines a productmodelling approach to delivering building product information and describes a proposed multi-tier client-server environment. ISO/STEP and IAI/IFC building product models are considered to facilitate representation, exchange and sharing of product information. The proposed architecture incorporates scalability with middleware components that would provide single or few points of entry to integrated product information. This paper is part of a research project, which builds on the results of related projects including ConstructIT Strategy, PROCAT-GEN, Active Catalog, COMBINE and ARROW, towards implementing the required software components

Report of the Stanford Linked Data Workshop

The Stanford University Libraries and Academic Information Resources (SULAIR) with the Council on Library and Information Resources (CLIR) conducted at week-long workshop on the prospects for a large scale, multi-national, multi-institutional prototype of a Linked Data environment for discovery of and navigation among the rapidly, chaotically expanding array of academic information resources. As preparation for the workshop, CLIR sponsored a survey by Jerry Persons, Chief Information Architect emeritus of SULAIR that was published originally for workshop participants as background to the workshop and is now publicly available. The original intention of the workshop was to devise a plan for such a prototype. However, such was the diversity of knowledge, experience, and views of the potential of Linked Data approaches that the workshop participants turned to two more fundamental goals: building common understanding and enthusiasm on the one hand and identifying opportunities and challenges to be confronted in the preparation of the intended prototype and its operation on the other. In pursuit of those objectives, the workshop participants produced:1. a value statement addressing the question of why a Linked Data approach is worth prototyping;2. a manifesto for Linked Libraries (and Museums and Archives and …);3. an outline of the phases in a life cycle of Linked Data approaches;4. a prioritized list of known issues in generating, harvesting & using Linked Data;5. a workflow with notes for converting library bibliographic records and other academic metadata to URIs;6. examples of potential “killer apps” using Linked Data: and7. a list of next steps and potential projects.This report includes a summary of the workshop agenda, a chart showing the use of Linked Data in cultural heritage venues, and short biographies and statements from each of the participants

Working Notes from the 1992 AAAI Workshop on Automating Software Design. Theme: Domain Specific Software Design

The goal of this workshop is to identify different architectural approaches to building domain-specific software design systems and to explore issues unique to domain-specific (vs. general-purpose) software design. Some general issues that cut across the particular software design domain include: (1) knowledge representation, acquisition, and maintenance; (2) specialized software design techniques; and (3) user interaction and user interface

A Review of Software Reliability Testing Techniques

In the era of intelligent systems, the safety and reliability of software have received more attention. Software reliability testing is a significant method to ensure reliability, safety and quality of software. The intelligent software technology has not only offered new opportunities but also posed challenges to software reliability technology. The focus of this paper is to explore the software reliability testing technology under the impact of intelligent software technology. In this study, the basic theories of traditional software and intelligent software reliability testing were investigated via related previous works, and a general software reliability testing framework was established. Then, the technologies of software reliability testing were analyzed, including reliability modeling, test case generation, reliability evaluation, testing criteria and testing methods. Finally, the challenges and opportunities of software reliability testing technology were discussed at the end of this paper

A Human-Centric Approach to Group-Based Context-Awareness

The emerging need for qualitative approaches in context-aware information processing calls for proper modeling of context information and efficient handling of its inherent uncertainty resulted from human interpretation and usage. Many of the current approaches to context-awareness either lack a solid theoretical basis for modeling or ignore important requirements such as modularity, high-order uncertainty management and group-based context-awareness. Therefore, their real-world application and extendability remains limited. In this paper, we present f-Context as a service-based context-awareness framework, based on language-action perspective (LAP) theory for modeling. Then we identify some of the complex, informational parts of context which contain high-order uncertainties due to differences between members of the group in defining them. An agent-based perceptual computer architecture is proposed for implementing f-Context that uses computing with words (CWW) for handling uncertainty. The feasibility of f-Context is analyzed using a realistic scenario involving a group of mobile users. We believe that the proposed approach can open the door to future research on context-awareness by offering a theoretical foundation based on human communication, and a service-based layered architecture which exploits CWW for context-aware, group-based and platform-independent access to information systems