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.
It is widely known that, for most computer applications, their users and contexts of usage are quite heterogeneous and change in time. A variability analysis approach was developed to bridge the gap between requirements engineering and human-computer interaction can help identify these variations and design flexible, adaptable and adaptive solutions that accommodate them at interaction time, i.e.,...
Over the last decade, many aspect-oriented (AO) programming and modeling languages have been developed. Pointcut expressions are a key concept of each of these languages as they define the patterns that must be matched for aspects to be applied to the base. To date, most pointcut expressions are constrained to one particular notation - the one for which they were designed - even though a goal of aspect-oriented...
For embedded systems quality requirements are equally if not even more important than functional requirements. The foundation for the fulfillment of these quality requirements has to be set in the architecture design phase. However, finding a suitable architecture design is a difficult task for software and system architects. Some of the reasons for this are an ever-increasing complexity of today's...
This paper presents our PABRE method for facilitating requirements elicitation on the basis of requirement patterns with the goal of saving time and reducing errors during this activity. The process presented applies for elicitation in off-the-shelf selection projects driven by call for tenders processes and uses a requirement patterns catalogue. The process selects patterns from the catalogue that...
Design decisions and constraints of a software system can be specified precisely using a formal notation such as the Object Constraint Language (OCL). However, they are not executable, and assuring the conformance of an implementation to its design is hard. The inability of expressing design constraints in an implementation and checking them at runtime invites, among others, the problem of design...
Traditional requirements engineering for single systems, while remaining a large challenge for engineers, has been extensively researched and many techniques have been proposed and used with varying degree of success. However, many modern systems of systems are being developed to support interaction across multiple controlling authorities and existing techniques are proving to be inadequate for meeting...
This paper deals with good software design principle. On what do you base your design decisions-established conventions, past experience, or principles? The author discusses about three principles that seemed to underlie many of those experts decisions: 1) distribute behavior among objects (rather than concentrate it into a single controlling object). 2) preserve design flexibility by hiding implementation...
Understanding the relationships between requirements is important in order to understand the requirements themselves. Existing requirements management tools mainly use lists, tables, trees, and matrices to visualize requirements and their interrelations. However, all these visualization forms have a limited capability to show multiple relationships of different types. In this paper, we propose to...
It is almost a truism that system stakeholders do not fully understand and communicate what they want, often until a system is produced and they see it isn't right. Such an outcome is wasteful, expensive, and unsatisfactory. Working with requirements in comic book style provides affordances, absent or weaker in other requirements forms, that may as- sist stakeholders in surfacing and expressing desires...
While the traditional focus of requirements engineering was mainly on the systematic, reliable and adequate translation of the customers intentions into requirements documentation, it became recently increasingly accepted that requirements engineering, especially for innovative and novel products, is probably more adequately described as a process of joint discovery of requirements that can be supported...
Requirements engineering (RE) is traditionally taught in academia using an RE process which starts from a well-defined problem. Our approach focuses on the early stages of requirements discovery where students have to learn both about the application domain and about what stakeholders feel is the problem. The approach comprises all the basic elements of requirements, and ways to discover them using...
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.