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.
The number of papers and articles on goals would suggest that goal-oriented requirements engineering is a well understood and mature area within the requirements engineering discipline. In particular, there is a wealth of published material on formal goal modelling approaches. However, the uptake of the goal approaches advocated by academics and researchers within real world settings appears to be...
Context: Designing new architectures is a challenging task. A common and also effective approach for this task is to apply architectural design experience. Problem: If, however, architectural design experience is not available, two major problems arise: (i) how can we identify architecturally significant requirements (ASRs) and (ii) how can we identify architectural design decisions (ADDs) which address...
Non-functional requirements (NFRs) are commonly distinguished from functional requirements by differentiating how the system shall do something in contrast to what the system shall do. This distinction is not only prevalent in research, but also influences how requirements are handled in practice. NFRs are usually documented separately from functional requirements, without quantitative measures, and...
Performance requirements play an important role in software development. They describe system behavior that directly impacts the user experience. Specifying performance requirements in a way that all necessary content is contained, i.e., the completeness of the individual requirements, is challenging, yet project critical. Furthermore, it is still an open question, what content is necessary to make...
Requirements are usually categorized in functional requirements (FRs) and quality requirements (QR). FRs describe "things the product must do" while QRs describe "qualities the product must have". Besides the definition, classification, and representation problems identified by Glinz, there are two further problems with current definitions of quality requirements: (i) the definitions...
[Background] Requirements Engineering is crucial for project success, and to this end, many measures for quality assurance of the software requirements specification (SRS) have been proposed. [Goal] However, we still need an empirical understanding on the extent to which SRS are created and used in practice, as well as the degree to which the quality of an SRS matters to subsequent development activities...
Context: Seamless model-based development provides integrated chains of models, covering all software engineering phases. Non-functional requirements (NFRs), like reusability, further play a vital role in software and systems engineering, but are often neglected in research and practice. It is still unclear how to integrate NFRs in a seamless model-based development. Goal: Our long-term goal is to...
Artefact-based requirements engineering (RE) describes the idea of establishing a company-wide RE reference model by putting the focus on the RE artefacts and their dependencies rather than dictating a strict process with interconnected methods. Previously conducted case studies already strengthen our confidence in certain advantages and shortcomings of the paradigm. Still, our case studies by now...
Artefact-based requirements engineering (RE) describes the idea of establishing a company-wide reference model by putting the focus on the RE artefacts and their dependencies rather than dictating a strict process with interconnected methods. Although we could make first empirical studies on the benefits and shortcomings of artefact-based RE, however, we still have little evidence for our first results...
Systems whose functionality and services span over multiple, interconnected application domains have become known as cyber-physical system (CPS) and currently receive much attention in research and practice. So far, CPS still come with a variety of development-process-related and technical challenges. These challenges include the interaction between the different domain-specific systems and possible...
The development of highly distributed Systems of Systems (SoS) poses a big challenge on the whole development process of such systems. Especially in Requirements Engineering, one has to cope with the resulting variety of stakeholders and their multitude of different and possibly contradictory goals. This is challenging for requirements elicitation, documentation, and management, especially with regard...
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.