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.
Runtime monitoring and assessment of software products, features, and requirements allow product managers and requirement engineers to verify the implemented features or requirements, and validate the user acceptance. Gaining insight into software quality and impact of the quality on user facilitates interpretation of quality against users' acceptance and vice versa. The insight also expedites root...
Industry and society as a whole are facing radical changes due to fast growing digital technologies and their penetration of practically all areas. Products and services will increasingly augment and integrate the real world with the digital world. This digital transformation has reached all business areas. The role of Requirements Engineering is therefore changing in becoming even more ubiquitous:...
Social engineering is the acquisition of informationabout computer systems by methods that deeply include non-technical means. While technical security of most critical systemsis high, the systems remain vulnerable to attacks from socialengineers. Social engineering is a technique that: (i) does notrequire any (advanced) technical tools, (ii) can be used by anyone,(iii) is cheap. Traditional security...
Urban computing is a process of acquisition, integration, and analysis of big and heterogeneous data generated by a diversity of sources in cities to tackle urban challenges, e.g. air pollution, energy consumption and traffic congestion. Urban computing connects unobtrusive and ubiquitous sensing technologies, advanced data management and analytics models, and novel visualization methods, to create...
Eliciting requirements in their real-world contexts and creating and transforming visual models which can help lead to early designs of software is a challenging and time-consuming step in software engineering processes. In order to support the creation of these models and generate artifacts useful for software designs, we have developed the Problem-to-Design tool (PROD) based on Jackson's Problem...
We report the strategies and outcomes of requirements analysis in the SAMS project, which aims to detect early signs of dementia from records of user behaviour derived from monitoring home computer activity. Initial requirements elicitation specified a complex monitoring system in the genre of awareness requirements. As the complexity of the requirements for interpreting user activity became apparent,...
Modelling and reasoning with prioritization of non-functional requirements (NFRs) is a research field that needs more attention. We demonstrate RE-PREF, an approach that supports the modelling of NFRs and their preferences, and discovery of possible scenarios where badly chosen preferences can either make the runtime system miss or suggest unnecessary adaptations that may degrade the behavior of a...
This paper introduces the idea of building a body of knowledge (BoK) to gather the better practices in software requirements traceability that could bring major benefits for analyzing, managing, and implementing software changes impact. The implementation of traceability in the organizations is still a challenge even many studies have been conducted on the subject. The aim of this work is to evaluate...
Graphical Requirements Modeling (GRM) consists of representing requirements in diagrams: requirements (and other relevant information) are represented as nodes, and relationships between them as edges. Relationships can show, for example, that one requirement refines another, that some are in conflict with others, that they are more or less desirable, and so on. Various software tools have been proposed...
In a previous case study and paper, data was presented indicating that requirements training alone was not sufficient to achieve a high-quality requirements set. Mentoring of requirements authors by a requirements Subject Matter Expert (SME) was necessary. The requirements SME provided constructive and detailed feedback on defects in the requirements and then assisted the author with rewrites to remove...
We live in the days of social software where socialinteractions, from simple notifications to complex business processes, are supported by software platforms such as Facebook andTwitter. But for any social software to be successful, it must beused by a sizeable portion of its intended user community. Usagerequirements are usually referred to as Acceptance Requirementsand they have been studied in...
Researchers in software engineering have been striving to produce new methods to improve the quality of development methodologies to consequently produce quality products. Proposition of iterative and evolutionary approaches was triggered by the realization that requirements engineering is not confined to the initial phases of software development only. With this shift of perspective, requirements...
The Systems Modeling Language (SysML) is a popular and standardized UML profile for systems engineering applications. In addition to seven conventional UML diagram types, SysML supports requirement diagrams and tables that can be used to capture requirements, their attributes, and their relationships. However, several important concepts such as goals and contributions are not predefined in SysML,...
When organizations enter domains that are entirely new to them, they need to invest significant time and effort to acquire domain knowledge. This typically involves searching through a broad set of domain documents, retrieving relevant ones, and analyzing the textual content in order to discover and specify pertinent requirements. Depending on the nature of the domain and the availability of documentation,...
Communication about requirements is often handled in issue tracking systems, especially in a distributed setting. As issue tracking systems also contain bug reports or programming tasks, the software feature requests of the users are often difficult to identify. This paper investigates natural language processing and machine learning features to detect software feature requests in natural language...
The i* community has published guidelines, including model layout guidelines, for the construction of models. Our goal is to evaluate the effect of the layout guidelines on the i* novice stakeholders' ability to understand and review i* models. We performed a quasi-experiment where participants were given two understanding and two reviewing tasks. Both tasks involved a model with a bad layout and...
Compared to building a single requirements view, modeling stakeholder viewpoints and then merging them is shown to improve the understanding of the problem domain, but also very time consuming. How has the situation changed? This paper reports our replication of a case study, where we take theoretical replication's advantage to mitigate the original study design's threat and to embrace an important...
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.