Trouble Shooting Manuals (TSMs) provide useful information and guidelines for machinery maintenance, in particular, for fault isolation given a failure mode. TSMs produced by OEMs are usually updated based on feedback or requests from end users. Performing such update is very demanding as it requires collecting information from maintenance practices and integrating the new findings into the tro...

In a modern approach to software design, development and maintenance, new models of application building are required, which replace the traditional phase-refinement, waterfall model with the notion of software evolution [1]. In fact, software systems are in practice always built incrementally, and requirement analysis continues, de facto, also during the development process (requirement adjust...

PC-FMEA is a method that combines the pairwise comparison and basic FMEA (Failure Modes Effects Analysis) methods. Using comparison, which of risks more severe, common or noticeable can be determined. The results evaluated by modeled with networks, where ranked according to criteria using PageRank weighted in-degree values. Applying these two solutions together, form risk assessment created are...

In the development of safety-critical systems, it is important to perform failure modes and effects analysis (FMEA) identify potential failures. However, traditional FMEA activities tend be considered difficult time-consuming tasks. To compensate for difficulty task, various types tools are used increase quality effectiveness reports. This paper explains an automatic tool that integrates model-...

Failure modes and effects analysis (FMEA) has been used to identify the critical risk events and predict a system failure to avoid or reduce the potential failure modes and their effect on operations. The risk priority number (RPN) is the classical method to evaluate the risk of failure in conventional FMEA. RPN, which ranges from 1 to 1000, is a mathematical product of three parameters—severit...

Defining software requirements is a complex and difficult process, which often leads to costly project failures. Requirements emerge from a collaborative and interactive negotiation process that involves heterogeneous stakeholders (people involved in an elicitation process such as users, analysts, developers, and customers). Practical experience shows that prioritizing requirements is not as st...

Proper management of requirements is crucial to successful development software within limited time and cost. Nonfunctional requirements (NFR) are one of the key criteria to derive a comparison among various software systems. In most of software development NFR have be specified as an additional requirement of software. NFRs such as performance, reliability, maintainability, security, accuracy ...