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.
Requirements engineering for complex systems often requires inter-disciplinary collaboration between domain experts who might not have software or systems engineering background. Existing requirements modeling languages unfortunately do not support this scenario well. First, the visual notation of languages like UML or SysML does not follow scientific heuristics and therefore does not provide a homogeneous...
Rationale and rationale management have been playing an increasingly prominent role in software system development mainly due to the knowledge demand during system evaluation, maintenance, and evolution, especially for large and complex systems. The rationale management for requirements engineering, as a commencing and critical phase in software development life cycle, is still under-exploited. In...
Developing software systems in heavily regulated industries requires methods to ensure systems comply with regulations and law. A method to acquire finite state machines (FSM) from stakeholder rights and obligations for compliance monitoring is proposed. Rights and obligations define what people are permitted or required to do; these rights and obligations affect software requirements and design....
The success of a software product depends on meeting the requirements and satisfying the needs of the users. The identification of these requirements and needs is the task of requirements engineering. This paper presents a method for the elicitation and documentation of requirements. The method uses collaborative technologies (a wiki system) and audio recordings to allow multiple stakeholders the...
Software product lines are inevitably subject to continuous evolution due to changing customer needs, market developments, or technology trends. Reactive evolution means that changes to the product line are driven by the requirements arising when deriving new products. In this process heterogeneous stakeholders need to negotiate about these emerging requirements. It is also crucial that stakeholders...
Selecting requirements for a release of software is a difficult undertaking as people have trouble comparing requirements of different types and have natural biases towards short-terms gains over longer-term sustainability. Portfolio theory is proposed as a solution to this problem, as it provides a method for balancing investment options to maximize the likelihood of a given return. This approach...
Successful software products frequently evolve into software product lines, whether intentionally or not. In such cases, product managers have to be involved in creating and specifying the commonality and variability of the evolving software product line in order to continuously assure a winning business case. In this paper we introduce feature unweaving, a novel approach that allows a product manager...
A case-based approach allows reuse without the usual and significant effort for making software explicitly reusable. We even support such reuse for only partially developed requirements, since it allows reuse already without the need to develop a “complete” specification first. The solution information (models and code) of (one of) the most similar problems can then be taken for reuse and adapted...
This paper presents an approach to the management and customization of variabilities in software processes. It supports the automatic handling of variations occurring in process specifications, and promotes the automatic derivation of specific customizations of these processes. In order to validate and demonstrate the approach benefits and feasibility, the paper presents an implementation that allows...
In this paper we present aspect composition using model transformation language - ATL. The aspects are represented as UML sequence diagrams. We propose and implement complete composition algorithm using three ATL transformation models - JoinPointsCount, Instantiate, and Compose. The JoinPointsCount transformation determines the number of join points in the primary (core system) model. The Instantiate...
Software connectors are external coordination devices which ensure the flow of data and enforce synchronization constraints within a component's network. The specification of software connectors through which context dependent behaviour is correctly propagated remains an open, non trivial issue in their semantics. This paper, building on previous work by the authors, revisits this problem and introduces...
Problem Frames (PF) approach is prospective for describing and analyzing software problems. Problem decomposition is fundamental for managing problem size and complexity in RE and `projection' has been argued to be an effective technique for analyzing and decomposing complex problems in PF. However, problem analysis in PF approach is still an empirical, tedious, and subjective process, and it heavily...
iGATE, the first integrated Technology & Operations (iTOPS) organization in India had a steady climb in the customer's value chain in terms of penetrating deeper (instead of wider) into customer portfolio. More and more customers were proposing `partnership' model. One of the focus areas in partnership was `requirements engineering' as the challenges faced in this area were affecting both iGATE...
The paper describes the quotations gathered during interviews and focus groups during a consulting engagement to help the client improve its requirements engineering (RE) process. The paper describes also a model of the software lifecycle derived from a Michael Jackson quotation, a model that explains about 95% of the quotations that we gathered. In particular, it explains why basic requirements determination...
System safety is the property of the system that characterizes its ability to prevent from hazards, which may lead to accidents or losses. Traditionally, system developers are not familiar with system safety analysis processes which are performed by safety engineers. One reason for this is the gap that exists between the traditional development processes, methodologies, notations and tools and the...
This paper describes the application of a UML profile in the requirements modeling of a multi-agent system project. The profile at issue was designed with the purpose of modeling reactive and cognitive agents, as well as actions, perceptions, goals and plans for those agents in a collecting and analysing requirements level. In this paper we will describe the developed profile as well as its application...
The quality of a software requirements specification (SRS) is critical to project success, especially in global software development (GSD). Devising a high quality SRS however is difficult. Moreover, companies have compiled their own specification method, and find it impossible to rewrite rolled-out methods so profoundly that they address GSD specific challenges. We describe how Capgemini sd&m...
Determining the quality of a software product basically deals with checking the fulfillment of functional and quality requirements. Therefore, specifying useful and testable quality requirements is a central challenge. Many existing approaches focus on eliciting quality requirements, but often neglect the specification of respective test criteria. We present a bipartite approach that focuses on collecting...
Modern automation systems shall be able to conjugate increasing complexity of controlled processes with agile production reconfiguration requirements. In such a context, structured design approaches based on formal reference models as well as integrated verification and validation process, have to be adopted. To such an aim, present paper proposes an approach based on Model-Checking methods and tools...
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.