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.
Traceability underlies many important software and systems engineering activities, such as change impact analysis and regression testing. Despite important research advances, as in the automated creation and maintenance of trace links, traceability implementation and use is still not pervasive in industry. A community of traceability researchers and practitioners has been collaborating to understand...
recognized as an important paradigm for software engineering. Several organizations are in the process of adopting and evolving SOA deployments. In this paper we present IntelliTrace, an intelligent traceability framework to support impact analysis across different modeling layers of a SOA based system. The framework uses traceability links among different SOA artifacts to analyze the impact that...
This paper presents a visual modeling notation for use in planning globally distributed requirements engineering projects. An underlying meta-model defines the elements of the modeling language, including site locations, stakeholder roles, communication flows, critical documents, and supporting tools and repositories. The modeling notation is motivated through the findings of eight in-depth interviews...
Requirements elicitation has long been recognized as a crucial activity in any software development project. Unfortunately, the traditional elicitation practices do not scale well when applied to larger projects, where knowledge is distributed across numerous geographically dispersed stakeholders. As a result, new distributed requirements elicitation tools have started to surface, such as online forums...
This panel builds upon a growing wave of reality television shows and proposes to go in search of requirements engineering's very own next top model. Through a series of tasks, some pre-prepared and some assigned on the fly, a number of small teams will compete for this prestigious title. Teams will be challenged to illustrate the power and flexibility of their favorite approach for requirements modeling,...
Many organizations invest considerable cost and effort in building traceability matrices in order to comply with regulatory requirements or process improvement initiatives. Unfortunately, these matrices are frequently left un-used and project stakeholders continue to perform critical software engineering activities such as change impact analysis or requirements satisfaction assessment without benefit...
This panel presents and discusses effective techniques for teaching requirements engineering principles and practices, in ways which actively engage students in the learning process.
Requirements related problems, especially those originating from inadequacies in the human-intensive task of eliciting stakeholderspsila needs and desires, have contributed to many failed and challenged software projects. This is especially true for large and complex projects in which requirements knowledge is distributed across thousands of stakeholders. This short paper introduces a new process...
As software projects increase in size and complexity, and involve stakeholders across geographic and organizational boundaries, it becomes increasingly important to develop new approaches and tools for supporting distributed, collaborative and scalable requirements elicitation processes. Such processes and related tools must support relatively open and inclusive collaborations, while simultaneously...
Successful software development involves the elicitation, implementation, and management of critical systemic requirements related to qualities such as security, usability, and performance. Unfortunately, even when such qualities are carefully incorporated into the initial design and implemented code, there are no guarantees that they will be consistently maintained throughout the lifetime of the...
Budgetary restrictions and time-to-market deadlines often require stakeholders to prioritize requirements and decide which ones to include in a given product release. Lack of an effective prioritization and triage process can lead to problems such as missed deadlines, disorganized development efforts, and late discovery of architecturally significant requirements. Existing prioritization techniques...
This panel will discuss the role of quality requirements in bringing products successfully to market. Techniques for eliciting, modeling, balancing, specifying, and measuring quality requirements will be explored.
Automated traceability facilitates the dynamic generation of candidate links between requirements and other software artifacts. It provides an alternative option to the arduous and error-prone process of manually creating and maintaining a trace matrix. However the result set contains both true and false links which must therefore be evaluated by an analyst. Current approaches display the candidate...
This paper describes an approach for automating the detection of early aspects. Based on hierarchical clustering and an underlying probabilistic algorithm, the technique generates initial requirements clusters representing relatively homogenous feature sets, use cases and potential cross-cutting concerns. A second clustering phase is then applied in which dominant terms are identified and removed...
Automated traceability applies information-retrieval techniques to generate candidate links, sharply reducing the effort of manual approaches to build and maintain a requirements trace matrix as well as providing after-the-fact traceability in legacy documents.The authors describe nine best practices for implementing effective automated traceability.
Goal oriented methods help software engineers to model high-level systemic goals, propose and evaluate architectural solutions, and detect and resolve conflicts that occur. This paper describes a new technique, known as softgoal traceability patterns, for enabling reusable class mechanisms such as design patterns to be applied within a goal-oriented framework. Softgoal traceability patterns increase...
This paper introduces an information retrieval based approach for automating the detection and classification of non-functional requirements (NFRs). Early detection of NFRs is useful because it enables system level constraints to be considered and incorporated into early architectural designs as opposed to being refactored in at a later time. Candidate NFRs can be detected in both structured and unstructured...
Even though traceability is legally required in most safety critical software applications and is a recognized component of many software process improvement initiatives, organizations continue to struggle to implement it in a cost-effective manner. This paper addresses the problems and challenges of requirements traceability and asks questions such as "How much traceability is enough?"...
Dynamic trace retrieval provides an alternate option to traditional traceability methods such as matrices, hyperlinks, and manual link construction. Instead of relying upon manually constructed and maintained traces, links are generated dynamically on an 'as-needed' basis using information retrieval techniques. Prior work in this area has indicated that in order to retrieve between 90% to 95% of the...
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.