A process and tool support for managing activity and resource conflicts based on requirements classification

Authors:
Hwasil Yang;Minseong Kim;Sooyong Park;Vijayan Sugumaran
Affiliations:
Department of Computer Science, Sogang University, Seoul, Republic of Korea;Department of Computer Science, Sogang University, Seoul, Republic of Korea;Department of Computer Science, Sogang University, Seoul, Republic of Korea;Department of Decision and Information Sciences, Oakland University, Rochester, MI
Venue:
NLDB'05 Proceedings of the 10th international conference on Natural Language Processing and Information Systems
Year:
2005

Citing 9
Cited 1

No Silver Bullet Essence and Accidents of Software Engineering

Computer
Integrating multiple specifications using domain goals

IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
Managing Conflicts in Goal-Driven Requirements Engineering

IEEE Transactions on Software Engineering
Guiding Goal Modeling Using Scenarios

IEEE Transactions on Software Engineering
Feature Interactions in Telecommunications and Software Systems V

Feature Interactions in Telecommunications and Software Systems V
Predictions and Farewells

IEEE Software
Feature-Oriented Project Line Engineering

IEEE Software
Goal-Based Requirements Analysis

ICRE '96 Proceedings of the 2nd International Conference on Requirements Engineering (ICRE '96)
A Method and Tool Support for Variant Requirements Analysis: Goal and Scenario Based Approach

APSEC '04 Proceedings of the 11th Asia-Pacific Software Engineering Conference

Function point extraction method from goal and scenario based requirements text

NLDB'06 Proceedings of the 11th international conference on Applications of Natural Language to Information Systems

Quantified Score

Hi-index	0.00

Visualization

Abstract

The more complicated and large-scaled software systems get, the more important software requirements become, and detecting conflicts between requirements is one of the essential matters that must be considered for successful software projects. Formal methods have been proposed to tackle this problem by adding formality and removing ambiguity. However, they are hard to understand by non-experts, which limit their application to restricted domains. In addition, there is no overall process that covers all the steps for managing conflicts. We propose a process for systematically identifying and managing requirements conflicts. This process is composed of four steps: requirements authoring, partition, conflicts detection and conflicts management. The detection and management of the conflicts are done based on the requirements partition in natural language and supported by a tool. To demonstrate its feasibility, the proposed process has been applied to a home integration system (HIS) and the results are analyzed.