18,555 research outputs found

    Spectral analysis of suspension system of a commercial city bus

    Get PDF
    There is an ever increasing demand for intelligent and efficient urban vehicle systems that fulfill several requirements, e.g., low cost maintainability and high passenger comfort. Concerning these goals reliable methods are needed to model and to evaluate the imposed performances. In this paper a spectral analysis of the suspension system of a commercial city bus is presented. Based on experimental data taken on a city bus, the vibrations emerging on the wheels and the body are analyzed in the frequency domain. The goal of the analysis is to characterize the main eigenfrequencies of the suspension system and its damping in amplitude and also to evaluate both the road and the suspension system in terms of passenger comfort according to ISO standards. © 2016 IEEE

    Integrating IVHM and Asset Design

    Get PDF
    Integrated Vehicle Health Management (IVHM) describes a set of capabilities that enable effective and efficient maintenance and operation of the target vehicle. It accounts for the collection of data, conducting analysis, and supporting the decision-making process for sustainment and operation. The design of IVHM systems endeavours to account for all causes of failure in a disciplined, systems engineering, manner. With industry striving to reduce through-life cost, IVHM is a powerful tool to give forewarning of impending failure and hence control over the outcome. Benefits have been realised from this approach across a number of different sectors but, hindering our ability to realise further benefit from this maturing technology, is the fact that IVHM is still treated as added on to the design of the asset, rather than being a sub-system in its own right, fully integrated with the asset design. The elevation and integration of IVHM in this way will enable architectures to be chosen that accommodate health ready sub-systems from the supply chain and design trade-offs to be made, to name but two major benefits. Barriers to IVHM being integrated with the asset design are examined in this paper. The paper presents progress in overcoming them, and suggests potential solutions for those that remain. It addresses the IVHM system design from a systems engineering perspective and the integration with the asset design will be described within an industrial design process

    Quality-aware model-driven service engineering

    Get PDF
    Service engineering and service-oriented architecture as an integration and platform technology is a recent approach to software systems integration. Quality aspects ranging from interoperability to maintainability to performance are of central importance for the integration of heterogeneous, distributed service-based systems. Architecture models can substantially influence quality attributes of the implemented software systems. Besides the benefits of explicit architectures on maintainability and reuse, architectural constraints such as styles, reference architectures and architectural patterns can influence observable software properties such as performance. Empirical performance evaluation is a process of measuring and evaluating the performance of implemented software. We present an approach for addressing the quality of services and service-based systems at the model-level in the context of model-driven service engineering. The focus on architecture-level models is a consequence of the black-box character of services

    Integrating IVHM and asset design

    Get PDF
    Integrated Vehicle Health Management (IVHM) describes a set of capabilities that enable effective and efficient maintenance and operation of the target vehicle. It accounts for the collecting of data, conducting analysis, and supporting the decision-making process for sustainment and operation. The design of IVHM systems endeavours to account for all causes of failure in a disciplined, systems engineering, manner. With industry striving to reduce through-life cost, IVHM is a powerful tool to give forewarning of impending failure and hence control over the outcome. Benefits have been realised from this approach across a number of different sectors but, hindering our ability to realise further benefit from this maturing technology, is the fact that IVHM is still treated as added on to the design of the asset, rather than being a sub-system in its own right, fully integrated with the asset design. The elevation and integration of IVHM in this way will enable architectures to be chosen that accommodate health ready sub-systems from the supply chain and design trade-offs to be made, to name but two major benefits. Barriers to IVHM being integrated with the asset design are examined in this paper. The paper presents progress in overcoming them, and suggests potential solutions for those that remain. It addresses the IVHM system design from a systems engineering perspective and the integration with the asset design will be described within an industrial design process

    A method for tailoring the information content of a software process model

    Get PDF
    The framework is defined for a general method for selecting a necessary and sufficient subset of a general software life cycle's information products, to support new software development process. Procedures for characterizing problem domains in general and mapping to a tailored set of life cycle processes and products is presented. An overview of the method is shown using the following steps: (1) During the problem concept definition phase, perform standardized interviews and dialogs between developer and user, and between user and customer; (2) Generate a quality needs profile of the software to be developed, based on information gathered in step 1; (3) Translate the quality needs profile into a profile of quality criteria that must be met by the software to satisfy the quality needs; (4) Map the quality criteria to set of accepted processes and products for achieving each criterion; (5) Select the information products which match or support the accepted processes and product of step 4; and (6) Select the design methodology which produces the information products selected in step 5

    The New NASA Approach to Reliability and Maintainability

    Get PDF
    In 2017, after 20 years, NASA issued a major revision of its reliability and maintainability (R&M) policy, NASA-STD- 8729.1A. Formerly NASA required certain specific R&M activities during each succeeding phase of project development. Now NASA requires a project to start by including the initial development of R&M requirements and the devising of strategies to implement and verify them. Rather than resolving all the requirements first and then designing the system, as has been usual in systems design, the design process now is to work top down by layers. It begins by first identifying the top level requirements and suggesting top level design strategies for those, then making these higher strategies the basis for a lower level set of requirements, and so on down to the lowest components. This approach is intended to ensure that R&M is designed in from the beginning rather than added later with difficulty to a completed design concept. The new R&M standard uses an innovative and effective top-down system design approach intended to effectively implement R&M

    A framework for selecting workflow tools in the context of composite information systems

    Get PDF
    When an organization faces the need of integrating some workflow-related activities in its information system, it becomes necessary to have at hand some well-defined informational model to be used as a framework for determining the selection criteria onto which the requirements of the organization can be mapped. Some proposals exist that provide such a framework, remarkably the WfMC reference model, but they are designed to be appl icable when workflow tools are selected independently from other software, and departing from a set of well-known requirements. Often this is not the case: workflow facilities are needed as a part of the procurement of a larger, composite information syste m and therefore the general goals of the system have to be analyzed, assigned to its individual components and further detailed. We propose in this paper the MULTSEC method in charge of analyzing the initial goals of the system, determining the types of components that form the system architecture, building quality models for each type and then mapping the goals into detailed requirements which can be measured using quality criteria. We develop in some detail the quality model (compliant with the ISO/IEC 9126-1 quality standard) for the workflow type of tools; we show how the quality model can be used to refine and clarify the requirements in order to guarantee a highly reliable selection result; and we use it to evaluate two particular workflow solutions a- ailable in the market (kept anonymous in the paper). We develop our proposal using a particular selection experience we have recently been involved in, namely the procurement of a document management subsystem to be integrated in an academic data management information system for our university.Peer ReviewedPostprint (author's final draft

    The impact of using pair programming on system evolution a simulation-based study

    Get PDF
    In this paper we investigate the impact of pair--programming on the long term evolution of software systems. We use system dynamics to build simulation models which predict the trend in system growth with and without pair programming. Initial results suggest that the extra effort needed for two people to code together may generate sufficient benefit to justify pair programming.Peer reviewe

    Determination and evaluation of web accessibility

    Get PDF
    The Web is the most pervasive collaborative technology in widespread use today; however, access to the web and its many applications cannot be taken for granted. Web accessibility encompasses a variety of concerns ranging from societal, political, and economic to individual, physical, and intellectual through to the purely technical. Thus, there are many perspectives from which web accessibility can be understood and evaluated. In order to discuss these concerns and to gain a better understanding of web accessibility, an accessibility framework is proposed using as its base a layered evaluation framework from Computer Supported Co-operative Work research and the ISO standard, ISO/IEC 9126 on software quality. The former is employed in recognition of the collaborative nature of the web and its importance in facilitating communication. The latter is employed to refine and extend the technical issues and to highlight the need for considering accessibility from the viewpoint of the web developer and maintainer as well as the web user. A technically inaccessible web is unlikely to be evolved over time. A final goal of the accessibility framework is to provide web developers and maintainers with a practical basis for considering web accessibility through the development of a set of accessibility factors associated with each identified layer
    • 

    corecore