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 heavily relies on oral and informal communication like meetings, phone calls, and e-mails. Some requirements are traditionally communicated outside formal documents in many companies. Considering document-based communication only is, therefore, not sufficient. Communication beyond documents should be taken into account when a company wants to improve its requirements engineering...
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...
This paper defines a framework of three dimensions which influence usability of trace visualizations: tasks, user roles, and information access. Based on this framework, we survey existing visualizations and conclude that future visualizations should focus more on users and tasks.
This paper presents a method for visualizing the scoping process in platform-based development of embedded systems. The proposed visualization shows the decision process of including or excluding features that are candidates for the next release. The presented visualization charts are evaluated in a large-size embedded system platform project. The evaluation indicates that the visualization of feature...
The goal of many software projects is the support of business processes. A typical business process spans multiple Use Cases. This poses the difficulty of making the set of encompassing Use Cases consistent with each other and functionality-wise complete with regards to the overall business process. Manual arrangements and reviews of Use Cases are burdensome and time-intensive. Therefore, an automatic...
Little effort has been put into understanding how trust can be modelled and reasoned when developing information systems. Equally little effort has been put into developing visual languages to support trust modelling. Our motivation comes from this situation and we aim to develop a visualization language for trust related requirements elicitation. In this paper we highlight the lack of substantial...
Developers must seriously address non-functional requirements (Quality of Service) in the production of software families that include variants for different customers. Most prior research in this area deals with design and implementation aspects such as mechanisms that help implement the variability in software architecture. Few researchers have addressed how to represent variability in non-functional...
Requirements Engineering (RE) of a program is closely related to that of the projects within the program. The relationships dictate timelines of the program and related projects. Further, the relationships determine the effect of Change on the program, and the intensity of risk management required to reduce program failures. Inherent complexity of RE phase forces the relationships intricate thus making...
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.