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 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...
This paper presents two system engineering Master lectures related to requirement engineering dealing with a physical product. It first introduces the framework of these lectures then gives some details about the two lectures: (1) during the first one, "exp.ert" students study tools and methodologies to manage requirements, (2) during the second one, "novice" students use requirement...
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...
Text-based approaches to the analysis of software evolution are attractive because of the fine-grained, token-level comparisons they can generate. The use of such approaches has, however, been constrained by the lack of an efficient implementation. In this paper we demonstrate the ability of Ferret, which uses n-grams of 3 tokens, to characterise the evolution of software code. Ferretpsilas implementation...
In early phases of the software cycle, requirements prioritization necessarily relies on the specified requirements and on predictions of benefit and cost of individual requirements. This paper presents results of a systematic review of literature, which investigates how existing methods approach the problem of requirements prioritization based on benefit and cost. From this review, it derives a set...
For several decades there has been a debate in the computing sciences about the relative roles of design and empirical research, and about the contribution of design and research methodology to the relevance of research results. In this minitutorial we review this debate and compare it with evidence about the relation between design and research in the history of science and technology. Our review...
End-user development has received a lot of attention in the research community. Despite the importance of requirements engineering in the software development life-cycle, comparatively little exists in the way of prescriptive advice or case studies on both requirements engineering and end-user development. This paper argues that end-user developers can obtain practical benefit by adopting professional...
Testing heterogeneous software systems raises new research challenges. Requirement-based testing is a promising approach for testing such systems. Research in motion (RIM), whose main product is indeed heterogeneous, has initiated an academia-industry collaborative project to investigate the automation of their requirement-based testing process. In this paper, we first identify research challenges...
In this paper, early aspects deal with crosscutting concerns in requirements analysis, domain analysis and architecture design. Work on early aspects focuses on systematically identifying, modularizing, and analyzing such crosscutting concerns and their impact at the early phases of the software development life cycle.
Developers typically rely on the information submitted by end-users to resolve bugs. We conducted a survey on information needs and commonly faced problems with bug reporting among several hundred developers and users of the APACHE, ECLIPSE and MOZILLA projects. In this paper, we present the results of a card sort on the 175 comments sent back to us by the responders of the survey. The card sort revealed...
Failures in properly identifying requirements are perhaps the major cause of the software industry's poor record of delivering working software systems on-time and to budget. Requirements engineering is the branch of software engineering concerned with identifying the real-world goals for, functions of, and constraints on software systems. This talk reflects on some current issues in requirements...
We propose an on-demand clustering framework for analyzing the functional requirements in a product line. Our approach is novel in that the objects to be clustered capture the domain's action themes at a primitive level, and the essential attributes are uncovered via semantic analysis. We provide automatic support to complement domain analysis by quickly identifying important entities and functionalities...
The objective of a systematic review is to obtain empirical evidence about the topic under review and to allow moving forward the body of knowledge of a discipline. Therefore, systematic reviewing is a tool we can apply in Software Engineering to develop well founded guidelines with the final goal of improving the quality of the software systems. However, we still do not have as much experience in...
Still, requirements and software design are often confused with one another. We provide a new (partial) explanation for this phenomenon, based on the insight that representations of concepts related to requirements and software design, respectively, may sometimes look very similar. This does not mean, however, that the requirements and design concepts are the same. So, we should distinguish requirements...
It is described that has been a noticeable increase in the use of agent oriented methodologies. Related to the process of requirements analysis and acquisition, various works have been published in recent years related to some methodologies. Despite this, there are not many proposals which seek to apply these results through its implementation with multiagent systems. This is the main aim of this...
Software development agile methodologies aim at promoting fast communication and incremental software delivery. The success of these methodologies in permanently evolving systems depends on how software engineers identify and structure changing requirements. Current agile methodologies fail to explicitly deal with the crosscutting nature of requirements, compromising the speed and capacity of systems...
One promising solution for meeting the demands of constantly-evolving real-time embedded (RTE) software is the model-driven development (MDD) paradigm, based on the principle of separating the description of an application from its platform-specific implementation. Existing model-driven approaches strive to achieve this separation through dedicated model transformations which actually embed a given...
The radar controller is a crucial, often over-looked, component of a radar system; allowing the transmitter to operate within a safe range and providing the flexibility to generate a variety of complex pulse schemes. Additionally, the radar controller provides precision timing to gate the radar systempsilas receiver(s) at regions of interest. Specifications for the design were chosen to match or exceed...
Secure systems are achieved by implementing appropriate controls and policies specified based on appropriate selection of minimum security requirements. Maintaining security for these systems is a major challenge. Systems may encounter threats that may arise due to exploitation of vulnerabilities or due to programming flaws. In this work we address security requirements engineering approaches and...
Dynamism in business has led to leaner organizations and multi-tasking role expectations. Software project planning and analysis durations are shorter. Developers are expected to play a larger role in planning, analyzing, elaborating and defining requirements. Developerspsila current methodologies and tools provide weak support in this role. They are especially inadequate for relating to, and for...
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.