408,473 research outputs found

    Sustainable Paths for Data-Intensive Research Communities at the University of Melbourne: A Report for the Australian Partnership for Sustainable Repositories

    Get PDF
    This report presents the local project findings with a view to identifying how these findings may add to the knowledge base for informing an e-research strategy for the University of Melbourne. It also provides important considerations for how major Government initiatives in research policy and funding might impact on research data and records management requirements. Eleven research communities from diverse disciplines were consulted for an audit of their data management practices. Researchers from these communities represent a number of diverse disciplines: Applied Economics; Astrophysics; Computer Science and Software Engineering; Education; Ethnography; Experimental Particle Physics; Humanities informatics; Hydrology and Environmental Engineering; Linguistics; Medical informatics; Neuroscience and the Performing Arts. In addition to the specific findings for each group audited, the project findings also provide information about sustainability issues around research data management practices at the university

    Analyse der Anforderungen an Risikomanagementsoftware fĂŒr Projektmanagement

    Get PDF
    Diese Masterarbeit beschĂ€ftigt sich mit der Thematik Risikomanagement und zeigt jene Anforderungen auf, die an eine Risikomanagementsoftware gestellt werden, die fĂŒr den Bereich des Projektmanagements eingesetzt werden kann. Die Arbeit ist in einen theoretischen Teil und einen empirischen Teil untergliedert. Im theoretischen Teil werden dem Leser im ersten Schritt die Vokabeln und Begriffe des Risiko- und Projektmanagements nĂ€her gebracht und ihm damit ein Überblick ĂŒber den Themenbereich Risikomanagement geboten. Im zweiten Schritt werden jene Methoden nĂ€her beschrieben, die laut Literaturquellen Anwendung in den einzelnen Phasen des Risikomanagements finden. Der empirische Teil der Arbeit beschĂ€ftigt sich mit der eigentlichen Analyse der Anforderungen, die an eine Risikomanagementsoftware fĂŒr Projektmanagement gestellt werden. Dazu werden die drei Wissensquellen Literatur, Fragebogen und Interviews herangezogen. Als Ergebnis dieser Wissensquellen werden dann die folgenden Anforderungen an eine Software dieser Art gestellt: Modularer Aufbau, Anpassbarkeit der Methoden an das Projekt, Kollaboratives Arbeiten, Usability Engineering & User Interface Design, Schnittstellen zu Projektmanagementtools, Schnittstellen zu WissensdatenbĂ€nkeThis master’s thesis is about risk management and points out the special requirements for risk management software which is used in project management. The thesis has a theoretical part and an empirical part. In the theoretical part, the reader will get an overview of the terminology used in risk and project management. This is meant to give a general view on the subject risk management. Second, there will be a description of the methods used in different phases of risk management according to the literature. The empirical part of the work presents an analysis of requirements for risk management software for project management. For that purpose the three knowledge sources literature, questionnaire and interviews were conducted. As a result of these sources the following requirements on risk management software were found: modular structure, adaptability of the methods depending on the project, collaborative working, usability engineering & user interface design, interfaces to project management tools, interfaces to knowledge data base

    Reusable Knowledge-based Components for Building Software Applications: A Knowledge Modelling Approach

    Get PDF
    In computer science, different types of reusable components for building software applications were proposed as a direct consequence of the emergence of new software programming paradigms. The success of these components for building applications depends on factors such as the flexibility in their combination or the facility for their selection in centralised or distributed environments such as internet. In this article, we propose a general type of reusable component, called primitive of representation, inspired by a knowledge-based approach that can promote reusability. The proposal can be understood as a generalisation of existing partial solutions that is applicable to both software and knowledge engineering for the development of hybrid applications that integrate conventional and knowledge based techniques. The article presents the structure and use of the component and describes our recent experience in the development of real-world applications based on this approach

    Integrating automated support for a software management cycle into the TAME system

    Get PDF
    Software managers are interested in the quantitative management of software quality, cost and progress. An integrated software management methodology, which can be applied throughout the software life cycle for any number purposes, is required. The TAME (Tailoring A Measurement Environment) methodology is based on the improvement paradigm and the goal/question/metric (GQM) paradigm. This methodology helps generate a software engineering process and measurement environment based on the project characteristics. The SQMAR (software quality measurement and assurance technology) is a software quality metric system and methodology applied to the development processes. It is based on the feed forward control principle. Quality target setting is carried out before the plan-do-check-action activities are performed. These methodologies are integrated to realize goal oriented measurement, process control and visual management. A metric setting procedure based on the GQM paradigm, a management system called the software management cycle (SMC), and its application to a case study based on NASA/SEL data are discussed. The expected effects of SMC are quality improvement, managerial cost reduction, accumulation and reuse of experience, and a highly visual management reporting system

    Process of designing robust, dependable, safe and secure software for medical devices: Point of care testing device as a case study

    Get PDF
    This article has been made available through the Brunel Open Access Publishing Fund.Copyright © 2013 Sivanesan Tulasidas et al. This paper presents a holistic methodology for the design of medical device software, which encompasses of a new way of eliciting requirements, system design process, security design guideline, cloud architecture design, combinatorial testing process and agile project management. The paper uses point of care diagnostics as a case study where the software and hardware must be robust, reliable to provide accurate diagnosis of diseases. As software and software intensive systems are becoming increasingly complex, the impact of failures can lead to significant property damage, or damage to the environment. Within the medical diagnostic device software domain such failures can result in misdiagnosis leading to clinical complications and in some cases death. Software faults can arise due to the interaction among the software, the hardware, third party software and the operating environment. Unanticipated environmental changes and latent coding errors lead to operation faults despite of the fact that usually a significant effort has been expended in the design, verification and validation of the software system. It is becoming increasingly more apparent that one needs to adopt different approaches, which will guarantee that a complex software system meets all safety, security, and reliability requirements, in addition to complying with standards such as IEC 62304. There are many initiatives taken to develop safety and security critical systems, at different development phases and in different contexts, ranging from infrastructure design to device design. Different approaches are implemented to design error free software for safety critical systems. By adopting the strategies and processes presented in this paper one can overcome the challenges in developing error free software for medical devices (or safety critical systems).Brunel Open Access Publishing Fund
    • 

    corecore