For large software projects it is important to have some traceability between artefacts from different phases (e.g., requirements, designs, code), and between artefacts and the involved developers. This is especially critical during maintenance, when people working on the software may be different from the original developers and therefore have a harder struggle to understand the artefacts and ...

The building sector accounts for nearly 41% of U.S. primary energy use. Various tools have been developed for estimating the embodied energy during the design and construction phase of a building. However, there is a lack of a comprehensive mechanism which can measure and control the energy flow occurring during the operation phase of a building. Loss of efficiency of building systems and deter...

Requirements continue to be a major source of problems during development and maintenance of software-intensive systems. Requirements engineering researchers, educators, and practitioners seek to create, identify, and transfer solutions to these problems into practice. However, the lack of mechanisms to integrate these efforts negatively impacts their effectiveness in improving the state-of-the...

Standards are consensus-based documents that codify best practices. The use of standards (such as IEEE/EIA 12207, a maintenance model) is noted to assure that software projects are successfully completed on time, within budget and with the intended benefits. However, available standards for software maintenance model are mainly meant for in-house custom software. Are the published standards suf...

The end-to-end response-time and delay analysis can verify timing requirements specified on vehicular distributed embedded systems without performing exhaustive testing. For this purpose, the timing requirements and constraints should be unambiguously translated among several models, methodologies and tools that are used at various abstraction levels and phases during the industrial development...

Handling inconsistency is an increasingly important issue in data and knowledge engineering. A number of logic-based proposals have been made for handling aspects of inconsistency in beliefs (where we use beliefs as a general term to encompass representations of the real world) including belief revision theory, truth-maintenance, argumentation systems, and knowledgebase merging. In contrast, th...

A management model for explaining software errors is developed and estimated. The model is used to analyze two years of error log data at a commercial site. The focus is on identifying managerially controllable factors which affect software reliability. At the research site, application systems which (1) underwent frequent modification; (2) were maintained by programmers with low levels of appl...

The Ramsey test provides an intuitive link between conditionals and belief revision. How easy is it to incorporate a Ramseyaccount of conditionals in a reason maintenance system? In this paper, it is shown that this is indeed possible, within a relevance-logical framework. In addition, it is shown that independently motivated requirements on reason maintenance systems allow us to gracefully cir...

The security of the functioning systems represents, through four specific components (security, availability, reliability and maintenance), a basic component processing requirement. Monitoring all intrinsic operating parameters oil gas pipelines can be technically detected diagnosed by: –existing defects; –rapid effective intervention to eliminate damage, if they occurred. To establish maintena...

The research described in this paper is concerned with the application of information retrieval to software maintenance, and in particular to the problem of recovering traceability links between the source code of a system and its free text documentation. We introduce a method based on the general idea of vector space information retrieval and apply it in two case studies to trace C++ source co...