Advertisement

A Process and Tool Support for Managing Activity and Resource Conflicts Based on Requirements Classification

  • Hwasil Yang
  • Minseong Kim
  • Sooyong Park
  • Vijayan Sugumaran
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3513)

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.

Keywords

Cellular Phone Software Product Line Feature Interaction Conflict Management Telephone Service 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Cameron, E.J., Velthuijsen, H.: Feature Interaction in Telecommunications systems. IEEE Communication Magazine 31(8), 46–51 (1993)CrossRefGoogle Scholar
  2. 2.
    M.: Requirements Interaction Detecting Using Semi- Formal Methods. In: Proceedings of the 10th IEEE International Conference and Workshop on the Engineering of Computer-Based System, ECBS 2003 (2003)Google Scholar
  3. 3.
    Kimbler, K., Bouma L.G.: Feature Interactions in Telecommunication and Software Systems V. IOS Press, Amsterdam (1998) Google Scholar
  4. 4.
    van Lamsweerde, A.: Managing Conflicts in Goal-Driven Requirements Engineering. IEEE Transactions on Software Engineering 23(11) (November 1998)Google Scholar
  5. 5.
    Kim, J., Kim, M., Yang, H., Park, S.: A Method and Tool Support for Variant Requirements Analysis: Goal and Scenario Based Approach. In: APSEC 2004, S. Korea, pp. 168–175 (2004)Google Scholar
  6. 6.
    Brooks, F.P.: No Silver Bullet: Essence and Accidents of Software Engineering. IEEE Computer 20(4), 10 (1987)MathSciNetGoogle Scholar
  7. 7.
    Zave, P.: Architectural Solutions to Feature Interaction problem in Telecommunication. In: Kimbler, V.K., Bouma, L.G. (eds.) Feature Interactions in Telecommunication and Software Systems, September 1998, pp. 10–22. IOS Press, Amsterdam (1998)Google Scholar
  8. 8.
    Peng, Y., Khendek, F., Grogono, P., Butler, G.: Feature Interactions Detection Technique Based On Feature Assumptions. In: Kimber, V.K., Bouma, L.G. (eds.) Feature Interaction in Telecommunication and Software system, September 1998, pp. 291–298. IOS Press, Amsterdam (1998)Google Scholar
  9. 9.
    Antón, A.I.: Goal-based requirements analysis. In: Proc. 2nd Int. Conf. Requirements Engineering (ICRE 1996), Colorado Springs, CO, April 1996, pp. 136–144 (1996)Google Scholar
  10. 10.
    Rolland, C., Souveyet, C., Ben Achour, C.: Guiding goal modeling using scenarios. IEEE Trans. Software Eng. 24, 1055–1071 (1998)CrossRefGoogle Scholar
  11. 11.
    Robinson, W.N.: Integrating Multiple Specifications Using Domain Goals. In: Proc. IWSSD-5-Fifth Int’T Workshop Software Specification and Design, pp. 219–225 (1989)Google Scholar
  12. 12.
    Kang, K.C., et al.: Feature-Oriented Product Line Engineering. IEEE Software 9(4), 58–65 (2002)CrossRefGoogle Scholar
  13. 13.
    Park, S., Kim, M., Sugumaran, V.: A Scenario, Goal and Feature Oriented Domain Analysis Approach for Developing Software Product Lines. Industrial Management & Data Systems 104(4), 296–308 (2004)CrossRefGoogle Scholar
  14. 14.
    Davis, A.M.: Predictions and farewells. IEEE Software 15(4), 6–9 (1998)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2005

Authors and Affiliations

  • Hwasil Yang
    • 1
  • Minseong Kim
    • 1
  • Sooyong Park
    • 1
  • Vijayan Sugumaran
    • 2
  1. 1.Department of Computer ScienceSogang UniversitySeoulRepublic of Korea
  2. 2.Department of Decision and Information SciencesOakland UniversityRochesterUSA

Personalised recommendations