The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
This paper describes our REDEPEND tool for i* goal modelling and analysis, and new features designed to make it more usable and useful. Pattern-based techniques that generate text requirements statements from graphical i* models improve the productivity and utility of REDEPEND in requirements projects
Poirot is a Web-based tool supporting traceability of distributed heterogeneous software artifacts. A probabilistic network model is used to generate traces between requirements, design elements, code and other artifacts stored in distributed 3rd party case tools such as DOORS, rational rose, and source code repositories. The tool is designed with extensibility in mind, so that additional artifact...
There is evidence to suggest that the software industry has not yet matured as regards management of nonfunctional requirements (NFRs). Consequently the cost of achieving required quality is unnecessarily high. To try and avoid this, the telecommunication systems provider Ericsson defined a research task to try and improve the management of requirements for capacity, which is one of the most critical...
Requirements engineering for video games must address a wide range of functional and non-functional requirements. Video game designers are most concerned with capturing and representing the player experience: the means by which the player's consciousness is cognitively engaged while simultaneously inducing emotional responses. We show that emotional requirements can be expressed in two parts: as the...
Jackson's concept of "problem frame" has influenced requirements engineering (RE) by emphasizing the constituent problems that system requirements address. But RE is itself a problem, one that may be supported by implemented systems for which, presumably, RE is the real-world domain in which the system operates. Even when the intention is not to specify RE support technology, the concept...
The selection of COTS components is made not only by an analysis of their technical quality but also (and sometimes mostly) by considering how they fulfill those non-technical requirements considered relevant, which refer to licensing, reputation, and similar issues. In this paper we present an approach for managing nontechnical requirements during COTS selection. The proposal is based on extending...
Explicitly addressing fault-tolerance during the requirements analysis phase facilitates the early detection of inconsistencies between functional and fault-tolerance requirements, which could potentially reduce the overall development costs. Most existing approaches use redundancy of services as a means to mask faults, where it is difficult to provide a systematic approach for modeling and analyzing...
Finding the right traceability process that delivers effective and efficient traceability can be difficult. This panel explores traceability challenges and solutions for finding the right techniques and process to deliver costeffective traceability within an organization.
Domain knowledge is one of crucial factors to get a great success in requirements elicitation of high quality, and only domain experts, not requirements analysts, have it. We propose a new requirements elicitation method ORE (ontology based requirements elicitation), where a domain ontology can be used as domain knowledge. In our method, a domain ontology plays a role on semantic domain which gives...
A technique is presented for obtaining a specification from a requirement through a series of incremental steps. The starting point is a problem frame description involving a requirement on the phenomena of the problem domain, and a decomposition of the environment into domains, connected to one another and to the machine being implemented by shared phenomena. In each step, the requirement is moved...
The U.S. DoD Joint Tactical Radio System (JTRS) Handheld, Manpack, Small Form Fit (HMS) program delivers power efficient, low-cost radio sets for installation in 16 different host platforms ranging from high-performance Manpacks to disposable sensors. Aggressive cost targets are achieved through the use of a modular design resulting in a product line of radio modules that leverage open standards for...
This paper presents a methodology for developing the requirements for general purpose scientific computing software. The first step in the methodology is to determine the general purpose scientific software of interest. The second step consists of a commonality analysis on this identified family of general purpose tools to document the terminology, commonalities and variabilities. The commonality...
As functionality in vehicles grows more complex and development becomes distributed over several geographical sites, elicitation and visualization of requirements become more critical. This paper presents a set of evaluation criteria for the quality of use cases. The criteria are applied to use cases that are currently used in industry and developed according to current industrial practice. The paper...
The dialogue between end-user and developer presents several challenges in requirements development. One issue is the gap between the conceptual models of end-users and formal specification/analysis models of developers. This paper presents a novel technique for the video analysis of scenarios, relating the use of video-based requirements to process models of software development. It uses a knowledge...
Representation and reasoning about information system (IS) requirements is facilitated with the use of goal models to describe the desired and undesired IS behaviors. One difficulty in building and using goal models is in knowing why a model instance is as it is at some point of the requirements engineering (RE) process. If justifications for modeling choices are missing, an instance of a goal model...
The i* approach is a consolidated modelling technique that has proven to be useful in the requirements engineering phases of software development. Using i* requires the adoption of a methodology for defining the models and tool support for manipulating them. For addressing those aspects, we propose J-PRiM, a tool that allows to define i* models by applying PRiM, our process reengineering i* methodology
Use cases often capture the expected behaviors of a system and its components. During requirements analysis, it is important to understand and model the relationship among different use cases. The information of such relationship can guide the design of object collaboration for realizing these use cases. In this paper, we analyze the limitations with the existing approaches for modeling the use-case...
DesCOTS is a system that has an aim to help clients in the selection of COTS components. This system is based in the use of quality models associated to a software domain for evaluating the products in that domain, and for defining in a formal way the requirements of the clients for finding a suitable product in that domain. The evaluation and the formal definition of requirements are facilitated...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.